Bridge is online, but thing reports COM error
Closed this issue · 3 comments
befi-ibm commented
This is, what I got when creating a new thing:
COMMUNICATION_ERROR
Communication problem fetching device features: Unable to request features from IoT API, server returned 502, DEVICE_COMMUNICATION_ERROR: DEVICE_COMMUNICATION_ERROR
openhab.log:
2022-11-14 19:31:02.304 [INFO ] [openhab.event.InboxRemovedEvent ] - Discovery Result with UID 'vicare:heating:c9888fa206:fb09ec0e-7f1d-3d77-b683-c987c56h62ba' has been removed.
2022-11-14 19:31:02.347 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'vicare:heating:c9888fa206:fb09ec0e-7f1d-3d77-b683-c987c56h62ba' changed from UNINITIALIZED to INITIALIZING
2022-11-14 19:31:03.223 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'vicare:heating:c9888fa206:fb09ec0e-7f1d-3d77-b683-c987c56h62ba' changed from INITIALIZING to OFFLINE (COMMUNICATION_ERROR): Communication problem fetching device features: Unable to request features from IoT API, server returned 502, DEVICE_COMMUNICATION_ERROR: DEVICE_COMMUNICATION_ERROR
Unfortunately I do not find any documentation, how to proceed ...
rtuck99 commented
Typically I have seen that when my boiler has trouble reaching the Viessmann servers, because the wifi connection to the boiler has dropped. Do you see any error messages in the Viessmann app?
befi-ibm commented
No, not that I can see. App runs fine
befi-ibm commented
magically, after 2 days, it works without any changes