Routines not marked as running Local (for Hub-Connected LAN driver)

Yes, I have to admit that when I saw routines with speaker notification ‘going local’ a while ago I did wonder how the speech was managed. I think I just trusted the tagging/messaging and put it down to magic!

I didn’t look at/notice other notification types a I knew these must rely on cloud by thier very nature. Kinda thought the speech may be encoded at time of creation and held locally… I guess, maybe :man_facepalming:

Only really look at these things as a general user these days - it works how it works and only really notice behaviour/changes when it impacts what I need. Tend to take everything else at face value.

Thanks @nayelyz , the behaviour actually makes a lot of sense in that notifications are lost but other actions are not. Previously all a routines actions would have been lost so this is a gain. Some clearer messaging for those like, in this instance, me (:roll_eyes:) would be good.

Good discussion. Notifications require a connection to the backend. A good use case is:
If a water leak is detected, then turn off the water valve and attempt to send an SMS notification.

I’m assuming the valve is also a local device. I should order and install one to test it out.