Jimbo.Automates

Any ERRORS shown in the Polyglot UI for ELK? Any ERROR in the Log file? Download log package and PM it to me.

I think you are the first to officially ask for this, unless I'm forgetting someone else, which is possible. It's going to take some time but I'll try to look into it next. Sent from my Pixel 6 Pro using Tapatalk

Great! And sorry for not giving those instructions sooner! I'll add to the OP.

UD Mobile, Notifications, Settings. I should make this optional. I'll try to do that today. Sent from my Pixel 6 Pro using Tapatalk

Are you putting it in the new portal_api_key setting? I'll check your log in a few. Sent from my Pixel 6 Pro using Tapatalk

PG3 Notification Node Server 3.5.4 has been released. See the Release Notes for more information.

PG3 Notification Node Server 3.5.2 has been released. See OP.

The node server does not control what is in that list, it uses the editor _sys_notify_short and is presented by the AC so I will have to defer to @Chris Jahn about why your list is incomplete. It is the same list presented in the ISY Portal Service Node "Short Custom Content".

The current ISY Portal service nodes will remain, they have many more options, and I will be adding groups to the list of devices. I was doing my production testing yesterday and this morning which is why it hadn't been officially announced.

1. No, it is a new parameter, the existing one on the ISY Portal Service node should still exist. 2. The preference is to use groups always so if you change the name of your phone it will still work, and when you get a new phone it can be put in the group and the old one removed. I will be adding groups to the "devices" list in the ISY Portal Service node so you can chose to use either.

PG3 Notification Node Server 3.5.4 has been released. See the Release Notes for more information. If you update from a version prior to 3.5.0 you will need to set your Portal API key in the "Custom Configuration Parameters". To find your portal_api_key open UDMobile, go to Notifications then Settings. I will release a new version soon which makes this optional. See the README for more information, including information on moving from PG2.

I see in the log it sets GV9 which is animal -> squirrel to zero: 2023-05-04 10:05:53,667 Thread-14 udi_interface.node DEBUG node:setDriver: 01_003_animal:Deck animal Reporting set GV9 to 0 to Polyglot 2023-05-04 10:05:53,667 Thread-14 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2023-05-04 10:05:53,667 Thread-14 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': '01_003_animal', 'driver': 'GV9', 'value': '0', 'uom': 2}]} 2023-05-04 10:05:53,667 Thread-14 udi_interface DEBUG BaseNode:set_driver: 01_003_animal:Deck animal set_driver(GV9,0) Then sets GV10 which is animal -> unknown animal to one: 2023-05-04 10:05:53,668 Thread-14 udi_interface.node DEBUG node:setDriver: 01_003_animal:Deck animal Reporting set GV10 to 1 to Polyglot 2023-05-04 10:05:53,668 Thread-14 udi_interface.node DEBUG node:reportDriver: Updating value to 1 2023-05-04 10:05:53,668 Thread-14 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': '01_003_animal', 'driver': 'GV10', 'value': '1', 'uom': 2}]} 2023-05-04 10:05:53,668 Thread-14 udi_interface DEBUG BaseNode:set_driver: 01_003_animal:Deck animal set_driver(GV10,1) There is a bug in ISY which I reported a long time ago when using Control and a node sends 0 (False) it still triggers a program that is looking for 1 (True). @Chris Jahn acknowledged the bug but it hasn't made it to the top of his list yet.

Are you running ELK NS 3.7.0 ? It doesn't look like it based on the log provided.

Thanks, I'll take a look. BTW, when posting Log, please enclose it in Code using the <> in the editor. Edit: I fixed your post for you

Just got this crash: 2023-04-14 04:23:29,225 Thread-24119 udi_interface DEBUG iaquaapi:getDevicesList: in API getDevicesList()... 2023-04-14 04:23:35,280 Thread-24119 udi_interface WARNING iaquaapi:_call_api: HTTP GET in _call_api() failed: HTTPSConnectionPool(host='p-api.iaqualink.net', port=443): Read timed out. (read timeout=6.05) 2023-04-14 04:23:35,281 Thread-24119 udi_interface ERROR udi_interface:write: Exception in thread 2023-04-14 04:23:35,281 Thread-24119 udi_interface ERROR udi_interface:write: Thread-24119 2023-04-14 04:23:35,281 Thread-24119 udi_interface ERROR udi_interface:write: : 2023-04-14 04:23:35,281 Thread-24119 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-04-14 04:23:35,281 Thread-24119 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2023-04-14 04:23:35,282 Thread-24119 udi_interface ERROR udi_interface:write: self.run() 2023-04-14 04:23:35,282 Thread-24119 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2023-04-14 04:23:35,282 Thread-24119 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2023-04-14 04:23:35,282 Thread-24119 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025d7d_20/iaqualinkns/nslib.py", line 81, in _poll_handler 2023-04-14 04:23:35,283 Thread-24119 udi_interface ERROR udi_interface:write: self.longPoll() 2023-04-14 04:23:35,283 Thread-24119 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025d7d_20/iaqualinkns/iaqualinkns.py", line 123, in longPoll 2023-04-14 04:23:35,283 Thread-24119 udi_interface ERROR udi_interface:write: self.serviceNode.updateNodeStates() 2023-04-14 04:23:35,283 Thread-24119 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025d7d_20/iaqualinkns/nodes.py", line 808, in updateNodeStates 2023-04-14 04:23:35,283 Thread-24119 udi_interface ERROR udi_interface:write: sys.updateNodeStates(forceReport) 2023-04-14 04:23:35,283 Thread-24119 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9025d7d_20/iaqualinkns/nodes.py", line 255, in updateNodeStates 2023-04-14 04:23:35,284 Thread-24119 udi_interface ERROR udi_interface:write: elif deviceName in devices: # type: ignore 2023-04-14 04:23:35,284 Thread-24119 udi_interface ERROR udi_interface:write: TypeError 2023-04-14 04:23:35,284 Thread-24119 udi_interface ERROR udi_interface:write: : 2023-04-14 04:23:35,284 Thread-24119 udi_interface ERROR udi_interface:write: argument of type 'NoneType' is not iterable 2023-04-14 04:23:37,102 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll

I tried reconnect account to UDI in the Home app, and it spins for a few seconds then says "Successfully linked your Universal Devices account" in a popup that only stays visible for a second. I goes away so quick I had to start a screen record and play it back slowly to see what it said. But devices still show as offline.

Google Home is showing my devices as offline for both homes. I can login to portal and send spokens which is successful, but the Home app still shows all offline.

The Polyglot Version 3 Node server for ELK Security Version 3.7.0 is released. See the Release Notes The 3.7.0 release added support for Export of ELK Lights see Light Node and Configuring the ELK Node Server. The 3.8.0 release added support for light_method=ELKALL to import all ELK Lights into the ISY as a light node. If you have issues or requests please check PG3 ELK Github issues to see it has already been listed. And if you want to thumbs up an issue I will try to prioritize fixing the ones with most votes.

This error in the log can be ignored, I need to fix that. It's just printing the defaults: 2023-04-06 15:10:15,992 Thread-3 udi_interface ERROR CamectController:customNS_handler: Got key=nsdata which is not in data={ "user": "", "password": "" }, In that configuration page from your pic it should show these instructions: https://github.com/UniversalDevicesInc-PG3/udi-poly-Camect/blob/main/configdoc.md and I don't see in your pic where you have added a Camect Host? When adding new cameras, you should just be able to hit Discover in the PG3 UI or In the AC.

LOL, that video is awesome! Love it.

Can the notice show the System name (alias in Portal) along with the UUID? I just got a notice and had to go look which one it was associated with.

I would caution people on this recommendation. The Kasa API is not supported by TP-Link so it can break at any time, it has been reverse engineered and the developers keep up with changes as much as possible, but TP-Link could decide to lock it up at any point. That said, I do like my Kasa bulbs, LED strips, Outlets & Power Strips.

Glad you got it working, feel free to post your experience with it and let me know if you have suggestions are questions. There are very few using this NS.

Sorry, I should add this to the instructions: Please open https://local.home.camect.com/ in browser, sign in as admin and accept TOS before you proceed.

Thanks, yes I saw that error, it happens when you have no lights configured in the Elk. You can safely ignore until I can get a new rele out. Sent from my Pixel 6 Pro using Tapatalk