rwsani99

Thanks for the replies and I'm sorry it's taken my so long to get back with a reply. Below is a copy of the Even Viewer when I try to Show Device Links Table and it fails. Since my original post, I have replaced the PLM and the device does seem to respond to most commands from my Polisy. But while my overall system seems more reliable with the new PLM, I still get these failed replies when I try to Show Device Links Table. Sat 05/03/2025 09:14:06 AM : [INST-TX-I2CS] 02 62 4E 7D 16 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 Sat 05/03/2025 09:14:06 AM : [INST-ACK ] 02 62 4E.7D.16 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06 (00) Sat 05/03/2025 09:14:15 AM : [INST-TX-I2CS] 02 62 4E 7D 16 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 Sat 05/03/2025 09:14:15 AM : [INST-ACK ] 02 62 4E.7D.16 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06 (00) Sat 05/03/2025 09:14:24 AM : [INST-TX-I2CS] 02 62 4E 7D 16 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 Sat 05/03/2025 09:14:24 AM : [INST-ACK ] 02 62 4E.7D.16 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 C2 06 (00) Sat 05/03/2025 09:14:28 AM : [All ] Writing 0 bytes to devices And when I issue a Restore Device, I see the following communications, but the device still shows writes pending to the device : Sat 05/03/2025 09:23:38 AM : [ 4E 7D 16 1] Preparing Device 'Kitchen Pantry Light' for Restore Sat 05/03/2025 09:23:38 AM : [ 4E 7D 16 1] Device 'Kitchen Pantry Light' ready for Full Restore Sat 05/03/2025 09:23:38 AM : [All ] Writing 19 bytes to devices Sat 05/03/2025 09:23:38 AM : [INST-TX-I1 ] 02 62 4E 7D 16 0F 0D 00 Sat 05/03/2025 09:23:38 AM : [INST-ACK ] 02 62 4E.7D.16 0F 0D 00 06 (00) Sat 05/03/2025 09:23:39 AM : [INST-SRX ] 02 50 4E.7D.16 71.17.44 2B 0D 02 (02) Sat 05/03/2025 09:23:39 AM : [Std-Direct Ack] 4E.7D.16-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 05/03/2025 09:23:39 AM : [4E 7D 16 0 ] Calibrating engine version Sat 05/03/2025 09:23:39 AM : [INST-TX-I2CS] 02 62 4E 7D 16 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Sat 05/03/2025 09:23:39 AM : [INST-ACK ] 02 62 4E.7D.16 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Sat 05/03/2025 09:23:40 AM : [INST-SRX ] 02 50 4E.7D.16 71.17.44 2B 2F 00 (00) Sat 05/03/2025 09:23:40 AM : [Std-Direct Ack] 4E.7D.16-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 05/03/2025 09:23:49 AM : [INST-TX-I2CS] 02 62 4E 7D 16 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Sat 05/03/2025 09:23:49 AM : [INST-ACK ] 02 62 4E.7D.16 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Sat 05/03/2025 09:23:58 AM : [INST-TX-I2CS] 02 62 4E 7D 16 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Sat 05/03/2025 09:23:58 AM : [INST-ACK ] 02 62 4E.7D.16 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Sat 05/03/2025 09:24:02 AM : [4E 7D 16 1 ] Memory : Write dbAddr=0x0032 [00] cmd1=0x2E cmd2=0x00 Sat 05/03/2025 09:24:02 AM : [INST-TX-I2CS] 02 62 4E 7D 16 1F 2E 00 01 06 00 00 00 00 00 00 00 00 00 00 00 CB Sat 05/03/2025 09:24:02 AM : [INST-ACK ] 02 62 4E.7D.16 1F 2E 00 01 06 00 00 00 00 00 00 00 00 00 00 00 CB 06 (00) Sat 05/03/2025 09:24:11 AM : [INST-TX-I2CS] 02 62 4E 7D 16 1F 2E 00 01 06 00 00 00 00 00 00 00 00 00 00 00 CB Sat 05/03/2025 09:24:11 AM : [INST-ACK ] 02 62 4E.7D.16 1F 2E 00 01 06 00 00 00 00 00 00 00 00 00 00 00 CB 06 (00) Sat 05/03/2025 09:24:14 AM : [INST-SRX ] 02 50 4E.7D.16 71.17.44 2B 2E 00 (00) Sat 05/03/2025 09:24:14 AM : [Std-Direct Ack] 4E.7D.16-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 05/03/2025 09:24:14 AM : [4E 7D 16 1 ] Memory : Write dbAddr=0x0021 [00] cmd1=0x2E cmd2=0x00 Sat 05/03/2025 09:24:14 AM : [INST-TX-I2CS] 02 62 4E 7D 16 1F 2E 00 01 05 00 00 00 00 00 00 00 00 00 00 00 CC Sat 05/03/2025 09:24:14 AM : [INST-ACK ] 02 62 4E.7D.16 1F 2E 00 01 05 00 00 00 00 00 00 00 00 00 00 00 CC 06 (00) Sat 05/03/2025 09:24:15 AM : [INST-SRX ] 02 50 4E.7D.16 71.17.44 23 2E 00 (00) Sat 05/03/2025 09:24:15 AM : [Std-Direct Ack] 4E.7D.16-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sat 05/03/2025 09:24:17 AM : [INST-SRX ] 02 50 4E.7D.16 71.17.44 2B 2E 00 (00) Sat 05/03/2025 09:24:17 AM : [Std-Direct Ack] 4E.7D.16-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

Polisy running 5.9.1. When using the Diagnostics->Show Device Links Table, I seem to be getting the subject error message for a large number of my Insteon devices. The error message pops up even while the Events Viewer shows that communication commands are still being sent back and forth between the device and PLM. In the past, I thought this type of error would show up after the Polisy had given up on polling the device. Has anything changed? Any suggestions on what I could try? Most of my devices are working reliably and those with only a couple of links succeed without this error. Any advice appreciated.

And now, an hour late it's working! I can't see anything in the log file that show what changed and I haven't restarted the NS or anything.

After updating to Climacell Version 2.0.3 today, I am now having the 'Current observation update failure', similar to what tmorse305 described. I.e. my Forcast0 data is fine. I am running IOX 5.8.3 and PG3x Version 3.2.22. I also use the ELK and Bond node servers and they seem to be fine, so my problem is just with Climacell. I've previously been using Climacell without problem for more than a year. Any ideas?

Just to clarify, I was experiencing the the same symptoms as described by sumguy in the first post of this thread. Yesterday (08/14/2023) I received a reply to my support ticket from Michel that PG3x 3.2.0 was being released yesterday and would address the problem(s) I was hitting. And after upgrading to PG3x 3.2.1 yesterday, all my node servers are currently up and running correctly.

Now I've hit this same problem. I've filed a support ticket and will wait for UD support. I just wanted to document for others that this problem is still occurring. I'm on IoX 5.6.4 and PG3x 3.1.36

I've bitten by this same issue too. I've been using 7 as my 'Forecast Days' for a year or more and it's worked fine. I suspect a 'policy' change at Climacell, but I don't know when. I've now switched to a 4 day forecast request. Thanks for posting this!

I think I've found the problem: my configuration setting of shortPoll 120 and longPoll 600 was exceeding my hourly and daily allowance of updates with my default (free) Tomorrow.io account. The allowance with a free Tomorrow.io account is 500/day, 25/hr, 3/sec. Now that I've changed to shortPoll 300 and longPoll 3600, I'm seeing no more errors. And updates of current weather ever 5 minutes and forecasts every hour are more than sufficient for my needs.

I've been using the Climacell node server with my Polisy for several months and it is working well. But I don't have any explanation for this recurring error in the log files. This error is logged every hour at the exact same time. At first I thought that was just a one off header check error, but it happens precisely once per hour and I use shorPoll 120 (2 minutes) and longPoll 600 (10 minutes). The normal shortPoll and longPoll calls seem to succeed without errors. So I don't know what's being called once per hour. My system firmware version and parameters are: Polisy 5.4.5 PG3: 3.1.15 Cilimacell Node Server: 2.0.1 Climacell configuration parameters: shortPoll 120, longPoll 600 Anything I can do to resolve this? Or maybe there is discrepancy between the Node Server and Tomorrow.io? 2022-12-04 09:42:54,058 Thread-704 udi_interface ERROR query:query_conditions: Current observation update failure 2022-12-04 09:42:54,059 Thread-704 udi_interface ERROR query:query_conditions: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing data: incorrect header check')) 2022-12-04 09:44:54,045 Thread-705 udi_interface ERROR query:query_conditions: Current observation update failure 2022-12-04 09:44:54,046 Thread-705 udi_interface ERROR query:query_conditions: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing data: incorrect header check')) 2022-12-04 09:46:54,065 Thread-706 udi_interface ERROR query:query_conditions: Current observation update failure 2022-12-04 09:46:54,066 Thread-706 udi_interface ERROR query:query_conditions: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing data: incorrect header check')) 2022-12-04 09:48:48,810 Thread-707 udi_interface ERROR query:query_forecast: Forecast data failure: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing data: incorrect header check')) 2022-12-04 09:48:54,063 Thread-708 udi_interface ERROR query:query_conditions: Current observation update failure 2022-12-04 09:48:54,065 Thread-708 udi_interface ERROR query:query_conditions: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing data: incorrect header check')) 2022-12-04 09:50:54,852 Thread-709 udi_interface ERROR query:query_conditions: Current observation update failure 2022-12-04 09:50:54,853 Thread-709 udi_interface ERROR query:query_conditions: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing data: incorrect header check')) 2022-12-04 09:52:54,146 Thread-710 udi_interface ERROR query:query_conditions: Current observation update failure 2022-12-04 09:52:54,147 Thread-710 udi_interface ERROR query:query_conditions: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing data: incorrect header check')) 2022-12-04 09:54:54,124 Thread-711 udi_interface ERROR query:query_conditions: Current observation update failure 2022-12-04 09:54:54,125 Thread-711 udi_interface ERROR query:query_conditions: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing data: incorrect header check')) 2022-12-04 09:56:54,127 Thread-712 udi_interface ERROR query:query_conditions: Current observation update failure 2022-12-04 09:56:54,128 Thread-712 udi_interface ERROR query:query_conditions: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing data: incorrect header check')) 2022-12-04 09:58:48,882 Thread-713 udi_interface ERROR query:query_forecast: Forecast data failure: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing data: incorrect header check')) 2022-12-04 09:58:54,828 Thread-714 udi_interface ERROR query:query_conditions: Current observation update failure 2022-12-04 09:58:54,829 Thread-714 udi_interface ERROR query:query_conditions: ('Received response with content-encoding: gzip, but failed to decode it.', error('Error -3 while decompressing data: incorrect header check'))

THANK YOU!! Yes I did use the copy button in UD Mobile, and I used copy/paste from Gmail on my PC. And when I went back into Edit of the API Key is doesn't show any extra spaces at the front or back. BUT I erased the existing API Key, pasted it a second time and before I hit SAVE, I noticed the paste added a SPACE after the API Key, so I deleted that before hitting SAVE. And voila! It works! Thanks again.

TCP client request failed I thought I had followed the Wiki directions carefully, downloaded the exampled and inserted my API Key from UDMoble. But when I try to TEST, I get the above error. Below is cut/paste from the ISY Error Log from this time along with a screenshot of the specific error message. Any thoughts on what I'm missing? I've also attached a txt file of the Error Log if that is easier to view. Time User Code Message Mon 1900/01/01 12:00:00 AM System -170001 [HTTP:0-61120896] ::fc8e:7fdf:ff7f:0:(51199)->6 Thu 2022/12/01 10:53:06 AM 0 -170001 <s:Envelope><s:Body><u:TestNetResource xmlns:u="urn:udi-com:service:X_IoX_Service:1"><id>3</id><flag>1</flag></u:TestNetResource></s:Body></s:Envelope> Thu 2022/12/01 10:53:06 AM 0 -170001 [HTTP:0-61120896]: POST[1]-->/services Thu 2022/12/01 10:53:06 AM 0 -140008 Net Module Rule: 3:403 Thu 2022/12/01 10:53:06 AM 0 -170001 [HTTP:1-86286336] ::fc9e:9fdf:ff7f:0:(51455)->6 Thu 2022/12/01 10:53:06 AM 0 -170001 [HTTP:1-86286336]: POST[1]-->/services Thu 2022/12/01 10:53:06 AM 0 -170001 <s:Envelope><s:Body><u:GetLastError xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetLastError></s:Body></s:Envelope> Thu 2022/12/01 10:53:07 AM 0 -170001 [HTTP:0-61120896] ::fc8e:7fdf:ff7f:0:(51711)->6 Thu 2022/12/01 10:53:07 AM 0 -170001 [HTTP:0-61120896]: POST[1]-->/services Thu 2022/12/01 10:53:07 AM 0 -170001 <s:Envelope><s:Body><u:ClearLastError xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:ClearLastError></s:Body></s:Envelope> Thu 2022/12/01 10:53:20 AM 0 -170001 [HTTP:1-86286336] ::fc9e:9fdf:ff7f:0:(51967)->6 Thu 2022/12/01 10:53:20 AM 0 -170001 [HTTP:1-86286336]: POST[1]-->/services Thu 2022/12/01 10:53:20 AM 0 -170001 <s:Envelope><s:Body><u:GetErrorLog xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetErrorLog></s:Body></s:Envelope> ISY Error Log.v5.4.5__Thu 2022.12.01 10.53.19 AM.txt

I'm actually running PG3 3.1.14 and getting this node server update failure

I also see it in the store, but a Restart fails to find/install the new version. I don't know if this is relevant, but a message in the log file states " No node server version specified. Using deprecated server.json version" Larger section of Log file: 2022-11-10 10:29:34,970 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-11-10 10:29:37,233 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.49 Starting... 2022-11-10 10:29:37,248 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.1.14 [ISY: 5.4.4, Slot: 4] 2022-11-10 10:29:37,250 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr':, 'netmask': '255.255.255.0', 'broadcast': '192.168.0.255'} 2022-11-10 10:29:37,252 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:1888 2022-11-10 10:29:37,257 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2022-11-10 10:29:37,259 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: controller not found in database. 2022-11-10 10:29:37,261 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '2.0.0'}} 2022-11-10 10:29:37,303 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2022-11-10 10:29:37,305 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:5e:e2:8c_4 - MID: 1 Result: 0 2022-11-10 10:29:37,310 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 1 - QoS: (0,) 2022-11-10 10:29:40,275 MainThread udi_interface.interface INFO interface:addNode: Adding node Climacell Weather(controller) [None] 2022-11-10 10:29:40,398 Thread-1 udi_interface ERROR climacell:parameterHandler: ***** Entered parameter handler.... 2022-11-10 10:29:40,402 Thread-1 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2022-11-10 10:29:40,501 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2022-11-10 10:29:41,294 Thread-3 udi_interface INFO climacell:start: Starting node server

This isn't an urgent issue for me as I'm having no current problems with version 3.0.9, but when I issue a restart of the node server, I get the following message in the Polyglot log file: 11/9/2022, 10:12:05 [pg3] info: startNs:: Bond 11/9/2022, 10:12:05 [pg3] info: startNs:: Bond is valid 11/9/2022, 10:12:06 [pg3] info: checkLicense:: Bond Valid perpetual license found. 11/9/2022, 10:12:06 [pg3] info: UPGRADE AVAILABLE for Bond from 3.0.9 to 3.0.10 11/9/2022, 10:12:09 [pg3] info: [Bond(3)] :: New Version detected: re-running install process... 11/9/2022, 10:12:15 [pg3] info: upload successful 11/9/2022, 10:12:15 [pg3] info: upload successful 11/9/2022, 10:12:16 [pg3] info: upload successful 11/9/2022, 10:12:16 [pg3] error: Node server update failed Bond :: Error: notices doesn't exist 11/9/2022, 10:12:16 [pg3] error: Bond automatic update failed

Great! Any estimate on when 2.0.1 will be released? This isn't an urgent issue for me, just curious if there's an estimate. Thanks!!