Nice! I recreated the device and it works! thanks for the help 
Has anyone noticed more issues today? Iâve had some lack of execution on scheduled rules, and Iâve started getting the error where SetLevel is not properly turning on my Hue bulbs. Iâm wondering if itâs related.
Aside from the fact I received an email yesterday letting me know that my hub firmware was going to be updated - how else would I have known the update happened ? It doesnât appear in the log / activity feed, I didnât get a ânotificationâ of the update or even that the hub had gone offline/online again or rebooted. There is no physical indication like a flashing light.
It seems to have been a totally stealth operation⌠and Iâm not sure that it really should be like that when itâs controlling my home. How do others feel ?
PS Donât get me wrong Iâm delighted that new firmware is available, especially if it improves thingsâŚ
Yup, see link above in my response to Mike
My presence/arrival sensor has stopped working today. It reported, correctly, when I left home this afternoon, but I have been back home for hours and it still has failed to register arrival.
The device responds to the beep command by beeping several times, but still does not register presence. Anyone else had this? Iâll get on to support tomorrow if I get chance
I believe when an update to the hub out the platform occurs that one of two things should happen.
- at the conclusion of the update the hub should perform a complete reboot.
Or
- a message should be pushed to the primary account holder that an update has occurred and that a hard reboot of the system is recommended.
I equate a platform/hub update to the same thing as changing the oil in your car without turning the engine off. It can be done, just not done right.
Confirmed that they wonât. Here is the email reply received from Support when I asked about my v1 (emphasis added):
[quote]Hi Bob,
This email regarding an update scheduled for hubs was only intended for certain users of our second generation hub, but you were inadvertently included on that email. As a result, your hub does not require an update, nor should you experience any interruption in service.
Please accept our apologies for any inconvenience, and if you have any questions, let me know.[/quote]
So it isnât even for *all *v2 hubs.
Well, all I can say is that I have not been experiencing the problems to the level of others⌠So this update better not make mine behave like theirs!
Pretty much no new issues here as wellâŚ
I actually have both hub 1 and hub 2 running at home. Still migrating⌠anyway. The update is for hub 2 and it went very smooth. Coincidentally⌠my hub 1 is dealing with schedule issue right now and itâs not even the one with the update.
What is new with the Smart Home Monitor?
So hub v1 firmware, the latest is 000.013.00013 ?
Mine says it is up to date when queried from the mobile app, and thatâs what I have.
Mine updated, no issues other than the Nest issue reported which was easy to fix (and I have doubts is related to hub update).
I didnât watch it like some do though, I have to work during the day.
Mine also says 000.013.00013. Donât know if it updated.
These release note might as well say âwe changed some stuffâ - details please!
Thanks for confirming. I was hoping to get some of the weird issues fixed (even though I know 99% of them are server-side).
Small update to the OP
- Some SHM child apps run locally now
Specifically the alerts, they can know take actions on local devices like an Alarm device in your SHM can run locally.
Remember the 3 requirements for locally executing apps
- App can run locally
- Devices can run locally
- The app doesnât include devices that canât run locally.
Most importantly would be the leak alarm => valve close. Is this running locally now? That would be a big deal.
EditâŚ
Just looked, we need to add valves to this list still.