Jimbo.Automates

This is fixed in 3.6.9

Sent from my Pixel 6 Pro using Tapatalk

It's mentioned in the release announcement.

Due to the issue mentioned in the first paragraph, you will get this message in the PG3 UI.
This version of PG3 3.1.31 will not work properly with Pushover or UDPortal nodes, Please upgrade modules and restart PG3. tisyVersion=5.6.2 isPG3x=True pg3Version=3.1.31
This is because the new version of PG3/PG3x is not out yet, hopefully soon.

Sent from my Pixel 6 Pro using Tapatalk

Yes, that's usually the ST driver ${sys.node.#.ST}
https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables
 
 

For that node server, the humidity is likely in the CLIHUM driver.  So you can add ${sys.node.node_address.CLIHUM} where node_address is n002_ followed by the "Address" shown in the the PG3 UI screenshot you posted.
 

That's perfect!  Didn't realize the Polisy would need a reboot.  Good to know.
When the actual node triggers the program the # will be replaced with the actual node.  But now I realize we should probably change the subject to include the node name that triggered it.
${sys.program.#.name} ${sys.node.#.name}  

Just disable the program so it can't run automatically.

But personally I'd just have UDMobile set a variable and add that to your if conditions because you may want to know that for other programs as well.

Sent from my Pixel 6 Pro using Tapatalk

You did nothing wrong. I did. But this will not affect anything. I'll fix it in the next release.

Sent from my Pixel 6 Pro using Tapatalk

I see in the log it sets GV9 which is animal -> squirrel to zero:
2023-05-04 10:05:53,667 Thread-14 udi_interface.node DEBUG node:setDriver: 01_003_animal:Deck animal Reporting set GV9 to 0 to Polyglot 2023-05-04 10:05:53,667 Thread-14 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2023-05-04 10:05:53,667 Thread-14 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': '01_003_animal', 'driver': 'GV9', 'value': '0', 'uom': 2}]} 2023-05-04 10:05:53,667 Thread-14 udi_interface DEBUG BaseNode:set_driver: 01_003_animal:Deck animal set_driver(GV9,0) Then sets GV10 which is animal -> unknown animal to one:
2023-05-04 10:05:53,668 Thread-14 udi_interface.node DEBUG node:setDriver: 01_003_animal:Deck animal Reporting set GV10 to 1 to Polyglot 2023-05-04 10:05:53,668 Thread-14 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2023-05-04 10:05:53,668 Thread-14 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': '01_003_animal', 'driver': 'GV10', 'value': '1', 'uom': 2}]} 2023-05-04 10:05:53,668 Thread-14 udi_interface DEBUG BaseNode:set_driver: 01_003_animal:Deck animal set_driver(GV10,1) There is a bug in ISY which I reported a long time ago when using Control and a node sends 0 (False) it still triggers a program that is looking for 1 (True).  @Chris Jahn acknowledged the bug but it hasn't made it to the top of his list yet.

Sorry, I should add this to the instructions: Please open https://local.home.camect.com/ in browser, sign in as admin and accept TOS before you proceed.
 

There is no way to automate restarting a Node Server.
Did the controller "Node Server Online" still show Connected?
 
 

For Polsiy & esiy set:
hue_port 8081
isy_port: 8080
and restart the node server.

Please update to the latest PG3, reinstall in the same slot and try again.

Sent from my SM-X808U using Tapatalk

That's a PG3 bug.  Go to "Node Server Store" , Select ELK, Select "Install" of the Perpetual version.  This will show in option "ELK is already installed in slot x, Reinstall here?".   To be safe, I'd backup PG3 first, but I've not heard of this causing any issues.
 

Please update to 3.5.8 and let me know if that helps.  I'm not home so I can't confirm.
 

It's a PG3 bug. Please reinstall in the same slot. Don't delete and install, choose the reinstall option. Sorry, not at a computer to give the exact procedure...

Sent from my Pixel 6 Pro using Tapatalk

Update to latest PG3 should resolve this.

Sent from my SM-X808U using Tapatalk

I had initially enabled WiFi, but switched to Ethernet and kept having problems.  I just reset networking with the 4 button pushes described in the user guide and it seems better so far.  https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Reset_Networking

Something else must be using port 8081?  What other node servers or programs do you have running on your Polisy?
You can change it to something else, like 8082 and restart the node server.
 

Yes that's the correct link, thanks for checking. If you order after clicking the link it will be credited.

Sent from my Pixel 6 Pro using Tapatalk

The doc: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/blob/master/README.md#zone-node
Shows Logical Status driver:ST
If it's still showing the raw value try rebooting the ISY.   It returns the correct for output because that uses a standard On/Off so a reboot is not required.
 

This is a bug in PG3 where it doesn't properly recognize a new version of a node server that was previously released with a very old version of PG3.

But, do not delete and reinstall. You can reinstall in the same slot from the store or purchases page.

Sent from my Pixel 6 Pro using Tapatalk

The nodes were deleted because you uninstalled the node server. That always deletes the nodes in PG3 and the ISY.

Sent from my Pixel 6 Pro using Tapatalk

Version 1.0.1 released to force an upgrade of the udi_interface which was out of date on your system.
 

It is released to beta @brians 
 

It pulls the name from what you define in the Kasa app when adding a new device, for existing devices if you want them to change to reflect a name in the Kasa app then set the change_node_names to true which I announced in the last release https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/blob/master/README.md#configuration-parameters
Then restart the node server.