kzboray

I recently picked up a couple of z-wave devices for testing; a Zooz32 and an Aeotec Smart Switch 7. The Zooz32 manual says it supports Associations: But I can't find any way to access them from IoP. I suspect that the Z-wave specification for "Associations" is fluid and each manufacturer may put their own spin on exactly how it works making interoperability rare. Or it's possible there is still some work that can be done with z-wave functionality on IoP. But at this point I feel that "Associations" are the mythical unicorn. This is all my opinion and I have no official knowledge of any of what I said. It's just based upon my personal experience and others comments about their experiences with z-wave. Your results may vary. I miss the days of plug and play with Insteon.

@brians try posing on this thread instead. it's specific to UD mobile. https://forum.universal-devices.com/forum/24-ud-mobile/

@asbril I don't believe your update was successful. SSH into your Polisy and check the version of udx: [admin@polisy ~]$ pkg info udx udx-2.6.0 Name : udx Version : 2.6.0 Installed on : Tue Mar 1 00:11:40 2022 PST Origin : misc/udx Architecture : FreeBSD:13:amd64 Prefix : /usr/local Categories : misc Licenses : Maintainer : michel@universal-devices.com WWW : https://www.universal-devices.com/ Comment : Polisy Admin Service Annotations : FreeBSD_version: 1300139 repo_type : binary repository : udi Flat size : 13.3MiB Description : UDX HW/Admin Service for Universal Devices Polisy It should be 2.6 Also you can check your version of ISY installed: [admin@polisy ~]$ pkg info isy isy-5.4.0 Name : isy Version : 5.4.0 Installed on : Tue Mar 1 00:11:41 2022 PST Origin : misc/isy Architecture : FreeBSD:13:amd64 Prefix : /usr/local Categories : misc Licenses : Maintainer : michel@universal-devices.com WWW : https://www.universal-devices.com/ Comment : ISY Port to Polisy Annotations : FreeBSD_version: 1300139 repo_type : binary repository : udi Flat size : 14.1MiB Description : ISY Service for Universal Devices Polisy It should be 5.4 If one or both of these isn't correct do the following: sudo pkg update sudo pkg upgrade Now check your versions of udx and isy again. If they still show older versions do this: sudo service udx restart sudo service isy restart That should get you up to date, but you will probably still need to update to UEFI from BIOS. If the front panel left most light facing the front is flashing non-stop, push the front panel hidden button 6 times sequentially. Please give the system time to update, this can take 15-20 minutes. Now your all set!

Updated, no issues with the update. Testing to follow.

@lilyoyo1 Yes I updated to 7_17_1_344. These are real world tests, not open air. I'm sure I could get better distance if I moved the stick higher and away from all metal, but I prefer to be realistic about performance and test things in the way they would actually be used.

@mmb The slow response time was due to the distance from the IoP z-wave stick and having no other z-wave devices to repeat the signal. I was surprised it worked at all given I only had 2 z-wave devices on the entire mesh.

Just wanted to test out a ZEN32 (z-wave 700) for it's scene capabilities. While it doesn't support native z-wave scene control, it is very similar to, but not as flexible as a 6-button Insteon controller. Each of the five buttons is individually programmable. I used the word programmable because you can only access the 4 scene buttons through programs! Their functions are not available via the buttons themselves. The five buttons shown as controller buttons (top red box) 10,2,4,6,& 8 and can only be queried. The same is true of the group of the same buttons. Buttons 1,2,3,4, & 5 (bottom red box). Why they are split into two groups I don't know. You can't make any changes to any of them except through programs. Only the button labeled as binary switch (green box) can be controlled directly or added to a scene. The other four have to be controlled via programs. The larger button can control a load as well. There are a few parameters that you can change mostly dealing with the LED indicators on each button. You can set their color to red, green, blue, or white and change their intensity to high, medium, or low. You can also set them to come on when the switch is on, or on when the switch is off, always on, and always off. Range seems to be decent. I put it on my test Polisy which only has two devices on it atm. I was able to move it downstairs and it worked OK, response times could sometimes be in seconds, but it worked. 30' with one wall proved to work well, anything more than that and I would need a better mesh. With only 2 devices this is truly a test bench scenario. Each button allows you to capture double tap, triple tap, quadruple tap and even quintuple tap actions. Although I doubt anyone would remember all of that. You can also capture press and hold (fade up.) Overall it has possibilities, but without native scene support in my mind its limited. I only tested with IoP. I did no testing via Home Assistant or any other controller. Results might vary.

Not trying to rush anyone I know you are all working hard on PG3. I'm just curious if the LifX NS is on someone's radar to port from PG2 to PG3.

@Jimbo & @DennisC you might have RP2 open as well. The Elk can only have one IP connection at a time. Make sure RP2 is closed and that may solve your connection issue.

@someguy Ha sorry about that. I was giving you instructions for PG2. PG3 is a bit different. You will want to put your TOKEN.TXT file in /var/polyglot/pg3/ns/00:01:b9:xx:xx:xx_xx Where 00:01:b9:xx:xx:xx_xx is the address of your IoP and slot number for the NS.

@Techman it should be port 22, port 22 by default is the telnet protocol. I'm not sure why you can't enter anything from the keyboard. Just for a test can you install Putty, link is above and see if that works?

@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.