Navigation

    Discussion Forum to share and further the development of home control and automation, independent of platforms.

    SmartHome Community
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Unsolved
    1. Home
    2. ronluna

    • HASS.OS Install

      V

      Hi,

      Am I correct in assuming that MSR cannot be installed on a pi running HASS.OS?

      Thanks.

      Multi-System Reactor

    • MSR Logic vs Reactor question

      R

      Hello,
      Trying to convert my Reactor scripts to MSR. Couldn't get the import to work so gave up on that. Anyway, curious on how to work with the following example.

      Have a motion sensor on my back porch. Very simple logic:
      7fbcd69e-9f85-4b7f-8138-1267d4e4ba1a-image.png The Reactor activities are as follows:
      34e715fd-c2f1-4b92-99ea-e2838fc5d3dc-image.png.

      In MSR, how do you tie activities to sub conditions like I have with the last action in activities.
      In this case I was to trigger BlueIris to trigger regardless of the time of day, but only want the light to come on at night. Do I need multiple Rule Sets?

      Thanks,
      Roger

      Multi-System Reactor

    • Unable to connect to HASS

      R

      Seeing this error in MSR logs:
      2021-07-29T02:01:27.663Z HassController:NOTICE HassController#hass attempting reconnection to ws://192.168.0.15:8123/api/websocket
      2021-07-29T02:01:27.664Z HassController:NOTICE HassController#hass connecting via WS to ws://192.168.0.15:8123/api/websocket
      2021-07-29T02:01:27.665Z HassController:WARN HassController#hass websocket error during open/negotation: Error: connect ECONNREFUSED 192.168.0.15:8123
      2021-07-29T02:01:27.666Z HassController:NOTICE HassController#hass websocket to ws://192.168.0.15:8123/api/websocket closed during open/negotiation
      2021-07-29T02:01:27.666Z HassController:WARN HassController#hass failed to connect/initialize communication: Error: connect ECONNREFUSED 192.168.0.15:8123

      On latest version of MSR. Also just installed HASS so it is latest as well.
      config.yaml in HASS looks like this:

      Configure a default setup of Home Assistant (frontend, api, etc)

      default_config:

      Text to speech

      tts:
      platform: google_translate

      http:
      server_host: 0.0.0.0

      websocket_api:

      sensor:
      platform: websocket_api

      group: !include groups.yaml
      automation: !include automations.yaml
      script: !include scripts.yaml
      scene: !include scenes.yaml

      Using new LTAT. Have tried several new ones.

      Any ideas on what is wrong?

      Multi-System Reactor

    • Release 1.0.0

      toggledbits

      Well, it's July 19th, and as previously advertised, Reactor (Multi-System, aka MSR) has been published at release 1.0.0.

      Docker images are on DockerHub, and download package for bare-metal installs is available at https://reactor.toggledbits.com/download/

      Those of you with access to the Mantis Bug Tracker for the project, please continue to use it, particularly if you stick with the "latest" docker image tag (which will continue to be updated periodically, as will the bare-metal tarball). Feel free to open issues there on behalf of other users who do not have accounts if it seems appropriate.

      Multi-System Reactor

    • openLuup: SmartSwitch plugin

      akbooer

      This plugin was updated by @vosmont to run under openLuup (and possibly UI7.)

      @DesT recently asked for a slight addition to its functionality, so I'm adding this thread to discuss the changes.

      Plugins

    • TTS in MSR?

      F

      Hi!

      In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
      But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
      Thanks!
      /Fanan

      Multi-System Reactor

    • HASS version not supported?

      Tom_D

      I am running MSR 1.0.0-21200-16a604f and am seeing the message:

      HomeAssistant on "hass" may be an unsupported version. The reported version (2021.7.3) has not been certified/tested with this version of Reactor and may cause errors. You must either modify your HomeAssistant install, or see if an update to Reactor has been made available.

      Multi-System Reactor

    • Renaming device name...

      DesT

      @akbooer

      What's the "logic" behind zway plugin about renaming ? Are you always renaming when starting openLuup ?

      Zway Bridge

    • Long-overdue roll-up of the last year's development!!!

      A

      "akbooer: Master Branch: 2021 Release 7.25
      Long-overdue roll-up of the last year's development updates!"

      ak - congratulations on some great improvements coming to fruition. I can only hope you aren't running out of ideas! It's not easy.

      I'd still like to see an "App Store" plugin download count but the invisible hands still need to be invoked by someone - whoever that may be!!

      openLuup

    • openLuup: Version Log

      akbooer

      A long while ago (May, 2015) I wrote my 2000-th post on another forum: openLuup - running unmodified plugins on any machine. Here’s the gist of it:

      ...I want to work in a more open and stable [Vera] environment...

      ...All would be solved if Luup was open source and could be run on the plethora of cheap and reliable hardware available today. But it’s not. But we could get something like that effect if we engineered a sufficient subset of Luup to run on such a platform. Could it be done? What would we need?

      1. UI
      2. scheduler
      3. web server
      4. Luup compatible API
      5. Device and Implementation xml file reader
      6. Zwave bridge to Vera
      7. runs most plugins without modification

      What we wouldn’t need is UPnP.

      What have we (nearly) got already?

      We have, courtesy of @amg0, the most excellent AltUI: Alternate UI to UI7, and that, I think, is probably the hardest one to do in the above list. Items 2 - 5, and 7, I’ve prototyped, in pure Lua, and posted elsewhere: DataYours on Raspberry Pi, running selected plugins unmodified, including: DataYours, EventWatcher, Netatmo, RBLuaTest, altUI. See screenshot attached.

      Is it worth the effort? Probably not. Will I pursue this quest? Yes.

      openLuup was the result.

      DE2056BF-E548-4611-972B-40276F00BFEB.jpeg

      openLuup

    • Fibaro TRV on ZWay/OpenLuup?

      I

      Having some trouble getting the Fibaro TRV device working with the ZWay bridge. The device works in the ZWay (Zwave.Me) Smart Home GUI, and creates a number of devices in OpenLuup, some of which appear to have the right variables in it. Changing the XML and JSON files makes no difference.

      I also tried creating a separate child device for Parameter 67 (using the gui for the ZWay bridge, see below), and setting the XML/JSON types for that device (like I've havd to do for a few other devices). This results in a device that correctly displays the TRV setpoint, but chaning the setpoint in the OpenLuup gui does not result in anything being transmitted to/by ZWay.

      20490 49-0 D_ComboDevice1.xml zNode #49-0
      49-0-113-8-12-A
      49-0-113-8-13-A
      49-0-113-8-14-A
      49-0-113-8-15-A
      49-0-113-9-3-A
      49-0-64
      49-0-67-1
      20491 49-1 D_ComboDevice1.xml zNode #49-1
      49-1-113-8-12-A
      49-1-113-8-13-A
      49-1-113-8-14-A
      49-1-113-8-15-A
      49-1-113-9-3-A
      49-1-64
      25031 49-1-67-1 D_Heater1.xml Radiator Bedroom
      20492 49-2 D_ComboDevice1.xml multi #49-2
      49-2-113-8-10-A
      49-2-113-8-11-A
      25030 49-2-49-1 D_TemperatureSensor1.xml Radiator Bedroom

      Zway Bridge

    • Ideas of project...

      DesT

      Curious to know if anyone play with Z-Uno to create some "z-wave sensors"

      Z-Uno

    • HomeWave Push notifications plugin (Update)

      I

      All,

      Due to changes in the push notification system by Apple, the plugin to send push notifications to HomeWave will have to be updated. Please use the link below. This plugin works on both Vera and OpenLuup platforms.

      Push messages will continue to work with the old and the new plugin. Once the server and the HomeWave app are updated, the old plugin will stop working

      http://www.intvelt.com/files/HomeWavePush.zip
      Vera/openLuup plugins

    • Support for Ezlo Atom controllers?

      cw-kid

      Hi

      I just tried to add a connection for my Ezlo Atom, its added the Atom system in to the MSR Entities, but it has a "false" state and hasn't found my devices that are paired to the Atom.

      ff7f286a-e987-4b2b-a56e-0b7a067aff6e-image.png

      Also note that on the Atom controller there is no settings for:

      offlineAnonymousAccess: true or false

      offlineInsecureAccess: true or false

      So this line in the reactor.yaml file won't work for Atom's.

      set_anonymous_access: true

      This was what I added to my reactor.yaml file.

      - id: ezlo-atom enabled: true implementation: EzloController name: Ezlo Atom config: source: "wss://192.168.0.101:17000" # change the IP address serial: "70060304" # put your hub's serial here username: "myusername" # put your username here between quotes password: "mypassword" # and password # set_anonymous_access: true

      Thanks

      Multi-System Reactor

    • Vera - Attempt to set primary to power_switch.state invalid

      cw-kid

      I am seeing errors like these in the log file:

      <VeraController:NOTICE> Controller VeraController#vera-edge is now online. 2021-07-22T15:41:29.586Z <default:ERR> [Entity:setPrimaryAttribute] Attempt to set primary to power_switch.state invalid, not in { "x_vera_device": { "device_number": 139, "device_type": "urn:schemas-upnp-org:device:RGBController:1", "parent_device": 0, "failed": false, "configured": --null--, "mapped_class": "rgbcontroller_plugin", "mapped_by": "*;device_type=urn:schemas-upnp-org:device:RGBController:1" }, "x_vera_svc_upnp_org_RGBController1": { }, "x_vera_svc_upnp_org_SwitchPower1": { }, "x_vera_svc_micasaverde_com_HaDevice1": { }, "x_vera_rgbcontroller_plugin": { "device_type": "FGRGBWM-441", "configured": true, "color": "#0000000000", "message": "" } } 2021-07-22T15:41:29.587Z <VeraController:ERR> VeraController#vera exception/error while updating VeraController#vera 2021-07-22T15:41:29.588Z <VeraController:CRIT> Error: Entity#vera>device_139:setPrimaryAttribute() can't set power_switch.state, not defined for entity Error: Entity#vera>device_139:setPrimaryAttribute() can't set power_switch.state, not defined for entity

      and

      <default:ERR> [Entity:setPrimaryAttribute] Attempt to set primary to power_switch.state invalid, not in { "x_vera_device": { "device_number": 75, "device_type": "urn:schemas-micasaverde-com:device:WindowCovering:1", "parent_device": 1, "failed": false, "configured": false, "mapped_class": "fibaro_cover_scenecontrol", "mapped_by": "*;device_type=urn:schemas-micasaverde-com:device:WindowCovering:1;pnp=/^(3222)$/" }, "x_vera_svc_upnp_org_SwitchPower1": { }, "x_vera_svc_upnp_org_Dimming1": { }, "x_vera_svc_upnp_org_WindowCovering1": { }, "x_vera_svc_micasaverde_com_Protection1": { }, "x_vera_svc_micasaverde_com_EnergyMetering1": { }, "x_vera_svc_micasaverde_com_HaDevice1": { }, "x_vera_svc_micasaverde_com_ZWaveDevice1": { }, "x_vera_svc_micasaverde_com_ZWaveNetwork1": { }, "x_vera_svc_micasaverde_com_GenericSensor1": { }, "x_vera_svc_micasaverde_com_Color1": { }, "x_vera_svc_micasaverde_com_SceneController1": { }, "cover": { "state": false }, "position": { "value": 0 }, "zwave_scene_controller": { "scene_activated": "0", "key_attribute": --null--, "scene_deactivated": --null--, "central_scene": --null-- }, "x_vera_scene_controller": { "last_scene_id": "26", "last_scene_time": "1626714753" } } 2021-07-22T15:41:28.925Z <VeraController:ERR> VeraController#vera exception/error while updating VeraController#vera 2021-07-22T15:41:28.926Z <VeraController:CRIT> Error: Entity#vera>device_75:setPrimaryAttribute() can't set power_switch.state, not defined for entity Error: Entity#vera>device_75:setPrimaryAttribute() can't set power_switch.state, not defined for entity

      What does it mean?

      One is an RGBW Plugin device the other is a real Z-Wave device, a Fibaro Roller Shutter 2.

      Thanks

      Multi-System Reactor

    • "Tunnel" to MSR from Openluup?

      PerH

      Not sure which category to use, but it's about external access..

      I'm using Dataplicity to connect from the web to openluup, and i'd like a similar connection for MSR. Thats not something i would use on a phone, but from a laptop situated elsewhere in the world (faulty logic always appears when i'm far away from home!)

      I could offcourse do the same procedure (described in the lower part of this ) for MSR, but if I colud put a link somewhere in Openluup that would take me there (like the openluup console link?) that would be easier?

      Don't know if it will work to connect to a different port?

      Any ideas?

      openLuup

    • Alt App Store - impact of GitHub changes

      akbooer

      It's worth noting this recent (?) GitHub change:

      GitHub - github/renaming: Guidance for changing the default branch name for GitHub repositories GitHub - github/renaming: Guidance for changing the default branch name for GitHub repositories

      Guidance for changing the default branch name for GitHub repositories - GitHub - github/renaming: Guidance for changing the default branch name for GitHub repositories

      This will have an impact on the AltAppStore which has previously assumed the default repository name of master. So when specifying releases, you should ensure that any new plugins explicitly reference the main branch if that's the one you're expecting to use.

      Vera/openLuup plugins

    • Ezlo device capabilities

      Elcid

      Having gotten the Ezlo controller to connect I see these device items
      x_ezlo_item.learn_ir_code=0
      x_ezlo_item.learn_rf_code=0
      x_ezlo_item.send_ir_code=""
      x_ezlo_item.send_rf_code=""

      But they are not listed in the capabilities. It would be nice if to send Ir and Rf codes direct from MSR.

      If possible couild you add this feature.

      Multi-System Reactor

    • Entities area is this expected?

      cw-kid

      In Entities area, I selected the Ezlo controller. However when using the Capabilities drop down list, I can also see capabilities from the Vera firmware hubs as well, is that expected behaviour?

      Thanks

      entities.png

      Multi-System Reactor
    For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used
    R
    • Profile
    • Following 1
    • Followers 0
    • Topics 5
    • Posts 42
    • Best 7
    • Groups 0

    ronluna

    @ronluna

    15
    Reputation
    14
    Profile views
    42
    Posts
    0
    Followers
    1
    Following
    Joined Last Online
    ronluna Unfollow Follow

    Best posts made by ronluna

    • Homebridge to Openluup

      Sharing what I believe is a great way to add support to devices that used to work but since existing plugin haven't been maintain by the original authors (or any other developer in the community) have stopped working as they've abandon or moved to other platform...

      Homebridge has a large and very active community and I think this type of plugin will a good way to benefit from it.

      It will bring any device that have been configured in homebridge into openluup.

      Currently it support, thermostat (Nest and others), Switches (Specially MyQ), Dimmers, Switches, Motion Sensors, Door Lock (Open/close) Support to other type of device can easily be added.

      Homebridge2Openluup
      Installation:

      • upload the files to /you_openluup_directory/files/
      • create a new device with D_Homebridge2openluup1.xml

      Screen Shot 2021-03-14 at 12.55.29 PM.png

      • Set your hombredige IP, username, password to the deivce's attributes

      Screen Shot 2021-03-14 at 12.57.00 PM.png

      • Capture the uuid of the device you would like to bring from Homebridge into openluup by looking at your openluup logs when starting

      Screen Shot 2021-03-14 at 1.00.53 PM.png

      • based on the device type, set DeviceList Variable

      Screen Shot 2021-03-14 at 1.02.51 PM.png

      T for thermostat
      D for dimmers
      S for switches
      G for garage doors
      L for Locks
      A for motion sensors

      and build a string device type are delimited by a ; (semicolong) and device's uui by a , (comma) like this:
      T:homebridge_thermostat1_uuid,homebridge_thermostat2_uuid;D:homebridge_dimmer1_uuid,homebridge_dimmer2_uuid etc

      This still in beta, would love to add async next and support to shades and other sensors.

      posted in Plugins
      R
      ronluna
    • RE: Generic support for vacuums

      @therealdb could use homebridge 2 openluup also...

      posted in Plugins
      R
      ronluna
    • Add Indicator commandClass to zNode metric

      I'm trying to monitor the indicator command class of a 5 button scene controller in Z-Way so openluup can properly create and track it.

      seems like Z-Way COMMAND_CLASS_INDICATOR (0x87 or 135) are not being monitored by the ZWave module as I couldn't find anything for this command class in (/z-way-server-path/automation/modules/ZWave/index.js)

      When a Get or Set Indicator command class request is sent to the controller. ZSniffer picks up the request and response just fine although this packets are not being monitored by the zwave module
      Example:

      ZWayIP:8083/ZWaveAPI/Run/SendData(NodeID,[ Command_Class, Instance, Value ])
ZWayIP:8083/ZWaveAPI/Run/SendData(2,[ 0x87, 0x01, 0x01 ]) (Hexa)
ZWayIP:8083/ZWaveAPI/Run/SendData(2,[ 135, 1, 1 ]) (Decimal)

      the answer looks like:

      [2020-04-24 19:59:36.261] [I] [zway] Waiting for job reply: Indicator Get
[2020-04-24 19:59:36.281] [D] [zway] RECEIVED: ( 01 0B 00 04 00 02 03 87 03 01 B6 00 C2 )
[2020-04-24 19:59:36.281] [D] [zway] SENT ACK

      I’d like to store the Indicator response “RECEIVED” correctly. I believe by modifying the index.js of the zwave module could do the trick and once the module start tracking the indicator command class values as a metric then openluup's z-way plugin would properly track any changes as well.

      I'm wondering if anyone around here could share any thoughts or comments that could make it easier...

      posted in Z-Wave.me
      R
      ronluna
    • RE: Apple Homepod mini

      @akbooer That's right... and just like that... apple is taking over then entire home automation industry.... too bad there is no Home app for Android. Well Front end and first layer voice control related...

      posted in General Discussion
      R
      ronluna
    • RE: Homebridge to Openluup

      thanks @akbooer . I'll be adding the installation instructions to the readme file... By the way, this plugin also works for ecobee thermostat, the native ecobee lua plugin by @rafale77 works ok when there is only one thermostat in the ecobee account but when more than one, ecobee server keeps deauthorizing the plugin...

      @rafale77 I also use homebridge the other way (openluup to homebridge) and is great.

      I'm currently using it for:

      • Nest thermostats with google accounts.
      • Ecobee accounts with multiple thermostats
      • AUX Mini split with built-in wifi modules

      Planning on adding control for AppleTV , Ring devices, Doorbird motion detection and many more...

      It will allow us to finally include many of the popular cloud based devices that own into the openluup environment...

      Something really cool about homebridge is that the manual and basic automation can be done from within homekit by the end-user, but deeper logic can be done from within openluup. Thinking about bringing node-red into the mix also... anyhow... I hope it can be useful for everyone here...

      posted in Plugins
      R
      ronluna
    • RE: Homebridge to Openluup

      @crille pushed new fix for celsius. the plugin is now available on the altappstore.

      posted in Plugins
      R
      ronluna
    • RE: Homebridge to Openluup

      @Crille I was using an older version. I have pushed a fixed to make device's name persistent after engine reload. please update the plugin and share the results when you get a chance.

      Thanks @akbooer for the pointing this out.

      posted in Plugins
      R
      ronluna

    Latest posts made by ronluna

    • RE: Apple Homepod mini

      @akbooer That's right... and just like that... apple is taking over then entire home automation industry.... too bad there is no Home app for Android. Well Front end and first layer voice control related...

      posted in General Discussion
      R
      ronluna
    • RE: Apple Homepod mini

      @akbooer get the latest copy directly from github at https://github.com/damianxd/homebridge-vera as npm is not current/synced with the github repo. In other words, install the plugin through the homebridge plugin section and then replace all the files located at "/usr/lib/node_modules/homebridge-vera/" with the latest on github.

      posted in General Discussion
      R
      ronluna
    • RE: BroadLink Mark II plugin

      @a-lurker the second broadlink device in the network is indeed Mini split A/C that uses AC Freedom app. Both device are well within the wifi range and working fine when using their native apps so I doubt the timeout message has something to do with the strength of the connection. What I've noticed in the past when I've seen a timeout like this is due to the socket expecting a special carrier return <CR> or something in that sort, simply not understanding what was sent back to it.

      I'm not familiar with the RM communication protocol... Although I'm all ears to see what else We could try to get this off the ground.

      2021-04-03 14:20:18.155   openLuup.scheduler:: [82] BroadLink-Mk2 device startup
2021-04-03 14:20:18.155   luup_log:82: BroadLink_Mk2 debug: Initialising plugin: BroadLink_Mk2
2021-04-03 14:20:18.155   luup_log:82: BroadLink_Mk2 debug: Using: Lua 5.1
2021-04-03 14:20:18.155   luup_log:82: BroadLink_Mk2 debug: 0.57a --> PluginVersion
2021-04-03 14:20:18.155   luup.variable_set:: 82.urn:a-lurker-com:serviceId:BroadLink_Mk2_1.PluginVersion was: 0.57 now: 0.57a #hooks:0
2021-04-03 14:20:18.156   luup_log:82: BroadLink_Mk2 debug: Using: dkjson
2021-04-03 14:20:18.157   luup_log:82: BroadLink_Mk2 debug: Broadcasting discovery message
2021-04-03 14:20:18.157   luup_log:82: BroadLink_Mk2 debug: 10.1.11.22
2021-04-03 14:20:19.157   luup_log:82: BroadLink_Mk2 debug: Number of BroadLink devices found is 1
2021-04-03 14:20:19.158   luup_log:82: BroadLink_Mk2 debug: Header to be sent follows (ex checksum):

5A A5 AA 55 5A A5 AA 55  00 00 00 00 00 00 00 00   Z..UZ..U........
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ................
00 00 00 00 9B 64 65 00  00 00 8D DE 18 B0 43 A0   .....de.......C.
00 00 00 00 FB C8 00 00   ........

2021-04-03 14:20:19.158   luup_log:82: BroadLink_Mk2 debug: Payload to be sent follows (unencrypted):

00 00 00 00 A7 C5 DF 0A  91 33 F1 88 C9 82 A5 6D   .........3.....m
C8 BC F9 DF 00 00 00 00  00 00 00 00 00 00 00 00   ................
00 00 00 00 00 00 00 00  00 00 00 00 00 01 00 00   ................
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ................
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ................

2021-04-03 14:20:19.177   luup_log:82: BroadLink_Mk2 debug: Sending:  Authorisation: txMsg length = 136
2021-04-03 14:20:20.177   luup_log:82: BroadLink_Mk2 debug: RX of Authorisation msg response from 10.1.11.20 failed: timeout
2021-04-03 14:20:20.177   luup_log:82: BroadLink_Mk2 debug: This device is probably offline - mac address: a0:43:b0:18:de:8d
2021-04-03 14:20:20.177   luup_log:82: BroadLink_Mk2 debug: k = rf433
2021-04-03 14:20:20.177   luup_log:82: BroadLink_Mk2 debug: k = rf433 has no associated code at this time
2021-04-03 14:20:20.177   luup_log:82: BroadLink_Mk2 debug: k = ir
2021-04-03 14:20:20.177   luup_log:82: BroadLink_Mk2 debug: a0:43:b0:18:de:8d_ir
2021-04-03 14:20:20.177   luup_log:82: BroadLink_Mk2 debug: a0:43:b0:18:de:8d
2021-04-03 14:20:20.177   luup_log:82: BroadLink_Mk2 debug: RM4 Pro - IR 1
2021-04-03 14:20:20.177   luup_log:82: BroadLink_Mk2 debug: urn:schemas-micasaverde-com:device:IrTransmitter:1
2021-04-03 14:20:20.177   luup_log:82: BroadLink_Mk2 debug: D_BroadLink_Mk2_IrRf_1.xml
2021-04-03 14:20:20.177   luup_log:82: BroadLink_Mk2 debug: type = function, value = function: 0x19a62d0
2021-04-03 14:20:20.177   luup_log:82: BroadLink_Mk2 debug: k = rf315
2021-04-03 14:20:20.177   luup_log:82: BroadLink_Mk2 debug: k = rf315 has no associated code at this time
2021-04-03 14:20:20.177   luup_log:82: BroadLink_Mk2 debug: {"a0:43:b0:18:de:8d":{"blInternalId":"00000001","blKey":"a7c5df0a9133f188c982a56dc8bcf9df","blDeviceType":25755,"blIp":"10.1.11.20","blDesc":"RM4 Pro"}} --> BroadLinkDevices
2021-04-03 14:20:20.177   luup.chdev.append:: [a0:43:b0:18:de:8d_ir] RM4 Pro - IR 1
2021-04-03 14:20:20.178   luup.chdev.sync:: [82] BroadLink-Mk2, syncing children
2021-04-03 14:20:20.178   luup.set_failure:: status = false
2021-04-03 14:20:20.178   luup.variable_set:: 82.urn:micasaverde-com:serviceId:HaDevice1.CommFailure was: false now: false #hooks:0
2021-04-03 14:20:20.178   luup.variable_set:: 82.urn:micasaverde-com:serviceId:HaDevice1.CommFailureTime was: 1617440329 now: 1617474020 #hooks:0
2021-04-03 14:20:20.178   openLuup.scheduler:: [82] BroadLink-Mk2 device startup completed: status=true, msg=All OK, name=BroadLink_Mk2
      posted in Plugins
      R
      ronluna
    • RE: BroadLink Mark II plugin

      I tested the latest changes to add support for the RM4 Pro and it created a "IR" Child although it did not list any of the devices that have been created inside the RM4 Pro itself (Probably because is an RF device and that child was not created?). Also the IP set in the plugin attributes is different than the IP This is what the logs are showing:

      2021-04-02 08:53:44.604   luup_log:82: BroadLink_Mk2 debug: The BroadLink device at IP address 10.1.11.126 and of type 0x4e2a is not known to this plugin

      I do have another Broadlink device in the network so I guess is trying to discover that one as well.

      2021-04-02 08:53:44.557   openLuup.scheduler:: [3] Alternate App Store device startup completed: status=true, msg=OK, name=AltAppStore
2021-04-02 08:53:44.557   openLuup.scheduler:: [82] BroadLink-Mk2 device startup
2021-04-02 08:53:44.557   luup_log:82: BroadLink_Mk2 debug: Initialising plugin: BroadLink_Mk2
2021-04-02 08:53:44.557   luup_log:82: BroadLink_Mk2 debug: Using: Lua 5.1
2021-04-02 08:53:44.557   luup_log:82: BroadLink_Mk2 debug: 0.57 --> PluginVersion
2021-04-02 08:53:44.558   luup_log:82: BroadLink_Mk2 debug: Using: dkjson
2021-04-02 08:53:44.559   luup_log:82: BroadLink_Mk2 debug: Broadcasting discovery message
2021-04-02 08:53:44.559   luup_log:82: BroadLink_Mk2 debug: 10.1.11.22
2021-04-02 08:53:44.603   luup_log:82: BroadLink_Mk2 debug: 10.1.11.126
2021-04-02 08:53:44.604   luup_log:82: BroadLink_Mk2 debug: Rx'ed a discovery response: rxMsg length = 128

5A A5 AA 55 5A A5 AA 55  00 00 00 00 00 00 00 00   Z..UZ..U........
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ................
E5 D6 00 00 2A 4E 07 00  00 00 DD 8A EB A7 DF 24   ....*N.........$
00 00 00 00 2A 4E 0A 01  0B 7E DD 8A EB A7 DF 24   ....*N...~.....$
E5 A5 A5 E5 85 8B E6 96  AF E7 A9 BA E8 B0 83 00   ................
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ................
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ................
00 00 00 00 00 00 00 00  00 00 00 00 00 00 02 01   ................

2021-04-02 08:53:44.604   luup_log:82: BroadLink_Mk2 debug: Looks like the Cloud bit is set - that's not good
2021-04-02 08:53:44.604   luup_log:82: BroadLink_Mk2 debug: Friendly name: e5a5a5e5858be696afe7a9bae8b083
2021-04-02 08:53:44.604   luup_log:82: BroadLink_Mk2 debug: The BroadLink device at IP address 10.1.11.126 and of type 0x4e2a is not known to this plugin
2021-04-02 08:53:45.604   luup_log:82: BroadLink_Mk2 debug: Number of BroadLink devices found is 1
2021-04-02 08:53:45.604   luup_log:82: BroadLink_Mk2 debug: Header to be sent follows (ex checksum):

5A A5 AA 55 5A A5 AA 55  00 00 00 00 00 00 00 00   Z..UZ..U........
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ................
00 00 00 00 9B 64 65 00  00 00 8D DE 18 B0 43 A0   .....de.......C.
00 00 00 00 FB C8 00 00   ........

2021-04-02 08:53:45.605   luup_log:82: BroadLink_Mk2 debug: Payload to be sent follows (unencrypted):

00 00 00 00 A7 C5 DF 0A  91 33 F1 88 C9 82 A5 6D   .........3.....m
C8 BC F9 DF 00 00 00 00  00 00 00 00 00 00 00 00   ................
00 00 00 00 00 00 00 00  00 00 00 00 00 01 00 00   ................
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ................
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ................

2021-04-02 08:53:45.618   luup_log:82: BroadLink_Mk2 debug: Sending:  Authorisation: txMsg length = 136
2021-04-02 08:53:45.632   luup_log:82: BroadLink_Mk2 debug: Broadlink device: 649b replied with: 03e9
2021-04-02 08:53:45.632   luup_log:82: BroadLink_Mk2 debug: Error: errorMsg = fff9
2021-04-02 08:53:45.632   luup_log:82: BroadLink_Mk2 debug: This device is probably offline - mac address: a0:43:b0:18:de:8d
2021-04-02 08:53:45.632   luup_log:82: BroadLink_Mk2 debug: k = ir
2021-04-02 08:53:45.632   luup_log:82: BroadLink_Mk2 debug: a0:43:b0:18:de:8d_ir
2021-04-02 08:53:45.632   luup_log:82: BroadLink_Mk2 debug: a0:43:b0:18:de:8d
2021-04-02 08:53:45.632   luup_log:82: BroadLink_Mk2 debug: RM4 Pro - IR 1
2021-04-02 08:53:45.632   luup_log:82: BroadLink_Mk2 debug: urn:schemas-micasaverde-com:device:IrTransmitter:1
2021-04-02 08:53:45.632   luup_log:82: BroadLink_Mk2 debug: D_BroadLink_Mk2_IrRf_1.xml
2021-04-02 08:53:45.633   luup_log:82: BroadLink_Mk2 debug: type = function, value = function: 0x1a03140
2021-04-02 08:53:45.633   luup_log:82: BroadLink_Mk2 debug: {"a0:43:b0:18:de:8d":{"blInternalId":"00000001","blKey":"a7c5df0a9133f188c982a56dc8bcf9df","blDeviceType":25755,"blIp":"10.1.11.20","blDesc":"RM4 Pro"}} --> BroadLinkDevices
2021-04-02 08:53:45.633   luup.chdev.append:: [a0:43:b0:18:de:8d_ir] RM4 Pro - IR 1
2021-04-02 08:53:45.633   luup.chdev.sync:: [82] BroadLink-Mk2, syncing children
2021-04-02 08:53:45.633   luup.set_failure:: status = false
2021-04-02 08:53:45.633   luup.variable_set:: 82.urn:micasaverde-com:serviceId:HaDevice1.CommFailure was: false now: false #hooks:0
2021-04-02 08:53:45.633   luup.variable_set:: 82.urn:micasaverde-com:serviceId:HaDevice1.CommFailureTime was: 1617316371 now: 1617368025 #hooks:0
2021-04-02 08:53:45.633   openLuup.scheduler:: [82] BroadLink-Mk2 device startup completed: status=true, msg=All OK, name=BroadLink_Mk2

      Any ideas how to get the RF portion working?

      posted in Plugins
      R
      ronluna
    • RE: Generic support for vacuums

      @therealdb could use homebridge 2 openluup also...

      posted in Plugins
      R
      ronluna
    • RE: Homebridge to Openluup

      @Crille I was using an older version. I have pushed a fixed to make device's name persistent after engine reload. please update the plugin and share the results when you get a chance.

      Thanks @akbooer for the pointing this out.

      posted in Plugins
      R
      ronluna
    • RE: Homebridge to Openluup

      @akbooer apparently on @Crille environment renaming plugin's children are not persistent after the engine reloads. although I can't replicate it on my end.

      posted in Plugins
      R
      ronluna
    • RE: Homebridge to Openluup

      @crille currently the plugin relies on an initial manual configuration and the current mechanism creates the children in a very dumb way. It is possible to build a more sophisticated interface although the plugin still in a "proof of concept state".

      Yes, the devices are named DeviceType_UUID by default when they are created for the first time but after that I can rename them any way I want and the names remain persistent after engine reloads.

      My understanding is that once a device is renamed on your setup it will get renamed back to the default deviceType_uuid after the engine reloads right? and that's what I can't replicate on my end.

      posted in Plugins
      R
      ronluna
    • RE: Homebridge to Openluup

      @crille said in Homebridge to Openluup:

      luup.chdev.append

      I'm really puzzled by this... Your logs looks just fine... The devices should not get renamed back when luup.chdev.append runs . if the devices where getting re-created the engine should be getting reloaded right away... What openluup version are you running?

      Wondering if @akbooer sees something weird in how the plugin is syncing the devices after the append runs that could be causing it... at line 601 of L_Homebridge2openllup1.lua as it is something I'm not experiencing on my end... and I'm not sure where else to look...😧

      posted in Plugins
      R
      ronluna
    • RE: Homebridge to Openluup

      @crille I've been renaming renaming devices on my end without experiencing what you are describing. Are both Mitsubishi thermostat? Do you mind sharing an entire log output after an engine reload, additional 5 second log for the first device've value refresh and log output while rename a homebridge device from within openluup?

      posted in Plugins
      R
      ronluna