Open dubocr opened 2 years ago
@qelanhari you said the error disappeared suddenly ?
Nope, it was just that i reduced back the refreshperiod. Still got it when it does refresh.
@IngmarStein @qelanhari
Full device refresh is not yet available on Local API : https://github.com/Somfy-Developer/Somfy-TaHoma-Developer-Mode/issues/26.
Until supported, the error could be ignored.
Can we use the setup endpoint instead ? :-p
What's the consequence of this API not being available, i.e. what feature requires full device refresh?
This endpoint request all devices to refresh their states.
This is used for devices that were operated locally (manually or by remote control) but don't report
their states to the controller (bridge).
With io-homecontrol, devices could be actuators or sensors (or both). actuators receive radio orders but don't notify their states. sensors notify their states.
In the case a device (eg. a garage door) is actuator
only, if it is operated locally (eg. with radio remote control) the OpenClosed
state of the device is updated internally but not reported (notified) to the controller (the bridge).
So we have to periodically refresh
the device states to make sure bridge (and so homebridge) is up to date.
Because of this limitation on actuators
, manufacturers generally implements new devices as actuator + sensor
to let them notify their states. But it is not the case for all devices, particularly old one.
Setup endpoint just retrieve the full configuration from the bridge. But as explained above, even the bridge is not up to date in this case. (getting the fresh data from the bridge is done with the fetch
request made every 10 seconds).
There hasn't been any activity on this issue recently. Please make sure to update to the latest Homebridge TaHoma version to see if that solves the issue. This issue will be closed in case of inactivity.
Have the same issue:
@IngmarStein @qelanhari
Full device refresh is not yet available on Local API : Somfy-Developer/Somfy-TaHoma-Developer-Mode#26.
Until supported, the error could be ignored.
@dubocr I have the same „issue“ or better annoyance. I understand the limitations of the local API here but would it be possible to hide that message in the homebridge logs for local API configuration?
Because it might take a while before this is supported by the local API, maybe catch and report accordingly in the console until then? Include URL to this issue.
Same issue here. Would be nice to hide this from the Logs until supported.
Bonjour Romain, c’est vrai que ce serait bien de pouvoir masquer ce message qui pollue les logs
Bonjour @dubocr est ce possible du supprimer ce message qui pollue les logs?
Bonjour @dubocr est ce possible du supprimer ce message qui pollue les logs? Merci
@dubocr up stp
Using the local API, I get Error 400 Unknown object. (UNSPECIFIED_ERROR)