Jimbo.Automates

Easiest way is with using a Simple shareable notifications where you use 
${sys.node.#.name} ${sys.node.#.GV0}
For Physical Status, or this for Logical Status
${sys.node.#.name} ${sys.node.#.ST}
 

I had and HS107 and HS300 I wasn't using anymore, so plugged them in and they work as expected.
@dbwarner5 When you deleted them, did you delete them in the PG3 UI by selecting the X to the right of the device in the nodes page?  I did this with mine to confirm they add back and it also worked as expected, but after deleting them all you should restart the plugin.
 

Yes, that is a ELK limitation.  I guess I could have the plugin do a Disarm if armed when you Arm...
I created an issue https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/109
 

Yes, it's an issue on their side
https://groups.google.com/u/2/g/wireless-sensor-tags

Sent from my Pixel 8 Pro using Tapatalk

Yes, works fine for me.  'Home' is my 'Area 1'.

There have been issues with Python installs during the updates. Please submit a support ticket and they'll get you fixed. I've not seen anyone with this issue post the solution and previously @Michel Kohanim just mentioned it was a Python install issue.

Sent from my Pixel 8 Pro using Tapatalk

Sorry, Kasa scenes are not supported at this time.

Sent from my Pixel 8 Pro using Tapatalk

Likely just a temporary Internet connection issue, or their service is flooded and not responding. If it happens frequently please report to their mailing list or create a support ticket. Lately they have become horrible at responding to support tickets, but did respond to the mailing list.

Sent from my Pixel 8 Pro using Tapatalk

It will look something like this:

Great, thanks. I'll get on it but no promises on schedule.

Sent from my Pixel 8 Pro using Tapatalk

Fixed in 3.1.1, that was the only change.

Need a program for each
if s_zone1Duration <= 0 or s_zone1Duration > 0 then s_zone1Duration (init) = s_zone1Duration  This will run anytime the variable changes and updates it's init value.
 

You should post in the sub-forum for the specific plugin in question: https://forum.universal-devices.com/forum/316-notification/
Why do you have notification node server installed in 2 slots?  Delete the one in slot 2.  But if you really want it for some reason installed twice, you'll have to change the "rest_port" to a different number in the PG3 UI for slot 2.
 

Did you close and restart the Admin Console after installing the Notifications plugin?
 

Sorry, no.  Make the key a short <= 8 character unique name which will be used as the node address.  The instruction says:
So make the Value: { "name": "HarmonyHub RomName", "host": "192.168.58.16" }
Including the curly braces and all..  I could spend time to make this a better way, but it's so rarely used it hasn't been worth the effort.
 

Sorry, not possible, they won't send it:
https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/18
 

3.1 released with this added, please confirm since I don't have a water meter that can use Flume anymore.
 

Your first example should work perfectly. This is simple example I previously posted of a program on IoX to lock the locks when the Elk is armed or disarmed.  The node "Home" is my main area.


Lock Example - [iD 01F7][Parent 020F][Enabled]
If
        'Alarm-Elk / Home' Armed Status is Disarmed
Then
        Set 'Locks / Garage Door Inside Lock' Unlock
Else
        Set 'Locks / Garage Door Inside Lock' Lock



Sent from my Pixel 8 Pro using Tapatalk

Looks like you are on a polisy with PG3? You'll need to upgrade to PG3x, this is a known bug in PG3. Search the wiki for more info on upgrading.

Sent from my Pixel 8 Pro using Tapatalk

That would explain it, I'll try to get a new release soon to fix it, issue 103 created.

Looks like you are still on PG3 not PG3x.  This is a know issue with PG3 on Polisy where files are not properly created during an install.  The issue was never resolved since it no longer happens with PG3x.
See "Upgrading to PG3x" at https://wiki.universal-devices.com/Polisy:User_Guide
 

@skunkiechris Release 3.0.9 has an attempt to fix this, please update and let me know if you see it again.
 

Looks like I never upgraded telegram to use the new method, it still uses the old method where you set the custom message on the controller then send it from the service node. I'll try to add the new method soon.

Yes, this is the same issue reported and fixed in the other thread. Sorry I misspoke upgrade vs. update. But good you figured it out.

ModuleNotFoundError: No module named 'kasa'

Sent from my Pixel 8 Pro using Tapatalk

No worries.  For others info the problem was solved in another thread.  https://forum.universal-devices.com/topic/42457-elk-m1-with-eisy-and-alexa-voice-control/#comment-375488