Problem with the latest beta (OpenZWave)
Moderator: leecollings
-
tjabas
- Posts: 562
- Joined: Sunday 11 December 2016 13:51
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Problem with the latest beta (OpenZWave)
Hi
i have uppdated to the lates beta but somehow all of my battery powered z-wave deviced has disappeared, i have restored several backups of domoticz and the z.wave config file, but the battery powered nodes are gone.
anyone else hwo have this problem?
i have uppdated to the lates beta but somehow all of my battery powered z-wave deviced has disappeared, i have restored several backups of domoticz and the z.wave config file, but the battery powered nodes are gone.
anyone else hwo have this problem?
-
tjabas
- Posts: 562
- Joined: Sunday 11 December 2016 13:51
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: problem with the latest domoticz beta
Anyone else with this problem?
-
AllesVanZelf
- Posts: 265
- Joined: Monday 05 February 2018 8:42
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 12467
- Location: Netherlands, near Haarlem
- Contact:
Re: problem with the latest domoticz beta
I've read somewhere that you have to wake up all zwave devices by button on the device. This was because of new openzwave. Can you try that?
Verstuurd vanaf mijn SM-G960F met Tapatalk
Verstuurd vanaf mijn SM-G960F met Tapatalk
Domoticz 2020.1 (12230) on Raspberry Pi 3B with Raspian Buster. Besides Domoticz, Rpi is running Pi-Hole.
-
akamming
- Posts: 422
- Joined: Friday 17 August 2018 14:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: problem with the latest domoticz beta
hard to say. i think i need a more proper description of what do you mean by "gone". Are the devices no longer in the device list? Are the Z-Wave nodes no longer visible in the z-wave hardware screen? Have they also dissapeard from the OZW control panel? Of is everything still there but it does not work? etc...
-
tjabas
- Posts: 562
- Joined: Sunday 11 December 2016 13:51
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: problem with the latest domoticz beta
Sorry, i mean that the nodes are still there, the manufacture name is also there, but the rest shows :ID 0*0000 and TYPE 0*0000.
Im at work now so i cant give you any more details than that.
And this has happend to all of my battery powered z-wave nodes.
Im at work now so i cant give you any more details than that.
And this has happend to all of my battery powered z-wave nodes.
-
akamming
- Posts: 422
- Joined: Friday 17 August 2018 14:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: problem with the latest domoticz beta
aha yes.. i had exactly the same issue (also on some non battery powered nodes). I fixed as follows
1. if you just did a reboot: wait till Z-Wave initialisation is finished (if it's still in progress you can see it on the z-wave hardware page)
2. then fix your invalid nodes by the following procedure (one a time: I tried several in parallel, but then it failed)
- Go to OZW control panel
- Select the 1st node which is not initialized correctly
- Give the Refresh Node Info command (select in drop down list under "controller" and press GO)
- Wait for the Node to get the "ready" status (if the device is battery powered you have to wake it up manually to get into this status)
- Select the node again
- Check the "current values" on the bottom of the page to see if all sensors are reported correctly
- if no: Repeat this procedure (for some nodes i had to do it a few times).
- if yes: Repeat the procedure for the next node
After i performed these steps on all my devices i had a fully functional Z-Wave config and stable system again. And now i am a happy OZW 1.6 user.
1. if you just did a reboot: wait till Z-Wave initialisation is finished (if it's still in progress you can see it on the z-wave hardware page)
2. then fix your invalid nodes by the following procedure (one a time: I tried several in parallel, but then it failed)
- Go to OZW control panel
- Select the 1st node which is not initialized correctly
- Give the Refresh Node Info command (select in drop down list under "controller" and press GO)
- Wait for the Node to get the "ready" status (if the device is battery powered you have to wake it up manually to get into this status)
- Select the node again
- Check the "current values" on the bottom of the page to see if all sensors are reported correctly
- if no: Repeat this procedure (for some nodes i had to do it a few times).
- if yes: Repeat the procedure for the next node
After i performed these steps on all my devices i had a fully functional Z-Wave config and stable system again. And now i am a happy OZW 1.6 user.
-
AllesVanZelf
- Posts: 265
- Joined: Monday 05 February 2018 8:42
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 12467
- Location: Netherlands, near Haarlem
- Contact:
Re: problem with the latest domoticz beta
Domoticz 2020.1 (12230) on Raspberry Pi 3B with Raspian Buster. Besides Domoticz, Rpi is running Pi-Hole.
-
tjabas
- Posts: 562
- Joined: Sunday 11 December 2016 13:51
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: problem with the latest domoticz beta
thank you for your help, but it wont work, i have tested to exclude and the include one of the wall switches , it get paired and everything seems fine, but when i restart the open z-wave plugin the newly paired wallswitch is set to 0*0000 again.
i really dont know what to do.
i really dont know what to do.
- gizmocuz
- Posts: 2712
- Joined: Thursday 11 July 2013 18:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Top of the world
- Contact:
Re: problem with the latest domoticz beta
This might have to do with the move to OZW 1.6 (which is still in beta phase in domoticz, but this will be the default)
First:
You do not have to exclude/include, you do not have to reset the controller or the node, all information is stored inside the controller/node, and this is hardware... and OZW 1.6 is software...
I see a lot of people freaking out and doing excludes/includes/resets... you will loose your logs, your timers, scripts etc... do not do this...
There have been many changes in the OZW library, and most (almost all) for the better.
There have been many changes as well in Domoticz related to OZW, and also all for the better, all is looking much clearer now, and also the working should be better, there could still be some issues, but hopefully not to much.
You're not the first one using the beta with OZW...
The configuration/cache file has been renamed, but it needs to be build from scratch anyway because a lot of index/instances has been changed.
This is easier said then done.... Sure OZW will ask kindly to all (powered) nodes to send it's configuration again, but some nodes (battery powered nodes), are probably in 'sleep' mode...
They will respond when they wake-up most times, but that could take up to some hours.
For those nodes, what has been working for me, was to have to node next to my computer, open, so i could (triple) click the wake-up button.
Select the node from the list, and press 'Refresh Node Info', now within a second, wake up the node
What works best for me is to open two browsers, on the left browser open the log, on the right browser open the OZW hardware setup
This way you could directly see if something is happening
Be patient, try waiting a few hours
Also search for (closed) issues on the github repository, like
https://github.com/domoticz/domoticz/is ... -514125507
First:
You do not have to exclude/include, you do not have to reset the controller or the node, all information is stored inside the controller/node, and this is hardware... and OZW 1.6 is software...
I see a lot of people freaking out and doing excludes/includes/resets... you will loose your logs, your timers, scripts etc... do not do this...
There have been many changes in the OZW library, and most (almost all) for the better.
There have been many changes as well in Domoticz related to OZW, and also all for the better, all is looking much clearer now, and also the working should be better, there could still be some issues, but hopefully not to much.
You're not the first one using the beta with OZW...
The configuration/cache file has been renamed, but it needs to be build from scratch anyway because a lot of index/instances has been changed.
This is easier said then done.... Sure OZW will ask kindly to all (powered) nodes to send it's configuration again, but some nodes (battery powered nodes), are probably in 'sleep' mode...
They will respond when they wake-up most times, but that could take up to some hours.
For those nodes, what has been working for me, was to have to node next to my computer, open, so i could (triple) click the wake-up button.
Select the node from the list, and press 'Refresh Node Info', now within a second, wake up the node
What works best for me is to open two browsers, on the left browser open the log, on the right browser open the OZW hardware setup
This way you could directly see if something is happening
Be patient, try waiting a few hours
Also search for (closed) issues on the github repository, like
https://github.com/domoticz/domoticz/is ... -514125507
Quality outlives Quantity!
-
tjabas
- Posts: 562
- Joined: Sunday 11 December 2016 13:51
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Problem with the latest beta (OpenZWave)
Thanks you for that detailed answer, really apreciate it.
Im going to dive into it during the weekend.
Im going to dive into it during the weekend.
- sincze
- Posts: 1302
- Joined: Monday 02 June 2014 22:46
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.4
- Location: Netherlands / Breda Area
- Contact:
Re: Problem with the latest beta (OpenZWave)
Running Zwave with Domoticz V4.11214, all up and running.
Pass2php
LAN: RFLink, P1, OTGW, MySensors
USB: RFXCom, ZWave, Sonoff 3
MQTT: ZIgbee2MQTT,
ZWAVE: Zwave-JS-UI
WIFI: Mi-light, Tasmota, Xiaomi Shelly
Solar: Omnik, PVOutput
Video: Kodi, Harmony HUB, Chromecast
Sensors: You name it I got 1.
LAN: RFLink, P1, OTGW, MySensors
USB: RFXCom, ZWave, Sonoff 3
MQTT: ZIgbee2MQTT,
ZWAVE: Zwave-JS-UI
WIFI: Mi-light, Tasmota, Xiaomi Shelly
Solar: Omnik, PVOutput
Video: Kodi, Harmony HUB, Chromecast
Sensors: You name it I got 1.
-
tjabas
- Posts: 562
- Joined: Sunday 11 December 2016 13:51
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: Problem with the latest beta (OpenZWave)
But do you run zigate together with z-wave?
- sincze
- Posts: 1302
- Joined: Monday 02 June 2014 22:46
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 2024.4
- Location: Netherlands / Breda Area
- Contact:
Re: Problem with the latest beta (OpenZWave)
Mmm need to move the zigate to production to confirm this. That is running in demo/test. Zwave in production.
Pass2php
LAN: RFLink, P1, OTGW, MySensors
USB: RFXCom, ZWave, Sonoff 3
MQTT: ZIgbee2MQTT,
ZWAVE: Zwave-JS-UI
WIFI: Mi-light, Tasmota, Xiaomi Shelly
Solar: Omnik, PVOutput
Video: Kodi, Harmony HUB, Chromecast
Sensors: You name it I got 1.
LAN: RFLink, P1, OTGW, MySensors
USB: RFXCom, ZWave, Sonoff 3
MQTT: ZIgbee2MQTT,
ZWAVE: Zwave-JS-UI
WIFI: Mi-light, Tasmota, Xiaomi Shelly
Solar: Omnik, PVOutput
Video: Kodi, Harmony HUB, Chromecast
Sensors: You name it I got 1.
Who is online
Users browsing this forum: No registered users and 1 guest