glarsen

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.

OK, I guess I'll dig some more.....

@JimboAutomates, I'm not sure whether this is an ELK or UD Mobile issue. Sometime in the past week after one upate or another (UD or ELK, I don't know which), I no longer see a drop-down for Armed Status. Is there now a different way to ARM/DISARM or am I missing something? I'm on IoP 5.4.3_1, PG3 3.0.59, ELK 3.2.7 and UD mobile 0.140. I've resynced UD Mobile, restarted the node server, restarte IoP, and in various orders and no change. Thanks!

Yes, because the status driver isn't used in the child node, it's used as one of the data drivers. The parent provides that status information. I'll change that in the next version so it doesn't show.

I'm not too sure, it seems Dyson doesn't like your credentials for some reason. Try the 'US' in lower case maybe. I've seen that Dyson seems to be case sensitive for some things, ie the serial number has to use all caps.

I think it's telling you that it wasn't succesful in connecting to your fan. Perhaps you can turn on DEBUG in logging, and then restart the node server again. You can PM the log to me instead if inserting in the public space. Double check your configuration - make sure there are no leading or trailing spaces in any of the elements. I know it's a bit tricky because of the Dyson API - acquiring that credential need to connect is a pain. I believe you can run two copies of a node server on PG3; they would just be installed in separate slots.

Too many variations for Holidays to make it worth the effort for me. Canada is different from the US. But there are a couple of new Holiday node servers on the PG3 store that are free. Take a look at those.

When the Area node is opened in UD Mobile. The zones are fine.

@Javi, @JimboAutomates, I think this update must have broken something with UD Mobile. I get "java.lang.error: Node Status Relation Cursor is empty. NodeId: 1551. Control:0.500. I have restarted the ISY and the reloaded the app with no change. Edit: The node status fields all display, but none of the CMD fields appear. All of the grouped nodes show.

There is also a restriction on which characters the ELK can display...for instance if a degree or percent symbol is embedded in the string, nothing will display. Ask me how I know this...?