General Category > Ideas/Feature requests

Force Sensor Polling

(1/3) > >>

fillibar:
The option of forcing a sensor poll from within the app would be nice. Select a sensor and trigger an individual poll or having an option to poll them all.
In usage actions I see it as:
1) Open sensor listing.
2a) Select and hold on a sensor. This would automatically trigger a poll of that sensor.
2b) Open the menu option for the page (none exists now) and select the Poll All option that would check all.

Sensor statuses will be updated as appropriate and will also flag if they did not receive a response (helpful for finding when sensors have died, out of range, etc...) within X time.

This helps reaffirm for people that the status is the latest one, even if a new poll is triggered (not sure) when the app is opened. Also helps if the app has been sitting open for a while.

Ex: My wife turned off one of the Link bulbs manually. I did not know it was not able to react until I tried to change the state and got an error.

This also brings up two potential configurable settings that would be nice (maybe in an Advanced Sensors menu on the Web US?):
1) Polling interval - How long between polls the Almond+ takes for the sensors.
2) Sensor timeout - How long before the Almond+ gives up waiting for a sensor response. Would obviously affect time it takes to poll if there are many sensors that are not responding.

Automate:
This assumes the sensor is line powered.  Most battery powered sensors go into a sleep mode to save battery and can not immediately respond to a poll.

fillibar:
An important caveat to be noted. So it might apply more to modules than sensors even though they currently all reside under sensors. Not sure how many sensors do this but as an example my motion sensors have batteries but can also receive line power.

LGNilsson:
I'm not even sure if this is possible with a lot of sensors, but what should be possible to do, but don't expect it any time soon, would be to add an option to set the poll time on the sensor, if supported.
So say you have a temperature sensor, then you should be able to set the poll time on it from x to y depending what range is supported by the sensor.

However, in your example, the bulb should've sent its status change within less than a second from it having been changed, so you might be seeing something entirely different here. We haven't tested these bulbs yet, but I know we have some coming, so there might still be room for improvement on how they work with the Almond+.

fillibar:
When the bulb is on I see response times of 0.025 to 0.033 seconds (I think, I could have an extra zero in there, but either way the response time is a nice little detail). It was when the bulb was off (no power to it) that the app had trouble.

Navigation

[0] Message Index

[#] Next page