Jimbo.Automates

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

It looks for devices coming back online since they can change IP address after a power outage. I don't think it hurts anything for it to always be looking for your unplugged devices, but I could add an option to turn it off but then you'll need to reserve IP address for Kasa devices.

If you still have issues, @bpwwer will have to help let us know what that error means. Sent from my Pixel 6 Pro using Tapatalk

Thanks for the log, it looks like your message id after 144 is not defined? This is causing my code to die, which I need to fix. If you have many messages to notify when a device is turned on or off, they can all share the same custom content, I'll try to create an example when I have time. Edit: Issue created: https://github.com/UniversalDevicesInc-PG3/udi-poly-notification/issues/43

Wow, that's a lot of messages! But no, there is no limit I am aware of. But you may have hit the maximum number of nodes? Dona download log package and PM it to me. I'm also curious why you need so many, you can do a lot with short custom content by embedding node or program names. Sent from my Pixel 6 Pro using Tapatalk

Awesome, glad that fixed it, and you are welcome.

Oh, that explains it. You need to do an "Upgrade Modules" to get the latest python: [admin@polisy-dev ~]$ python3 -V Python 3.9.14

Try this: sudo -u polyglot bash ./install.sh

That's odd, something must not have installed correctly, can you log into your polisy and run this? Replace the _4 with the slot number of the ELK node server: cd /var/polyglot/pg3/ns/*_4 sudo -u polyglot ./install.sh

Issue added: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/90