Jimbo.Automates

Next error 2022-08-16 16:50:39,095 MainThread udi_interface INFO controller:start: Starting Lutron Caseta Node Server 2022-08-16 16:50:39,097 MainThread udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2022-08-16 16:50:39,099 MainThread udi_interface DEBUG controller:start: Waiting for configuration False 2022-08-16 16:50:49,201 Thread-3 udi_interface ERROR picos:dataHandler: No custom data yet.... 2022-08-16 16:50:49,236 Thread-4 udi_interface ERROR picos:dataHandler: No custom data yet.... 2022-08-16 16:50:53,880 Thread-6 udi_interface ERROR udi_interface:write: Exception in thread 2022-08-16 16:50:53,882 Thread-6 udi_interface ERROR udi_interface:write: Thread-6 2022-08-16 16:50:53,883 Thread-6 udi_interface ERROR udi_interface:write: : 2022-08-16 16:50:53,883 Thread-6 udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-08-16 16:50:53,884 Thread-6 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner 2022-08-16 16:50:53,889 Thread-6 udi_interface ERROR udi_interface:write: self.run() 2022-08-16 16:50:53,889 Thread-6 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run 2022-08-16 16:50:53,892 Thread-6 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs) 2022-08-16 16:50:53,893 Thread-6 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_18/nodes/remote.py", line 189, in start 2022-08-16 16:50:53,895 Thread-6 udi_interface ERROR udi_interface:write: elif self.buttons[button]['button_number'] == self.button_nums[1]: 2022-08-16 16:50:53,895 Thread-6 udi_interface ERROR udi_interface:write: IndexError 2022-08-16 16:50:53,896 Thread-6 udi_interface ERROR udi_interface:write: : 2022-08-16 16:50:53,897 Thread-6 udi_interface ERROR udi_interface:write: list index out of range

Got a crash: 2022-08-15 17:58:17,903 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-08-15 17:58:17,904 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_18/./caseta.py", line 12, in <module> 2022-08-15 17:58:17,906 MainThread udi_interface ERROR udi_interface:write: LutronCasetaController(polyglot) 2022-08-15 17:58:17,906 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_18/nodes/controller.py", line 47, in __init__ 2022-08-15 17:58:17,908 MainThread udi_interface ERROR udi_interface:write: self.start() 2022-08-15 17:58:17,909 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_18/nodes/controller.py", line 134, in start 2022-08-15 17:58:17,911 MainThread udi_interface ERROR udi_interface:write: self.discover() 2022-08-15 17:58:17,912 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/asgiref/sync.py", line 218, in __call__ 2022-08-15 17:58:17,915 MainThread udi_interface ERROR udi_interface:write: return call_result.result() 2022-08-15 17:58:17,916 MainThread udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/concurrent/futures/_base.py", line 439, in result 2022-08-15 17:58:17,922 MainThread udi_interface ERROR udi_interface:write: return self.__get_result() 2022-08-15 17:58:17,923 MainThread udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/concurrent/futures/_base.py", line 391, in __get_result 2022-08-15 17:58:17,925 MainThread udi_interface ERROR udi_interface:write: raise self._exception 2022-08-15 17:58:17,927 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/.local/lib/python3.9/site-packages/asgiref/sync.py", line 284, in main_wrap 2022-08-15 17:58:17,929 MainThread udi_interface ERROR udi_interface:write: result = await self.awaitable(*args, **kwargs) 2022-08-15 17:58:17,931 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_18/nodes/controller.py", line 376, in discover 2022-08-15 17:58:17,933 MainThread udi_interface ERROR udi_interface:write: self.createPicoCfgNode(Remote4Group, device, device_id, '1', ' - A', [1], 'DON') # default on 2022-08-15 17:58:17,934 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:52:bf:fc_18/nodes/controller.py", line 187, in createPicoCfgNode 2022-08-15 17:58:17,936 MainThread udi_interface ERROR udi_interface:write: NodeType( 2022-08-15 17:58:17,938 MainThread udi_interface ERROR udi_interface:write: TypeError 2022-08-15 17:58:17,938 MainThread udi_interface ERROR udi_interface:write: : 2022-08-15 17:58:17,939 MainThread udi_interface ERROR udi_interface:write: __init__() takes 9 positional arguments but 10 were given

For some reason it says unavailable. Would be nice to understand why this has happened to you multiple times.

and yes, there are buttons for full open/close, and incremental open/close, and 4 more to control 4 devices Individually, 1-4 and an "all" button, pressing those just says which device is going to be controlled with the 4 open/close buttons. Then the "silver" button which moves all shades to their preset.

Hey @bpwwer, it showed new version available and I restarted, but still shows 1.0.1: 2022-08-15 17:27:05,842 MainThread udi_interface.interface WARNING interface:send: MQTT Send waiting on connection :: {'config': {'version': '1.0.1'}}

>> but do IoP events also end up on that queue IoP events do not go on the PG3 queue, it can talk to itself directly. I have weatherflow running as well, with Rapid Wind disabled so it sends less data. I don't notice any delays, I have lights triggered based on doors opening using the ELK node server and it happens very fast. I've heard of issues with ST-Inventory filling up ISY subscription connections, but not crashing it. >> If the Airthings NS needs to call for each device's data one device at a time anyway, that would be an easy place to put in a break Each query to the Airthings server takes a little time, so that is a built in break between each one. I could add an optional user delay in between each one, but that will take some effort to avoid other potential issues it may cause with Node server functionality. As I mentioned I have 19 node servers running and a couple are very busy, like WirelessTag's and I have not noticed issues with ISY On Polisy.

Works great! Thanks @Javi

It goes to the same place all other downloads go, which depends on what web browser you are using. Sent from my Pixel 6 Pro using Tapatalk

Is that from pressing the "Download Log Package" button? (Not the "Download Log" button)

Hi, So updating the devices puts very little load on the Polisy, all processes in PG3 are threaded so they don't even block each other. I have 19 node servers running, with a lot of devices and programs with no issues. But, the query of all devices is run on each short poll, so just changing the short poll and restarting the node server controls how often it is done. I also emailed their support and asked them to provide one API call to get data for all devices, and they said that will not be done for Consumer devices.

You had the same issue with Ecobee: https://forum.universal-devices.com/topic/37951-ployglot-v3-cant-get-ecobee-node-server-to-start/?do=findComment&comment=345938 Where I asked if you could do this: "Download log package and send it to me, then I can see the PG3 log."

Great! I'll confirm once I get it and test. Sent from my Pixel 6 Pro using Tapatalk

@Javi, I have a command favorite which uses the value of an integer variable to show status, and I sync integer variables which all works great. The problem occurs if the value of that variable changes during initial startup of UD Mobile. This happens when I start the app, and before it shows me the value of that variable, I press the command which arm/disarm's my ELK and changes the value of that variable. This quickly shows the correct value of the variable, but then when the app finishes the initial load it shows the old value. Hopefully that makes sense, if not I can send screen video.

Download log package and send it to me, then I can see the PG3 log. Sent from my Pixel 6 Pro using Tapatalk

Sorry, need more information, not sure what Can't connect means. Did you follow the instuctions https://github.com/UniversalDevicesInc-PG3/udi-poly-ecobee/blob/master/README.md#installation If so, please download log package from the Node server log page and PM that to me.

Hey @bpwwer, Great job on this node server! I never knew the little black button on the hub could be used for access control. Can you add support for this shade? It was working in the PG2 version: 2022-08-12 18:12:51,596 ThreadPoolExecutor-2_0 udi_interface ERROR controller:discover: Unsupported device type: TriathlonRollerShade 2022-08-12 18:12:51,598 ThreadPoolExecutor-2_0 udi_interface ERROR controller:discover: To get support for this device added, please send the following to the developer: 2022-08-12 18:12:51,599 ThreadPoolExecutor-2_0 udi_interface ERROR controller:discover: { "device_id": "5", "current_state": 100, "fan_speed": null, "tilt": null, "zone": "1", "name": "Family Room_Door Shade", "button_groups": null, "occupancy_sensors": null, "type": "TriathlonRollerShade", "model": "QSFRJ-S2A13-XX", "serial": 19023737 } and these, although not sure I really need them in the ISY: 2022-08-12 18:12:51,579 ThreadPoolExecutor-2_0 udi_interface ERROR controller:discover: Unsupported device type: FourGroupRemote 2022-08-12 18:12:51,581 ThreadPoolExecutor-2_0 udi_interface ERROR controller:discover: To get support for this device added, please send the following to the developer: 2022-08-12 18:12:51,582 ThreadPoolExecutor-2_0 udi_interface ERROR controller:discover: { "device_id": "3", "current_state": -1, "fan_speed": null, "tilt": null, "zone": null, "name": "Family Room_Shade Remote", "button_groups": [ "3", "4", "5", "6", "7" ], "occupancy_sensors": null, "type": "FourGroupRemote", "model": "CS-YJ-4GC-WH", "serial": 47103488 } 2022-08-12 18:12:51,610 ThreadPoolExecutor-2_0 udi_interface ERROR controller:discover: Unsupported device type: FourGroupRemote 2022-08-12 18:12:51,611 ThreadPoolExecutor-2_0 udi_interface ERROR controller:discover: To get support for this device added, please send the following to the developer: 2022-08-12 18:12:51,612 ThreadPoolExecutor-2_0 udi_interface ERROR controller:discover: { "device_id": "11", "current_state": -1, "fan_speed": null, "tilt": null, "zone": null, "name": "Master Bedroom_Shade Remote", "button_groups": [ "9", "10", "11", "12", "13" ], "occupancy_sensors": null, "type": "FourGroupRemote", "model": "CS-YJ-4GC-WH", "serial": 47103566 }

Great! Sorry I somehow missed your previous post. Sent from my Pixel 6 Pro using Tapatalk

Looking at @btreinders errors, it may be a python version issue. Please make sure you have done an 'Upgrade Packages' in the ISY Admin Console before upgrading.

I'll pm you Sent from my Pixel 6 Pro using Tapatalk

Sorry that's unreadable, can you download the log package and PM it to me? Sent from my Pixel 6 Pro using Tapatalk

Any clue in the node server log? Sent from my Pixel 6 Pro using Tapatalk

ELK PG3 NS Issues fixed and 3.4.2 released.

I found an issue with this version where arming and disarming from a program is not working, I will work on a fix today.

The Polyglot Version 3 Node server for ELK Security Version 3.4.7 is released. See the Release Notes Please make sure your Polisy is up to date by running Upgrade Packages in the Admin Console -> Configuration -> System section. See the README for more information, including information on moving from PG2. 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.

All my batteries look fine. Must be a bad batch of batteries? Sent from my Pixel 6 Pro using Tapatalk