brians

I agree that it was UDI's effort with their ISY that actually brought some stabilization to Insteon owners such as myself, being an early adopter from the beginning, with all the different revisions throughout the years.

I have a three or four of those working but haven’t changed since 5.5.3 so maybe is a bug ? Therefore I don’t want to exclude them to test. I do have a spare dimmer version DZPD3 which is basically same thing but a dimmer, and I just successfully excluded and included it again no problem on v5.5.3. Were those DZPA1 working for you on v5.5.2 and this problem was just introduced in v5.5.3? Are you excluding/including on the Leviton by pressing the button for several seconds until it flashes red, then let go and press once? I do like the DZPA1's and nobody really seems to make a unit as nice for the price. Being typical Leviton, they don't support instant status. Since they are not really designed to be a controller where you would switch on/off locally I have never missed this - I never would turn on the device local by reaching down to the plug and pressing the button. They do support hail if this is necessary to get status, but with ZMatter this is broken for now.

I tried this and works good. On my Zen71 I had to set parameter 9 to 1 which enables scene buttons then it started working. I set button 1 command to on and button 2 command to off for an Insteon switchlinc. I found most other nodes have to be set to ignore the scene buttons otherwise the scene buttons may turn on devices you don't want on. One can even make old style pre-zmatter slower zwave scenes this way which go through the IoX controller (ie. central scene) instead of using basic associations (which are direct switch-to-switch) if need to for whatever reason - maybe an older zwave device want to turn on/off from another that doesn't support direct accociations. I recommend using basic association between Z-Wave devices wherever possible since it is much faster - in a virtual 3-way test, is as fast as Insteon on my Zen71s (other ZWave brands/models may vary). When controlling Insteon from Zen71, as describe previously using scene buttons, it is slower than insteon-to-insteon or zwave-to-zwave, but not that bad since IoX receives a command on ZWave, it is able to send it out Insteon right away. In comparison, when controlling ZWave form ZWave the same way using central scene (through IoX) only, it is significantly slower because of ZWave network overhead ACK, having to wait for ZWave network to be available before it sends to command to other switch. I added screenshot how the scene buttons on Zen71 switch ZY 022 work to control Insteon device named "Stairs", and also control another Zen71 switch ZY 023 using Basic Set. The other ZY 023 is set similarly in scene except its Basic Set is controlling ZY 022 of course. There is not one Node to control all, must use multiple nodes now with ZMatter. Remember that ZWave scene commands send an On command. On Zen71 switch: Scene Button 1 = top paddle Scene Button 2 = bottom paddle Program the scene so: The top paddle Scene Button 1 sends an Insteon On to Stairs The bottom paddle Scene Button 2 sends and Insteon OFF to Stairs. There is no equivalent of a default where it will turn on/off automatically when controlling this way, must handle both cases for pressing top or bottom paddle. NOTE: Both on-off power switches are set to ignore scene commands, otherwise the scene will turn on these switches by default from a scene command. Although, you can set these to same way as the Insteon Stairs with a Command On or Off to use old method of central scene I mention above, this is not desirable because I have the ZWave setup together using basic association and having both methods could cause confusion of the switches. Therefore, in this scene, I have two Zen71 setup using basic set to turn each other directly on/off and also each one turns the Insteon Stairs switch on/off using separate scene button nodes.

Working now again.

I posted issue in the portal forum. Also affects admin console connecting via portal.

Noticed today issue that I cannot seem to connect to portal on both UD Mobile and AC via portal account. Stuck on Initializing, Starting Subscription. I have restarted my Polisy, and then restarted IoX afterwards again which did not resolve. Portal shows it connected however.

In my case I just want the folder to display status of a program (Idle true, Idle false etc.) and I would use those values to change the color indicating a light is on/off in that folder/room, instead of the program setting a variable. The behavior of a folder when changing the display node to a program is not desirable in this case because selecting the icon does not take me into the folder. Not an issue since I currently use variables, was just thinking it as a shortcut without having to make a variable.

I did some tests tonight and was able to set parameter 3 to 3 which has built in momentary garage door setting on button so it turns off relay 2 after a few seconds. I have garage door open sensor on relay 1. The issue seems to be with anything with parameter 4 and above, it does not show the extra nodes. The Zooz instructions say to either exclude/include or re-interview. Neither work. Because of this we cannot get extra parameters and isolate the inputs. Note that it is important to set the parameter using the one ZWave node that contains the parameter option... right clicking on a different node and selecting zwave write configuration parameter did not seem to work for me. In case of Zen17 specifically it is the node named default ZY xxx Binary Switch. The ones named ZY xxx.1 or .2 do not work. Hopefully UDI can fix this Zen17 configuration issue since this is a very useful and popular device... would be nice to be able to separate the inputs from the relay and set different types of contacts. If this was possible to isolate, I could have the switch on relay 2 and sensor on input 2 and could run two separate doors, or maybe other sensors and switches. It worked fine before with Zooz dongle so thing there is just something overlooked hopefully.

@JaviI had an idea that I could just use the program status true or false to determine the status and color of a folder icon for on/off instead of having a variable eg. 1 and 0 for on/off. However, when I set the status of a folder to display a program node, the top half does not operate as a folder and clicking on it runs the program instead, clicking bottom half opens the folder. Is this expected operation? Seems like a bug to me.

This is what the ZMatter menu looks like, a bit different than the Zooz.

What is the brand and model of the sensor? It may have a timeout which keeps it on for several minutes especially if it is a battery sensor. For example, here is what my ancient Insteon wireless sensor does: WHEN MOTION IS SENSED 1.When motion is sensed the Motion Sensor will send an “On” command to up to 32 linked INSTEON responders and flash it’s LED (unless it is daytime and unit is in night-only mode) 2.Sensor will begin a 1 minute countdown 3. Whenever motion is sensed during countdown, the countdown will be reset to 1 minute to easily allow you to create “occupied” versus unoccupied modes for your home. 4. When countdown expires the Sensor will send an “Off” command to all linked responders (unless it is in on-only mode)

@asbril please let us know if that works turning the lamp on with Motion. I am wondering that it may turn the lamp off when motion is off however - be interesting to see. Maybe there is a parameter that sets this behaviour.

I found one of my sensors has basic set so I added to test scene and took screenshot for you. Select the Basic Control on Left eg. ZY016 Basic Control Select the device you want to control (Responder) on right side eg. ZY023 On-Off Power Switch Click on the pulldown that is Default and select Z-Wave Basic Then click update.

Ya I just started doing more with UD Mobile here is example of sorta what you want. I even made my home screen folder display different status of everything if a light is on in a room it shows Yellow and displays On. In particular, if garage door is open/closed and lights on/off the room folder changes color of door appropriately. If I open the door with light on I make it sorta orange color and if open and no light on it is red (not shown). Then I also monitor my septic lift pump, it displays status of a couple leak sensors labelled OK, and will turn red and say Leak. Also if pump is running and how many times it ran today.

What brand/model are these smart plugs?

Installed 1.07 and works good, changing from default to toggle

Seems that the support calls for DHCP and not finding the IoX may outweigh this soon LOL. I agree it should default to a default static IP, or this is probably not necessary because one of the features of EISY is able to connect and configure locally with a keyboard and monitor in case someone sets static IP incorrectly. I would look for another job so you can properly play with EISY at work

In favourites, have many lights with default icon just want to press on/off, but if I press the bottom half of icon it pops up with another screen and I don't always want this. Is there an option to make the entire area turn on/off instead?

My interim solution was to purchase a couple dual band Insteon Lamplinc dimmers off eBay, and put aside these Z-Wave dimmers for now

Thanks, guess this was changed sometime in the past. I remember I used be able to launch the web interface and it would connect/download a java applet. I like this way better.

I also tried parameter 8 and 17 to set the auto off to 1 second for relay 2... to simulate a momentary press. This did not work. I currently have a program that turns off relay 2 button after 1 second for garage door button but before I programmed the Zen17 to handle it on its own. Seems like configuration parameters are not working correctly still for me anyways. In case of my garage door, I have the button on relay 2 and the garage door sensor on input 1 (which both will trigger the relay)... Currently when garage door is closed the relay 1 sensor shows On. I have adjusted programs to compensate. Since I am currently using both my Zen17s, It is difficult for me to experiment with them without breaking other things. Maybe UD can test Zen17 on their end and make sure all the parameters work, including one to change input type parameter 2 and parameter 3 for each relay. Below example when I used Zooz ZWave dongle, I set to 7 and after excluding/including again shows a device type named barrier for the door and shows as open/close status not on/off. Here is the instructions I used before on Zooz Z-Wave dongle which work fine... For Garage Door --------------- Will hook up the switch and the sensor on separate sensor/relays just in case the isolation is not set correctly. Reset Include in ISY Set for Door Open/Close sensor Set Parameter 2 to 7 Set Parameter 3 to 7 Exclude/Include in ISY This will add additional nodes each sensor Set Parameter 10 to 0 Set Parameter 11 to 0 This isolates the relays being triggered from the inputs Garage Door Sensor (Sensor 1) ZW XXX.1 Barrier 1 Garage Door Switch (Relay 2) ZW XXX.2 Binary Switch To set simulate momentary 1 second Parameter 8: auto turn-off timer for Relay 2 Parameter 17: auto turn-off timer unit for Relay 2 Set Parameter 17 to 1 (seconds) Set Paramter 8 to 1 (1 second) *** must use 4 byte to write Parameter 20: Reverse the reported values for your selected input on S2 C terminals (select same value as parameter 3 eg. 7) (not reversed set to 0) Closed on Sensor 1 will show door closed Set Parameter 20 to 7 if your door sensor switch is NO when closed.

I believe that the ZMatter can work in Polisy either internally or externally in USB enclosure that you have. The process for your migration should be to plug it back in the Polisy when asked and do the migration on Polisy. Then do a backup of Polisy and restore on EISY and move the ZMatter dongle over to EISY. I would get confirmation from UD first on this however. It is not clear in the instructions if you are supposed to remove the ZMatter board from Polisy and most people who got ZMatter went ahead and installed before migration - UD should make this clear if it is to be uninstalled before migration in this case. In your case because of USB it should be easier.

What I am asking is I wish to make a separate account in IoX other than the admin/default account. But when I connect via the portal is there a way to specify a specific user on IoX? Connecting local I specify a user, but via the portal I guess it doesn't really use a local account setup on IoX and uses the portal accounts as the account, is that correct? I would not want someone with a portal account to login the portal and mess with stuff they shouldn't be (not likely in this case, but just wondering how it all works). Would a non-admin user on portal still be able to login via UDMobile?

Since v5.5.2 has anyone tried reconfiguring parameters on a Zen17? I have mine working as-is with ZMatter and I only use one separate input and output relay on each one so I don't really have a need to reconfigure at this time to isolate the relays from the inputs... just wondering if works properly now though.

I have issues with Hail also and he is going to try to experiment with some switches to see if can get working. Regarding scenes, I noticed that I haven't been able to trigger a scene using a zwave device either.. doesn't really bother me since I don't require it at this time and all my zwave devices in scenes are responders, but I am pretty sure it worked before when I tested - the ISY would "fake" an insteon type scene.