landolfi

OK, same thing again with 5.6.2 firmware and multiple Lamplincs and an Icon on/off module. After an IoX restart, these devices do not respond to any commands until I query them. Once queried, they are fine until the next IoX restart. The IOLinc shows its correct status without a query. Is this the expected behavior?

The situation has improved for me too. I got notifications from multiple node servers at around 0200 Central today, that was the first time in a while. But just now when I went to check to see if that was possibly related to an automatic restart of PG3x after a version upgrade, I can't log in to PG3x, I get 408 Request Timeout errors. I haven't seen that error before that I know of. EDIT: I ran the SSH sudo service udx restart command as described in the PG3x 3.1.36 support thread and I am still on 3.1.36. So the 0200 restart and the subsequent need to restart UDX are unexplained, at least in my case.

Same here, many notifications in UD Mobile. It's especially problematic for me because when my watch chimes our standard poodle thinks it means the garage door is opening and goes nuts. I'm running PG3x 3.1.36 with Polisy IoX 5.6.2.

One way would be to create a special notification for anything that isn't "th". But then you'd need 3 more I guess: 1 that has variable + "st", a second that has variable + "nd", and a third with variable + "rd", all in addition to the standard one that has "th". I hate the English language sometimes.

Tuya Zigbee temp and humidity sensor (cheap!): https://www.amazon.com/JUGAN-Temperature-Humidity-Intelligent-Compatible/dp/B0BM4KP67S

I should have mentioned that too--I only used S2 unauthenticated, mainly because I didn't know where the PIN/DSK was at the time I interviewed them.

I had that happen with a few Zooz devices that I migrated because they never completed the interview process even though they got added to IoX and were functioning for a short time. Try adding them again, and after doing so, check Zwave/XRay. Under the XRay, all the Command Classes for the device have a section that says InterviewDone=True/False. Make sure all of the Command Class sections have InterviewDone=True.

Thanks, UD Support tried that with me on 5.6.3 too, and after almost 2 hours we decided to downgrade. 5.6.2 appears fine. My case appears to be an outlier since y'all are finding success with workarounds. I could try 5.6.3 at some point, but more likely I'll wait for 5.6.4 and upgrade during business hours.

I wish it had worked because one of the times I did it I accidentally on purpose reset to factory settings and had no Zwave backup, so I even when Zwave was working on 5.6.2, I had to start over. Fortunately I only have about 40 Zwave devices and things are better organized this time around.

That was one of the many things I had tried. Did not work for me. I also tried it several times with UD support watching, so they know it did not help my situation.

I was unable to get 5.6.3 working, so UD Support (which was excellent) helped me downgrade back to 5.6.2, which is now working. They do not yet know why, but 5.6.3 somehow completely disabled Zwave for me (Polisy with the internal Zmatter board).

In my case, something was definitely wrong with the 5.6.3 update. UD Support helped me downgrade to 5.6.2 because we could not get 5.6.3 to work with Zwave on my Polisy with Zmatter. 5.6.2 is running fine once again, although dummy here accidentally reset to factory settings and I thought IoX backup also backed up Zwave--WRONG! Zwave backup is separate and on the Zwave menu, so I had none. I had to add everything back again, which was rather painful for the battery devices. Battery devices have always been challenging for me. I just bring them all reasonably close to the Polisy and make sure to keep them awake during their interview. For some of my devices, this took quite a long time. In a couple cases I had to exclude and re-include because the interview never succeeded. UD Support noticed a Zooz outlet on my network whose frequent power meter reports were likely interfering with the device interviews, so you might check the event log to see if anything is chatting up your network. As usual, UD support is top notch and the product is generally rock solid.

In my case, I get that instead of the menu. So sounds like a different issue for me. My case is odd because I followed the standard upgrade process and I seem to be the only one having this problem. I'm suspecting hardware failure.

When you go to the Z-Wave menu in the admin console, does it say "Zmatter Z-Wave not responding"?

You might want to hold tight and monitor this space. I have a Polisy with the Zmatter board also and my Zwave stopped working after the 5.6.3 upgrade. I have an open ticket with UD support.

What IoX firmware version are you running now? Is this a Polisy with Zmatter board or Eisy?

Interestingly, if I check the Zigbee option it works, it tries to discover devices. But Zwave doesn't work whether Zigbee is enabled or not.

Thanks for the suggestion!

I did open a ticket. It's a Polisy and the Zmatter board is internal.

OK, I tried that too with the same result. Restoring backup just reverted all my devices, programs, and settings to where they were at time of the backup, which was fortunately recent. Still IoX 5.6.3. This could be a coincidental hardware failure of the Zmatter board, but I haven't had any issues until after doing the upgrade.

Thanks, I tried that. When it restarts it initializes Zwave for a moment, then the initialization stops. Apparently the software is detecting the Zmatter board and rechecking the Zwave option automatically at restart. My question: If I restore a 5.6.2 backup, will that downgrade IoX version in the process? Everything was rock solid on 5.6.2.

Just about to open a ticket. Polisy with internal Zmatter board, upgraded from 5.6.2 to 5.6.3 and now the Zwave menu says Zmatter Z-Wave not responding. Node servers work, but all ZWave device queries fail. Here were my upgrade steps. Did this 2X just in case: a) upgrade packages, got 5 beeps. b) clear Java cache c) download fresh start.jnlp d) multiple reboots/1 power cycle Any other suggestions?

Can you tell us how? I have a Polisy but have wondered about doing this myself.

My notification includes that. It's Homer Simpson saying "Three simple words: (AOL You've Got Mail) Woohoo!"

Thanks for this! In my case, to detect the mail arriving, I use a Yolink motion sensor (which is fortunately magnetic) attached to the inside side wall of the mailbox to monitor the lid opening. I then have a program use the Yolink node server to detect motion and fire a Sonos MP3 clip. It's very accurate and the time to reset to no motion is perfect if I happen to get the mail within 1-2 minutes after it's delivered. But in my case the mailbox is right outside the front door, once again proving how lazy I am.