Jimbo.Automates

This should have been posted in the PG3 -> Elk forum, and is being discussed here: 
 

Yes. You'll need to allow UDP discovery across the network if that's possible. There are also options to manually add devices or networks in the config, although those options have not been extensively tested.

Sent from my Pixel 8 Pro using Tapatalk

Not yet. The library I reference is working on support but not released yet.

Sent from my Pixel 8 Pro using Tapatalk

Yes, it sends DON/DOF.

Sent from my Pixel 8 Pro using Tapatalk

What PG3x version are you on? Will need help from @bmercier

Sent from my Pixel 6 Pro using Tapatalk

OK, understand now.  What you want is currently not available, it was actually how it worked when I originally released, but nobody wanted it that way.  It'll take some time, but I can add that as a different light_method.
 

This looks like the PG3 issue they decided not to fix, you will need to upgraded to PG3x.
 

1. No, it is a new parameter, the existing one on the ISY Portal Service node should still exist.
2. The preference is to use groups always so if you change the name of your phone it will still work, and when you get a new phone it can be put in the group and the old one removed.  I will be adding groups to the "devices" list in the ISY Portal Service node so you can chose to use either.

Version 3.8.1 released with the fix.
 

Added https://github.com/UniversalDevicesInc-PG3/udi-poly-ecobee/issues/7
 

Thanks, no other issue I can see in the log besides what you showed
8/17/2023, 24:45:01 [pg3] error: createNS: Error: udx: /rest/pg3.install.ns returned error status 500 at call_udx (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/udx.js:70:15) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Object.UDXdeploy (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/udx.js:128:3) at async Object.createNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/nodeservers.js:450:7) Probably best to upgrade modules so you are on the latest PG3x and try again, unless @bmercier has another suggestion?

Kasa devices sometimes don't respond initially, the NS does try to discover devices on each long poll so they may eventually show up. I can try increasing the timeout while looking for devices if possible.

Device status is only updated on short poll, Kasa doesn't allow immediate updates. Remember we are using an undocumented API.

Some new devices use a new method which is not currently supported, not sure if yours is one of them.


Sent from my Pixel 6 Pro using Tapatalk

Yes open your area node and set armed status. You can create a favorite to armed status to make it easier.



Sent from my Pixel 6 Pro using Tapatalk

You are testing Control, not Status in your program? Status always changes, but control is handl with send on/off for.

Sent from my Pixel 6 Pro using Tapatalk

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

It's in the Polisy/eisy version uom 131
https://wiki.universal-devices.com/index.php?title=Polisy_Developers:ISY:API:Appendix:Units_of_Measure

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?