Theolsen wrote:That would be perfect.
Yesterday I was testing over 3g and it was largely spot on.
Couple of bugs:
At one point I had poor 3g coverage and got a dialogue that the alertme servers where not responding as quickly as we would like. That was followed by several of the same dialogue within the space of a second or two...each had to be closed individually before I could regain control of the UI.
Switching a smart plug on or off on the overview screen does not always correlate with what is shown on the device screen.
The issue with behaviour over laggy connections (like any 3G) is something that needs improvement, if only not telling you so many times! There are a few fetches that need to be made before a screen update is made, and each of these is given a 15 second timeout. A failure of any one will generate the error, so I need to put some kind of block in there.
The issue with the SmartPlug status is a little trickier... The app 'fakes' the correct setting when you switch, but then will receive an update at the usual interval to get the 'real' state from the API. The API doesn't always know yet that the device has been switched, so that 'real' data can actually be outdated. To confuse matters further, there's a delay within the API itself; some calls will become aware of a change in a device status earlier than others. If you check on the Devices screen, that is often showing the correct information earlier, sometimes up to a minute before the Overview screen! They use different calls, which is the cause.
I've written a new method that uses what appear to be the faster API calls, then uses the processing power of the phone to rebuild the value dictionaries into something more complete, rather than waiting for the API to do it (which may be working on many systems' data input simultaneously). Now I need to change the data model to take the new format... That might have to be in v1.02.
Theolsen wrote:Feature request:
Device screen; Personally I would find it more useful if the location and font characteristics of the battery level and temperature were exchanged. Turning red when my batteries may need attention or signal is lost.
I'd like the option to pick just one device to return its temperature and maybe include that on the overview screen.
Ooh, could you explain that first one a bit more, please? The devices should grey out (but remain touchable) if the signal is lost and the battery level should already display in orange when low and red when very low. Is it not doing this for you? Picking correct values for the batteries to be considered 'dead' is something that might need tweaking, as devices close to the Hub with lower batteries will probably keep working longer than those that are distant.
Temperature stuff... yes, that's something I'm wanting to add to the Overview screen. My eventual plan is to have something similar to the Security and Energy blocks, giving a household average. But how to deal with outdoor sensors...?
Theolsen wrote:That's all I have for you now...I feel like I'm nagging but believe me I'm not...the app is fantastic. I hope this info helps.
Not at all - it's very helpful! Even things I might not get around to for a while are good, because I can have them in the back of my mind while coding some other bit. Hopefully means I don't have to backtrack so often (like that API call change - that's a right faff!).