kzboray

@someguy If there is no sub directory /August Lock, then then the Node Server (NS) did not install. Here is what the directory contents should look like once the NS is installed. First you will need to figure out what happened to the NS install then go back to creating the necessary .txt file. As for permissions, @larryllix is correct if you fat finger a command or try something your not sure of it can really complicate things. The single command supplied, sudo chown polyglot:polyglot token.txt and when to use it, is necessary for Polyglot to be able to read the .txt file once you put it into the right place. So don't be afraid to use it.

@Techman The problem with using Windows built in SSH is that it requires a bit of added syntax to make things work correctly. By default the user name of the Windows account is used as the log in name during an SSH session. To log into Polisy you need to log in as Admin. To do this here is the command. SSH admin@IP_Addr of Polisy I would highly recommend you setup Putty to use for SSH connections. It's a bit more friendly and you can keep multiple profiles available at a single click.

@brians When you load up the new firmware it is like doing a factory reset to the Z-Wave dongle. I'm pretty sure you will need to re-add your z-wave devices to your Polisy.

@someguy There are a couple of ways to go about this. Probably the easiest is to create the file on your PC using your favorite text editor, then using SCP or WinSCP copy it to: /var/polyglot/nodeservers/AugustLock/ Now you'll need to change ownership of the file from admin to polyglot sudo chown polyglot:polyglot token.txt That should do it.

Yes, I used OTW (Over the Wire, Not OTA Over the Air)

@hart2hart I had to guess at a couple of install steps, but they made sense so things went pretty much per the instructions. The main difference was that when doing the "Install by Technology Type" I selected "32-Bit and Wireless MCU's" Not all. This seems to have worked as I was able to do the update and under "Tools" Z-Wave PC Controller" is an option. Here are the steps I took. These are from memory, so I may have missed a step or two, but this should get you most of the way there. 1.) Register an account with Silicon Labs 2.) Install Simplicity Studio https://www.silabs.com/developers/simplicity-studio 3.) Accept the License and log in using the credentials you created 4.) Click "Install" and Select "Install by Technology Type" 5.) Check "32-Bit and Wireless MCU's" then click "Next" (This will take a few minutes to complete.) 6.) Select "Auto" & Accept the license agreement 7.) Open Simplicity Studio and click on "Tools" 8.) Select "Z-Wave PC Controller" and install the new firmware

One thing I notice that is different is the Tools panel. Mine is fully populated with available selections. Yours seems to be grayed out. Maybe verify you have completed the installation for Simplicity Studio? It took a bit of doing for me to get all the right pieces installed.

@roberthleeii As far as I know the Hubitat PG2 Node Server is the only interface for Zigbee devices and it is limited to one way communications. Others might know of other ways to accomplish this.

I can confirm that the supplied file is indeed for version 7.17.x and I was successful in updating my own S2 700. When queried now it reports 7.17.x and not 7.15.x as it did before I did the update. I wish I could offer more help, but it's the blind leading the blind at this point.

I believe you will get that error when the version of firmware you are installing is the same as what is already installed. Anyway that's what happens when I try to install the same version using Simplicity Studio.

@tbuchber Also if it's the only device being managed by the ISY and you want to eliminate the ISY, you could also do a factory reset on the ISY as well. To be safe please make a backup of your ISY first. 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)

@tbuchber It sounds like you've done everything right to trouble shoot this issue. Sometimes the internal HW of a particular Insteon device can become damaged causing weird behavior. I would suggest you try replacing the switch with a new one. It doesn't happen often, but I've seen others occasionally report errant behavior that can't be fixed with even the air-gap reset. Also if it beeps on all Insteon traffic. It's a great test tool for active Insteon traffic. It won't tell you much, but at least you know when something sends Insteon traffic and if the Insteon network is reaching the location you are testing. I'd keep it around network trouble shooting.

@JoelW One correction to the above. Polisy / Polisy pro both support Z-wave natively with an additional Z-Wave dongle plugged into one of the USB ports on the back. Currently supported Z-Wave dongle is the Zooz S2 stick 700. Zigbee is NOT supported natively, but there is the Hubitat Node Server (NS) in the Polyglot 2 (PG2) store, which I imagine will be ported to Polyglot 3 (PG3) at some point in the future. This NS offers some Zigbee support. A PLM (USB or Serial) is only required for powerline communications with Insteon devices.

@SHM, try httpS://ip_addr of your Polisy. That should get you up and running.

@asbril SSH into your PoliSy and do this.... Check that you have the correct version installed. pkg info pg3 It should be: pg3-3.0.38_1 If it is then simply restart the PG3 server. sudo service pg3 restart If you don't have the correct version, you can install it by. sudo pkg install pg3 sudo service pg3 enable sudo service pg3 start That should get you up and running.

@JTsaoSSH into your Polisy and CD to /var/polyglot/nodeservers. I'm not sure about the NS names but you'll get the idea. rm -r ./Climacell rm -r ./MyQ Make sure that you only delete the directories you don't want the NS for anymore. You will probably need to restart Polyglot for the changes to take effect.

@asbril I don't have much experience with z-wave, but as for how to do what you want with an Insteon sensor and light switch I would use two programs. In this example the sensor turns on the light when active and the light goes off after 5 minutes. You can vary the time to suit your needs. First program: IF motion sensor is active Then Turn on light Run "light timer" THEN PATH Else Turn off light Second program: IF Then Wait 5 minutes Run the first program ELSE

@Teken I have the same. It must be a bug.

@lalang Your Polisy may just have to old an install on it. You can use the following commands to install both MongoDB and ISY on your Polisy. For the older Polisy's that are a bit behind in updates, you can try the following. First: curl -s https://pkg.isy.io/script/update121.sh | sudo bash sudo shutdown -r now Wait for the Polisy to completely reboot, this can take quite awhile (~15min). Now: cat /usr/local/etc/udx.d/static/update13.sh | sudo bash sudo shutdown -r now Once again wait for your Polisy to completely reboot. Your Polisy should now be available in the ISY Launcher.

@Stagehand You might also check that you have a valid DNS server address set. Easy to remember and use DNS servers are 1.1.1.1 | 9.9.9.9 | 8.8.8.8. Login to your Polisy and then go to <Settings / Polisy Configuration> Scroll to the bottom and verify that you have valid DNS servers listed. If they are all 0.0.0.0 change them to what ever you are comfortable with or the suggested server addresses.

@jesusmr Just a thought. I recall something about having to use an older install of Raspbian to allow everything to work. You might try one of the older OS installs here. Maybe 2019?

#2 above will give you a good idea if its the PLM <Tools> <Diagnostics> <PLM Info / Status>, if the PLM is not showing as "Connected", then check the cable between the PLM and your ISY (swap it out with a known good one, standard cat5/6 cable), if the cable is good then unfortunately your in need of a new PLM. That's a whole other conversation.

@JHardy This is what I would do and I am not UDI, but if you like here's a way to rid yourself of a particular NS.You can open an SSH connection to your Polisy using Putty or your favorite SSH tool. cd /var/polygolt/nodeservers/ ls You should now see a list of the installed Node Servers by directory. rm -rf directory_name Warning: If you type in the wrong name it is possible to delete the wrong directory. You may need to now remove the same NS form your ISY. To do this go to your ISY and open the <Node Server> pull and scroll to the bottom. Click <Configure> You should now see a list of installed Node Servers, click on Nest2 and at the bottom of the next dialog box click delete.

@keepersgSomeone else had a similar problem recently and the issue was the age of their Polisy. If you are working with an older (early purchase) Polisy that hasn't been updated recently you can try the following. I assume no responsibility for the results. For the older Polisy's that are a bit behind in updates, you can try the following. First: curl -s https://pkg.isy.io/script/update121.sh | sudo bash sudo shutdown -r now Wait for the Polisy to completely reboot, this can take quite awhile (~10min). Now: cat /usr/local/etc/udx.d/static/update13.sh | sudo bash sudo shutdown -r now Once again wait for your Polisy to completely reboot. Your Polisy should now be available in the ISY Launcher.

@SLP, You will need a z-wave dongle. This is the one UDI is testing with. https://www.amazon.com/gp/product/B07GNZ56BK/ref=ppx_yo_dt_b_asin_title_o06_s00?ie=UTF8&psc=1