kzboray

As a long time user of the LifX NS's going back to the original PG1 I have a love hate relationship with this NS. It is actually still working if you set it up correctly.

1.) In AC go to configuration and click the Install Dev Packages button. This can take a long time to finish 20 minutes or longer depending on the platform you are using. Polisy or eISY
2.) Install the LifX nodeserver, if it is already installed delete it and reinstall it from scratch.
3.) Create a devlist.yaml that includes all your LifX devices, and groups. While this is optional, it provides the best results in usability.
https://forum.universal-devices.com/topic/40737-devlistyaml/#comment-362430
4.) Configure the LifX NS to use the devlist.yaml and restart the NS.
In Custom Parameters add a key of Devlist and a Value of the location where you put the devlist. The easiest place to put it is in the admin home directory. In that case the value would be /usr/home/admin/devlist.yaml
5.) Update all your programs/scenes with the new devices created per the devlist vs discovery.

I will also share with you that if you open a ticket with UD Micheal will do his best to help you get it working. Michael has always been extremely helpful anytime I opened a ticket.

https://www.universal-devices.com/contact-us/

 

=============Update=============
1/21/2022
This has been resolved. Use the following to install the necessary bitstring dependency on Polisy
sudo -u polyglot bash pip3 uninstall bitstring pip3 uninstall --prefix /var/polyglot/.local bitstring pip3 install --prefix /var/polyglot/.local bitstring==3.1.9 Use the following for the eisy
sudo -u polyglot bash pip3 uninstall bitstring pip3 uninstall --prefix /var/polyglot/pg3/ns/0021b9026038_7/.local bitstring pip3 install --prefix /var/polyglot/pg3/ns/0021b9026038_7/.local bitstring==3.1.9 ================================================================================================
If you rely on the LifX NS you may want to hold off on updating to 5.5.4 until a fix is found for the NS's failure to discover devices after update.
@xKing suggested patch:
 
sudo -u polyglot bash pip3 uninstall bitstring pip3 install bitstring==3.1.9
Unfortunately this did not work on Polysi.

@edwaud TPM is short for Trusted Platform Module. It is a cryptographic device (hardware) that is becoming more and more prevalent in all manner of tech. It makes hacking of a device so equipped, much more difficult.

I just skipped over a lot of really important information and summarized in a not quit technically correct way, but that's the jist of it. It keeps your eisy safe.

@TRI0N https://www.universal-devices.com/docs/ZMatter-Assembly- Instructions.pdf

@3jtexas Auto DR should not be removed, nor do I believe it can be.

AutoDR is Automatic Demand Response. Where supported, it allows the utility (power company) to send a message that the ISY would react to by turning off heavy loads during peak times. There is likely more to it but that is my understanding. The AutoDR scene I believe is where you would place the "Heavy Loads" that should be turned off on request.

@Dan Torbeck
Factory Reset
There are only a very few reasons for performing a Factory Reset:
Corrupted File system (blinking ERR light) Also instead of a factory reset another option for corrupt file systems issues is Replacing/Formatting an SD Card To start fresh ... i.e. if you are going to restore your old backup on the same ISY, then in all likelihood factory reset is NOT going to fix anything Reuse one ISY for more than one location You have configured your ISY with a static IP address, changed router/network, and can no longer access ISY IMPORTANT: You must reconfigure ISY again or restore your backup after the factory reset.
Use a sharp object to push in the Reset Button till the RX, TX, Mem, Error lights start blinking (every second) Hold for at least 30 seconds until all of the the RX, TX, Mem, Error lights turn off and Mem light starts flashing quickly Release and wait for system reboot (reboot is complete when Mem light stops flashing) You may wish to also reset the PLM at this time. 2412S Quick Start Guide

I don't have access to a mini-remote atm, but if you manually link it to a device that has been added to AC, you should then be able to see the min-remote address in AC. After linking them manually, I would recommend you factory reset both devices and instead re- link them in AC.

Manual Linking:
1) Tap Mini Remote scene button of choice
2) Press and hold Mini Remote set button until it beeps
Mini Remote LED will start blinking green
3) Turn responder on (or any other state such as on 50% or even off)
4) Press and hold responder set button until it double-beeps
Mini Remote will double-beep and its LED will stop blinking
5) Test by tapping Mini Remote scene button just programmed
Responder load will respond appropriately

Often times surge protectors also filter line noise. Unfortunately line noise and Insteon signaling look a lot alike to filters. Your best bet is to try one and see what happens.

@JSchumann You will need to update your ISY994i to 5.3.4 which supports TLS 1.2.

The 5.3.4 Update is now available for the ISY994 product.
Notes:
  -  SSLv3 is now disabled. All models now support TLS1.2 and high grade cipher suites
  -  4.1.1 backups may corrupt Z-Wave configuration in case they are restored. 4.1.2 and above releases fix this issue
-  See our Wiki for additional information (e.g. Program Variables)

Please follow the upgrade instructions on the 5.3.4 page.