RRalston

Hi @xlurkr My switches reflect properly in the AC when activated manually (i.e., at the physical switch). Hard to understand why yours is coming up "ZY 007.1 On-Off Power Switch". None of my nodes has that label. Hopefully support can help you out. Here are screen captures of my two switch nodes reflecting on or 100% when operating the switch manually.

@xlurkr, that is correct. The nodes were always there. I just had to play around to figure out which nodes did what when a switch was physically changed, or changed via a program or via Admin Console. The Advanced parameters I used were just to control switch behavior.

@xlurkr So far I only have Zwave devices from Zooz, and I do have a ZEN30 in use. Before I get into specifics, I find the Zwave implementation in eISY to be less than satisfactory on so many levels. I had hopes with the 5.9.1 release where Zwave fixes/improvements were apparently implemented, but I have seen no improvement yet. For this ZEN30, UD's implementation won't even let you do an OTA firmware upgrade because they have experienced devices being "bricked". Zooz support does not understand that, but UD does not seem willing to work with Zooz to figure it out. But for devices where you can do OTA upgrades, the process can make a mess out of your device requiring multiple bizarre reboots and "Synchronizations|Update with interview" operations that make no sense. OK, enough complaining. I'm sure given enough time they will figure it out. Now, back to your post. My ZEN30 use case was really to have the equivalent of two separate ON/OFF switches in one device, which with device "Advanced Configuration Parameters" I was able to achieve. I use both switches within programs to control other Zwave devices and not for any scenes. My device has multiple nodes as well, some of which seem to have no value and do not reflect anything useful when the device is operated. In fact the "Y003_147-Binary Switch" is such a node. That node belongs to the upper "dimmer switch" portion of the device. Sounds like it would toggle on and off, but no. You will find operational status under your "ZY003_1 - Dimmer Switch" node, which will represent "OFF" through 100%. Mine now only toggles between those two values based on my configuration. You might find it useful to use the "Group Devices" operation for the device by right clicking on any node for the ZEN30. This will separate the top and bottom switch nodes for you into two separate branches so it makes a "little more" sense. My device node which represents the bottom button "ZYxxx_001_1 - Binary Switch" (yours is shown as "ZY003_001_1") has a Status field present, while yours does not, which can't be right as I believe it is the only functional node for the bottom physical switch. That would explain at least part of your problem. Seems like you may need to work with UD support on this. Here are a couple of captures from my installation: This is my bottom switch node: This is my Top Dimmer switch node, which as I said is configured to act as a binary switch via configuration: My device nodes:

@Illusion I have not experienced this problem. However, from the test scenarios and results you have described, suggest a hardware issue on your policy, specifically related to the hardwired NIC interface. When it sees an electrical status change on the port, it is somehow causing the IoX restart. Hopefully there is a way to capture IoX diagnostic logs around the NIC event to help diagnose. -Rob

Jim, After you set the parameter value to 2, then query the parameter, are you saying the retrieved value is not "2"? Also, try using the XRay menu item and access the "DH Command Classes" for more info you might use when communicating with the vendor. For example, the configuration section should list all of the parameters and current values that can be set. You can also find current firmware data there in case you need to update that.

Hello Jim I have several ZooZ Z-Wave devices. I am no expert on this but I do have some experience to share which may help. First, the device must be awake to receive configuration commands. I looked at your device and since it is apparently continuously powered by DC, it theoretically should always be awake to accept the commands. So I do not think that is your issue. Second, I have had much better success setting configuration parameters in the following ways: 1) via a program 2) using the Zwave | Set Configuration Menu item for a specific device which provides a dialog like this. Notice you can query the parameter here as well. Accessed here: Hope this helps you. -Rob

I also have Zooz ZSE42 leak detectors and the Zooz Titan valve actuator. Water detection has been solid. But like @ldb I have found battery reporting is very unreliable, although the eISY could easily be part of that problem. I have given up trying to resolve that. Too much finger pointing between UD and Zooz. I do not have any other brand of Zwave battery devices to compare to.

I upgraded both IoX and PG3x at the same time as well. Upgrades went fine, but I did experience a problem with the AC as well as UD Mobile app. While I could log in to AC, the status icon at the bottom left would immediately go red. Also, UD Mobile, while seemingly connected was actually rapidly retrying connections as seen on the main top level home screen. I was drawn to that screen attempting to figure out what the little icon next to the House/Home icon was trying to tell me. Turns out, at least for me, this update requires another outbound port, TCP:8003 for something related to the ISY Portal communications. Once that was configured, everything started to behave normally.

Thanks to both of you for your experience. I hope to have the charger in a couple of weeks and will give it a shot. Rob

Thanks for that info @tazman. There is no documentation at github. I guess when I add the charger to the system I will see more nodes and capabilities available. Sounds like I will have flexibility. Thanks again. Rob

Hello, In the Plug In description it says "...Vue Electric Vehicle chargers. Allows you to monitor usage and control outlets and chargers." Is there any documentation around controlling chargers? I am acquiring the EV Charger with Load Management, and would like to understand what the plug in will allow me to do. Thank you, Rob Ralston

There is also a drop down list for Zwave on the configuration menu of the AC which you may have missed:

Hi, I have experience with Zooz, but not Aeotec, though I suspect this may be the same or very similar. Go to X-Ray for the device and select DH Command Classes, then hit Go. A lot of data will come back, but look for a section called: Command Class 134 0x86 VERSION Within that section look for two values: .data.applicationMajor .data.applicationMinor

I know nothing about Kwikset 620 Zwave 700 deadbolts, but doesn't it seem plausible that particular lock is malfunctioning? It's apparently communicating and accepting commands, but it still has to convert those commands into a mechanical action. It may make sense to contact Kwikset support as well.

First, I agree, a simple way to comment out line(s) of code would be nice, but I have used the following method with success. Check out the last comment in this thread:

I submitted a support ticket and found out the BIOS update is indeed a separate process and requires a monitor & keyboard connected to the eISY to complete. However, I also determined the intended method is not currently working as designed, but Michel provided a work around, which I completed successfully. If you really want to get this BIOS update installed, I suggest you open a support ticket for specific guidance. Michel is very helpful and responsive. Rob

I submitted a ticket, and Benoit was able to reproduce. Per Benoit, the fix will be in the next PG3x release.

I submitted a ticket, and Benoit was able to reproduce. Per Benoit, the fix will be in the next PG3x release.

That makes sense. I indicated in my initial post I didn't know which component was the problem. Anyway I submitted a ticket and logs.

I will open a support ticket for this and the VUE plugin.

Hi Bob, Thanks for the response. What you say makes sense, but it is not my experience. Stopping the node server shows Disconnected in PG3x, but Connected in AC. Only the reinstall behaves as expected. I will open a ticket to work through this. Rob

Updated without issue. BIOS security update is stated in release notes. Is that update automatically included in the "Upgrade Packages" operation, or are we supposed to know to also push the "Upgrade BIOS" button? sysconfig.txt makes no mention of BIOS version, so a bit difficult to know BIOS status. Thank you.

So this is interesting. I received notification about the Python 3.2.4 update. I had time, so I quickly did a "re-install all" to get this update. During the reinstall, I received a VUE disconnected notification email, then about 30 seconds later, received a connected notification email (per my programs). After that I stopped the VUE plugin again to test, but still no notification for that. Thought this info might be helpful to whoever would look into this issue:

Hello, I am on eISY v5.7.0_5 and PG3x v3.2.15 and VUE Version: 1.0.26 [Production] Trying to create notifications for a couple of node servers when they may be stopped and disconnected. What I have found is that the status for VUE and one other always shows "Connected" in the eISY AC, when I manually stop the plugins. Not sure if this is a plugin, PG3x or eISY issue, but my notifications are never triggered. Rob

Hello, I am on eISY v5.7.0_5 and PG3x v3.2.15 and Climacell Version: 2.0.1 [Production] Trying to create notifications for a couple of node servers when they may be stopped and disconnected. What I have found is that the status for Climacell and one other always shows "Connected" in the eISY AC, when I manually stop the plugins. Not sure if this is a plugin, PG3x or eISY issue, but my notifications are never triggered. Rob