RRalston

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