kzboray

@Westlake Ventures It will be ID'ed as an ISY. It sounds like your ISY isn't on the network. Do you see the error light and memory light on the front of the ISY blinking? This would indicate the ISY isn't connected to a network. If they are not blinking then, do you have multiple networks? Wifi 2.4MHz and 5MHz. You need your phone to be on the same network to use Fing. Error light and Memory light blinking simultaneously: ISY is not able to get on the network.Please ensure: The Network jack on the back of ISY is connected to your router The lights on the Network jack have one steady on and the other one blinking. If not, check cable and connectivity to the router Your router provides DHCP There are no other devices on the network with the same IP address (IP Conflict) If you have configured your ISY to use DHCP, then you will have to search your network for devices that might be in the same DHCP range as your router is providing If you have configured your ISY with a static IP address, and as long as you have a good backup, you can Factory Reset your ISY and then restore a good backup (File | Restore ISY). Once prompted to change the network settings, choose No

@Westlake Ventures There is a free, ad driven application called "Fing - Network Tools" available for Android phones. Install it then scan your network. It will list the ISY and it's IP.

@DClausen When you start ISY Launcher the UUID will be listed for all located ISY's including IoP's.

UDI years back developed a PLM, but Smarthome reneged on the deal to supply the Insteon chip required. So, design is done. UDI just needs the IP.

I have installed over a thousand Insteon products including switches, dimmers, door sensors, on / off modules, etc in homes all over the bay area since 2005. In that time I've had one switch fail which was my fault (I wired it incorrectly and blew it up). That includes 20 something PLM's without a single failure. The one exception to this is the FanLinc, what a POS. I've had so many fail I've lost count. In the past I simply had Smarthome replace them since they often failed within a year or two. Now I suppose I'll have to figure out how to repair them. Fingers crossed I haven't had one fail in almost two years, but I do have spares on hand for when one does. I'm not sure what I'm doing differently than others who have high failure rates, but I've found the Insteon product line to be very reliable. I do make sure the the ISY / Polisy / PLM's I install are in climate controlled conditions. In closed spaces I install active cooling, but otherwise I'm really not sure why people have such high failure rates.

@brians I'm not sure if you looked over the advanced programming for the Zen32, but it is possible to disable the relay using parameters 19 through 22. Disable / enable control on the relay Parameter 19: Enable or disable paddle on/off control (aka disable the relay). If disabled, you’ll only be able to control the connected light via Z-Wave. Scenes and other functionality will still be available through buttons. Values: 0 – Disable local / physical control (from the button), enable Z-Wave control; 1 – Enable local / physical control (from the button), enable Z-Wave control (default); 2 – Disable local / physical control (from the button), disable Z-Wave control Size: 1 byte dec Relay behavior with disabled local / Z-Wave control Parameter 20: Set reporting behavior for disabled physical control. Values: 0 – report on/off status when button is pressed and change LED indicator status if Parameter 19 is set to value 0 or 2; 1 – DON’T report on/off status when button is pressed and DON’T change LED indicator status if Parameter 19 is set to value 0 or 2 (but the relay will always send central scene command) (default) Size: 1 byte dec 3-way switch type Parameter 21: Choose the type of 3-way switch you want to use with this switch in a 3-way set-up. Values: 0 – regular mechanical 3-way on/off switch, use the connected 3-way switch to turn the light on or off (default); 1 – momentary switch, click once to change status (light on or off) Size: 1 byte dec Enable / disable programming on the relay button Parameter 22: Enable or disable programming functionality on the relay button. If this setting is disabled, then inclusion, exclusion, manual LED indicator change mode no longer work when the relay button is activated (factory reset and scene control will still work) - that means you can now use triple-tap triggers on the relay button for scenes and remote control of other devices. Values: 0 – programming enabled (default). 1 – programming disabled. Size: 1 byte dec ASSOCIATIONS: Group 1: Main button binary switch (Z-Wave) / basic set (button) lifeline to hub Group 2: Main button basic set (pressed only, doesn’t send anything when switch turned on via hub) Group 3: Main button multilevel (held) Group 4: Small button #1 basic set (pressed) Group 5: Small button #1 multilevel (held) > in sequence > held = increase brightness, release = stop level, held = decrease brightness, release = stop level Group 6: Small button #2 basic set (pressed) Group 7: Small button #2 multilevel (held) > in sequence > held = increase brightness, release = stop level, held = decrease brightness, release = stop level Group 8: Small button #3 basic set (pressed) Group 9: Small button #3 multilevel (held) > in sequence > held = increase brightness, release = stop level, held = decrease brightness, release = stop level Group 10: Small button #4 basic set (pressed) Group 11: Small button #4 multilevel (held) > in sequence > held = increase brightness, release = stop level, held = decrease brightness, release = stop level But it remains a PITA having to write programs for every conceivable on/off of each button press.

@JimboAutomates Is there a way to control each zone independently? The KL420 series supports up to 50 zones, but I don't see a way to control them from the NS. What did I miss?

@Athlon & @bpwwer Also not able to access PG2 store. Last night I went to check for something in the PG2 store and my Bitdefender AV software flagged the URL. I created an exception and was still unable to access the PG2 store. I then checked PG3 and had the same AV issue, created another exception and was able to access the PG3 store with no issue. PG2 remains unavailable. It's possible the URL I marked for exception in my AV software is wrong, but when I disable my AV software I am still unable to access the PG2 store. This leads me to believe it might be on the server side, but it's also possible it's on my PC side. Whats weird is that I've never had to create an exception in my AV software for any of the UDI sites until last night.

@tlightne You might try entering the Polisy Address manually in Launcher. Click Add then enter the following. Using your local IP address for the Polisy http://ip_addr:8080

@Wes Westhaver If you are referring to the two overly bright red LED's on the fanlinc unit itself I don't believe there is control of those available via the fanlinc's firmware, so UDI can't expose a non-existent function in the GUI. I personally just put some black electrical tape over them once I'm done configuring the fanlinc's.

@brians I can confirm your Zen32 is working the same as the one I have. It is my belief that this device is specifically designed to work with other controllers. I need to try it out with Home Assistant, and from what I have read it works really well with Hubitat. As for IoP or the ISY994, it's going to require multiple programs and variables.

@oskrypuch If you are doing this remotely, I've had this issue as well. You might have better success dong it locally (on the same LAN as the ISY) Other wise the only thing I can think of to try would be to give things a bit more memory. -Xms1024m instead of Xms512m. If neither of those work, then I'd open a ticket with UDI, they will get you sorted.

@Carey737 If you have a PG2 Polyglot server it's possibly your camera might be supported by the "Camera" or "Camect" Node Servers. Alternatively you could setup a BlueIris server and then use the "BlueIris" Node Server in PG2. I would expect to see this available in the future on PG3 as well.

@davbow & @Techman This is a known oddity. Here's my Polisy. 5.4.1

@ssalzman You should refer to the release notes found here. https://forum.universal-devices.com/topic/33287-534-update-for-isy994-july-30-2021/ Here's the section that is specific to your issue. Sometimes all you need to do is open Programs then select each program in the left hand table, then click on the right hand table anywhere in the program. This should bring up the three buttons on the bottom. Click update and move to the next program and repeat. For battery operated devices you will need to wake them manually first.

I just played with my Volumio a bit and found that the Volumio Phone app has a bug. It incorrectly reflects the status of "Shuffle" in real time. Pressing the Volumio shuffle icon actually toggles shuffle in AC and I assume in Volumio as well because as soon as there is a refresh of the screen either due to a new song starting or the user changing to a different app/screen and then back, the icon correctly shows the "Shuffle" status on on the phone app. I was not able to reproduce the Stop / Pause issue reported. My AC correctly shows the status of Play / Pause / Stop with one caveat. When pressing the next song icon on the phone app, AC first reports "Pause" then immediately reports "Play." Volumio Primo 3.233 Volumio Mobile App 1.1 ISY994i 5.3.4 PG2 Volumio NS 1.0.2

@KCrater I use a Smartenit EZIO2X4 that works well with the ISY994i, I haven't moved it to IoP yet so I can't say if there will be any issues with IoP. https://smartenit.com/shop/ezio2x4/

@JNaccarato If you can access the switch from the admin console, then you can see the Insteon address right in the console. I guess I don't understand the problem well enough. What version of ISY are you using? Is this on an ISY994i or IoP? What changed that you need the Insteon address of this device if it is working? What do you mean by, not sync'ing? Do you mean the switches status isn't updating when you use UD Mobile?

@JNaccarato If you can't locate the device address from the label and auto discovery isn't working, the next thing to try is to factory reset the switch. Typically this can be done by pulling gently (I use a small screw driver) the small de-dented button in the center bottom of the switch, between the switch paddle and the rim. It will come out about 1/8" and you will see the switch indicator light go off. Wait 30seconds and press it back in and hold it in until the switch emits a steady beep. This will factory reset the switch. At this point you can try auto discovery again. It should be found. If it isn't then there is either a communications issue, noise on the AC line, or the switch is potentially bad. If you have another switch, you can try swapping locations to eliminate both problems. If it's noise, you will have the same issues with the working switch you use to test with, if it's a bad switch the test switch will work fine.

@telljcl Try this. locate the small pin hole on the front of the Polisy and press it once, then sit back and wait at least 20 minutes. Try logging in again. I have a hunch the update didn't finish, this process may allow the update to finish properly.

I am running a few TEST z-wave devices on a isolated Polisy. This is not real world testing and certainly has not past the wifey test. The most notable difference is a speed improvement of response from my Zooz ZEN32 switch. It's almost instant and I can toggle it on and off as fast as I can click my mouse. The Aeotec Smart Switch 7 is still a half second delay in response and takes a full second to toggle back and forth. No change from previous FW. So very limited testing seems to indicate better performance with Zooz products in the 700 family.

Firmware 7.17.2.406 update process changes. If you are going to install this version of Firmware and you have not recently updated Simplicity Studio, do that FIRST! After doing all updates there is a process change in updating the firmware. Previously you would select Tools/OTA to update the firmware, now you use Tools/OTW, then select the correct firmware file and the update should start automatically. It was NOT necessary to do NVM Backup/Restore. No data was lost during the firmware update. A simple reboot of the Polisy [admin@polisy ~]$ sudo shutdown -r now And everything was back working with the updated Zooz stick.

Link to 7.17.2.406 Firmware for Zooz ZST10 700 Stick ONLY https://github.com/SiliconLabs/gecko_sdk/blob/gsdk_4.0/protocol/z-wave/Apps/bin/gbl/ZW_SerialAPI_Controller_7_17_2_406_ZGM130S_REGION_US.gbl?raw=true

@telljcl There is an excellent guide written by @dbwarner5 for migration from the ISY994i to the IoP (ISY on Polisy) here. I'd read this and then ask any questions you might have in the migration thread at: https://forum.universal-devices.com/topic/34617-migration-to-isy-on-polisy-an-attempt-to-collect-organize-and-share-simplified-directions/ Because of the age of your Polisy you may run into issues doing the initial Firmware update. You can try the instructions contained in the above guide, but I suspect you will need to do the following only for the first firmware update. After the first time you can use the update option in the web GUI.

@jjc60631 OK Make sure to clear your java cache after that the only thing I can think of is antivirus or windows defender blocking the launcher. I've never heard of that, but there is always a first.