zwavejs2mqtt
Moderator: leecollings
-
- Posts: 177
- Joined: Sunday 13 November 2016 10:43
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2021.1
- Location: Germany
- Contact:
Re: zwavejs2mqtt
Can anybody tell me, which devices for the eurotronics spirit will be created. I use the setpoint device for normal temperatur, mode device to switch between off and on and level mode and the level device to get opening of the velve. Will these devices be all available in zwavej2mqtt? Thanks!
- heggink
- Posts: 972
- Joined: Tuesday 08 September 2015 21:44
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 12451
- Location: NL
- Contact:
Re: zwavejs2mqtt
Here's mine. It has a weird 'dimmer' device that I just hide and ignore. So far, it works quite fine for me but then I don't do very special stuff.
Docker in Truenas scale, close to latest beta
DASHTICZ 🙃
RFXCOM, zwavejs2mqtt, zigbee2mqtt,
P1 meter & solar panel
Google home, Wifi Cams motion detection
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest, lots more :-)
DASHTICZ 🙃
RFXCOM, zwavejs2mqtt, zigbee2mqtt,
P1 meter & solar panel
Google home, Wifi Cams motion detection
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest, lots more :-)
-
- Posts: 177
- Joined: Sunday 13 November 2016 10:43
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2021.1
- Location: Germany
- Contact:
Re: zwavejs2mqtt
Thanks. So it wont work for me because the level device is missing.
-
- Posts: 177
- Joined: Sunday 13 November 2016 10:43
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2021.1
- Location: Germany
- Contact:
Re: zwavejs2mqtt
Sorry, I was wrong. The thermostat dimmer seems to be the device.
-
- Posts: 94
- Joined: Wednesday 30 October 2019 14:11
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Great Britain
- Contact:
Re: zwavejs2mqtt
Issues with (some) Battery operated Setpoints (Device names and device polling)
I have had two problems with my Zwave thermostat (so far) since switching to Zwavejs2mqtt and am sharing my findings here.
My thermostat shows in Zwavejs2mqtt control panel as
The thermostat has amongst other things a value for:
Problem 2- Values not updating in Domoticz
I have found that although my thermostat is detected, the values in the Domoticz widgets for the room temperature were not being updated at all and the setpoint was only updating the widget (& timestamp) if the setpoint was changed. So after a few hours/days the temperature in Domoticz was way out and the setpoint might be accurate but Domoticz would show a very old timestamp if the setpoint hadn't been changed.
I checked the Zwavejs2mqtt control panel and found that the values there were also wrong and I could force them to update by choosing the Device, then clicking the Advanced button, followed by the Refresh Values button. Looking through the documentaion I found this: https://zwave-js.github.io/zwavejs2mqtt ... rt/polling.
Solution: I have now added an additional polling interval (of 10 seconds) for both the temperature sensor and the setpoint.
After doing this the temperature and setpoint values started to update the Domoticz dashboard widgets like they used to under OpenZWave.
I don't really have a clue what I'm doing here and the documentation says:
Thanks
I have had two problems with my Zwave thermostat (so far) since switching to Zwavejs2mqtt and am sharing my findings here.
My thermostat shows in Zwavejs2mqtt control panel as
Problem 1 - Device names being ignored in scripts"productLabel": "HRT4-ZW / SRT321",
"productDescription": "Battery Powered Wall Thermostat",
"manufacturer": "Secure Meters (UK) Ltd.",
"firmwareVersion": "6.0",
"protocolVersion": 2,
The thermostat has amongst other things a value for:
- Setpoint
- Current Room temperature
- Battery Level
- Wake Interval
Solution: For me, simply renaming my setpoint in Domoticz and then using that name in the script fixed this problem.Error: dzVents: Error: (3.1.8) Multiple items found for nodeID_7_hrt4-zw (device). Please make sure your names are unique or use ids instead
Problem 2- Values not updating in Domoticz
I have found that although my thermostat is detected, the values in the Domoticz widgets for the room temperature were not being updated at all and the setpoint was only updating the widget (& timestamp) if the setpoint was changed. So after a few hours/days the temperature in Domoticz was way out and the setpoint might be accurate but Domoticz would show a very old timestamp if the setpoint hadn't been changed.
I checked the Zwavejs2mqtt control panel and found that the values there were also wrong and I could force them to update by choosing the Device, then clicking the Advanced button, followed by the Refresh Values button. Looking through the documentaion I found this: https://zwave-js.github.io/zwavejs2mqtt ... rt/polling.
Solution: I have now added an additional polling interval (of 10 seconds) for both the temperature sensor and the setpoint.
After doing this the temperature and setpoint values started to update the Domoticz dashboard widgets like they used to under OpenZWave.
I don't really have a clue what I'm doing here and the documentation says:
So, if anyone can advise how often I should configure this polling please share your advice.Because such polling can have detrimental effects on your mesh network, Z-Wave JS does not poll devices by default. Polling can quickly lead to network congestion and should be used very sparingly and only where necessary.
Thanks
Running Domoticz and Dashticz beta on Raspberry Pi OS 32 bit - has anyone had success with 64 bit?
Desktop access from Ubuntu Linux
Desktop access from Ubuntu Linux
-
- Posts: 177
- Joined: Sunday 13 November 2016 10:43
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2021.1
- Location: Germany
- Contact:
Re: zwavejs2mqtt
Some questions before migration from ozw.
1. I already have under hardware installed MQTT Client Gateway with LAN interface. I use it for example for shelly-integration. For Zwavej2mqtt MQTT Auto Discover Client Gateway with LAN Interface is needed. Do I need both interfaces or does the second one replace the first?
2. If I don't want to use a docker install, which is the easiest way to install zwavejs2mqtt?
Thanks for your answers.
1. I already have under hardware installed MQTT Client Gateway with LAN interface. I use it for example for shelly-integration. For Zwavej2mqtt MQTT Auto Discover Client Gateway with LAN Interface is needed. Do I need both interfaces or does the second one replace the first?
2. If I don't want to use a docker install, which is the easiest way to install zwavejs2mqtt?
Thanks for your answers.
-
- Posts: 722
- Joined: Friday 02 October 2015 12:12
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Finland
- Contact:
Re: zwavejs2mqtt
Hi again. I wonder which setting is off in my zwavejs2mqtt config. I am now repeatedly getting new devices created in Domoticz from zwave nodes that have been completely removed and not visible in zwavejs2mqtt. I am also getting very weird devices like air temperature for fibaro plug. These are created at Domoticz start and do not update after that. I guess some flags are incorrect in the mqtt, gateway or homeassistant section...?
Relevant earlier posts with regards to my initial struggles to get it working:
Relevant earlier posts with regards to my initial struggles to get it working:
Nautilus wrote: ↑Tuesday 04 January 2022 9:42 All in all I have to say I'm very impressed about some of the changes with regards to stability and overall functionality observed now after running zwavejs2mqtt together with Domoticz for about a week. Maybe someone can help me with one question. Initially when zwavejs2mqtt discovers the devices, they do not have a name (of course). After adding some names, I noticed the devices stopped working in Domoticz (sort of - some did, most did not).
I configured zwavejs2mqtt with the help of these recommendations:
https://github.com/moroen/ZWave-MQTT-pl ... avejs2mqttBut as mentioned couple of posts above:Gateway configuration:
Use node names instead of numeric nodeIDs: Off
Ignore location: On
Include Node Info: On
Note: Specifying node names and locations in zwavejs2mqtt is not required, but recommended. This will generate somewhat sane names of the devices when they are added to domoticz.So my retained flag was on. I took it off and everything started working again. I thought this was it. But then I needed to do one more change and when testing the device in Domoticz after the change, it did not work right away. And I'm not fully sure what I did to make it start working againNow, when I look at the topics in mqtt explorer, I can see only one ID under discovery node, yesterday I saw several of them. I can see them under zwave node though. Why have they disappeared from discovery? Can it be the fact that I enable OZW for a while to get my old device names? Since then I've restarted the system and everything so shouldn't it recover? Can I force the discovery topics to be populated somehow again?
edit. I turned the "retained discovery" switch on in zwavejs2mqtt to "on" and now I have the nodes back under discovery topic. Not sure if this is the right way to do as it was mentioned to best to keep it off...
Now I wonder which is the best practice to change device name in zwavejs2mqtt and keep everything working in Domoticz. Is it just this:So do I need to save preferences once after each name update to re-generate status messages? Or something else?Hint: To add all devices at once, enable the plugin in domoticz, and press "Save" in zwavejs2mqtt preferences. This will generate status messages for all devices.
-
- Posts: 48
- Joined: Sunday 01 September 2019 18:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2021.1
- Location: DE
- Contact:
Re: zwavejs2mqtt
Hi all,
so after some struggle with this whole docker and mosquitto conif I'm now facing an issue I can't resolve by myself.
I think domoticz is connectet with mqtt but no devices are created.
This is the mosquitto log: And this the domoticz log: And thats it. No more logs regarding zwavejs2mqqt on both sides.
MQTT Discorvery is activated in zwavejs2mqtt config.
Help is greatly appreciated.Thanks
EDIT: Okay, just after submit this post I remembered that there is a third party.
This is the zwavejs log: But why it cannot connect?
so after some struggle with this whole docker and mosquitto conif I'm now facing an issue I can't resolve by myself.
I think domoticz is connectet with mqtt but no devices are created.
This is the mosquitto log: And this the domoticz log: And thats it. No more logs regarding zwavejs2mqqt on both sides.
MQTT Discorvery is activated in zwavejs2mqtt config.
Help is greatly appreciated.Thanks
EDIT: Okay, just after submit this post I remembered that there is a third party.
This is the zwavejs log: But why it cannot connect?
-
- Posts: 300
- Joined: Thursday 01 November 2018 19:47
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.6
- Location: Portugal
- Contact:
Re: zwavejs2mqtt
If using docker I think you need to use the actual IP of the device rather than "localhost". That could cause connection issues.
Intel NUC with Ubuntu Server VM (Proxmox),mosquitto(docker),RFXtrx433E,zwavejsUI (docker),Zigbee2mqtt(docker),SMA Hub (docker),Harmony Hub plugin, Kodi plugin,Homebridge(docker)+Google Home,APC UPS,SMA Modbus,Mitsubishi MQTT, Broadlink,Dombus
-
- Posts: 20
- Joined: Monday 16 March 2020 15:51
- Target OS: -
- Domoticz version:
- Contact:
Re: zwavejs2mqtt
I have an issue adding the Wallmote Quad ZW130.
Adding this wireless switch to domoticz using autodiscover Zwavejs2mqtt the scene selector (4 switches) are added as general Custom sensor.
In OZW they are added as Light/Switch Switch.
Using the MQTT explorer i see this Wallmote (WM Aanrecht) is added as sensor and binary sensor in stead of as switch.
Anyone can help me out how to configure the wallmote to switch scenes ?
Adding this wireless switch to domoticz using autodiscover Zwavejs2mqtt the scene selector (4 switches) are added as general Custom sensor.
In OZW they are added as Light/Switch Switch.
Using the MQTT explorer i see this Wallmote (WM Aanrecht) is added as sensor and binary sensor in stead of as switch.
Anyone can help me out how to configure the wallmote to switch scenes ?
- Attachments
-
- Wallmote.png (22.34 KiB) Viewed 3561 times
-
- Posts: 722
- Joined: Friday 02 October 2015 12:12
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Finland
- Contact:
Re: zwavejs2mqtt
Strange saga with zwavejs2mqtt continues. After adjusting the config with recommended settings, I have found the platform to be stable for few weeks. But since yesteday (or Domoticz restart at night, not sure) I have been experiencing weird issues. Switches did not function when set from Domoticz, when set from zwavejs2mqtt they worked. I went to debug and e.g. when trying to open my Danalock lock I saw message:
Message received on zwave/Etuoven_lukko/98/0/targetMode/set: '0'
Etuoven_lukko (front door lock) is the friendly name of the device. Nothing happened with the lock. Then I'm not sure what I exactly did next but at least I save the zwavejs2mqtt config, deleted few unused nodes with mqtt explorere that keeps reappearing even though they are not in zwavejs2mqtt anymore. Then suddenly the switches started working again from Domoticz. Now if I look what happens with the same lock, I see:
Message received on zwave/46/98/0/targetMode/set: '0'
So it is again using the node id. What in Domoticz controls this? Why did it change in the first place and what prompted it to change back?
edit: I tested by deleting all friendly name topics, when I press "Save" in zwavejs2mqtt I get the friendly name topics back, is this expected:
-
- Posts: 20
- Joined: Monday 16 March 2020 15:51
- Target OS: -
- Domoticz version:
- Contact:
Re: zwavejs2mqtt
Using Open Zwave the buttons of the wallmote will be recognized as switch after adding them to a scene where you press the add device button, preass the button on the wallmote (in this case button 1). And then in the device list it is listed as a switchPietjePuck wrote: ↑Tuesday 12 April 2022 15:47 I have an issue adding the Wallmote Quad ZW130.
Adding this wireless switch to domoticz using autodiscover Zwavejs2mqtt the scene selector (4 switches) are added as general Custom sensor.
In OZW they are added as Light/Switch Switch.
Using the MQTT explorer i see this Wallmote (WM Aanrecht) is added as sensor and binary sensor in stead of as switch.
Anyone can help me out how to configure the wallmote to switch scenes ?
- Attachments
-
- Device showed up ad switch
- Screenshot 2022-04-26 155227.png (5.04 KiB) Viewed 3453 times
-
- Adding button to scene
- Screenshot 2022-04-26 155014.png (49.61 KiB) Viewed 3453 times
-
- Posts: 402
- Joined: Wednesday 26 February 2014 15:28
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: the Netherlands
- Contact:
Re: zwavejs2mqtt
I am testing this zwave2MQTT and managed to get the control panel running, am able to include a device and in domoticz the auto discovery function is addin the included devices. But I have some trouble with the following:
The device I included is a Fibaro FGMS001 motion sensor. In the control panel it is not recognized because in the manufacturer column it says "Unknown manufacturer 0x010f". I also am missing some functions for instance the lux measurement. The strange thing is that when I open the link next to the device ID it goes to the zwave JS database where the FGM001 is listed. So it seems the FGMS001 is in the database but still not recognized. Excluding and including it again gives the same result.
The MQTT explorer shows the FGMS001 (I named it "TEST" and gave it the location "Tafel".
Maybe the next is related to the above but the values of the device are not updated, not in the control panel (i'm not sure where I can see the values?) and also not updated in Domoticz.
The device I included is a Fibaro FGMS001 motion sensor. In the control panel it is not recognized because in the manufacturer column it says "Unknown manufacturer 0x010f". I also am missing some functions for instance the lux measurement. The strange thing is that when I open the link next to the device ID it goes to the zwave JS database where the FGM001 is listed. So it seems the FGMS001 is in the database but still not recognized. Excluding and including it again gives the same result.
The MQTT explorer shows the FGMS001 (I named it "TEST" and gave it the location "Tafel".
Maybe the next is related to the above but the values of the device are not updated, not in the control panel (i'm not sure where I can see the values?) and also not updated in Domoticz.
-
- Posts: 14
- Joined: Sunday 09 November 2014 18:36
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.5877
- Location: Netherlands
- Contact:
Re: zwavejs2mqtt
I have the same question, an answer would be appreciatedharrykausl wrote: ↑Sunday 03 April 2022 15:04 Some questions before migration from ozw.
1. I already have under hardware installed MQTT Client Gateway with LAN interface. I use it for example for shelly-integration. For Zwavej2mqtt MQTT Auto Discover Client Gateway with LAN Interface is needed. Do I need both interfaces or does the second one replace the first?
2. If I don't want to use a docker install, which is the easiest way to install zwavejs2mqtt?
Thanks for your answers.
KAKU switches/receivers/Motion sensor/Doorbell
Oregon Temp sensors, TFA Temp sensor
Mertik controller
Raspberry Pi, RFXCom
Oregon Temp sensors, TFA Temp sensor
Mertik controller
Raspberry Pi, RFXCom
- waltervl
- Posts: 5149
- Joined: Monday 28 January 2019 18:48
- Target OS: Linux
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: zwavejs2mqtt
1. You can have multiple Domoticz MQTT gateways. You have to name them differently.
2. See the zwaveJS2MQTT website: https://zwave-js.github.io/zwavejs2mqtt ... kg-version
2. See the zwaveJS2MQTT website: https://zwave-js.github.io/zwavejs2mqtt ... kg-version
Domoticz running on Udoo X86 (on Ubuntu)
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
Devices/plugins: ZigbeeforDomoticz (with Xiaomi, Ikea, Tuya devices), Nefit Easy, Midea Airco, Omnik Solar, Goodwe Solar
-
- Posts: 14
- Joined: Sunday 09 November 2014 18:36
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.5877
- Location: Netherlands
- Contact:
Re: zwavejs2mqtt
Thanks for the quick response!
KAKU switches/receivers/Motion sensor/Doorbell
Oregon Temp sensors, TFA Temp sensor
Mertik controller
Raspberry Pi, RFXCom
Oregon Temp sensors, TFA Temp sensor
Mertik controller
Raspberry Pi, RFXCom
-
- Posts: 195
- Joined: Wednesday 31 May 2017 16:06
- Target OS: NAS (Synology & others)
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: zwavejs2mqtt
Since a few days I have connection lost between the Zwave stick (Aeotec Z-Stick Gen5 (ZW090) - UZB - Sigma Designs, Inc.) and Zwave2MQTT in docker on my Synology NAS. (DSM 6.2)
This is part of the log-file in Docker:
This is part of logfile in Zwave2MQTT:
Stick is recognized by the OS, this is part of output I got from the command dmesg:
In Zwave2MQTT I configured that port:
Downloaded the latest version this morning:
zwavejs2mqtt: 6.15.2
zwave-js: 9.6.2
home id: undefined
home hex: undefined
But no luck
In Domoticz I have only the MQTT Auto Discovery Client Gateway with LAN interface as hardware.
Any idea to get this working?
This is part of the log-file in Docker:
Code: Select all
2022-08-13 13:10:17.147 INFO ZWAVE: Connecting to /dev/ttyACM0
Logging to file:
/usr/src/app/store/zwavejs_2022-08-13.log
2022-08-13 13:10:26.172 WARN ZWAVE: Retry connection in 3 seconds...
Code: Select all
DRIVER version 9.6.2
2022-08-13T13:04:52.282Z DRIVER
2022-08-13T13:04:52.282Z DRIVER starting driver...
2022-08-13T13:04:52.285Z DRIVER opening serial port /dev/ttyACM0
2022-08-13T13:05:01.305Z DRIVER Failed to open the serial port: Error: No such file or directory, cannot open /dev/ttyACM0
2022-08-13T13:05:01.306Z DRIVER destroying driver instance...
2022-08-13T13:05:01.307Z DRIVER driver instance destroyed
Code: Select all
[10513.247528] usb 3-1: USB disconnect, device number 8
[10517.144316] usb 3-2: new full-speed USB device number 9 using etxhci_hcd-170202
[10517.188001] Got empty serial number. Generate serial number from product.
[10517.196636] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
[10517.609754] usbcore: deregistering interface driver cdc_acm
[10517.669985] PPP generic driver version 2.4.2
[10517.681355] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
[10517.688606] usbcore: registered new interface driver cdc_acm
[10517.695002] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[10884.341327] usb 3-2: USB disconnect, device number 9
[10888.951740] usbcore: deregistering interface driver cdc_acm
[11646.479731] usb 3-2: new full-speed USB device number 10 using etxhci_hcd-170202
[11646.522193] Got empty serial number. Generate serial number from product.
[11646.914227] PPP generic driver version 2.4.2
[11646.925588] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
[11646.932931] usbcore: registered new interface driver cdc_acm
[11646.939263] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[11789.959892] dockerc1ae276: renamed from eth0
[11789.973230] docker0: port 1(dockerbcfa126) entered disabled state
[11790.193380] docker0: port 1(dockerbcfa126) entered disabled state
[11790.201207] device dockerbcfa126 left promiscuous mode
[11790.207089] docker0: port 1(dockerbcfa126) entered disabled state
[11795.707731] device dockerc00c1b2 entered promiscuous mode
[11795.715224] IPv6: ADDRCONF(NETDEV_UP): dockerc00c1b2: link is not ready
[11796.955765] IPVS: Creating netns size=2096 id=15
[11797.097400] eth0: renamed from dockerdd0298c
[11797.107244] IPv6: ADDRCONF(NETDEV_CHANGE): dockerc00c1b2: link becomes ready
[11797.115456] docker0: port 1(dockerc00c1b2) entered forwarding state
[11797.122525] docker0: port 1(dockerc00c1b2) entered forwarding state
[11812.139353] docker0: port 1(dockerc00c1b2) entered forwarding state
Downloaded the latest version this morning:
zwavejs2mqtt: 6.15.2
zwave-js: 9.6.2
home id: undefined
home hex: undefined
But no luck
In Domoticz I have only the MQTT Auto Discovery Client Gateway with LAN interface as hardware.
Any idea to get this working?
Synology with Domoticz build (V2024.7) in Docker
-
- Posts: 195
- Joined: Wednesday 31 May 2017 16:06
- Target OS: NAS (Synology & others)
- Domoticz version: 2024.7
- Location: NL
- Contact:
Re: zwavejs2mqtt
Some followup: Problem solved!
I was running this container in Docker on my Syno. As said, it was running oke for months. Suddenly stopped!
Searching on the web I read about Run container with high privileges.... Tried... That was the trick!
I was running this container in Docker on my Syno. As said, it was running oke for months. Suddenly stopped!
Searching on the web I read about Run container with high privileges.... Tried... That was the trick!
Synology with Domoticz build (V2024.7) in Docker
-
- Posts: 402
- Joined: Wednesday 26 February 2014 15:28
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: the Netherlands
- Contact:
Re: zwavejs2mqtt
I also have finally managed to switch from OZW to Zwavejs2MQTT. I've even managed to successfully update the firmware of mij Heltun thermostat. So kuddo's to everyone who invested time and energy in make this work!
But there are some small problems. Mainly caused by devices not being completely recognized.
But there are some small problems. Mainly caused by devices not being completely recognized.
- I have several Fibargroup Wall Plug Switches (FGWPE/F-101) some of them are recognized, others don't. What I've tried is of course the reinterview and also "Refresh values", the interview is completed and most of the the configuration settings are shown but still the name stays on "Unknown manufacturer 0xXXXX". Also when I click on the link to zwave-js.io database next to the device ID I get the message
Is there something that I can do about that?The device configuration file was not found in the Database. - I also have Fibaro smoke detectors these are recognized and added by MQTT discovery but there are only two devices added for each detector.
- Air Temperature
- battery_islow
But in OZW I had several more, like heat switch, housing switch, fire alarm, etc. Especially the last one is quite mandatory for a smoke detector. Also the configuration settings are not fully loaded. Can I solve this and if yes how?
Re: zwavejs2mqtt
Hi all, 2 questions…
Q1: Is there a guide for a Windows 10 domoticz user to follow? I used to use a pi - but the win10 stability has been amazing. No downtime in over a year.
Q2: Does zwavejsmqtt fix the issue domoticz has with reporting the state of a z-wave device? In ozw CP - devices ON/Off state are correct to what a device currently is. But Domoticz never reports this correctly - often shadowing an “on bulb” when a device is off.
Many thanks.
Q1: Is there a guide for a Windows 10 domoticz user to follow? I used to use a pi - but the win10 stability has been amazing. No downtime in over a year.
Q2: Does zwavejsmqtt fix the issue domoticz has with reporting the state of a z-wave device? In ozw CP - devices ON/Off state are correct to what a device currently is. But Domoticz never reports this correctly - often shadowing an “on bulb” when a device is off.
Many thanks.
Who is online
Users browsing this forum: No registered users and 1 guest