[Solved] After Update to Openhab 2.5.1-2: warnings in openhab.log / loosing connection for z-wave devices

Add-ons Bindings
,
1

Hi folks,

my openhab installation was running for nearly a year without major issues. There was some work to do for the upgrade from 2.4 to 2.5, but everything was fine after that was done.
Until the update to 2.5.1-2 arrived with “apt-get upgrade” on 13.01.2020. I got huge delays in my z-wave network, which wasn’t better after the first reboot. As all bindings and things looks good I rebooted again and after that everything seems to work again as expected.

But I still find from time to time multiple entries within seconds, which normally comes every 5 minutes only.

2020-01-16 00:10:02.674 [INFO ] [veClimateControlScheduleCommandClass] - NODE 18 reported: Override type: NO_OVERRIDE, ScheduleState: [UNUSED]
2020-01-16 00:10:03.013 [INFO ] [veClimateControlScheduleCommandClass] - NODE 18 reported: Override type: NO_OVERRIDE, ScheduleState: [UNUSED]
2020-01-16 00:10:03.388 [INFO ] [veClimateControlScheduleCommandClass] - NODE 18 reported: Override type: NO_OVERRIDE, ScheduleState: [UNUSED]
2020-01-16 00:10:03.478 [INFO ] [veClimateControlScheduleCommandClass] - NODE 18 reported: Override type: NO_OVERRIDE, ScheduleState: [UNUSED]
2020-01-16 00:10:03.518 [INFO ] [veClimateControlScheduleCommandClass] - NODE 18 reported: Override type: NO_OVERRIDE, ScheduleState: [UNUSED]
2020-01-16 00:10:03.738 [INFO ] [veClimateControlScheduleCommandClass] - NODE 18 reported: Override type: NO_OVERRIDE, ScheduleState: [UNUSED]
2020-01-16 00:10:04.442 [INFO ] [veClimateControlScheduleCommandClass] - NODE 18 reported: Override type: NO_OVERRIDE, ScheduleState: [UNUSED]
2020-01-16 00:10:04.483 [INFO ] [veClimateControlScheduleCommandClass] - NODE 18 reported: Override type: NO_OVERRIDE, ScheduleState: [UNUSED]

Would setting debug options for the z-wave binding help to get a better view on this?

And afte the update I found lots of TODO entries in the openhab.log. Sometime there are 20 minutes between 2 entries, but that could be also as less as 30 seconds. In total there are now 240 entries in 3 days.

2020-01-15 23:06:07.599 [WARN ] [essage.ApplicationUpdateMessageClass] - TODO: Implement Application Update Request Handling of New ID Assigned (64).

Any idea from which part of openhab this could come?

Furthermore I’ve lost the communication for 2 wall plug switches (one fibaro FGWP102, the other aeon smart switch 6). The fibaro was no longer included in the z-wave network on Monday, the aeon still was in Tuesday, but no communicating with the controller anymore. Even bringing him close to the controller doesn’t help. I had to reset him.
Both were easy to include again in the network, they had been added as new nodes. I’m not sure, if that was just by chance together with the update, but I never had have this ever all the months before.

  • Platform information:
    • Hardware: Raspberry Pi 3 Model B Plus Rev 1.3
    • OS: Raspbian GNU/Linux 9 (stretch) / Linux 4.19.66-v7+
    • Java Runtime Environment: OpenJDK Runtime Environment (Zulu Embedded 8.25.0.76-linux-aarch32hf) (build 1.8.0_152-b76)
    • openHAB version: 2.5.1-2
2

Debug logs could be helpful but do NOT filter them. Filtered logs are useless for troubleshooting.

Check here for how to get debug logs.(When things do not go as planned)

3

It’s always the same. After I enabled DEBUG for z-wave and restarted the binding, the message is gone, I don’t get delayed reports and I’ve not lost any device since my post.

Let’s cross fingers, that it will stay from now on.

Thanks jan

1 Like