kzboray

@Bumbershoot Yes! Using devlist.yml was a good solution, but unfortunately it's no longer an option as the new NS directories are locked down and you can't change, add to or delete files.

I've been using the lifX NS since it was first Introduced. It has always been flaky but recently it has become almost unusable. This seems to be the problem. 2023-12-25 11:05:51,591 Thread-4 udi_interface ERROR lifx-poly:_discovery_process: discovery Error: WorkflowException: Did not receive [<class 'lifxlan.msgtypes.StateVersion'>] from d0:73:d5:32:89:b6 (Name: None) in response to <class 'lifxlan.msgtypes.GetVersion'> On startup of the node server during discovery inevitably this error will occur. It happens at different points during startup and for different bulbs (MAC addresses) with each restart; sometimes even prior to any bulbs being added. If the NS has found 10 bulbs and is adding them and this error happens on the second bulb that's it. Additional bulbs fail to be added. It always seems to occur early in the bulb addition process. Restarting the NS time after time will eventually result in a clean start, but it sometimes takes 30 restarts to get that one good time, and the minute I need to reboot for a system update etc. it's a nightmare to get the LifX NS running again. Any suggestions? System Configuration: *** OS *** FreeBSD polisy 13.2-RELEASE-p4 FreeBSD 13.2-RELEASE-p4 releng/13.2-n254638-d20ece445acf POLISY amd64 *** Package Information *** udx-3.5.4_4 ---- Name : isy Version : 5.7.1_7 LiFX Current Status: Connected Current Version: 2.1.26 [Production] Startup Log: 2023-12-25 11:20:32,347 Command udi_interface.interface INFO interface:_handleInput: Received stop from Polyglot... Shutting Down. 2023-12-25 11:20:32,350 Thread-37 udi_interface INFO lifx-poly:stop: Stopping LiFX Polyglot v2 NodeServer version 2.1.26 2023-12-25 11:20:37,943 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2023-12-25 11:20:37,946 MainThread udi_interface INFO __init__:<module>: UDI interface initializing 2023-12-25 11:20:37,947 MainThread udi_interface INFO __init__:<module>: User=000db9560fac_3 2023-12-25 11:20:37,948 MainThread udi_interface INFO __init__:<module>: Home=/var/polyglot/pg3/ns/000db9560fac_3 2023-12-25 11:20:37,949 MainThread udi_interface INFO __init__:<module>: Node Server Path=/var/polyglot/pg3/ns/000db9560fac_3 2023-12-25 11:20:37,949 MainThread udi_interface INFO __init__:<module>: PG3INIT=eyJ1dWlkIjoiMDA6MGQ6Yjk6NTY6MGY6YWMiLCJwcm9maWxlTnVtIjozLCJsb2dMZXZlbCI6IklORk8iLCJ0b2tlbiI6Ik4qSTl3NSVzKEdEbEsyZDciLCJtcXR0SG9zdCI6ImxvY2FsaG9zdCIsIm1xdHRQb3J0Ijo4ODgzLCJzZWN1cmUiOjEsImlzUEczeCI6dHJ1ZSwicGczVmVyc2lvbiI6IjMuMi4xNyIsImlzeVZlcnNpb24iOiI1LjcuMSIsImVkaXRpb24iOiJGcmVlIn0= 2023-12-25 11:20:37,950 MainThread udi_interface INFO __init__:<module>: Loading interface module 2023-12-25 11:20:38,355 MainThread udi_interface INFO interface:<module>: Loading MQTT module 2023-12-25 11:20:38,590 MainThread udi_interface INFO interface:<module>: MQTT module loaded 2023-12-25 11:20:40,633 MainThread udi_interface INFO __init__:<module>: Loading udi_interface module 2023-12-25 11:20:40,639 MainThread udi_interface INFO __init__:<module>: Loading node module 2023-12-25 11:20:40,640 MainThread udi_interface INFO __init__:<module>: Loading custom module 2023-12-25 11:20:40,641 MainThread udi_interface INFO __init__:<module>: Loading isy module 2023-12-25 11:20:40,642 MainThread udi_interface INFO __init__:<module>: UDI interface initialized 2023-12-25 11:20:40,642 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.2.4 Starting... 2023-12-25 11:20:41,068 MainThread udi_interface.interface INFO interface:__init__: Initialization received from Polyglot V3 3.2.17 [ISY: 5.7.1, Slot: 3] 2023-12-25 11:20:41,070 MainThread udi_interface.interface INFO interface:__init__: Connect: Network Interface: {'addr': '10.0.0.241', 'netmask': '255.255.255.0', 'broadcast': '10.0.0.255'} 2023-12-25 11:20:41,073 Interface udi_interface.interface INFO interface:_startMqtt: Connecting to MQTT... localhost:8883 2023-12-25 11:20:41,078 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version 2023-12-25 11:20:41,079 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 000db9560fac_3.cert key: 000db9560fac_3.key ca: /usr/local/etc/ssl/certs/ud.ca.cert 2023-12-25 11:20:41,080 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: lifxctl not found in database. 2023-12-25 11:20:41,083 MainThread udi_interface.interface INFO interface:addNode: Adding node LiFX Controller(lifxctl) [None] 2023-12-25 11:20:41,178 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2023-12-25 11:20:41,182 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:0d:b9:56:0f:ac_3 - MID: 2 Result: 0 2023-12-25 11:20:41,228 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2023-12-25 11:20:41,431 Thread-2 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-12-25 11:20:41,437 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Starting LiFX Discovery thread... 2023-12-25 11:20:41,573 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-12-25 11:20:41,626 Thread-6 udi_interface INFO lifx-poly:start: Starting LiFX Polyglot v2 NodeServer version 2.1.26, LiFX LAN: 1.2.7 2023-12-25 11:20:41,627 Thread-6 udi_interface.interface INFO interface:updateProfile: Sending Install Profile command to Polyglot. 2023-12-25 11:20:41,854 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2023-12-25 11:20:41,933 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': '<h1>UDI LiFX Poly</h1>\n\n<p>This is a simple integration of LiFX lights to ISY994i. Please install via <a href="https://github.com/UniversalDevicesInc/polyglot-v2">Polyglot v2</a> Store. Report any problems on <a href="https://forum.universal-devices.com/topic/19021-polyglot-lifx-nodesever/">UDI User Forum</a>.</p>\n\n<h3>Custom parameters supported:</h3>\n\n<ul>\n<li><code>devlist</code> - link to a YAML manifest of devices, skips automatic discovery. See <a href="https://forum.universal-devices.com/topic/19021-polyglot-lifx-nodesever/?do=findComment&comment=257145">this post</a>.</li>\n<li><code>change_no_pon</code> - change of color won\'t power the device on.</li>\n<li><code>ignore_second_on</code> - power on command will be ignored if device is already on.</li>\n</ul>\n'} 2023-12-25 11:20:41,977 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2023-12-25 11:20:51,287 Thread-4 udi_interface INFO lifx-poly:_discovery_process: 14 bulbs found. Checking status and adding to ISY if necessary. 2023-12-25 11:20:51,633 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found Bulb: LIFX Chand-4 Mini 3D8961(d073d53d8961) 2023-12-25 11:20:51,636 Thread-4 udi_interface.interface INFO interface:addNode: Adding node LIFX Chand-4 Mini 3D8961(d073d53d8961) [None] 2023-12-25 11:20:51,966 Thread-4 udi_interface INFO lifx-poly:_discovery_process: Found LiFX Group: Chandelier 2023-12-25 11:20:57,833 Thread-4 udi_interface ERROR lifx-poly:_discovery_process: discovery Error: WorkflowException: Did not receive [<class 'lifxlan.msgtypes.StateVersion'>] from d0:73:d5:51:9c:71 (Name: None) in response to <class 'lifxlan.msgtypes.GetVersion'> 2023-12-25 11:20:57,835 Thread-4 udi_interface INFO lifx-poly:_discovery_process: NOTICE: Bulb count 1 is different, was 0 previously 2023-12-25 11:20:57,836 Thread-4 udi_interface INFO lifx-poly:_discovery_process: LiFX Discovery thread is complete. 2023-12-25 11:20:58,066 MQTT udi_interface.interface INFO interface:_message: Successfully set lifxctl :: GV0 to 1 UOM 56 2023-12-25 11:21:07,755 MQTT udi_interface.interface INFO interface:_message: Successfully set d073d53d8961 :: GV1 to 45800 UOM 56 2023-12-25 11:21:07,840 MQTT udi_interface.interface INFO interface:_message: Successfully set d073d53d8961 :: GV2 to 65535 UOM 56 2023-12-25 11:21:07,877 MQTT udi_interface.interface INFO interface:_message: Successfully set d073d53d8961 :: GV3 to 65535 UOM 56 2023-12-25 11:21:07,917 MQTT udi_interface.interface INFO interface:_message: Successfully set d073d53d8961 :: CLITEMP to 9000 UOM 26 2023-12-25 11:21:08,044 MQTT udi_interface.interface INFO interface:_message: Successfully set d073d53d8961 :: ST to 0 UOM 51 2023-12-25 11:21:08,086 MQTT udi_interface.interface INFO interface:_message: Successfully set d073d53d8961 :: GV5 to 1 UOM 2 2023-12-25 11:21:08,147 MQTT udi_interface.interface INFO interface:_message: Successfully set d073d53d8961 :: RR to 0 UOM 42

@david-4 I'd suggest you open a support ticket for this question. If your router isn't setting the DHCP address via a DHCP reservation then Michel's merry band of elf's will need to sleigh this beast.

@K-bert Try changing the URL to https://xxx.xxx.xxx.xxx:3000/ where xxx is the IP address of your eisy.

@BGage You have to use adjust scene for each switch in the scene. I wrote a how to a while back for setting up automated brightness changes by time of day. It talks a lot about adjust scene and how to use it correctly. Take a look at it and I think it will fix your problems. How to setup automated brightness changes

Here's the link for a thermostat. https://www.nuheat.com/products/thermostats/home-thermostat This is supported via the ST-NuHeat Nodeserver in the production store.

@oskrypuch Honestly the worst case scenario is that you have all your programs disabled and simply restart IoX to fix it. It's an extra step, but not catastrophic should things go wonky.

@AllDigital You can setup a duress user. I often use 5150 as the code. In this example it's user 32 which is set as duress in Area RC and User RC. That gets the alarm company on board and while I haven't tried it. I bet you can activate that code or user from the Elk NS. I don't have access to an ELK NS atm to try, but this is how I'd set it up.

Updated from PG3x 3.2.8 to 3.2.9 on a Polisy Pro. All Programs where marked as disabled and had to be manually re-enabled. No other issues noted at this time.

AC upgrade Packages. I haven't used SSH since 5.5.x

Upgraded Polisy IoX 5.7.0, PG3x 3.2.4, OS 13.1 to IoX 5.7.0, PG3x 3.2.8, OS 13.2 Took about 5 minutes with two reboots that happened automatically. No issues on restart.

@bmercier Thank you! You got it in one. Disabled VPN and no more 406.

PoliSy Pro PG3x 3.2.28 IoX 5.7 I've tried on two different Polisy both up to date and they both give a 406 error when I click the authenticate button.

I wasn't clear, that was my fault. You can only use ONE IP address at a time to access the Elk, however you can run multiple sessions via it's non-secure PORT. Ports and IP address are very different in terms of how they can be accessed. If you want more information on this do a search for "OSI model." TCP/IP communications is handled at layer 3, while ports are handled by layer's 4 & 5. Each layer relays on the layers before it. So you can have only one IP address at layer 3, but on top of that you can stack all kinds of ports that access via that one IP address. There are 1024 "Well Known Ports" i.e. port 25 (POP), port 80 (HTTP) etc. These are off limits for devices for obvious reasons, but ports above 1024 are available. Some of these have been defined by manufactures for their equipment as in the case of Elk with their use of ports 2101 and 2601. Don't confuse ports with IP's, they are very different things. In every day terms, every device on your network has to have it's own unique IP address. If you accidentally assign the same IP to multiple devices, bad things will happen so for that reason and NAT addressing, DHCP is used in most networks to handle IP address assignments.

@keepersg You may be running into simple IP communications problems. The Elk can only connect to one device at a time. So if it's connected to something other than the eisy that may be the problem. Same thing applies to RP2. When you are connected via RP2, the Elk NS won't be communicating with the panel.

Update on Polisy running 5.6.4. Opened AC <Config><Upgrade Packages> Polisy beeped after about 5 seconds, then 10 seconds later beeped again with a different tone. Approximately 1 minute later I heard 5 beeps and then a single beep signalling the reboot. Cleared Java et all downloaded the new start.jnlp and started AC. AC started but complained that the version of AC and the version of IoX did not match and asked to reboot the Polisy again. I clicked reboot and about 30seconds later the Polisy was up and running 5.7.0 and I was able to access it via SSH and AC. No disabled programs The OS did NOT update from 13.1 to 13.2 at that time. Clicking on <Upgrade Packages> from 5.7.0 A dialog box came up indicating that an OS update was available and it would take approximately 30 minutes to complete. That update is running now. STATUS UPDATE: The update of the OS did not complete. Tried three times. Opened a ticket with UD. I will update as more information is available.

@GTench please DM Chris as the instructions say to do. You can also open a support ticket.

@GTench

I had an unusual issue following 5.6.4_6/7 snafu. We know that one or more versions of 5.6.4 caused a weirdness with sockets that resulted in system files being corrupted. If you had a backup all you had to do was update to 5.6.4_8 dated 8/11/2023 and then restore your system which I did, but a couple of programs would not work post restore. I tried for hours to figure out why the devices in the associated scenes / programs could not be controlled by AC, but worked fine from UD Mobile. Finally I just deleted the programs that didn't work and starting from scratch rewrote them exactly as they had been. This fixed the problem. So if you have any weirdness post 5.6.4 with your programs, I'd try that as a solution.

@pinlawr Based upon @Rick Kacel post above, you might open AC go to <Config><System> and click <Install Dev Packages>. This can take quite some time as I recall. Up to 20 minutes so wait patiently for your Polisy to beep five times and then reboot followed by a single beep. If that fails I'd go ahead and open a support ticket with UD support. They will need to take a look at whats going on.

@Rick Kacel sounds like you're half way there! Go ahead and open a support ticket with UD at https://www.universal-devices.com/my-tickets/ Changing permissions is something I'd prefer UD walk you through. And if you would be so kind as to post the fix, we can use it to help others in the future.

@CoolToys, it's important to understand that not only did you change hardware but you also changed from a dedicated ISY Elk Module to the new ELk Polyglot Node Server (NS) which replaces the older ISY Elk Module. On eisy there is no longer any module support so that is why you need to purchase and install the new Elk NS before you can do anything. I believe from the last line of your post that you have done this. If not, then open your web browser and type in https://your_eisy_IP:3000. This will start the Polyglot server interface. You will be promoted to sign in if you haven't already. The default user is <admin> and the default password is also <admin> if you have changed the password in AC then you should use that password instead. Now that you are logged in you will need to click on <Node Server Store> Top menu. Then scroll down to Elk and click on the name Elk on the far left. Now find the button labeled <More Info> and click on that. Now you need to read all of this thoroughly. You should also check out the Elk NS Configuration Help section. Use this link as the one on the above page is broken ATM. Now that you have some idea of what the Elk NS can do, it's time to change every single program that used the older Elk Module on your ISY manually. There is no migration available for this complex Elk update, you have to manually update each program for the new Elk NS commands that replace the older ISY Elk module. If you don't have copies of your old ISY programs this is going to be difficult. Hopefully you have that information available. If not you will need to rebuild from scratch all your programs that used to talk to the ISY Elk Module. A quick way to see which programs are broken is to start AC and then go to <Programs><Details> and click the small + button on the top ribbon. Every program that is broken will be shown with a yellow icon. These are the ones you need to look at and rebuild. As far as the MSII's they are not part of the Elk setup nor were they ever. Recently there was a post about the MSII's no longer being found by IoX on eisy. I don't have any verification of this as I don't use MSII's and no longer have any to test with. The recommendation I saw posted was to migrate to a supported z-wave device like the Aeotec MultiSensor 6. https://aeotec.com/products/aeotec-multi-sensor-6/ The newer MultiSensor 7 was not recommended by the posters. Your call. If you find the MSII is indeed not being discovered by IoX on eisy then you can also open a support ticket at... https://www.universal-devices.com/my-tickets/

For the eisy you need to use: You will need to use putty or something similar to access the eisy via SSH. You can log in with the user name <admin> and the password <admin>, then just copy and past the lines below one at a time and hit <enter> after each one. On the first command you will be promoted for password; use <admin> again. sudo -u polyglot bash pip3 uninstall bitstring pip3 uninstall --prefix /var/polyglot/pg3/ns/0021b90260e8_2/.local bitstring pip3 install --prefix /var/polyglot/pg3/ns/0021b90260e8_2/.local bitstring==3.1.9 Note that the directory /0021b90260e8_2/ may need to be changed for your installation of the LifX NS. Look at your Polyglot dashboard and find the LifX NS slot number; in your case slot 2, then open putty and <cd> to /var/polyglot/pg3/ns. Then type <ls> you will see a list of NS by slot number, cut and past the correct NS name into the above command lines replacing /0021b90260e8_2/ in both lines with your specific NS name. I have updated the above command for the NS listed in the output you supplied, but if something has changed you will need to verify it first.Be sure to use the correct one. When you type <ls> you should see an output similar to the below with more or less directories depending on your particular setup. Just find the NS with a name ending with the proper slot number. [admin@polisy /var/polyglot/pg3/ns]$ ls 000db9560fac_1 000db9560fac_11 000db9560fac_3 000db9560fac_5 000db9560fac_7 000db9560fac_9 000db9560fac_10 000db9560fac_2 000db9560fac_4 000db9560fac_6 000db9560fac_8 You will need to restart Polyglot after you install Bitstrng 3.1.9. You should then see device discovery working. If not open a ticket with UD as the problem is not Bitstring.

@Rick Kacel Sorry mate, but we need a lot more information before any help can be offered. What platform are you on? ISY w/RPi. Polisy, or eisy, and what versions of firmware are you running? A log of the NS output would be especially nice. Please change it from INFO to DEBUG and then do a restart so we can see what is happening in more detail.

@pinlawr You may be running into the btistring problem from awhile back. Check and see if the module that's not loading is bitstring. The version of bitstring that the LifX NS relies on is old and since no one is maintaining the NS you'll need to down rev the module being called. Here are the commands to do that. sudo -u polyglot bash pip3 uninstall bitstring pip3 uninstall --prefix /var/polyglot/.local bitstring pip3 install --prefix /var/polyglot/.local bitstring==3.1.9 Restart the LifX NS from the web interface and you should be good to go. I don't recall having to reboot the Polisy, but if you have problems after this I'd give that a shot before you get back to us.