I was unable to get MQTT to work correctly in openluup... I had to give up... It's a real shame ... as ZwaveJS is by far the best thing I've seen to manage zwave networks.
R
ronluna
@ronluna
If you’re like me and still running HABridge to control your devices locally via Alexa, you might need to tweak your endpoints to call Reactor via HTTP. Here’s the best way to do it, IMO:
Insert the Reactor Canonical ID (e.g., zwavejs>71-1) into the MapID field, but make sure it’s URL-encoded like this: zwavejs%3E71-1.
Then, configure these endpoints as needed:
On: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.on
Off: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.off
Dim:
For lights: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/dimming.set?level=${intensity.decimal_percent}
For roller shutters: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/position.set?value=${intensity.decimal_percent}
Color: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/rgb_color.set_rgb?red=${color.r}&green=${color.g}&blue=${color.b}
Just replace [ReactorIP] with your actual IP address. By using these placeholders, you can standardize your endpoints across all devices, making maintenance easier.
This setup works with any device mapped under MSR, regardless of the controller (ZWaveJS, Vera, HASS, OpenSprinkler, virtual, MQTT, DynamicEntities, etc.). If you need different calls, just go to the entities, get the action and parameters, and adjust accordingly. Enjoy super fast access to your devices via Alexa!
If you're migrating from Vera, the endpoints are (URL-encoded) in a file called device.db, in JSON format, under your config. You'd write a script to align the new endpoints to the new one, if you prefer to do it automatically. YMMV.
Just for the record, in case anyone is following, I'm really rather impressed.
I have installed one of these:
https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1
That's connected (physically) to the VM running on my Synology, with a 2m USB extension.
The same host also runs Openluup, Mosquito, HA Bridge.
Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions.
Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor
I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA.
https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title
The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so...
https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title
Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt.
And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one).
A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....)
Commended to the house. Thanks for everyone that got me on the right lines.
C
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Good evening all,
For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time.
Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed.
Thanks.
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations.
Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction?
Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for.
I guess it's something of an edge case so no huge issue.
TIA!
C
I'm sure this has been asked, and answered, but damned if I can figure it out
Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage.
Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts.
After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!)
What I would like is for the 3 minute delay until the lights go off to start from the latest door open event.
That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity.
I've tried 'hacking' with a virtual switch, but can't seem to stop the delay.
Any pointers?
TIA
C
Hello oh great ones.
After a couple of hours messing with ports and permissions I have Zigbee2mqtt installed and running on my virtual pi
Can connect to the front end and everything
Odd one though, simply cannot get systemctl to work and the error is, well, unhelpful. The service file is this:
[Unit]
Description=zigbee2mqtt
After=network.target
[Service]
Environment=NODE_ENV=production
Type=notify
ExecStart=/usr/local/bin/node index.js
WorkingDirectory=/opt/zigbee2mqtt
StandardOutput=inherit
# Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5)
StandardError=inherit
WatchdogSec=10s
Restart=always
RestartSec=10s
User=pi
[Install]
WantedBy=multi-user.target
Straight out of the docs with the change to point to my local node install (which we know works as it's the same as the very fine Reactor is using.
Running manually pnpm start
in /opt/zigbee2mqtt works fine
However:
catman@openluup:/etc/systemd/system$ sudo systemctl start zigbee2mqtt.service
Job for zigbee2mqtt.service failed because the control process exited with error code.
See "systemctl status zigbee2mqtt.service" and "journalctl -xe" for details.
Which I have
catman@openluup:/etc/systemd/system$ sudo systemctl status zigbee2mqtt.service
● zigbee2mqtt.service - zigbee2mqtt
Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2025-12-16 12:32:42 GMT; 4s ago
Process: 3093 ExecStart=/usr/local/bin/node index.js (code=exited, status=217/USER)
Main PID: 3093 (code=exited, status=217/USER)
and
-- A start job for unit zigbee2mqtt.service has begun execution.
--
-- The job identifier is 17477.
Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed to determine user credentials: No such process
Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed at step USER spawning /usr/local/bin/node: No such process
-- Subject: Process /usr/local/bin/node could not be executed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The process /usr/local/bin/node could not be executed and failed.
--
-- The error number returned by this process is ERRNO.
Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=217/USER
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit zigbee2mqtt.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 217.
Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit zigbee2mqtt.service has entered the 'failed' state with result 'exit-code'.
Dec 16 12:35:16 openluup systemd[1]: Failed to start zigbee2mqtt.
-- Subject: A start job for unit zigbee2mqtt.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit zigbee2mqtt.service has finished with a failure.
Which strikes me as very odd.
Any blindingly obvious things I'm missing?
TIA!
C
Obviously a quiet forum, but perhaps it's time
I'm looking at rolling Zigbee into my system, in large part for the Aqara FP300 presence sensors which seem to finally provide a solution to if the wasp is actually in the box.
My current set up is as follows:
One Debian VM on Synology NAS running:
Z-wave Server
Open Luup
Multi system reactor
HA bridge
Mosquito MQQT broker
This machine has a UZB Z-wave stick connected via the USB port on the NAS
Another HAOS VM on the same NAS running HAOS
I've got some older Z-wave stuff that I keep around until it fails.
I have some Tuya stuff integrated in HA
My thought was to get either a SMLIGHT SLZB-06M
or an Aqara Hub M2
Integrate them via Zigbee2MQQT (running on the Debian machine) and then expose them in HA so I can continue to automate in MSR.
Thoughts on which of those devices wold be preferable long term. Both are POE capable which is good. It also appears I could add a USB dongle to the NAS and expose it to the HAOS machine.
Any thoughts from the assembled experts here? TIA
C
Another question to the hive mind. Prompted by the fact that I lost yet another z-wave device over the weekend due to a power issue. It looks like z-way server is reporting another device failed (although it's working fine) and message queue is far too long IMHO. Also the failed device has been removed in the expert interface, but still there in the 'normal' one. Sigh.
Currently I have z-wave, Tuya, thinking about Zigbee.... Does anyone use one single protocol for everything? Right now I'm feeling that as the z-wave stuff dies, I'm just gonna replace it with something else....
C
Not really Smart Home stuff, but going to ask as we have smart people...
Bear with me on this one. Asking here because of the font of knowledge!
For many eek years I have had a Virgin V6 box and a Raspberry Pi running Kodi connected to my TV through a cheap *** HDMI switch. It all worked beautifully but the absolutely critical thing was that the TV remote passed the signals back to the Pi to allow remote control of Kodi.
Couple of changes of late:
Installed a soundbar on the TV using the ARC (audio return channel). That then turns the soundbar on and off when the TV turns on and off and the TV volume control controls the soundbar volume direct.
Everything continues to work
Upgraded the software of the Tivo box to Virgin 360. This is literally software only. You get sent a snacky new Bluetooth remote hit 'upgrade' on the screen and off it goes.
Now, things are not playing well. Typically when I turn on to watch Kodi the soundbar comes on (as it should) but the TV either puts out sound through its own speakers and the soundbar, or just the soundbar. It's not possible to control the volume of the soundbar through the TV. Also it's not longer possible to control Kodi using the TV remote.
If I turn the TV360 box off, i.e. power it down, before turning on to watch Kodi, everything is fine.
This makes little to no sense to me. My assumption is that the cheap *** HDMI switch is getting something from the TV360 connection that it didn't used to get when the software was Tivo and that's screwing up the HDMI communications. I'm upgrading the switch to something a little less chap, but wondered if anyone could validate my theory at all?
TIA
C
Posts
-
ZWaveJS and MQTT -
openLuup: MQTT serverIf there is something I can do to help, please let me know.
-
openLuup: MQTT serverI had to disable the MQTT Handler from the startup as it was crashing the entire engine.
-
openLuup: MQTT server@akbooer with DEBUG enabled the logs show:
2022-03-20 15:54:54.501 openLuup.mqtt:: CONNECT tcp{client}: 0x55ae0e8b8318 2022-03-20 15:54:54.501 openLuup.mqtt:: ClientId: ZWAVE_GATEWAY-Zwavejs2Mqtt 2022-03-20 15:54:54.501 openLuup.mqtt:: WillTopic: zwave/_CLIENTS/ZWAVE_GATEWAY-Zwavejs2Mqtt/status 2022-03-20 15:54:54.501 openLuup.mqtt:: WillMessage: {"value":false} 2022-03-20 15:54:54.502 openLuup.mqtt:: UserName: ******** 2022-03-20 15:54:54.502 openLuup.mqtt:: Password: ******** 2022-03-20 15:54:54.502 openLuup.io.server:: MQTT:1829 connection closed tcp{client}: 0x55ae0a5f7e78 2022-03-20 15:54:54.502 openLuup.mqtt:: RECEIVE ERROR: closed tcp{client}: 0x55ae0a5f7e78 2022-03-20 15:54:54.519 openLuup.server:: request completed (16415 bytes, 2 chunks, 1068 ms) tcp{client}: 0x55ae0c39f788 2022-03-20 15:54:54.587 openLuup.server:: error 'closed' sending 6 bytes to tcp{client}: 0x55ae0dfce198 2022-03-20 15:54:54.587 openLuup.server:: ...only 0 bytes sent 2022-03-20 15:54:54.587 openLuup.server:: error 'closed' sending 94946 bytes to tcp{client}: 0x55ae0dfce198 2022-03-20 15:54:54.587 openLuup.server:: ...only 0 bytes sent 2022-03-20 15:54:54.587 openLuup.server:: error 'closed' sending 2 bytes to tcp{client}: 0x55ae0dfce198Seems like is related to what @toggledbits has shared a couple weeks ago. clues?
-
openLuup: MQTT serverI'm currently having a problem where the only way to get openluup to start processing messages from subscribed topics is by restarting the ZWaveJS service. When the ZWaveJS MQTT service is restarted the ZWaveJS Clients send the subscribe messages to openluup and only then is when messages start to get processed.
Testing with the following inserted in the startup:
local json = require "openLuup.json" function MyMQTThandler (topic, message) local info = json.decode (message) local currentLevel = info.value luup.variable_set ("urn:upnp-org:serviceId:Dimming1", "LoadLevelStatus", currentLevel, 68) luup.log("Processed") end luup.register_handler ("MyMQTThandler", "mqtt:zwave/Hallway_2/DImmer_1/38/0/currentValue")I Couldn't find anything on ZWaveJS nor in openluup that might explain this behavior and my short mqtt knowledge is not helpful either.
Any ideas?
-
openLuup: MQTT serverBased out L_ShellyBridge.lua I've created initial L_ZWaveBridge.lua made changes in virtualfilesystem.lua to create D_ZWaveBridge.xml, D_ZWaveBridge.json and subcribed to zwave topic. which is how the MQTT messages are sent from ZWaveJS2MQTT by default.
my startup lua looks like:
luup.attr_set ("openLuup.MQTT.Username", "*********") luup.attr_set ("openLuup.MQTT.Password", "*********") luup.attr_set ("openLuup.MQTT.Port", 1811) luup.attr_set ("openLuup.MQTT.PublishVariableUpdates", true) luup.attr_set ("openLuup.MQTT.DEBUG", true)With my short mqtt understanding ZWaveJS is connecting and authenticating just fine to openluup although I've been unable to properly modify L_ZWaveBridge.lua to capture and parse the messages that ZWaveJS is sending.
-
openLuup: MQTT serverWould be awesome to get ZWaveJS2Mqtt added to openluup. As much as ZWay has proven to be faster and much more reliable than Vera... ZWaveJS has a bright future...
-
io module async ?Maybe adding sockproxyd natively into openluup and modifying io.lua to optionally use sockproxyd could be a real winner to finally solve the limitations/problems in the I/O module.
-
io module async ?There is a little issue I'm currently facing with openluup and plugins that relies on io module.
If openluup is watching a variable that belongs to a devices that relies on io module and there is an action attached that also relies on io module, when that watcher gets triggered, the action in question will get processed in openluup (it will show in the logs) but the parent device won't process it.
I have a feeling that this could be due to io packets crossing between each others somehow modifying the final message received by the parent device. it's feels like the io communication is happening in the same room for all plugins and sometimes they get crossed. Wondering if anyone has experienced something of that sort and if there is a way to prevent it?
-
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...
-
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.
-
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 -
BroadLink Mark II pluginI 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 pluginI 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_Mk2Any ideas how to get the RF portion working?
-
Generic support for vacuums@therealdb could use homebridge 2 openluup also...
-
Homebridge to Openluup -
Homebridge to Openluup -
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.
-
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...
-
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?
-
Homebridge to Openluup@crille said in Homebridge to Openluup:
THERMOSTAT_uuid
That's odd... It shouldn't do that...
is your deviceList Variable ending with a semicolon ";" after your uuid ?