Jimbo.Automates

Something else must be using port 8081? What other node servers or programs do you have running on your Polisy? You can change it to something else, like 8082 and restart the node server.

There should be a button that says reinstall in slot #. Where # is the current slot. If not, then you are on a pretty old version of PG3. Sent from my Pixel 6 Pro using Tapatalk

The nodes were deleted because you uninstalled the node server. That always deletes the nodes in PG3 and the ISY. Sent from my Pixel 6 Pro using Tapatalk

This is a bug in PG3 where it doesn't properly recognize a new version of a node server that was previously released with a very old version of PG3. But, do not delete and reinstall. You can reinstall in the same slot from the store or purchases page. Sent from my Pixel 6 Pro using Tapatalk

Yes, you will have to use the "Turn on For" inside UDI Mobile. But, if everyone using the ELK would like that to be the default On action, I could be convinced to change it or make it an option.

PG3 Airthings Consumer node server 1.0.1 released.

Do not uninstall then install again, you can re-install in the same slot from the node server store, or by going to the purchases tab. Sorry Bob did not make that clear enough.

Version 1.0.1 released to force an upgrade of the udi_interface which was out of date on your system.

Are there any errors in the node server log? Sent from my Pixel 6 Pro using Tapatalk

Sorry, I see the exception now, missed that. I'll review your log and see if I can get it fixed tonight. Sent from my Pixel 6 Pro using Tapatalk

Sorry, you shouldn't have uninstalled, just reinstall in the same slot due to the pg3 issue. Do the nodes not show up in the ISY? Sent from my Pixel 6 Pro using Tapatalk

Fixed this and most other issues:

PG3 Airthings Consumer node server 1.2.6 See the README and Release Notes I've resolved all current issues that I plan to work on, or can fix are done. if you have an issue that is not listed please add it, or let me know.

@bpwwer Did you figure out if this was your fault? The log shows the name was added properly? 2022-12-01 08:58:20,380 Thread-11 udi_interface.interface INFO interface:addNode: Adding node wave 103(s_2930133779) [None] 2022-12-01 08:58:20,381 Thread-11 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 's_2930133779', 'name': 'wave 103', 'nodeDefId': 'Sensor', 'primaryNode': 'controller', 'drivers': [{'driver': 'ST', 'value': 0, 'uom': 2}, {'driver': 'CLITEMP', 'value': 0, 'uom': 4}, {'driver': 'CLIHUM', 'value': 0, 'uom': 22}, {'driver': 'CO2LVL', 'value': 0, 'uom': 54}, {'driver': 'BARPRES', 'value': 0, 'uom': 56}, {'driver': 'GV1', 'value': 0, 'uom': 56}, {'driver': 'GV2', 'value': 0, 'uom': 56}, {'driver': 'GV3', 'value': 0, 'uom': 56}, {'driver': 'GV4', 'value': 0, 'uom': 56}, {'driver': 'VOCLVL', 'value': 0, 'uom': 96}, {'driver': 'BATLVL', 'value': 0, 'uom': 51}], 'hint': [0, 0, 0, 0], 'private': None}]} 2022-12-01 08:58:20,433 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-12-01 08:58:20,435 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-12-01 08:58:20,438 Thread-16 udi_interface DEBUG Sensor:handler_start: enter 2022-12-01 08:58:20,439 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '7f8900b2-e0bb-4a1a-80ab-d6d0d5fa76da', 'uuid': '00:21:b9:02:55:cd', 'profileNum': 1, 'address': 's_2930133445', 'name': 'wave 202', 'nodeDefId': 'Sensor', 'nls': None, 'hint': '0x00000000', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1662147489313, 'timeModified': 1669588388787, 'dbVersion': 1} 20

There was a long discussion here: https://forum.universal-devices.com/topic/38897-how-to-import-devices-into-elrp-using-a-node-server/#comment-350498 and the issue exists here: https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/67 No direct resolution yet.

Sorry, after fixing permissions, guess I had a typo in my password...

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.