mcf68k
commented
1 year ago I have a similar problem, when I open/close my AXOVIA 3S io using the Tahoma App, the status is correctly updated, but when I'm using the KeyGo IO, the status is not updated until I'm opening the Tahoma App.
Any Idea ?
When i open or close a Somfy Axovia 220B 3S io it return the following state :
10/01 19:45:29.553 [{"deviceURL":"----","deviceStates":[{"type":3,"name":"core:OpenClosedPedestrianState","value":"unknown"}],"name":"DeviceStateChangedEvent"}]About 15 secondes after the gate is closed or is open, the real state is sent :
10/01 19:45:53.859> [{"deviceURL":"----","deviceStates":[{"type":3,"name":"core:OpenClosedPedestrianState","value":"open"}],"name":"DeviceStateChangedEvent"}]When opening the pedestrian (only one side of the gate) it return "pedestrian".
10/01 19:49:09.455 > [{"deviceURL":"----","deviceStates":[{"type":3,"name":"core:OpenClosedPedestrianState","value":"pedestrian"}],"name":"DeviceStateChangedEvent"}]A) "unknown" is a real problem beacause we do not know if the gate is going to open or close. So we cannot rely on this event to trigger something.
B) open / close states are really too late, as you can see 24 secondes after the command was sent. Why this so long delay to sent the event ? The gate is close or open in less than 10 seconds, why waiting 15 seconds more to update the event ? Again, we cannot use it to trigger something since it is really to late.
The online API behind www.tahomalink.com doesn't have theses problems, nor this "unknow" state, nor this delay once gate is open/close.
Please fix it.