OpenZwave reinterviewing all nodes after every reboot
Moderator: leecollings
-
- Posts: 338
- Joined: Friday 17 August 2018 14:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
OpenZwave reinterviewing all nodes after every reboot
I have a RPI4 on latest stable (2020.2). I don't know when this issue started (cause i don't restart domoticz a lot), but i found out that on every restart Domoticz ignores the ozwcache files and starts rebuilding the ozw config by re-interviewing all devices. This also means that after every restart i have to wake up all battery powered devices to get them working again.
This problem might be there some time, cause i noticed that in the upgrades to 2020.1, 2020.2 and a beta before 2020.1 this also happened. I thought this was part of the upgrade of the release and i did not reboot in between.
i checked the ozw cache.xml file (and the config is there after the restart and waking up all devices), so there should not be a need to reinterview.
Does any know how i can fix this, so i can reboot without having to wake up all my battery powered devices again?
This problem might be there some time, cause i noticed that in the upgrades to 2020.1, 2020.2 and a beta before 2020.1 this also happened. I thought this was part of the upgrade of the release and i did not reboot in between.
i checked the ozw cache.xml file (and the config is there after the restart and waking up all devices), so there should not be a need to reinterview.
Does any know how i can fix this, so i can reboot without having to wake up all my battery powered devices again?
-
- Posts: 4
- Joined: Thursday 10 March 2016 12:36
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.4834
- Contact:
Re: OpenZwave reinterviewing all nodes after every reboot
This has been going on for a long time. Before 2020.1 release.
After the update I have frequent crashes and that makes Domoticz unusable for me.
I have taken the step to buy a new RPi and are in the process of merging. I hope the crashes will go away but even without them this behaviour with the cache file is not good.
After the update I have frequent crashes and that makes Domoticz unusable for me.
I have taken the step to buy a new RPi and are in the process of merging. I hope the crashes will go away but even without them this behaviour with the cache file is not good.
-
- Posts: 338
- Joined: Friday 17 August 2018 14:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: OpenZwave reinterviewing all nodes after every reboot
Tx for sharing. In my case domoticz is quite stable. So that's why i almost never restart.
Did/Do also have the issue that domoticz re-interviews the nodes after reboot? Or "just" the instability issues?
Did/Do also have the issue that domoticz re-interviews the nodes after reboot? Or "just" the instability issues?
-
- Posts: 4
- Joined: Thursday 10 March 2016 12:36
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 3.4834
- Contact:
Re: OpenZwave reinterviewing all nodes after every reboot
Yes, I do have the re-interview problem. That is the problem that was introduced before 2020.1 release. The crashing within 20 minutes is new for med from 2020.2.
It has been a bit of a gamble. Sometimes the information is there after reboot, other times it is gone.
It has been a bit of a gamble. Sometimes the information is there after reboot, other times it is gone.
-
- Posts: 62
- Joined: Saturday 07 November 2015 12:30
- Target OS: Windows
- Domoticz version: Beta
- Location: Sweden
- Contact:
Re: OpenZwave reinterviewing all nodes after every reboot
There is a known issue, at least before, in OZW that makes OZW crash first time it is started with a new release. I also had a crash after updating to 2020.2 but after the crash and a power-cycle of the hardware it works perfectly. I do not get re-interview problems since the re-boot (dont forget power-cycle or the Zwave controller/serial interface may have issues).
-
- Posts: 338
- Joined: Friday 17 August 2018 14:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: OpenZwave reinterviewing all nodes after every reboot
ok apparently it is not limited to my instance, so i opened an issue on github: https://github.com/domoticz/domoticz/issues/4119bcaroll wrote: ↑Wednesday 29 April 2020 16:31 Yes, I do have the re-interview problem. That is the problem that was introduced before 2020.1 release. The crashing within 20 minutes is new for med from 2020.2.
It has been a bit of a gamble. Sometimes the information is there after reboot, other times it is gone.
-
- Posts: 338
- Joined: Friday 17 August 2018 14:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: OpenZwave reinterviewing all nodes after every reboot
what do you mean with "power-cycle" ? Shutting down the hardware completely and switching off the power ?Ricard1 wrote: ↑Wednesday 29 April 2020 22:04 There is a known issue, at least before, in OZW that makes OZW crash first time it is started with a new release. I also had a crash after updating to 2020.2 but after the crash and a power-cycle of the hardware it works perfectly. I do not get re-interview problems since the re-boot (dont forget power-cycle or the Zwave controller/serial interface may have issues).
Update: I just had to reboot the system anyway (for another reason), so i decided based on the remark of Ricard1 to also shutdown the power completely for 1 minute. I did not have any effect. Domoticz is now re-inverviewing all devices again. Here is my domoticz logging:
Code: Select all
2020-04-29 22:32:33.298 Status: OpenZWave: ManufacturerSpecificDB Ready
2020-04-29 22:32:33.598 Status: OpenZWave: Driver Ready
2020-04-29 22:32:33.606 OpenZWave: Value_Added: Node: 98 (0x62), CommandClass: SWITCH BINARY, Label: Instance 1: Switch, Instance: 1, Index: 0
2020-04-29 22:32:33.607 OpenZWave: Value_Added: Node: 98 (0x62), CommandClass: SWITCH BINARY, Label: Instance 2: Switch, Instance: 2, Index: 0
2020-04-29 22:32:33.607 OpenZWave: Value_Added: Node: 98 (0x62), CommandClass: SWITCH BINARY, Label: Instance 3: Switch, Instance: 3, Index: 0
2020-04-29 22:32:33.607 OpenZWave: Value_Added: Node: 98 (0x62), CommandClass: SCENE ACTIVATION, Label: Scene, Instance: 1, Index: 0
2020-04-29 22:32:33.607 OpenZWave: Value_Added: Node: 98 (0x62), CommandClass: SCENE ACTIVATION, Label: Duration, Instance: 1, Index: 1
2020-04-29 22:32:33.608 OpenZWave: Value_Added: Node: 100 (0x64), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1, Index: 0
2020-04-29 22:32:33.609 OpenZWave: Value_Added: Node: 100 (0x64), CommandClass: METER, Label: Electric - kWh, Instance: 1, Index: 0
2020-04-29 22:32:33.609 OpenZWave: Value_Added: Node: 100 (0x64), CommandClass: METER, Label: Electric - W, Instance: 1, Index: 2
2020-04-29 22:32:33.609 OpenZWave: Value_Added: Node: 100 (0x64), CommandClass: METER, Label: Electric - V, Instance: 1, Index: 4
2020-04-29 22:32:33.609 OpenZWave: Value_Added: Node: 100 (0x64), CommandClass: METER, Label: Electric - A, Instance: 1, Index: 5
2020-04-29 22:32:33.609 OpenZWave: Value_Added: Node: 100 (0x64), CommandClass: METER, Label: Electric - PF, Instance: 1, Index: 6
2020-04-29 22:32:33.609 OpenZWave: Value_Added: Node: 100 (0x64), CommandClass: METER, Label: Exporting, Instance: 1, Index: 256
2020-04-29 22:32:33.610 OpenZWave: Value_Added: Node: 100 (0x64), CommandClass: ALARM, Label: Power Management, Instance: 1, Index: 8
2020-04-29 22:32:33.610 OpenZWave: Value_Added: Node: 100 (0x64), CommandClass: ALARM, Label: Previous Event Cleared, Instance: 1, Index: 256
2020-04-29 22:32:33.612 OpenZWave: Value_Added: Node: 179 (0xb3), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 1, Index: 0
2020-04-29 22:32:33.612 OpenZWave: Value_Added: Node: 179 (0xb3), CommandClass: ALARM, Label: Home Security, Instance: 1, Index: 7
2020-04-29 22:32:33.612 OpenZWave: Value_Added: Node: 179 (0xb3), CommandClass: ALARM, Label: Previous Event Cleared, Instance: 1, Index: 256
2020-04-29 22:32:33.613 Status: SendSwitchIfNotExists: Device '179.instance.1.index.256.commandClasses.113' (Previous Event Cleared) with DeviceID '0000B300' matches '179.instance.1.index.0.commandClasses.48' (Sensor). Domoticz will use the Dimmer (and hide the Switch).
2020-04-29 22:32:33.613 OpenZWave: Value_Added: Node: 179 (0xb3), CommandClass: BATTERY, Label: Battery Level, Instance: 1, Index: 0
2020-04-29 22:32:33.614 OpenZWave: Value_Added: Node: 180 (0xb4), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 1, Index: 0
2020-04-29 22:32:33.614 OpenZWave: Value_Added: Node: 180 (0xb4), CommandClass: SENSOR MULTILEVEL, Label: Air Temperature, Instance: 1, Index: 1
2020-04-29 22:32:33.614 OpenZWave: Value_Added: Node: 180 (0xb4), CommandClass: SENSOR MULTILEVEL, Label: Humidity, Instance: 1, Index: 5
2020-04-29 22:32:33.615 OpenZWave: Value_Added: Node: 180 (0xb4), CommandClass: BATTERY, Label: Battery Level, Instance: 1, Index: 0
2020-04-29 22:32:33.616 OpenZWave: Value_Added: Node: 181 (0xb5), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1, Index: 0
2020-04-29 22:32:33.616 OpenZWave: Value_Added: Node: 181 (0xb5), CommandClass: METER, Label: Electric - kWh, Instance: 1, Index: 0
2020-04-29 22:32:33.616 OpenZWave: Value_Added: Node: 181 (0xb5), CommandClass: METER, Label: Electric - W, Instance: 1, Index: 2
2020-04-29 22:32:33.616 OpenZWave: Value_Added: Node: 181 (0xb5), CommandClass: METER, Label: Electric - V, Instance: 1, Index: 4
2020-04-29 22:32:33.616 OpenZWave: Value_Added: Node: 181 (0xb5), CommandClass: METER, Label: Electric - A, Instance: 1, Index: 5
2020-04-29 22:32:33.616 OpenZWave: Value_Added: Node: 181 (0xb5), CommandClass: METER, Label: Electric - PF, Instance: 1, Index: 6
2020-04-29 22:32:33.617 OpenZWave: Value_Added: Node: 181 (0xb5), CommandClass: METER, Label: Exporting, Instance: 1, Index: 256
2020-04-29 22:32:33.617 OpenZWave: Value_Added: Node: 181 (0xb5), CommandClass: ALARM, Label: Power Management, Instance: 1, Index: 8
2020-04-29 22:32:33.617 OpenZWave: Value_Added: Node: 181 (0xb5), CommandClass: ALARM, Label: Previous Event Cleared, Instance: 1, Index: 256
2020-04-29 22:32:33.618 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 12 (0x0c)
2020-04-29 22:32:33.618 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 13 (0x0d)
2020-04-29 22:32:33.618 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 15 (0x0f)
2020-04-29 22:32:33.619 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 17 (0x11)
2020-04-29 22:32:33.619 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 19 (0x13)
2020-04-29 22:32:33.619 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 33 (0x21)
2020-04-29 22:32:33.619 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 35 (0x23)
2020-04-29 22:32:33.620 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 39 (0x27)
2020-04-29 22:32:33.620 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 40 (0x28)
2020-04-29 22:32:33.620 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 47 (0x2f)
2020-04-29 22:32:33.620 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 51 (0x33)
2020-04-29 22:32:33.620 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 54 (0x36)
2020-04-29 22:32:33.621 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 55 (0x37)
2020-04-29 22:32:33.621 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 56 (0x38)
2020-04-29 22:32:33.621 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 57 (0x39)
2020-04-29 22:32:33.621 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 58 (0x3a)
2020-04-29 22:32:33.621 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 65 (0x41)
2020-04-29 22:32:33.622 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 70 (0x46)
2020-04-29 22:32:33.622 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 71 (0x47)
2020-04-29 22:32:33.622 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 72 (0x48)
2020-04-29 22:32:33.622 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 82 (0x52)
2020-04-29 22:32:33.622 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 83 (0x53)
2020-04-29 22:32:33.623 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 84 (0x54)
2020-04-29 22:32:33.623 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 85 (0x55)
2020-04-29 22:32:33.623 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 86 (0x56)
2020-04-29 22:32:33.623 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 87 (0x57)
2020-04-29 22:32:33.623 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 89 (0x59)
2020-04-29 22:32:33.624 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 90 (0x5a)
2020-04-29 22:32:33.624 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 91 (0x5b)
2020-04-29 22:32:33.624 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 92 (0x5c)
2020-04-29 22:32:33.624 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 93 (0x5d)
2020-04-29 22:32:33.624 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 94 (0x5e)
2020-04-29 22:32:33.625 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 95 (0x5f)
2020-04-29 22:32:33.625 Status: OpenZWave: New Node added. HomeID: 3959520233, NodeID: 96 (0x60)
-
- Posts: 62
- Joined: Saturday 07 November 2015 12:30
- Target OS: Windows
- Domoticz version: Beta
- Location: Sweden
- Contact:
Re: OpenZwave reinterviewing all nodes after every reboot
akamming, Ok maybe maybe it as well depends on that the interview phase was not really fully completed for some reason? Some nodes not completed? What about if you wake them up and triple click, I have a one battery device that never complete the interview process without manual triple click.
-
- Posts: 338
- Joined: Friday 17 August 2018 14:03
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Contact:
Re: OpenZwave reinterviewing all nodes after every reboot
Already tried this. No effect. The interview phase succeeds btw: devices get status ready in controle panel and the ozwcache xml is populated...Ricard1 wrote: ↑Wednesday 29 April 2020 23:16 akamming, Ok maybe maybe it as well depends on that the interview phase was not really fully completed for some reason? Some nodes not completed? What about if you wake them up and triple click, I have a one battery device that never complete the interview process without manual triple click.
Re: OpenZwave reinterviewing all nodes after every reboot
Is your problem solved?
Otherwise try this: https://www.domoticz.com/forum/viewtopi ... 24&t=32568
Otherwise try this: https://www.domoticz.com/forum/viewtopi ... 24&t=32568
Who is online
Users browsing this forum: No registered users and 0 guests