undefined node

[johnnyt]

I restarted what is a 2nd instance of the this NS (with separate API as first instance) after several weeks of not using it. One of the airthings device that was fine before, was labeled as "undefined" instead of the name I gave it in Airthings. The data seems to be coming through to ISY okay and I was able to rename it on ISY side but it's stuck as 'undefined' in NS. 

 

 

I tried deleting it on ISY side to see if the process of re-adding it would clean things up. It appeared to go through a process that I thought would have re-added it but without doing so. It then sent data to the node even though it no longer exists on ISY

2022-11-28 09:01:52,847 Thread-339 udi_interface      INFO     Controller:shortPoll: enter
2022-11-28 09:01:52,849 Thread-339 udi_interface      INFO     Controller:_query_all: enter
2022-11-28 09:01:52,849 Thread-339 udi_interface      INFO     Sensor:shortPoll: enter
2022-11-28 09:01:52,850 Thread-339 udi_interface      INFO     Sensor:query: enter
2022-11-28 09:01:53,806 Thread-339 udi_interface      INFO     Sensor:query: exit
2022-11-28 09:01:53,807 Thread-339 udi_interface      INFO     Sensor:shortPoll: exit
2022-11-28 09:01:53,808 Thread-339 udi_interface      INFO     Sensor:shortPoll: enter
2022-11-28 09:01:53,809 Thread-339 udi_interface      INFO     Sensor:query: enter
2022-11-28 09:01:54,168 Thread-339 udi_interface      INFO     Sensor:query: exit
2022-11-28 09:01:54,169 Thread-339 udi_interface      INFO     Sensor:shortPoll: exit
2022-11-28 09:01:54,170 Thread-339 udi_interface      INFO     Sensor:shortPoll: enter
2022-11-28 09:01:54,171 Thread-339 udi_interface      INFO     Sensor:query: enter
2022-11-28 09:01:54,449 Thread-339 udi_interface      INFO     Sensor:query: exit
2022-11-28 09:01:54,450 Thread-339 udi_interface      INFO     Sensor:shortPoll: exit
2022-11-28 09:01:54,451 Thread-339 udi_interface      INFO     Sensor:shortPoll: enter
2022-11-28 09:01:54,452 Thread-339 udi_interface      INFO     Sensor:query: enter
2022-11-28 09:01:54,789 Thread-339 udi_interface      INFO     Sensor:query: exit
2022-11-28 09:01:54,790 Thread-339 udi_interface      INFO     Sensor:shortPoll: exit
2022-11-28 09:01:54,791 Thread-339 udi_interface      INFO     Sensor:shortPoll: enter
2022-11-28 09:01:54,792 Thread-339 udi_interface      INFO     Sensor:query: enter
2022-11-28 09:01:55,217 Thread-339 udi_interface      INFO     Sensor:query: exit
2022-11-28 09:01:55,219 Thread-339 udi_interface      INFO     Sensor:shortPoll: exit
2022-11-28 09:01:55,219 Thread-339 udi_interface      INFO     Controller:_query_all: exit
2022-11-28 09:01:55,220 Thread-339 udi_interface      INFO     Controller:shortPoll: exit

2022-11-28 09:02:01,537 MQTT       udi_interface.interface INFO     interface:_message: Successfully set s_2930133779 :: CO2LVL to 501.0 UOM 54
2022-11-28 09:02:01,578 MQTT       udi_interface.interface INFO     interface:_message: Successfully set s_2930133779 :: BARPRES to 998.4 UOM 56
2022-11-28 09:02:01,580 MQTT       udi_interface.interface INFO     interface:_message: Successfully set s_2930133779 :: GV3 to -37 UOM 56
2022-11-28 09:02:01,582 MQTT       udi_interface.interface INFO     interface:_message: Successfully set s_2930133779 :: CLITEMP to 22.7 UOM 4
2022-11-28 09:02:01,584 MQTT       udi_interface.interface INFO     interface:_message: Successfully set s_2930133779 :: GV2 to 1669644043 UOM 56
2022-11-28 09:02:01,620 MQTT       udi_interface.interface INFO     interface:_message: Successfully set s_2930133779 :: GV4 to 125.0 UOM 56

I restarted the NS and that resulted in recreation of the device in ISY as "undefined"

Seems like a bug that the NS isn't using the device name that I gave it in Airthings in first place, and then isn't self correcting, though maybe the latter is more of a feature than a bug assuming this doesn't stem from an Airthings device defect - is there a way to tell? It looks fine on my Airthings Dashboard:

I haven't tried unpairing device from hub then re-pairing it. I may do that later as another potential workaround. For now I've just renamed it in ISY

 

[Jimbo.Automates]

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

[bpwwer]

That's probably my fault.  I added some code to PG3 to try and make sure the name matched in the PG3 database and the ISY and that may be doing some unexpected things.

I also made some changes to the addnode function to give it the ability to rename nodes so I'd like to see the PG3 log entries for the time period when you deleted the node from the ISY and had the node server re-create it.

[Jimbo.Automates]

@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

 

[bpwwer]

Should be fixed in PG3 3.1.16