glarsen

It turns out, after running your sample program overnight, that it doesn't replicate this every hour, only periodically, with no pattern I can discern. I'm thinking it has something to do with timing related to when the Node Server was started (how close to the change of the actual minute), which then may cause some logic confusion in the ISY. There is nothing in the Node Server code that would make it trigger differently from one minute to the next, nor is there any dependency on the hour changing. Are you able to use the built-in time/date functions of the ISY for this? The Node Server only changes the display of the minute on the next shortPoll after the minute actually changes, which may be up to 59 seconds late, depending upon when in the minute the Node Server was last started.

While I can replicate this phenomenon, I am not clear on why it is happening. In checking both the code and my local logs, the Node Server only updates the minute value once each time the minute changes. I can't explain why the program is triggered on the 00 minute of the next hour. Try reversing the order of the hour and minute conditions in the program and see if it makes any difference. Also, you can try changing your shortPoll value to 60 from the default of 30. :

Same for me this morning

Same here.

I also reinstalled using 1.0.9. Everything thing works as expected.

So, the heartbeat fix was trivial. 3.2.1 is indeed there now with the fix. Note: Since 3.2.0 was so old, and with significant changes to PG3x since it was released, you may have to re-install rather than just restart to update.

I've noticed that ping error too, but haven't had time to look into it. I thnk something changed with the ping API call. It's only a status check and had no operational effect on the NS, so I haven't prioritized it yet. There is no 3.2.1, that seems to have crept in during another node server update. (though I guess there will be once the ping check is fixed)

See the same thing - the Confirm/Cancel dialog is greyed out/inactive after installing 3.1.24

Updated to 5.5.9 with no issues on eisy with pg3x 3.1.22. The "Update Packages" message seems to have gone.

@jwagner010, @bpwwer, thanks for your patience and help in resolving this. A brain **** when cleaning up old node server entries in my dev list caused it all.

@CStockard, the Meteobridge node server should be back in the PG3 store.

That's odd, there is no 'Free' version. There was a 'Free Trial' version in the Beta store, but not in the Production store. The Beta has been removed.

There's something odd about that screenshot too. This is what I see in the node server info display on the production store, and what you should be seeing:

Oops, sorry, my bad. Accidentally deleted production instead of pre-prod. It was never on github. I'll try to fix it now.

It was an update of a setting in the PG3 store.

Same with me. Android 13

@bpwwer, any thoughts on why @auger66 and I can't get the ST-Sonos node server to start properly? I am experiencing the same issue with St-NuHeat. (Reported earlier in topic - log snippet attached). Node.js issues? Thanks!

Seeing the same thing with ST-Sonos (same for ST-NuHeat). PG3x 3.1.20 also. No node server log, not much in the pg3x log (attached): 1/19/2023, 14:46:51 [pg3] info: Installing ST-Sonos on IoX 1/19/2023, 14:46:51 [pg3] info: [00:21:b9:02:62:8f_24] 'ST-Sonos' installed into ISY successfully... 1/19/2023, 14:46:51 [pg3] info: Installing ST-Sonos's profile files on IoX 1/19/2023, 14:46:51 [pg3] info: installProfile: ST-Sonos :: read /var/polyglot/pg3/ns/0021b902628f_24/profile/nodedef 1/19/2023, 14:46:51 [pg3] info: Uploading nodedefs.xml 1/19/2023, 14:46:51 [pg3] info: installProfile: ST-Sonos :: read /var/polyglot/pg3/ns/0021b902628f_24/profile/editor 1/19/2023, 14:46:51 [pg3] info: Uploading editors.xml 1/19/2023, 14:46:51 [pg3] info: installProfile: ST-Sonos :: read /var/polyglot/pg3/ns/0021b902628f_24/profile/nls 1/19/2023, 14:46:51 [pg3] info: Uploading en_US.txt 1/19/2023, 14:46:51 [pg3] info: Installation complete. Starting ST-Sonos 1/19/2023, 14:46:51 [pg3] info: startNs:: ST-Sonos 1/19/2023, 14:46:51 [pg3] info: startNs:: ST-Sonos is valid 1/19/2023, 14:46:51 [pg3] info: upload successful 1/19/2023, 14:46:51 [pg3] info: upload successful 1/19/2023, 14:46:51 [pg3] info: checkLicense:: ST-Sonos Valid subscription license found. Expires: 2023-01-25T18:22:45.000Z 1/19/2023, 14:46:51 [pg3] info: startNs:: ST-Sonos finished update check 1/19/2023, 14:46:51 [pg3] info: Making reqeust to socket for /rest/pg3.start.ns 1/19/2023, 14:46:51 [pg3] info: startNs:: ST-Sonos starting polls 1/19/2023, 14:46:51 [pg3] info: Checking if ${Node Server.name} has expired 1/19/2023, 14:46:51 [pg3] info: Starting Node Server Info timer 0 1/19/2023, 14:46:51 [pg3] info: startNs:: ST-Sonos updating database (enabled, timestarted) 1/19/2023, 14:46:51 [pg3] info: upload successful 1/19/2023, 14:46:52 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:46:52 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:46:52 [pg3] info: [00:21:b9:02:62:8f_24] Set customparams 1/19/2023, 14:46:52 [pg3] error: No code in error response 1/19/2023, 14:46:52 [pg3] error: ISY Response: [Try: 1] [00:21:b9:02:62:8f] :: [404 - OK] :: 41.833657ms - http://127.0.0.1:8080/rest/nodes/n024_controller 1/19/2023, 14:46:52 [pg3] warn: node controller on profile 00:21:b9:02:62:8f/24 not in the database. Adding... 1/19/2023, 14:46:52 [pg3] info: [00:21:b9:02:62:8f_24] adding node controller to ISY 1/19/2023, 14:46:52 [pg3] info: [00:21:b9:02:62:8f_24] addnode sucessfully added node controller 1/19/2023, 14:46:52 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:46:56 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:46:56 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:01 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:01 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:05 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:05 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:09 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:09 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:14 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:14 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:18 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:18 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:22 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:22 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:23 [pg3] info: Starting log stream for pg3frontend_JX4GN :: /var/polyglot/pg3/ns/0021b902628f_24/logs/debug.log 1/19/2023, 14:47:27 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:27 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:29 [pg3] info: Verifying node servers are installed on IoX correctly 1/19/2023, 14:47:29 [pg3] info: IoX entry for ELK::3 OK 1/19/2023, 14:47:29 [pg3] info: IoX entry for ST-Sonos::24 OK 1/19/2023, 14:47:30 [pg3] warn: stopLogging: unwatch failed, TypeError: Cannot read properties of undefined (reading 'pg3frontend_JX4GN') 1/19/2023, 14:47:30 [pg3] info: [00:21:b9:02:62:8f_24] Retrieved customparams 1/19/2023, 14:47:30 [pg3] info: [00:21:b9:02:62:8f_24] Retrieved customparamsdoc 1/19/2023, 14:47:30 [pg3] info: [00:21:b9:02:62:8f_24] Retrieved notices 1/19/2023, 14:47:30 [pg3] info: [00:21:b9:02:62:8f_24] Retrieved oauth 1/19/2023, 14:47:30 [pg3] info: [00:21:b9:02:62:8f_24] Retrieved customparams 1/19/2023, 14:47:30 [pg3] info: [00:21:b9:02:62:8f_24] Retrieved customparamsdoc 1/19/2023, 14:47:30 [pg3] info: [00:21:b9:02:62:8f_24] Retrieved notices 1/19/2023, 14:47:31 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:31 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:32 [pg3] info: Starting log stream for pg3frontend_1XRrL :: /var/polyglot/pg3/ns/0021b902628f_24/logs/debug.log 1/19/2023, 14:47:36 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:36 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:40 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:40 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:44 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:44 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:49 [pg3] info: [00:21:b9:02:62:8f_24] Set notices 1/19/2023, 14:47:49 [pg3] info: [00:21:b9:02:62:8f_24] Set customparamsdoc 1/19/2023, 14:47:52 [pg3] warn: stopLogging: unwatch failed, TypeError: Cannot read properties of undefined (reading 'pg3frontend_1XRrL') 1/19/2023, 14:47:52 [pg3] info: set to expire on 2023-01-25T18:22:45.000Z

No, the price listed for the node server is a one time charge. The subscription fee is charged by the Rainmachine organization for remote access using their servers. You can avoid that too if you know how to set up port forwarding through your router to your Rainmachine. I suppose you could say that by using UDI Mobile in remote mode you'd have remote access without using the RM servers.

The delay seems to have disappeared.

Yes, definitely elkm1-lib 2.2.1. It happened when I did a polisy upgrade last week. I'll have to see if I can roll it back. The delay I'm seeing is much shorter than what those reporting it on the eisy say.

I am running on polisy still (eisy is in the mail 🙂), PG3 3.1.16 and ELK 3.5.7. Since the upgrade to 3.5.7 and to library version 2.2.1 I see this in the Node Server log frequently: 023-01-13 06:42:17,479 Thread-4691 elkm1_lib.connection WARNING connection:disconnect: ElkM1 at elk://elkm1g.internal.home disconnecting 2023-01-13 06:42:17,489 Thread-4691 udi_interface ERROR udi_interface:write: Exception in thread 2023-01-13 06:42:17,490 Thread-4691 udi_interface ERROR udi_interface:write: Thread-4691 2023-01-13 06:42:17,491 Thread-4691 udi_interface ERROR udi_interface:write: : 2023-01-13 06:42:17,492 Thread-4691 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-01-13 06:42:17,493 Thread-4691 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2023-01-13 06:42:17,497 Thread-4691 udi_interface ERROR udi_interface:write: self.run() 2023-01-13 06:42:17,498 Thread-4691 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2023-01-13 06:42:17,501 Thread-4691 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2023-01-13 06:42:17,502 Thread-4691 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db952bff4_3/nodes/Controller.py", line 593, in stop 2023-01-13 06:42:17,506 Thread-4691 udi_interface ERROR udi_interface:write: self.elk_stop() 2023-01-13 06:42:17,507 Thread-4691 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db952bff4_3/nodes/Controller.py", line 571, in elk_stop 2023-01-13 06:42:17,509 Thread-4691 udi_interface ERROR udi_interface:write: self.elk.disconnect() 2023-01-13 06:42:17,510 Thread-4691 udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/elkm1_lib/elk.py", line 141, in disconnect 2023-01-13 06:42:17,512 Thread-4691 udi_interface ERROR udi_interface:write: self._connection.disconnect() 2023-01-13 06:42:17,513 Thread-4691 udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/elkm1_lib/connection.py", line 178, in disconnect 2023-01-13 06:42:17,516 Thread-4691 udi_interface ERROR udi_interface:write: if asyncio.current_task() != task: 2023-01-13 06:42:17,516 Thread-4691 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/asyncio/tasks.py", line 38, in current_task 2023-01-13 06:42:17,520 Thread-4691 udi_interface ERROR udi_interface:write: loop = events.get_running_loop() 2023-01-13 06:42:17,521 Thread-4691 udi_interface ERROR udi_interface:write: RuntimeError 2023-01-13 06:42:17,521 Thread-4691 udi_interface ERROR udi_interface:write: : 2023-01-13 06:42:17,522 Thread-4691 udi_interface ERROR udi_interface:write: no running event loop 2023-01-13 06:42:35,621 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-01-13 06:42:38,656 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.51 Starting... This happened this morning when disarming the ELK. The response from commands is also somewhat slower, maybe 2 or 3 seconds after sending them the ELK responds. The node server appears to recover as it seems a restart happens. The loglevel was only set to ERROR when this ocurred. I'll set it to debug and see what else is shown. Edit: I just noticed that the same error occurs at the point a manual stop or restart is issued to the node server.

Looks like upgrading the elkm1_lib library was the fix. Thanks

I encountered this error this morning after updating my Polisy and restarting PG3 (twice). Python3 is at version 3.9.16, PG3 at 3.1.16. Library elkm1 0.5.0 and elkm1-lib 2.0.0

i did try to re-install through the Node Server store, which is when I received the pop-up about the purchase option. I'll try the PG3 upgrade and see what happens. Thanks Edit: Was able to re-install after upgrade to 3.1.16. Thanks again