glarsen

@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

I am unable to upgrade from 3.0.16 to 3.0.18. The only thing I see in the NS log on restart is "WARNING interface:start: No node server version specified. Using deprecated server.json version". This is in the PG3 log 12/16/2022, 14:17:29 [pg3] info: startNs:: Kasa 12/16/2022, 14:17:29 [pg3] info: startNs:: Kasa is valid 12/16/2022, 14:17:29 [pg3] info: checkLicense:: Kasa Valid perpetual license found. 12/16/2022, 14:17:29 [pg3] info: startNs:: Kasa finished update check 12/16/2022, 14:17:30 [pg3] info: [Kasa(16)] :: Starting Node Server - Version 3.0.16 12/16/2022, 14:17:30 [pg3] info: startNs:: Kasa updating database (enabled, timestarted) 12/16/2022, 14:17:31 [pg3] info: startNs:: Kasa starting polls 12/16/2022, 14:17:31 [pg3] info: Starting Node Server Info timer 0 12/16/2022, 14:17:34 [pg3] info: MQTTS: Client Connected: 00:0d:b9:52:bf:f4_16 12/16/2022, 14:17:37 [pg3] info: [00:0d:b9:52:bf:f4_16] Set notices 12/16/2022, 14:17:37 [pg3] info: node tplkasactl on profile 16 already exists, no nodeDef or driver changes detected If I try to re-install in stead I get: "Can't find purchase option for license record". There is a order ID in the purchased servers display so it should be ok to reinstall. PG3 3.1.15 and IoX 5.4.5 Thanks

There is a configuration setting called "Active Only". If it is set to true unused zones won't display. Is that perhaps the reason? It works fine on my 16 zone device.

@stevehoyt, thanks for letting me know. Enjoy!

@stevehoyt, would you please set the loglevel to "DEBUG" in the Polisy Dashboard control for the Rainmachine Node server and resubmit the log?

Hi @stevehoyt, Sorry Steve, I'm away on vacation until after the middle of August with limited access to any development systems. I'll try look through your attachments but it's a little hard on a phone screen. I'll let you know if anything obvious shows. G

This is the PG2 forum, there's a separate forum for the PG3 version. I don't see any issues in either log and am unable to replicate the issue here yet.

Yes. I received no further feedback on the beta version so removed it. I will release it to production sometime next week once I'm back at home.

Yes, this is because the TP02 isn't supported (yet). I'm working with another user to try to add support. You can try the beta version in the non- production store if you like. It's the first attempt at adding model 475 support. Let me know what the log shows if you do. The AC probably won't be right yet either. I can't find much info about this model. What features does it have?

I, and others, have used 'CA' or 'US' and all lower case email addresses successfully. Can you login via web to your Dyson account successfully? Maybe a password mismatch?

I don't know exactly what was going on. I uninstalled and reinstalled the app and it's fine now. Thanks anyway.