EJones01

Looks like a phone reboot was all that was needed. Weirdly UD mobile now shows the correct last time I went through the fence...4 hours ago. Thanks

I have never seen those manual controls on Android. The logs do not show any location changes...but Android settings do show that its asking for them. I wonder if there's been a change in message format or something that the App is not able to read now.

The GPS has worked flawlessly for months. 3 days ago it stopped. I see in my Android settings that the app is still requesting the location but its not triggering the GEO fence anymore. The UD Mobile logs do not show updated locations anymore so I'm presuming there's a disconnect between the ask for location from the App and then not getting it. App still has full permissions. Was there an update?

Updated Policy with no issues just now. Rebooted by itself and all online.

Oh my, I remember doing this when I created these years ago. Thats for the brain jerk! Whilst I can see the extra flexibility this feature may offer, for me it's a needles extra step for my many scenes with multiple switches controlling them. Anyway, thank you! All good now.

I'm not sure I understand. I've been using UD for years, have 20 scenes, 50+ devices. Insteon, ZWave all work OK. Of course I have set the level in the scene....how would it work otherwise. Again, when recalled via either Alexa or a sensor it works correctly, just not from a switch. You are saying to set the level of the controller, but in your picture you show what looks like a receiver?

Of course, they work fine if the scene is triggered from Alexa. I also noticed that in the scenes with motion sensors they work fine too and turn the Zigbee device to the set scene level. Its only when the screen is triggered by an Insteon Switch that the level uses the devices default on level and not the scene on level.

The scene does work correctly from Alexa commands through Polisy, its only when the scene is triggered from an Insteon switch it doesnt work correctly. Further investigation is that it does come on, but at the default On Level, not the level set in the scene. (ZWave and Insteon devices work OK in the same scenes, coming on at the scene level set for the device (not the device default level)) Is this a known limitation, bug or??

I have been on to Amazon Customer Care this morning. The fix is to disable the ISY skill and re-log back into it.

I have been on to Amazon Customer Care this morning. The fix is to disable the ISY skill and re-log back into it.

Mine two

This seems to have broken again, not sure on who's end. I can see the sensor/switch trigger in Alexa OK. I can manually run the routine from Alexa. But the routines will not work triggered by these sensors/switches. This hasn't worked for a few days so don't think this is related to the CrowdStrike stuff.

So nobody is using one of these? 😕

These new type of sensor have revolutionized smart home control. Instead of the old way of setting a timer and having the lights go out, then having to wave your arms around to get the lights back on, this just works. I'm surprised by the lack of comments/asks for these to be supported? Could I make a suggestion....that UD picks one device, that has good reviews and incorporates it into the system. These devices do require extra setup. Setting areas of detection for example. Maybe this is an opportunity for UD to make their own? Someone has done this for Home Assistant The Everything Presence One - Available for Pre-order now! (everythingsmarthome.co.uk) Or am I missing something and there is already a way?

and......its working again.....This feels like what has been going one for over a week now.