Jimbo.Automates

Issue created, will try to take a look https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/95 Sent from my Pixel 6 Pro using Tapatalk

Based on or PM discussion I created a 2 bug reports https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/14 https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/15 I will get to it when I have time and higher priority issues with other node servers are resolved.

Great, thanks. If wireless tags are important you should monitor the connection state and the heartbeat. Sent from my Pixel 6 Pro using Tapatalk

Thanks, this is something that @bpwwer will need to review. Sent from my Pixel 6 Pro using Tapatalk

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

Set log to debug, press restart, and if problem persists download log package and PM to me. Sent from my Pixel 6 Pro using Tapatalk

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

Set Log Level to Debug, restart node server, download log package and PM that to me.

Any errors in the node in log? There is a migration from pg2 documented in https://github.com/UniversalDevicesInc-PG3/udi-poly-hue-emu/blob/master/README.md The old default hue port of 8080 doesn't work in Polisy so you have to change to something else like 8081 https://github.com/UniversalDevicesInc-PG3/udi-poly-hue-emu/blob/master/POLYGLOT_CONFIG.md Sent from my Pixel 6 Pro using Tapatalk

Sorry, can you change the node server log level to debug, restart wait of couple minutes then download another log package? It's best to just PM it to me and not post on the forum.

Yes, but does the Honeywell NS use a discovery to find thermostats or are they manually entered? There was/is a problem with the way an IP address is defined on eisy when using WiFi which causes problems for some NS like this one. Please download log package and PM it to me and also let me know the IP address of one Kasa device. Sent from my Pixel 6 Pro using Tapatalk

Ok, thanks for the clarification. Totally understand. There's no way to tell who is arming thru ISY be it AC, UD Mobile or program all look the same. I can tell if it comes from the ELk and can give those details when I'm at a computer if you really need to know. Sent from my SM-X808U using Tapatalk

Thanks, I got your PM and I'll look thru it. But, I'm still confused. Previously you mention the NS log doesn't show anything, when running commands from the AC but in the statement above it seems to say that you do see activity?

Is your eisy using only a wired Ethernet connection? And is it on the same LAN? Some have segmented their lan which causes discover to fail. Sent from my Pixel 6 Pro using Tapatalk

You shouldn't have to reboot, usually just closing and reopen the AC will fix it. Sent from my Pixel 6 Pro using Tapatalk

I don't see any info about UD Mobile when migrating from Polisy -> esiy in https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration What are the steps required to switch all existing Favorites and not loosing them?

Sorry but this does not show the PG3 log that we asked for, that is viewed from the "Log" button in the upper-right of the PG3 UI. Please do it again and "Download Log Package" which will grab both the NS and PG3 logs. Also, don't post them, please PM them to Bob and I. The first set armed status in the log you sent is at 12:02 for disarm, then 12:03 stay instant, then 12:29 to stay instant, then quickly disarmed, then disarmed at 1:39, stay instant at 6:07 then disarmed, night instant at 6:43 and disarmed all by user number 1. All of these looked to succeed as far as I can tell. Also, I'm confused because earlier you had said when you push the "Set Armed Status" that nothing shows up in the node server log, but now you are saying messages do show up in the log? If the messages are properly showing up in the Node Server log when you press set armed status, then please set log to Debug+Modules so I can see the interaction with the ELK. Also, do different armed status from the AC and UD Mobile and let me know which is which. As for the "eisy" way comment, remember this is a brand new system, I'm sure when you started using ISY & ELK together that was a much more mature environment.

Go to edit system and set up your local connection settings. Sent from my Pixel 6 Pro using Tapatalk

Yes, good idea Bob. @SLiss please check the PG3 log, not the node server log. But it still baffles me that it works from UD Mobile. Sent from my Pixel 6 Pro using Tapatalk

Open the node server configuration in the AC and check the IP address. I think on eisy it should be 127.0.0.1 ? Sent from my Pixel 6 Pro using Tapatalk

Does changing the chime mode work from the AC? Sent from my Pixel 6 Pro using Tapatalk

If it's true and node server is restarted it should change the name. If your log was in debug mode you can download log package and PM that to me and mention what time a restart was done that didn't change a name, and what names were involved. Sent from my Pixel 6 Pro using Tapatalk

Is the change node names configuration option set to true? Sent from my SM-X808U using Tapatalk

It's been discussed but not implemented yet. Was actually pondering it this morning and have some ideas. It's a big effort... But also need to move my home from polisy to eisy. Discussion and link to issue here; /topic/38897-how-to-import-devices-into-elrp-using-a-node-server Sent from my Pixel 6 Pro using Tapatalk

@bpwwer any idea what could be wrong? Command works through UD Mobile but not the AC. Sent from my Pixel 6 Pro using Tapatalk