Jimbo.Automates

I had this issue now after moving to a new phone and restoring backup. But even after giving permission the test never says success? Sent from my Pixel 6 Pro using Tapatalk

Download the log package and PM to me, I'll try to take a look when I'm home later this week. But just renaming in the ISY is fine for now. Sent from my Pixel 6 Pro using Tapatalk

Seeing the same on one of mine that I upgraded. Sent from my Pixel 6 Pro using Tapatalk

Our replies overlapped, I didn't see your latest one while I was replying. It should handle bad characters in the name like # which should be removed. Sent from my Pixel 6 Pro using Tapatalk

Any warning or error in the NS log? If not, set log to debug, restart and after a couple minutes download log package and send to me with the node names that should have changed. Sent from my Pixel 6 Pro using Tapatalk

The Polyglot Version 3 Node Server for Kasa TP-Link Version 3.0.16 is released with a couple small bug fixes, see the Release Notes.

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.

Zero is False, One is True. I'll add that to the list of bugs, https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/16 Sent from my Pixel 6 Pro using Tapatalk

I added info about the server status, hopefully this clears it up: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/blob/main/README.md#controller Sorry, I can't really have a timeline, it all depends on my real job, and what is going in in my life. I try to keep up on enhancements as much as I can. Typically I will work on those node servers which are used by more users, and sadly Airthings has the least number of users, so I never get to it, but that doesn't mean it will never happen. But with 12 node servers in production I get a lot of requests. But, that being said, a crash is always highest priority, so that will make it this a priority, and when I start working on one, I like to clean up as many issues as possible while I'm in it.

That shouldn't have happened if you manually killed the process.

Thanks for the report @johnnyt, Issue added: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/15 The NS received a HTTP 403 "Forbidden" error from the Airthings server and was trying to print the error message, which didn't look like it typically does. Will need to fix the code to handle this case.

Did you watch the log while restarting? You will see it get stopped if it was running, and then after a while, possibly a couple minutes depending on what needs upgrading, it will show that it is starting. Also, it looks like there is a bug, if you press restart while a restart is still in progress you will end up with an orphaned Node server. Bob is looking into it. That was part of your problem. Sent from my Pixel 6 Pro using Tapatalk

Thanks @bpwwer ! I didn't notice the date. And @macjeff Please don't always resort to "reinstall", that should rarely be needed, and when you do that it makes debugging the original issue more difficult.

@Michel Kohanim We need a way for the user to tell the NS which devices they want to export. Without the ELK Module in IoP how can we do that? I can have them manually type in the device addresses into the PG3 UI but that is very painful. Would be easier to tag devices somehow in the Admin Console.

You can't kill the grep that command is done. But that does look fine, I expected to see 2 kasa-poly.py lines. Can you "kill 4728" then try to start the NS and watch the log for errors?

For some reason the PG3 MQTT connection is failing, I asked @bpwwer for help 2022-11-16 06:30:19,320 MQTT udi_interface.interface ERROR interface:_connect: MQTT Failed to connect, invalid identifier It's possible there are two copies running, log into your Polisy and run: ps -uax | grep kasa You should only see one kasa line like this: polyglot 90285 0.0 1.2 107180 51788 - I 06:16 0:09.53 python3 ./kasa-poly.py (python3.9) If you see more, then run "kill n" for each, where n is the process Id from second column.

The Polyglot Version 3 Node Server for Kasa TP-Link Version 3.0.14 is released, see the Release Notes. You can now have the node server rename nodes to match what they are called in the Kasa app https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/issues/10 see doc https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/blob/master/README.md#change_node_names

This has nothing to do with ELK node server, it's part of the Notification node server. But, this is an admin console issue, nothing I can do about it. We will need @Chris Jahn or @Michel Kohanim to fix that. IN the meantime, make those long names shorter

Could be a bug in latest version, as always, check the PG3 NS log for errors, and send them to me in a PM, or Download Log Package and PM that to me.

Looks good now. I hadn't announced this version yet since I am testing on my production system and wanted to make sure there were no issues first.

Thanks for the log, this means there was an, but it's not being cleared. Issue entered: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/91

Check the PG3 UI for an error. Download log package and PM it to me. Sent from my Pixel 6 Pro using Tapatalk

As mentioned in the GitHub issue I previously posted, there is no easy way for the node server to know what devices you want to import into the ELK. So I'm stuck until @Michel Kohanim or @Chris Jahn can offer suggestions, Sent from my Pixel 6 Pro using Tapatalk

Yes, this ability was only recently added to the PG3 API and I've been adding it to my node servers as I have time. I've created an issue for this one: https://github.com/UniversalDevicesInc-PG3/udi-poly-Airthings-Consumer/issues/14 It's not a problem to just rename them in the ISY.

There is a tiny little box to the right which you can click on to delete the custom data item, we need @bpwwer to fix PG3 so it shows an X icon there. Glad you figured it out, I have updated the documentation to show sending custom content with the "Send Sys Short with Params" method: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/blob/master/README.md#custom-content-example