TJF1960

Hi @DennisC, I have read the this thread. My major concern is that I hadn't seen anyone mention getting the "wrong part" listed in the console. I don't want to upgrade and take a chance of being in the same boat as Larry above. Also, I don't know what the time frame is for the early units that was referred to? I think I bought mine in the first half of last year.

I was getting ready to update from 5.4.0 but ran "sudo cat /var/udx/logs/log | grep bios" first. I am wondering if anyone else's came up with "wrong part?" I am a little worried about whether I should upgrade or not. [admin@polisy ~]$ sudo cat /var/udx/logs/log | grep bios Password: Sat Feb 19 08:51:51 PST 2022: bios mfr: Sat Feb 19 08:51:51 PST 2022: bios product: Sat Feb 19 08:51:51 PST 2022: bios has wrong mfr/product Sat Feb 19 09:05:24 PST 2022: bios mfr: Sat Feb 19 09:05:24 PST 2022: bios product: Sat Feb 19 09:05:24 PST 2022: bios has wrong mfr/product Sat Feb 19 11:20:10 PST 2022: bios mfr: Sat Feb 19 11:20:10 PST 2022: bios product: Sat Feb 19 11:20:10 PST 2022: bios has wrong mfr/product Sun Feb 27 06:54:52 PST 2022: bios mfr: Sun Feb 27 06:54:52 PST 2022: bios product: Sun Feb 27 06:54:52 PST 2022: bios has wrong mfr/product Sun Feb 27 16:03:24 PST 2022: bios mfr: Sun Feb 27 16:03:24 PST 2022: bios product: Sun Feb 27 16:03:24 PST 2022: bios has wrong mfr/product Sun Mar 6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Sun Mar 6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Sun Mar 6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0 Sun Mar 6 06:02:35 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded Sun Mar 6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Sun Mar 6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Sun Mar 6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0 Sun Mar 6 06:04:04 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded Sun Mar 6 06:42:27 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices Sun Mar 6 06:42:27 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy Sun Mar 6 06:42:27 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.0.0 Sun Mar 6 06:42:26 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios version 100 is old and needs to be upgraded [admin@polisy ~]$

Thank you for the quick response. I will stop messing with it. Tim

Hi @simplextech, Updated Polisy per Michel's last post via ssh. IoP on v5.4.0, PG3 on v3.0.41. After all rebooted and functioning normally I noticed ST-Inventory not connected. Version installed was 1.0.2, I stopped and started the node a number of times. Never would connect. I noticed you rolled out a new version this morning. But during restarts it was not updating. So I deleted the node and tried to reinstall in the same slot. It will not install. I tried installing in 2 other free slots, same results. Thank you, Tim 3/6/2022, 07:17:42 [pg3] debug: Stopping log stream for pg3frontend_YJPSY 3/6/2022, 07:17:55 [pg3] debug: Getting status for MyQ 00:0d:b9:59:39:b0 3cac3bad-92bb-40f4-966f-3b541e85c898 3/6/2022, 07:17:55 [pg3] info: [00:0d:b9:59:39:b0_10] tplkasactl reporting command DON 3/6/2022, 07:17:55 [pg3] debug: Scheduling http://localhost:8080/rest/ns/10/nodes/n010_tplkasactl/report/cmd/DON to group commandGroup 3/6/2022, 07:17:55 [pg3] debug: ISY Response: [Try: 1] [00:0d:b9:59:39:b0] :: [200] :: 7.062209ms - http://localhost:8080/rest/ns/10/nodes/n010_tplkasactl/report/cmd/DON 3/6/2022, 07:17:55 [pg3] debug: MQTT Results: [ns/command/00:0d:b9:59:39:b0,10] :: {"command":[{"address":"tplkasactl","success":true}]} 3/6/2022, 07:17:55 [pg3] debug: Scheduling http://localhost:8080/rest/ns/6/nodes/n006_cg085008f7c6/report/status/GV0/7397/58 to group statusGroup 3/6/2022, 07:17:55 [pg3] debug: ISY Response: [Try: 1] [00:0d:b9:59:39:b0] :: [200] :: 5.460989ms - http://localhost:8080/rest/ns/6/nodes/n006_cg085008f7c6/report/status/GV0/7397/58 3/6/2022, 07:17:55 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '6', 'cg085008f7c6', 'GV0') 3/6/2022, 07:17:55 [pg3] debug: UPDATE driver SET value = '7397',uom = '58',timeModified = 1646579875814 WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '6', 'cg085008f7c6', 'GV0') 3/6/2022, 07:17:55 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '6', 'cg085008f7c6', 'GV0') 3/6/2022, 07:17:55 [pg3] debug: MQTT Results: [ns/status/00:0d:b9:59:39:b0,6] :: {"set":[{"address":"cg085008f7c6","driver":"GV0","value":"7397","uom":58}]} 3/6/2022, 07:17:55 [pg3] debug: Found info {"found":true,"isActive":true,"isInstalled":true,"expiry":"2023-02-06T03:16:34.000Z"} 3/6/2022, 07:17:55 [pg3] info: set to expire on 2023-02-06T03:16:34.000Z 3/6/2022, 07:18:03 [pg3] debug: ########## {"docs":"https://github.com/simplextech/pg3_docs/tree/main/ST-Inventory","version":"1.0.4","status":"active","oauth":"","prem":true,"url":"https://pg3store.isy.io/v2/nodeservers/production/pg3_inventory.zip","name":"ST-Inventory","language":"node","nsdata":"","desc":"Inventory of ISY nodes. Includes Insteon, Z-Wave, Scenes, Programs, Folders, Int and State Variables and Error log lines.","developer":"jeubanks@simplextech.net","ip_added":"107.77.204.108","purchaseOptions":[{"price":20,"isPerpetual":true}],"branch":"","uuid":"00:0d:b9:59:39:b0","ts_added":"1644790722","ts_updated":"1646539323","author":"Simplex Technology","price":20,"modified":"2022-03-06 04:02","profileNum":"17","nsid":"c126923a-afcd-4e6d-9e46-58576796f551","expires":0} 3/6/2022, 07:18:03 [pg3] info: [00:0d:b9:59:39:b0_17] :: Creating Nodeserver 'ST-Inventory' 3/6/2022, 07:18:04 [pg3] error: unhandledRejection REPORT THIS!: [object Promise], reason: Error: Request failed with status code 404 3/6/2022, 07:18:07 [pg3] debug: Sending logfile to frontend :: /var/polyglot/pg3/logs/pg3-current.log 3/6/2022, 07:18:16 [pg3] debug: Starting log stream for pg3frontend_YJPSY :: /var/polyglot/pg3/logs/pg3-current.log 3/6/2022, 07:18:25 [pg3] debug: Scheduling http://localhost:8080/rest/ns/2/nodes/n002_controller/report/status/GV1/18/0 to group statusGroup 3/6/2022, 07:18:25 [pg3] debug: ISY Response: [Try: 1] [00:0d:b9:59:39:b0] :: [200] :: 18.382399ms - http://localhost:8080/rest/ns/2/nodes/n002_controller/report/status/GV1/18/0 3/6/2022, 07:18:25 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '2', 'controller', 'GV1') 3/6/2022, 07:18:25 [pg3] debug: UPDATE driver SET value = '18',uom = '0',timeModified = 1646579905764 WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '2', 'controller', 'GV1') 3/6/2022, 07:18:25 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '2', 'controller', 'GV1') 3/6/2022, 07:18:25 [pg3] debug: Scheduling http://localhost:8080/rest/ns/2/nodes/n002_controller/report/status/GV9/92598/0 to group statusGroup 3/6/2022, 07:18:25 [pg3] debug: MQTT Results: [ns/status/00:0d:b9:59:39:b0,2] :: {"set":[{"address":"controller","driver":"GV1","value":"18","uom":0}]} 3/6/2022, 07:18:25 [pg3] debug: ISY Response: [Try: 1] [00:0d:b9:59:39:b0] :: [200] :: 5.746094ms - http://localhost:8080/rest/ns/2/nodes/n002_controller/report/status/GV9/92598/0 3/6/2022, 07:18:25 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '2', 'controller', 'GV9') 3/6/2022, 07:18:25 [pg3] debug: UPDATE driver SET value = '92598',uom = '0',timeModified = 1646579905841 WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '2', 'controller', 'GV9') 3/6/2022, 07:18:25 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '2', 'controller', 'GV9') 3/6/2022, 07:18:25 [pg3] debug: MQTT Results: [ns/status/00:0d:b9:59:39:b0,2] :: {"set":[{"address":"controller","driver":"GV9","value":"92598","uom":0}]} 3/6/2022, 07:18:55 [pg3] debug: Getting status for MyQ 00:0d:b9:59:39:b0 3cac3bad-92bb-40f4-966f-3b541e85c898 3/6/2022, 07:18:55 [pg3] debug: Scheduling http://localhost:8080/rest/ns/6/nodes/n006_cg085008f7c6/report/status/GV0/7457/58 to group statusGroup 3/6/2022, 07:18:55 [pg3] debug: ISY Response: [Try: 1] [00:0d:b9:59:39:b0] :: [200] :: 6.670109ms - http://localhost:8080/rest/ns/6/nodes/n006_cg085008f7c6/report/status/GV0/7457/58 3/6/2022, 07:18:55 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '6', 'cg085008f7c6', 'GV0') 3/6/2022, 07:18:55 [pg3] debug: UPDATE driver SET value = '7457',uom = '58',timeModified = 1646579935682 WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '6', 'cg085008f7c6', 'GV0') 3/6/2022, 07:18:55 [pg3] debug: SELECT * FROM driver WHERE (uuid, profileNum, address, driver) is ('00:0d:b9:59:39:b0', '6', 'cg085008f7c6', 'GV0') 3/6/2022, 07:18:55 [pg3] debug: MQTT Results: [ns/status/00:0d:b9:59:39:b0,6] :: {"set":[{"address":"cg085008f7c6","driver":"GV0","value":"7457","uom":58}]} 3/6/2022, 07:18:55 [pg3] debug: Found info {"found":true,"isActive":true,"isInstalled":true,"expiry":"2023-02-06T03:16:34.000Z"} 3/6/2022, 07:18:55 [pg3] info: set to expire on 2023-02-06T03:16:34.000Z

Hi @bpwwer, disappearing node issue seems to be fixed! Thank You! -Tim

@kzborayThat is exactly where he posted.....Lol. @briansProbably due to the title of your post. Also, No real mention of UD mobile in the 1st post, I can see where the confusion could occur. @JaviShould be able to help.

Well, looking over PG3 I found 2 other node servers with the same problem. I deleted one of them then installed it into the same slot and its back working properly. I did the same with the 2nd one which had some programs associated with it. After reinstallation all programs were intact and working as they should have been. So I bit the bullet and did the same to the tag node server with, thankfully the same results. There is peace and harmony with PG3 again! Thanks, Tim

Hi @JimboAutomatesand @bpwwer, Unless PG3 updated to v3.0.39 without me seeing it, but pretty sure I went from 37 or38 to 40 directly. I ran the command as Jimbo suggested but I am not sure what this output means, : [admin@polisy ~]$ ls -l /var/polyglot/pg3/ns total 9 drwxr-xr-x 6 polyglot polyglot 19 Feb 19 15:16 00:0d:b9:59:39:b0_10 drwxr-xr-x 6 polyglot polyglot 14 Feb 19 11:31 00:0d:b9:59:39:b0_14 drwxr-xr-x 5 polyglot polyglot 14 Feb 19 11:20 00:0d:b9:59:39:b0_3 drwxr-xr-x 7 polyglot polyglot 19 Feb 12 12:10 00:0d:b9:59:39:b0_4 drwxr-xr-x 5 polyglot polyglot 13 Feb 19 11:37 00:0d:b9:59:39:b0_6 drwxr-xr-x 6 polyglot polyglot 16 Feb 19 11:20 00:0d:b9:59:39:b0_7 [admin@polisy ~]$ Thank you, Tim

Thanks, I will look tonight. I did not run 3.0.39, I went from 37 or38 to 40. What would be you recommendation if the node database is gone? Can I simply reinstall?

Hi @JimboAutomates, I am sorry, I am back with another weird one. I noticed I didn't get a notification from one of the tags. Turns out I am at least a couple of firmware upgrades back. When I rebooted the node server I got an error about can't find it. Also noticed that the "time started" is reporting as Feb 1st but PG3 and Polisy have both been rebooted a few times after that. I get the same message, or similar, when trying to download the log file for you. I can retrieve PG3 logs but not the nodes logs. I am thinking maybe this happed when I updated PG3 last week? On v3.0.40 Please let me know how to proceed. Thanks, Tim

Thanks very much @Jimbo it works great now. -Tim

@simplextechWill ST Inventory be ported to PG3 soon? Also, I am assuming this will be similar to ISY Inventory in PG2? Thanks, Tim

Yes, it looks like the latest firmware date on 1/28 took care of it. Working Fine. Thank you @glarsen Tim

@Goose66, I had wondered if Force Update could be used in programs the way query had been but thought I had better double check. Thank you for the explanation! This is a dumb question, but I was hoping for clarification. MyQ Service node page indicates that MyQ service is connecting to MyQ node server and supplying updates, correct? Likewise the Main Door node page, indicator Online indicates that the MyQ nodeserver in PG3 is down and not communicating with ISY, correct? Thanks, Tim

Thank you @Goose66, installed MyQ on IoP PG3 last night. Working great. I noticed "query" from My Service node is missing, along with some readings. Is this by design? Thanks, Tim Screenshot of PG2: Screenshot PG3:

Hi @bpwwer wasn't sure if you had seen this thread or not. Please see above. Thanks, Tim

@bpwwer Two things I am seeing. 1) after a restart of WeatherPoly NS if you watch the Node tab you will see it count down from, in my case, 6 nodes to 1 or 2. If you hit restart again it will count up to 6 then drop to 5 nodes. These node count changes also affect ISY-Polisy, meaning the nodes in ISY appear or disappear. 2) from a browser if I type in https://192.168.0.165:8088/acuparse?tempf=23 or http://192.168.0.165:8088/acuparse?tempf=23 neither command make it to the node server. During config I had to change the port becasue ISY-Polisy uses port 8080. Any thoughts? Thank you, Tim 2022-01-30 07:22:57,920 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-30 07:23:08,277 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message stop 2022-01-30 07:23:08,279 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING stop 2022-01-30 07:23:08,281 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2022-01-30 07:23:08,282 Command udi_interface.interface INFO interface:stop: Disconnecting from MQTT... localhost:1888 2022-01-30 07:23:08,283 Command udi_interface.interface INFO interface:_disconnect: MQTT Graceful disconnection. 2022-01-30 07:23:08,286 MQTT udi_interface.interface DEBUG interface:_startMqtt: MQTT: Done 2022-01-30 07:23:34,901 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-01-30 07:23:39,977 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.33 Starting... 2022-01-30 07:23:40,034 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '192.168.0.165', 'netmask': '255.255.255.0', 'broadcast': '192.168.0.255'} 2022-01-30 07:23:40,036 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2022-01-30 07:23:40,046 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: nodeserver config has not yet been recieved. 2022-01-30 07:23:40,048 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {}} 2022-01-30 07:23:40,698 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2022-01-30 07:23:40,700 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:59:39:b0_6 - MID: 1 Result: 0 2022-01-30 07:23:40,753 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-01-30 07:23:43,055 MainThread udi_interface.interface INFO interface:addNode: Adding node WeatherPoly(controller) [None] 2022-01-30 07:23:46,338 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getAll 2022-01-30 07:23:46,340 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getAll 2022-01-30 07:23:46,342 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: load {'Port': '8088', 'Units': 'us', 'IncomingUnits': 'us', 'humidity-main': 'humidity', 'pressure-sealevel': 'baromin', 'rain-daily': 'dailyrainin', 'rain-rate': 'rainin', 'temperature-dewpoint': 'dewptf', 'temperature-main': 'tempf', 'wind-avgwindspeed': 'windspdmph_avg2m', 'wind-winddir': 'winddir', 'wind-windspeed': 'windspeedmph'} 2022-01-30 07:23:46,343 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {} 2022-01-30 07:23:46,343 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking Port / 8088 2022-01-30 07:23:46,344 Command udi_interface.interface DEBUG interface:_handleInput: Key nsdata should be passed to node server. 2022-01-30 07:23:46,345 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking Units / us 2022-01-30 07:23:46,346 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking IncomingUnits / us 2022-01-30 07:23:46,346 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking humidity-main / humidity 2022-01-30 07:23:46,347 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking pressure-sealevel / baromin 2022-01-30 07:23:46,347 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking rain-daily / dailyrainin 2022-01-30 07:23:46,348 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking rain-rate / rainin 2022-01-30 07:23:46,348 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-dewpoint / dewptf 2022-01-30 07:23:46,349 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking temperature-main / tempf 2022-01-30 07:23:46,349 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking wind-avgwindspeed / windspdmph_avg2m 2022-01-30 07:23:46,350 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking wind-winddir / winddir 2022-01-30 07:23:46,350 Thread-1 udi_interface.custom DEBUG custom:load: CUSTOM: -- checking wind-windspeed / windspeedmph 2022-01-30 07:23:46,351 Thread-1 udi_interface.custom DEBUG custom:clear: CUSTOM: Clear ...saving 2022-01-30 07:23:46,351 Thread-1 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2022-01-30 07:23:46,352 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'notices', 'value': {}}]} 2022-01-30 07:23:46,353 Thread-1 udi_interface INFO weatherstation:set_configuration: Check for existing configuration value 2022-01-30 07:23:46,354 Thread-1 udi_interface INFO weatherstation:map_nodes: Trying to create a mapping 2022-01-30 07:23:46,355 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING humidity to humidity-main 2022-01-30 07:23:46,356 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING baromin to pressure-sealevel 2022-01-30 07:23:46,358 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message getNsInfo 2022-01-30 07:23:46,359 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING dailyrainin to rain-daily 2022-01-30 07:23:46,360 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING getNsInfo 2022-01-30 07:23:46,360 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING rainin to rain-rate 2022-01-30 07:23:46,362 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING dewptf to temperature-dewpoint 2022-01-30 07:23:46,362 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING tempf to temperature-main 2022-01-30 07:23:46,363 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING windspdmph_avg2m to wind-avgwindspeed 2022-01-30 07:23:46,363 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING winddir to wind-winddir 2022-01-30 07:23:46,364 Thread-1 udi_interface INFO weatherstation:map_nodes: MAPPING windspeedmph to wind-windspeed 2022-01-30 07:23:46,365 Thread-1 udi_interface INFO weatherstation:map_nodes: Try to create node definition profile based on config. 2022-01-30 07:23:46,366 Thread-1 udi_interface INFO write_profile:write_profile: write_profile: Writing profile/nodedef/nodedefs.xml 2022-01-30 07:23:46,370 Thread-1 udi_interface INFO write_profile:write_profile_zip: write_profile_zip: profile/version.txt as version.txt 2022-01-30 07:23:46,374 Thread-1 udi_interface INFO write_profile:write_profile_zip: write_profile_zip: profile/nodedef/nodedefs.xml as nodedef/nodedefs.xml 2022-01-30 07:23:46,377 Thread-1 udi_interface INFO write_profile:write_profile_zip: write_profile_zip: profile/nls/en_us.txt as nls/en_us.txt 2022-01-30 07:23:46,379 Thread-1 udi_interface INFO write_profile:write_profile_zip: write_profile_zip: profile/editor/editors.xml as editor/editors.xml 2022-01-30 07:23:46,382 Thread-1 udi_interface INFO write_profile:write_profile: write_profile: done. 2022-01-30 07:23:46,382 Thread-1 udi_interface.interface INFO interface:installprofile: Sending Install Profile command to Polyglot. 2022-01-30 07:23:46,383 Thread-1 udi_interface.interface WARNING interface:installprofile: installprofile() is deprecated. Use updateProfile() instead. 2022-01-30 07:23:46,383 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'installprofile': {'reboot': False}} 2022-01-30 07:23:46,384 Thread-1 udi_interface INFO weatherstation:discover: Creating nodes. 2022-01-30 07:23:46,385 Thread-1 udi_interface INFO weatherstation:discover: Creating Temperature node 2022-01-30 07:23:46,386 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Temperatures(temperature) [None] 2022-01-30 07:23:46,386 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'temperature', 'name': 'Temperatures', 'nodeDefId': 'temperature', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV0', 'value': 0, 'uom': 17}, {'driver': 'ST', 'value': 0, 'uom': 17}], 'hint': 16777215, 'private': None}]} 2022-01-30 07:23:46,388 Thread-1 udi_interface INFO weatherstation:discover: Creating Humidity node 2022-01-30 07:23:46,389 Thread-1 udi_interface.node DEBUG node:_updateDrivers: Update humidity default ST to 0 / 51 2022-01-30 07:23:46,389 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Humidity(humidity) [None] 2022-01-30 07:23:46,390 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'humidity', 'name': 'Humidity', 'nodeDefId': 'humidity', 'primaryNode': 'controller', 'drivers': [{'driver': 'ST', 'value': 0, 'uom': 51}], 'hint': 16777215, 'private': None}]} 2022-01-30 07:23:46,391 Thread-1 udi_interface INFO weatherstation:discover: Creating Pressure node 2022-01-30 07:23:46,392 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Barometric Pressure(pressure) [None] 2022-01-30 07:23:46,392 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'pressure', 'name': 'Barometric Pressure', 'nodeDefId': 'pressure', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV0', 'value': 0, 'uom': 23}], 'hint': 16777215, 'private': None}]} 2022-01-30 07:23:46,394 Thread-1 udi_interface INFO weatherstation:discover: Creating Wind node 2022-01-30 07:23:46,395 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Wind(wind) [None] 2022-01-30 07:23:46,396 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'wind', 'name': 'Wind', 'nodeDefId': 'wind', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV4', 'value': 0, 'uom': 48}, {'driver': 'GV0', 'value': 0, 'uom': 14}, {'driver': 'ST', 'value': 0, 'uom': 48}], 'hint': 16777215, 'private': None}]} 2022-01-30 07:23:46,398 Thread-1 udi_interface INFO weatherstation:discover: Creating Precipitation node 2022-01-30 07:23:46,399 Thread-1 udi_interface.interface INFO interface:addNode: Adding node Precipitation(rain) [None] 2022-01-30 07:23:46,399 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'rain', 'name': 'Precipitation', 'nodeDefId': 'precipitation', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV1', 'value': 0, 'uom': 105}, {'driver': 'ST', 'value': 0, 'uom': 24}], 'hint': 16777215, 'private': None}]} 2022-01-30 07:23:46,400 Thread-1 udi_interface INFO weatherstation:discover: Deleting orphaned light node 2022-01-30 07:23:46,401 Thread-1 udi_interface.interface INFO interface:delNode: Removing node light 2022-01-30 07:23:46,401 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'light'}]} 2022-01-30 07:23:46,402 Thread-1 udi_interface INFO weatherstation:discover: Deleting orphaned lightning node 2022-01-30 07:23:46,403 Thread-1 udi_interface.interface INFO interface:delNode: Removing node lightning 2022-01-30 07:23:46,403 Thread-1 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'lightning'}]} 2022-01-30 07:23:47,534 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-30 07:23:47,535 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-30 07:23:47,538 Thread-3 udi_interface INFO weatherstation:start: Starting WeatherPoly Node Server 2022-01-30 07:23:47,539 Thread-3 udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2022-01-30 07:23:47,540 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '2828ef24-73ba-4fe8-bbd6-af98f8b00cd3', 'uuid': '00:0d:b9:59:39:b0', 'profileNum': 6, 'address': 'controller', 'name': 'WeatherPoly', 'nodeDefId': 'WeatherPoly', 'nls': None, 'hint': '0x00000000', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 1, 'enabled': 1, 'timeAdded': 1643499288131, 'timeModified': 1643499288131, 'dbVersion': 1} 2022-01-30 07:23:47,540 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'installprofile': {'reboot': False}} 2022-01-30 07:23:47,665 Thread-3 udi_interface.interface DEBUG interface:setCustomParamsDoc: Sending customparamsdoc to Polyglot. 2022-01-30 07:23:47,667 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'customparamsdoc', 'value': '<h2>Configuration</h2>\n\n<p>The WeatherPoly node server has the following user configuration\nparameters:</p>\n\n<ul>\n<li>Port : The TCP port to listen on for connections from weather software.</li>\n<li>Units : The units used to display the data. Valid settings are: \'metric\', \'us\', or \'uk\'. The default is \'metric\'</li>\n<li>IncomingUnits: The units used by the data provider. Valid settings are \'metric\', \'us\', and \'uk\'. Default is \'metric\'.</li>\n</ul>\n\n<p>A mapping between the incoming data fields and the node server\'s nodes must be configured. The key is a node and data type combination and the value represents the incoming data field. How a data field is represented depends on the weather software.</p>\n\n<p>Valid nodes are: temperature, humidity, pressure, rain, wind, light, and lightning. See <a href="NODE_VALUE.md">node-value combinations</a> for a full list of node-values that can be used.</p>\n\n<h3>Cumulus software</h3>\n\n<p>Cumulus software allows you to configure what text string is used to represent each value. See the Cumulus documentation for a list of valid tags. A Cumulus HTTP API value of:</p>\n\n<p>http://<node server ip>:8080/cumulus?temp=&lt;#temp>&amp;humidity=&lt;#humidity></p>\n\n<p>Will send temperature and humidity data. This can be mapped to node server nodes using:</p>\n\n<p>temperature-main : temp\nhumidity-main : humidity</p>\n\n<h3>acuparse</h3>\n\n<p>acuparse software for Acurite weather stations https://github.com/acuparse/acuparse can be configured to send data to a generic service. To configure acuparse to send data to WeatherPoly, set the generic URL to:</p>\n\n<p>http://<node server ip>:8080/acuparse</p>\n\n<h4>Configure WeatherPoly with the following mapping:</h4>\n\n<ul>\n<li>temperature-main = tempf</li>\n<li>temperature-dewpoint = dewptf</li>\n<li>humidity-main = humidity</li>\n<li>pressure-sealevel = baromin</li>\n<li>wind-windspeed = windspeedmph</li>\n<li>wind-winddir = winddir</li>\n<li>wind-avgwindspeed = windspdmph_avg2m</li>\n<li>rain-rate = rainin</li>\n<li>rain-daily = dailyrainin</li>\n</ul>\n\n<p>Input units should be set as US.</p>\n\n<h3>WeeWX</h3>\n\n<p>WeeWX data is supported through an extension to WeeWX called weewx-crt which can output the data in Cumulus Real Time format. The weewx-crt extension is configured by setting the realtime_url to:</p>\n\n<p>http://<node server ip>:8080/weewx</p>\n\n<h4>Configure WeatherPoly mappings:</h4>\n\n<p>The real-time data file is a fixed format file with the weather values separated by spaces. This is split so that the space separated value\'s index is mapped to the node servers nodes-values. For example:\n* temperature-main = 2\n* temperature-dewpoint = 3\n* humidity-main = 4\n* etc.</p>\n\n<h3>MeteoBridge</h3>\n\n<p>MeteoBridge data is supported using the Home Weather Station weather network configuration. For the API URL use</p>\n\n<p>http://<node server ip>:8080/</p>\n\n<p>MeteoBridge will send a space separated list of values. These are mapped to the node server\'s nodes using the value\'s position in that list. The table below shows the values and numeric position.</p>\n\n<h4>MeteoBridge Field list</h4>\n\n<p><a href="METEOBRIDGE.md">MeteoBridge field list</a></p>\n'}]} 2022-01-30 07:23:47,669 Thread-3 udi_interface INFO weatherstation:discover: Creating nodes. 2022-01-30 07:23:47,671 Thread-3 udi_interface INFO weatherstation:discover: Creating Temperature node 2022-01-30 07:23:47,671 Thread-3 udi_interface.interface INFO interface:delNode: Removing node temperature 2022-01-30 07:23:47,672 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'temperature'}]} 2022-01-30 07:23:47,674 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Temperatures(temperature) [None] 2022-01-30 07:23:47,676 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'temperature', 'name': 'Temperatures', 'nodeDefId': 'temperature', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV0', 'value': 0, 'uom': 17}, {'driver': 'ST', 'value': 0, 'uom': 17}], 'hint': 16777215, 'private': None}]} 2022-01-30 07:23:47,678 Thread-3 udi_interface INFO weatherstation:discover: Creating Humidity node 2022-01-30 07:23:47,679 Thread-3 udi_interface.interface INFO interface:delNode: Removing node humidity 2022-01-30 07:23:47,681 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'humidity'}]} 2022-01-30 07:23:47,683 Thread-3 udi_interface.node DEBUG node:_updateDrivers: Update humidity default ST to 0 / 51 2022-01-30 07:23:47,684 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Humidity(humidity) [None] 2022-01-30 07:23:47,684 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'humidity', 'name': 'Humidity', 'nodeDefId': 'humidity', 'primaryNode': 'controller', 'drivers': [{'driver': 'ST', 'value': 0, 'uom': 51}], 'hint': 16777215, 'private': None}]} 2022-01-30 07:23:47,685 Thread-3 udi_interface INFO weatherstation:discover: Creating Pressure node 2022-01-30 07:23:47,686 Thread-3 udi_interface.interface INFO interface:delNode: Removing node pressure 2022-01-30 07:23:47,687 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'pressure'}]} 2022-01-30 07:23:47,688 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Barometric Pressure(pressure) [None] 2022-01-30 07:23:47,689 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'pressure', 'name': 'Barometric Pressure', 'nodeDefId': 'pressure', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV0', 'value': 0, 'uom': 23}], 'hint': 16777215, 'private': None}]} 2022-01-30 07:23:47,690 Thread-3 udi_interface INFO weatherstation:discover: Creating Wind node 2022-01-30 07:23:47,691 Thread-3 udi_interface.interface INFO interface:delNode: Removing node wind 2022-01-30 07:23:47,691 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'wind'}]} 2022-01-30 07:23:47,693 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Wind(wind) [None] 2022-01-30 07:23:47,693 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'wind', 'name': 'Wind', 'nodeDefId': 'wind', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV4', 'value': 0, 'uom': 48}, {'driver': 'GV0', 'value': 0, 'uom': 14}, {'driver': 'ST', 'value': 0, 'uom': 48}], 'hint': 16777215, 'private': None}]} 2022-01-30 07:23:47,695 Thread-3 udi_interface INFO weatherstation:discover: Creating Precipitation node 2022-01-30 07:23:47,695 Thread-3 udi_interface.interface INFO interface:delNode: Removing node rain 2022-01-30 07:23:47,696 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'rain'}]} 2022-01-30 07:23:47,697 Thread-3 udi_interface.interface INFO interface:addNode: Adding node Precipitation(rain) [None] 2022-01-30 07:23:47,698 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'addnode': [{'address': 'rain', 'name': 'Precipitation', 'nodeDefId': 'precipitation', 'primaryNode': 'controller', 'drivers': [{'driver': 'GV1', 'value': 0, 'uom': 105}, {'driver': 'ST', 'value': 0, 'uom': 24}], 'hint': 16777215, 'private': None}]} 2022-01-30 07:23:47,699 Thread-3 udi_interface INFO weatherstation:discover: Deleting orphaned light node 2022-01-30 07:23:47,700 Thread-3 udi_interface.interface INFO interface:delNode: Removing node light 2022-01-30 07:23:47,700 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'light'}]} 2022-01-30 07:23:47,701 Thread-3 udi_interface INFO weatherstation:discover: Deleting orphaned lightning node 2022-01-30 07:23:47,702 Thread-3 udi_interface.interface INFO interface:delNode: Removing node lightning 2022-01-30 07:23:47,703 Thread-3 udi_interface.interface DEBUG interface:send: PUBLISHING {'removenode': [{'address': 'lightning'}]} 2022-01-30 07:23:47,704 Thread-3 udi_interface INFO weatherstation:start: WeatherPoly Node Server Started. 2022-01-30 07:23:48,052 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-30 07:23:48,054 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-30 07:23:51,690 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message notices 2022-01-30 07:23:51,692 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING notices 2022-01-30 07:23:51,692 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {} 2022-01-30 07:23:51,731 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2022-01-30 07:23:51,864 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': '<h2>Configuration</h2>\n\n<p>The WeatherPoly node server has the following user configuration\nparameters:</p>\n\n<ul>\n<li>Port : The TCP port to listen on for connections from weather software.</li>\n<li>Units : The units used to display the data. Valid settings are: \'metric\', \'us\', or \'uk\'. The default is \'metric\'</li>\n<li>IncomingUnits: The units used by the data provider. Valid settings are \'metric\', \'us\', and \'uk\'. Default is \'metric\'.</li>\n</ul>\n\n<p>A mapping between the incoming data fields and the node server\'s nodes must be configured. The key is a node and data type combination and the value represents the incoming data field. How a data field is represented depends on the weather software.</p>\n\n<p>Valid nodes are: temperature, humidity, pressure, rain, wind, light, and lightning. See <a href="NODE_VALUE.md">node-value combinations</a> for a full list of node-values that can be used.</p>\n\n<h3>Cumulus software</h3>\n\n<p>Cumulus software allows you to configure what text string is used to represent each value. See the Cumulus documentation for a list of valid tags. A Cumulus HTTP API value of:</p>\n\n<p>http://<node server ip>:8080/cumulus?temp=&lt;#temp>&amp;humidity=&lt;#humidity></p>\n\n<p>Will send temperature and humidity data. This can be mapped to node server nodes using:</p>\n\n<p>temperature-main : temp\nhumidity-main : humidity</p>\n\n<h3>acuparse</h3>\n\n<p>acuparse software for Acurite weather stations https://github.com/acuparse/acuparse can be configured to send data to a generic service. To configure acuparse to send data to WeatherPoly, set the generic URL to:</p>\n\n<p>http://<node server ip>:8080/acuparse</p>\n\n<h4>Configure WeatherPoly with the following mapping:</h4>\n\n<ul>\n<li>temperature-main = tempf</li>\n<li>temperature-dewpoint = dewptf</li>\n<li>humidity-main = humidity</li>\n<li>pressure-sealevel = baromin</li>\n<li>wind-windspeed = windspeedmph</li>\n<li>wind-winddir = winddir</li>\n<li>wind-avgwindspeed = windspdmph_avg2m</li>\n<li>rain-rate = rainin</li>\n<li>rain-daily = dailyrainin</li>\n</ul>\n\n<p>Input units should be set as US.</p>\n\n<h3>WeeWX</h3>\n\n<p>WeeWX data is supported through an extension to WeeWX called weewx-crt which can output the data in Cumulus Real Time format. The weewx-crt extension is configured by setting the realtime_url to:</p>\n\n<p>http://<node server ip>:8080/weewx</p>\n\n<h4>Configure WeatherPoly mappings:</h4>\n\n<p>The real-time data file is a fixed format file with the weather values separated by spaces. This is split so that the space separated value\'s index is mapped to the node servers nodes-values. For example:\n* temperature-main = 2\n* temperature-dewpoint = 3\n* humidity-main = 4\n* etc.</p>\n\n<h3>MeteoBridge</h3>\n\n<p>MeteoBridge data is supported using the Home Weather Station weather network configuration. For the API URL use</p>\n\n<p>http://<node server ip>:8080/</p>\n\n<p>MeteoBridge will send a space separated list of values. These are mapped to the node server\'s nodes using the value\'s position in that list. The table below shows the values and numeric position.</p>\n\n<h4>MeteoBridge Field list</h4>\n\n<p><a href="METEOBRIDGE.md">MeteoBridge field list</a></p>\n'} 2022-01-30 07:23:51,917 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2022-01-30 07:23:52,287 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-30 07:23:52,288 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-30 07:23:52,290 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '29807fd3-6010-4b6e-9643-8de355958074', 'uuid': '00:0d:b9:59:39:b0', 'profileNum': 6, 'address': 'humidity', 'name': 'Humidity', 'nodeDefId': 'humidity', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643555738067, 'timeModified': 1643556232149, 'dbVersion': 1} 2022-01-30 07:23:52,328 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2022-01-30 07:23:52,437 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-30 07:23:52,439 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-30 07:23:52,441 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': 'b211e6a1-02b4-4d32-85cd-327bae730caf', 'uuid': '00:0d:b9:59:39:b0', 'profileNum': 6, 'address': 'pressure', 'name': 'Barometric Pressure', 'nodeDefId': 'pressure', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643555738154, 'timeModified': 1643556232322, 'dbVersion': 1} 2022-01-30 07:23:52,657 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-30 07:23:52,659 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-30 07:23:52,660 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': 'a4b17277-9ccf-456a-b13c-778f4e4ffa00', 'uuid': '00:0d:b9:59:39:b0', 'profileNum': 6, 'address': 'wind', 'name': 'Wind', 'nodeDefId': 'wind', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643555738466, 'timeModified': 1643556232491, 'dbVersion': 1} 2022-01-30 07:23:52,787 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'light', 'success': False}] 2022-01-30 07:23:52,911 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-30 07:23:52,912 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-30 07:23:52,914 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '53dc1903-603e-410f-8095-90633332efb9', 'uuid': '00:0d:b9:59:39:b0', 'profileNum': 6, 'address': 'rain', 'name': 'Precipitation', 'nodeDefId': 'precipitation', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643555738627, 'timeModified': 1643556232736, 'dbVersion': 1} 2022-01-30 07:23:52,950 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'lightning', 'success': False}] 2022-01-30 07:23:53,027 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-30 07:23:53,029 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-30 07:23:53,370 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-30 07:23:53,372 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-30 07:23:53,373 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '29807fd3-6010-4b6e-9643-8de355958074', 'uuid': '00:0d:b9:59:39:b0', 'profileNum': 6, 'address': 'humidity', 'name': 'Humidity', 'nodeDefId': 'humidity', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643555738067, 'timeModified': 1643556233092, 'dbVersion': 1} 2022-01-30 07:23:53,489 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2022-01-30 07:23:53,939 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'humidity', 'success': True}] 2022-01-30 07:23:54,144 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'temperature', 'success': False}] 2022-01-30 07:23:54,242 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-30 07:23:54,244 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-30 07:23:54,246 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': 'b211e6a1-02b4-4d32-85cd-327bae730caf', 'uuid': '00:0d:b9:59:39:b0', 'profileNum': 6, 'address': 'pressure', 'name': 'Barometric Pressure', 'nodeDefId': 'pressure', 'nls': None, 'hint': '16777215', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643555738154, 'timeModified': 1643556233715, 'dbVersion': 1} 2022-01-30 07:23:54,281 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'pressure', 'success': True}] 2022-01-30 07:23:54,489 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'wind', 'success': True}] 2022-01-30 07:23:54,615 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-30 07:23:54,616 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-30 07:23:54,618 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': 'ce8de222-8b35-4da9-a9fd-a9587a3e7a96', 'uuid': '00:0d:b9:59:39:b0', 'profileNum': 6, 'address': 'wind', 'name': 'Wind', 'nodeDefId': 'wind', 'nls': None, 'hint': '16777215.0', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643556234382, 'timeModified': 1643556234382, 'dbVersion': 1} 2022-01-30 07:23:54,657 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'rain', 'success': True}] 2022-01-30 07:23:54,969 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'light', 'success': False}] 2022-01-30 07:23:55,068 MQTT udi_interface.interface ERROR interface:_message: Invalid command received in message from PG3: 'removenode' [{'address': 'lightning', 'success': False}] 2022-01-30 07:23:55,212 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-30 07:23:55,213 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-30 07:23:55,215 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'address': 'temperature'} 2022-01-30 07:23:56,413 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-30 07:23:56,414 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-30 07:23:56,416 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '876ca813-949f-4156-992b-252d86b2d9a6', 'uuid': '00:0d:b9:59:39:b0', 'profileNum': 6, 'address': 'temperature', 'name': 'Temperatures', 'nodeDefId': 'temperature', 'nls': None, 'hint': '16777215.0', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643556232203, 'timeModified': 1643556232203, 'dbVersion': 1} 2022-01-30 07:23:57,521 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2022-01-30 07:23:57,522 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2022-01-30 07:23:57,524 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': 'ee8fa22c-cd04-40fb-b167-837c538a8cf5', 'uuid': '00:0d:b9:59:39:b0', 'profileNum': 6, 'address': 'rain', 'name': 'Precipitation', 'nodeDefId': 'precipitation', 'nls': None, 'hint': '16777215.0', 'controller': 0, 'primaryNode': 'controller', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1643556235563, 'timeModified': 1643556235563, 'dbVersion': 1} 2022-01-30 07:23:58,238 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-30 07:23:58,239 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-30 07:24:03,233 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-30 07:24:03,235 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-30 07:24:08,184 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-30 07:24:08,185 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-30 07:24:13,330 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-30 07:24:13,332 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-30 07:24:18,429 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-30 07:24:18,430 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-30 07:24:23,344 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-30 07:24:23,346 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-30 07:24:28,360 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-30 07:24:28,361 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-30 07:24:33,382 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-30 07:24:33,384 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-30 07:24:37,849 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message longPoll 2022-01-30 07:24:37,850 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING longPoll 2022-01-30 07:24:38,456 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-30 07:24:38,458 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-30 07:24:43,490 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-30 07:24:43,492 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-30 07:24:48,514 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-30 07:24:48,515 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2022-01-30 07:24:53,560 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2022-01-30 07:24:53,562 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll

Yes, thank you Jimbo! This is working well for me too! Tim

You're awesome! Thank you and will do. Tim

@bpwwerFunny, I just this second was looking for it on PG3 as well. I am ready willing and able to test it out. -Tim

@glarsen Time data had been running fine but noticed recently some calendar based programs not running. PG3 reported the node server was not running. Spent the evening trying to fix it. Deleted and tried to install but PG3 complained that node server time data file not found. I noticed the firmware date for time data was 1/23/2022 so just within the last week. Is it possible there is a glitch in the new file, or its missing in the store? I am on the latest PG3 and ISY-Polisy. Any help would greatly be appreciated. Tim

Hi @Jimbo, Great job on Kasa. I thought I would venture out and try the output dual switch plug, the ep40. The node server found it and listed it in ISY on Polisy no problem. ISY will control each switch just fine but the status for each switch does not update in the admin console. Interestingly the SmartStrip node has an on and off button at the bottom of the page. Which when turned on the status updates but nothing happens to the switch, same when it is turned off, the status updates but nothing happens at the switch. I am thinking this switch isn't supported yet, I know I am a bit slow sometimes, lol. But I also noticed when I went to copy the log in Kasa ns, it hasn't updated since last night. But about 5 minutes after I set it to debug it started spitting out data. Has there been any other reports of a log issue or kasa issue like this? Kasa v3.0.7 PG3 v3.0.36 with front end same ISY-Polisy v5.3.0 Thanks, Tim

Hi @Jimbo, Installed Wireless tag node server over the weekend and had the same error on PG3 that Gary had, ERROR: Unable to authorize, no client id returned in Node Server Data. Check Log for ERROR I was able to revert PG2 back into operation. Will you post once we should try again? Thanks! Tim

@waffles , in answer to your original question, if all you use is Insteon, a few programs and some Alexa commands then you shouldn't have any trouble moving right into ISY-Polisy right now. The migration set up seems to be working perfectly, and the portal migration for Alexa seems to work perfectly as well. I have a similar set up as you only with a bunch of different note servers on polyglot and node link and I had very little problem switching over. Just remember to back up, back up, back up! There's no guarantee in life, but with the tools that UDI provides it made it a pretty smooth transition.

Hi @tmorse305 , Not an expert and cannot provide you answers but thought I would let you know, for what its worth that I have encountered the same errors for 2-3 months (or however long ISY has been working on Polisy). I have 3 WCLinks plus I had 3 or 4 other node servers all running on it all pointing to ISY on Polisy. It has been and is working great despite the errors. -Tim