wmcneil

I just installed 1.1.50, and both polisy are now visible on the home screen. Thanks!

thanks, I will keep an eye out for 11.50 When I select the edit icon on the home screen, I see the help text stating "press the +/- icon to toggle node visibility", but I don't see any +/- icon in edit mode. I see an icon for each polisy box, pressing either one of those results in a Configure option, but pressing that does not provide a +/- icon (unless I am missing something)

Both of my polisy boxes have disappeared from the Home screen. I can still see them, and synchronize, under Settings, but both are missing from the Home screen. If I select the edit icon, both are present, but as soon as I exit edit, they both are gone. UD Mobile android version 1.1.49

So Resideo has announced they are no longer providing developer support for what exactly? If in fact Honeywell Home is no longer an option, I have several Honeywell T6 Pro Zwave and am happy with them. This thermostat supports up to 3H/2C heat pumps, 2H/2C conventional, and dual fuel. Supports use of either a wired indoor, or a wired outdoor temp sensor (but not both). The outside temp sensor that works with it is Honeywell C7089U . It can use its local sensor, or the wired indoor sensor, or the average of the wired indoor sensor and its local sensor, for controlling. The only feature that the T6 Pro Zwave does not have that I miss is that it is not capable of showing the outside temperature on its display (even with a wired outdoor temp sensor connected). It does display inside humidity (and temperature, of course.)

Yes, I am keeping my network going up until I actually close on the sale of the house. I have removed (excluded) the few devices that I am taking with me (and modified programming appropriately). On closing day, I will simply unplug the polisy box and take it with me. I would be happy to sell/leave it if the buyer had interest in learning how to use it, but the chances of that are very small. And of course, even if the person is interested, they would have to be highly motivated, as I most definitely do not have much time I can spend on education (I am moving, looking for another house, etc. etc.)

Good points: I'll factory reset the ZMatter dongle using the AC I'm not bringing any devices that have any parameters that have been modified, but in the general case, it is a good thing to remember to factory reset the zwave devices when moving them to a new install I'm also not moving an insteon plm, if I was the plm would need a factory reset as well.

I am going to be moving my Polisy from an existing home to a new home. I have both insteon and zwave devices installed currently. Most of those existing devices are not going to be migrated from existing home to new home, rather I will be purchasing new devices and installing them in the new home and building the network up in the new home over time. In this scenario, what is the best practice to restore IoX and PG3x to a "new install" state on the polisy box? I assume the answer is: "Do a Factory Reset (Press and hold Multi Function Button until all three LEDs are flashing), then follow Bootup Sequence directions in the Polisy User Guide to start over with the install process." I just wanted to double check to see if there is anything else I might be missing.

The number of issues with updates this year has been high, and 5.7.0 is no exception. Yes, there has been a huge amount of function rollout this year, so issues are expected. What is frustrating is that communication about those issues is not crisp. Case in point, the enable/disable issue was advertised as fixed, but apparently does not seem to be so. I'm a long term user and supporter of UD, but communication could and should be better. I absolutely continue to support UD, but I also support users who voice legitimate concerns.

I've been waiting for empty zmatter USB enclosures to be available in the store once again. I own two zmatter cards (currently installed inside polisy boxes), and will eventually migrate to EISY. When are the enclosures going to be available again?

I've been running an experimental build from UD for 6 days now without any spurious ISY Service restarts. Hopefully the problem has been fixed, and if so, an upcoming release will have that fix.

Unfortunately a new polisy box did not solve the problem with spurious ISY Service restarts at my home location. I am also seeing occasional restarts at my second home. In both cases, when this happens, it is not long after a query all operation. Sometimes a core file is generated. The UD folks are back to looking at one of the core dumps.

My Polisy is continuing to restart the ISY service typically at least once when a program runs a query all at 3AM. This frequently also coincides with a core file dump. UD folks weren't able to pinpoint anything with the first core file I gave them. I have given them a second core file....It's certainly possible some hardware is broken in my polisy I guess.

Update: The new power supply did not solve the problem. The isy service restarted several times early this morning, then when I manually initiated a 'query all', the box crashed and generated a *.core file (and then restarted), which the UD folks are debugging now.

The UD folks are helping me with the ticket I opened. Debug is not complete yet, but a couple of points that may help others: I have a rather old polisy. It shipped with a 12VDC 1amp power supply. One of the things I am trying currently is the use of a 12VDC 2amp supply. This was at the suggestion of UD. (I am using the ZMatter card in the polisy.) I have a program with an empty 'if' section and an email notification in the 'then' section. I have the "run at startup" option selected for this program. This causes the email notification to occur whenever the ISY service on the polisy box restarts. What UD has clarified is that the restart of the ISY service does necessarily been the box has rebooted. "Random" ISY service restarts should not be happening, nor should "random" reboots. In my case, I have been experiencing "random" ISY service restarts, not "random" reboots. Time will tell if the different power supply affects the behavior.

@kzborayYes, there was a reboot issue resolved in a firmware version prior to 5.5.9 , so the reboot issue I am experiencing is something different. I realized today that the reboot is frequently happening not long after a query all is issued, so that may be a hint. I do have a ticket open and am waiting for UD response.

@kzboray, I've been getting spontaneous reboots of my polisy about once a day or so. Luckily so far, there has not been any loss of functionality. I'm running IoX 5.5.9 , and am waiting for the next IoX code release and hoping it fixes the problem.

There is a bug with IoX not recognizing that a device has woken up, and therefore not performing writes to the device which are pending. I have a ticket open concerning this for my Zooz ZSE29 motion sensor, and in the last update to that ticket (about a month ago) UD was working to understand why the bug is occurring. I don't know if this same bug could apply to the Aeotec Water Sensor Pro 7 or not.

There is discussion from myself and others about Zooz ZSE29 in the support thread for IoX 5.5.7 release. I have a ticket open, and thought I would open a new thread and give an update: My ZSE29 is hardware version 1.0 At the suggestion of UD, I did more testing, and confirmed the following: * Wake-up does not occur due to motion detection. Wake-up occurs at power-on, and at the wake-up interval, which is set by default to 4 hours. Once woken up, the device stays awake for 10 seconds. The wake up interval value does not appear to be configurable in any way. There is no difference in behavior for battery powered vs continuous DC power supply. I did a test where I initiated a write changes from the AC immediately after having applied power to the ZSE29. The writes did complete for this scenario, as evidenced by the green 1011 icons in the AC going away after just a few seconds. Even with the default wake up interval of 4 hours, the write changes should have been written at the first wake up event. UD is continuing to investigate why IoX code is not performing the write when the wake up happens.

My ZSE29 is HW version 1.0, which does not support firmware version updates.

Good suggestion, unfortunately did not work. I kept the motion sensor triggering while attempting a write changes, and got the same result. Also on the wake up node, I changed the keep awake setting to on, tried the write again, and got the same result.

The device is connected to continuous 5V power. Selecting Write Changes causes the icons to change to WRITING briefly, then they return to 1011 and appear to be stuck there. I do have a ticket open.

Thanks for the info. I have excluded/included my zse29 several times. If I select no security options, the motion sensor node gets added. The motion sensor node is now working (reports status ON in the AC when motion is detected), but the motion sensor and all of the other nodes show the green outstanding write icon (has 1011 digits in it) that does not go away (has not gone away after 24 hours or so.)

Yes. Writes still seem to be stuck. Doing a synchronize/update or synchronize/replace with interview (after having previously done an exclude/include) actually causes several of the associated nodes to disappear, including the motion sensor node.

Thanks @brians and @DennisC for the suggestions. I tried excluding/including with no security options checked. That resulted in more associated nodes, and the AC is showing the IOW icon for all the associated nodes (seems to be stuck trying to write). I still have blank status for the Motion Sensor node, and when I try a query on it I get an error popup window. I also tried turning compatability mode off, then rebooted polisy. When reboot was finished, I tried a query of the motion sensor node, and got a TCP client read response failed. I am wondering if the zse29 hardware has gone bad. I only have one of them.

Updated both my polisy/ZMatter systems to 5.5.7 . The IoX spurious reboot problem appears to be gone. I do continue to have a problem with my Zooz Zse29 outdoor motion sensor. It is continuously connected to a 5V power supply. I did an exclude, and a secure include. The primary device shows three values in the AC: V1 Alarm Type, V1 Alarm level, Battery Level. All three values are blank. When I attempt a query in the AC, I get a pop up window that says Error Request Failed. I will open a ticket.