Jimbo.Automates

I don't understand what this has to do with the Notification node server, it has nothing to do with location services. What location services method are you using? UD Mobile or ?

Do you have the Harmony Hub IP address reserved so it doesn't change? Please restart the nodeserver and it should find the correct one, and reserve it in your router so it doesn't change.

Please download log package and PM it to me. Sent from my Pixel 6 Pro using Tapatalk

If it has shown disconnected or failed then please download log package and PM it to me. Not sure why it would not work in a scene it's very reliable for me. Put log in debug + modules mode activate the scene a couple times and download log package and PM it to me and mention what device is not working. Sent from my Pixel 6 Pro using Tapatalk

Please download log package and PM it to me. Sent from my Pixel 6 Pro using Tapatalk

Ok, that is odd. Shouldn't be necessary but glad it's all good. Sent from my Pixel 6 Pro using Tapatalk

Oh that's good! A full reboot of eisy/polisy, PG3 or the node server?

Looks like it doesn't know what type of device that is, it should show the device type next to where it shows n006_xxx - Check the node server log for ERROR and WARNING. The next enhancement I'd like to work on is making errors show up as notices on the PG3 UI, just ran out of time to do that.

@Chris McKean, @mjrush, my bad. You actually have the 3.1.0 but it just displays the wrong version. Re-install in the same slot and it will now show the correct version.

Fixed in 3.1.0

The Polyglot Version 3 Node Server for Kasa TP-Link 3.1.4 is released. See the Release Notes for all information. IMPORTANT: You must have the latest updates released 12/03/2023 for this to install. If you are not sure, please 'Update Modules' and reboot when complete before installing. Thanks to @Michel Kohanim for the fixes.

I have 60 disabled programs so going thru and finding them all is very painful. I just upgraded to 5.7.0 last night and all programs were disabled, so I restored my previous backup.

Unless I'm remembering wrong, the problem was the version of PG3 didn't support it. But it should all be working now. I'll try to confirm this weekend. Sent from my Pixel 6 Pro using Tapatalk

There's a configuration param change_node_names set it to true and restart the node server. Sent from my Pixel 6 Pro using Tapatalk

Sorry, which node server? Sent from my Pixel 6 Pro using Tapatalk

Anyone using ELK Thermostats able to test this?

This is a PG3 issue, not sure what it means. Will need help from @bmercier or @Michel Kohanim Sent from my Pixel 6 Pro using Tapatalk

Thanks for the post. I also had this issue yesterday with Windows 11 Pro. I finally uninstalled from windows add/remove programs, rebooted and installed with their off line installer. Very annoying. I submitted a support ticket with all the Java console errors, hopefully @Chris can make sense of it all.

I have uploaded ELK Node Server 3.10.0 to the beta store with Thermostat support. Please install in a new slot and test. I don't have a real thermostat connected to my ELK so I can't test a real one, but I was able to simulate it and all seems to be working. One thing I don't know is if ELK sends updates when temperature changes, or if it must be polled. Please give it a try and let me know on this thread if you have issues. If you see an ERROR, please download log package and PM or email it to me.

@DennisC & @MMAltair, key press events are now working in 3.9.0

ELK NS 3.9.0 released:

The Polyglot Version 3 Node server for ELK Security Version 3.9.0 is released. See the Release Notes Working on new documentation at ELK Node Server If you have issues or requests please check PG3 ELK Github issues to see it has already been listed. And if you want to thumbs up an issue I will try to prioritize fixing the ones with most votes.

Yes, it is on the list Issue 50 hopefully I can find the spare time to work on this soon.

You can detect function key presses with status But there are known issues with this implementation since without control events you can not see multiple presses of the same key. Some issues are documented in Issue 69 I will try to look into this and other more requested fixes and enhancements soon

What PG3x version are you on? Will need help from @bmercier Sent from my Pixel 6 Pro using Tapatalk