I am very dissatisfied with OpenHab at the moment.
I actually only look after the system sporadically, as it runs very reliably with my few requirements (ZWave shutters, Zwave switches, Zwave heating thermostat, Hue system and Fritzbox). So far. After my last update from version 4.0.1 to 4.3.4, I have problems that I can’t easily fix.
Philips Hue Bridge no longer works (error message: Fatal error ‘TIMEOUT’ from ‘Clip2Bridge’ => closing session and when trying to set up again: Cannot update bridge thing ‘hue:bridge-api2:xxxxxxxxxxxxxxxx’ from legacy since handler already initialized).
I have tried various suggestions from the forum here. All without success.
FritzBox Presence Detection runs very unreliably. Before the update, the Openhab detected that I was connected to the WLAN when I was still outside the door. Now with version 4.3.4. it takes 1-2 hours until “I am at home”, although my cell phone still logs in immediately.
However, I can’t find any information on how to fix this or what I can try.
I’m very unhappy with the latest update at the moment. I’ve already invested hours in Google and the community again and to no avail.
hard to troubleshoot without knowing more details.
I can just comment that I am running 4.3.4 as well and the HUE binding and Fritz Binding is working very well and reliable (here).
Maybe some basic troubleshooting first: Did you make sure that bindings are installed? Especially after installation of a new(er) openHAB version I sometime recognize, that some bindings were not installed anymore. Check this first.
Timeout to Bridge maybe means the token is not available anymore? Try to do a reconnect to HUE bridge as described in the Binding info.
Same is valid for AVM.
Thank you for taking care of my problem.
I disconnected the items, deleted the things, uninstalled the bindings, cleared the cache, restarted several times and added the bindings and things again. With no result.
What I noticed, however, is that the time (comes via the NTP binding and the local:dateTime channel) is not correct.
After restarting or after binding out and back in, the system gets the correct time but is wrong again shortly afterwards.
The NTP is connected but does not seem to update. I have checked all settings again and also removed and reinstalled the binding. Again without success. But at the moment I am guessing that this time is the cause of my problems.
What else can I test here?
I have a Raspberry Pi 4 Model B Rev 1.2 and Openhabian 4.3.4 - Release Build
What do you mean exactly? Is the difference to current time a couple of hours? Then we should start looking into adjusting the time zones.
Do you find any errors in journalctl?
Timezone is correct. I startet the System at 10:15 and also the NTP Item is 10:15. Now at 11:20 the Item (and only the item) shows 11:15. the Logs show correct Time and also the raspi.
What do you mean with journalctl?
now, at 12:00 it is already 12 minutes difference.
the internal (Java?) clock is too slow and the NTP binding does not update it cyclically. The debug log of the NTP binding only reports something when restarting.
journalctl is a command to view the system log.
In the past there have been some problems where 2 time sync daemons were interfering each other. You will see this sort of problems in the system log, if you have several start stop time sync entries.
in the journalctl I find no references to timesync
neither errors nor start-stop references.
Only a single entry after the last start:
Apr 16 09:26:27 openhabian systemd[1]: systemd-timesyncd.service: Succeeded
