search

PArns / ioBroker.innogy-smarthome

Livisi Innogy SmartHome Adapter for ioBroker
https://www.iobroker.net/
MIT License
8 stars 6 forks source link

Fehlender WDS Knoten bei einigen Fenstern #101

Closed tom3kcgn closed 1 year ago

tom3kcgn commented 1 year ago

Describe the bug
In einigen Knotepunkten der Fensterkontakte fehlt der Knoten WDS und damit auch der Status, ob ein Fenster offen oder geschlossen ist.

To Reproduce
Nach einem Neustart des Adapters kann es vorkommen, dass ein anderes Fenster von den Problem betroffen ist, was vor dem Neustart noch den Knoten hatte.

Expected behavior
Alle Fensterkontakte haben den Knoten WDS und den Status "IsOpen"

Screenshots & Logfiles
Screenshot 2023-01-08 22 36 26

Versions:

Additional context
Die IoBroker Instanz läuft als Docker Container. In der alten Version hat dies jedenfalls keine Probleme veruracht.

Apollon77 commented 1 year ago

Please delete all objects and then restart the adapter. The shown structure seems like the old "pre 1.0" one. And make sure to reload the admin browser window after that first initial start and after all objects were created.

If still an issue please set loglevel to debug and post logfile from Log on disk (/opt/iobroker/log/...) from whole start

tom3kcgn commented 1 year ago

Please delete all objects and then restart the adapter. The shown structure seems like the old "pre 1.0" one. And make sure to reload the admin browser window after that first initial start and after all objects were created.

If still an issue please set loglevel to debug and post logfile from Log on disk (/opt/iobroker/log/...) from whole start

Just followed your instructions. Deleted the whole Innogy-Objects-Folder, restarted the adapter, refresh browser. But there are still two devices without the WDS Folder. The logfile you requested: current-log.log

The structure seems to be the same as before: image

tom3kcgn commented 1 year ago

Nodes are now available. Although the value for "IsReachable" was true and "LowBattery" was false, the contacts were not reachable. After a battery change the contacts were reachable and after deleting the nodes and restarting the adapter the data points were available.

Sorry for the circumstances

Apollon77 commented 1 year ago

Although the value for "IsReachable" was true and "LowBattery" was false, the contacts were not reachable.

For this a debug log would have been interesting. Were there messages in Livisi odr were they already deleted/acknowledged? The adapter reads all messages on start and checks for battery/recachability ones and set the states accordingly ... so acknowledging these alerts in Livisi will hide it for the adapter on start ... Could this be?