wmcneil

I opened a ticket. Michel responded and stated that this is a known issue and a fix is hoped for by tomorrow.

I've updated and migrated my home polisy/5.5.0/pg3_3.1.17/zooz_zst10 to 5.5.6/pg3_3.1.17/ZMatter. After manually initiating an update and interview for each of my zwave devices they all seem to be working. But, the polisy keeps rebooting itself. The time between reboots seems to varying from around 15 minutes to 60 minutes. PG3 is reporting that 3.1.18 is available, but the AC update does not cause 3.1.18 to be installed (or at least it is not being reported as installed in the web browser) sudo pkg info udx reports 3.3.6_3 sudo pkg info isy reports 5.5.6 sudo pkg info pg3 reports 3.1.17_1

Started with polisy/5.5.5/pg3 1.1.17 I did an upgrade packges using AC button. After 4 beeps power cycled polisy. AC showed 5.5.6 , but PG3 was not started. I tried a couple of polisy reboots. PG3 still not started. Then I opened an SSH and ran the update command that @brians posted. That resulted in the same package update shown in @brians post, and now PG3 is running.

I had done a reboot not too long before I was trying to authenticate, so that could be a strong hint.

Polisy/5.5.5 , Today suddenly when I attempt login to AC using the http link in IoX Finder, my user/password will not authenticate (I tried admin/admin and that was not working either). This happened every time I tried over the course of about 15 minutes. When I tried the https link in IoX Finder, authentication worked correctly. Given all the other churn going on with ZMatter, and eisy, I thought I would mention this in a form post, in the hope it helps someone else. I'm not going to open a ticket at this point, as there are so many other more pressing issues at the moment.

In the AC, right click the sensor / ZWave / Set Configuration parameter use the pull down to select parameter number 64, then click on Query

My Multisensor 6 is now displaying farenheit in the AC. I am running Polisy/5.5.5/ZMatter. After verifying that parameter 64 was configured to a value of 2, I had to do an update with interview to get this working. The AC started displaying farenheit immediately after the update with interview completed.

UD provided the solution in my ticket. The REST API is slightly different for ZMatter zwave than it is for the original zwave: original zwave: http://uname:password@IP:port/rest/zwave/node/... ZMatter zwave: http://uname:password@IP:port/rest/zmatter/zwave/node/... EX: http://uname:password@IP:port/rest/zmatter/zwave/node/ZY002_306/security/user/2/delete

5.5.3/ZMatter: Kwikset 914 deadbolt lock. The following two rest commands no longer work. When entered in a web browser no data is returned and eventually the browser displays "the connection was reset. http://uname:password@IP:port/rest/zwave/node/ZY###_###/security/user/2/delete http://uname:password@IP:port/rest/zwave/node/ZY###_###/security/user/2/set/code/WXYZ ZY###_### is the address of the Access Control Alarm that is associated with the ZWave lock. I have opened a ticket.

Any code you have that was accessing the lock primary device / User Number can be changed to now access the lock Access Control Alarm associated device / User Number

I am experiencing the same problem - status never updates. gocontrol GD00Z-8 garage door controller, 5.5.3, ZMatter. Did you file a ticket? If I issue an open comand or a close command, it works, but my programs that are using the status value do not work, of course.

Thanks for the update, appreciate it.

I am running ZMatter with 5.5.3 and have restored a migration backup that was created with Zooz zst10. My Aeotec Multisensor 6 does not appear to be recognizing the parameter decimal 64 value. This parameter is supposed to control whether temperature units are Celsius or Fahrenheit. Value 1 is supposed to be Celsius, value 2 is supposed to be Fahrenheit. Temperature is displaying as Celsius in the AC, regardless of whether I set this value to 1 or 2. I am able to confirm the write value is being accepted, because if I do a query after the write, it is returning the value I am writing. So it appears that the Multisensor 6 is accepting the parameter write, but it is not affecting the units displayed in the AC. Some additional info: I have successfully used parameter 64 to control the displayed units in the past when I was using zooz zst10. I have a different polisy in another location that is running 5.5.0 with Zooz zst10. This system also has a Multisensor 6, and it has been reporting in Fahrenheit for at least a couple years (When I first installed it I wrote parameter 64 to a 2). Today I tried changing parameter 64 to 1, and the reporting changed to Celsius. BUT, I have changed the value back to 2, and now the reporting will not change back to Fahrenheit. I have tried rebooting IoX to no avail. So now it is not clear where the problem(s) are. Edit: Now that some time has passed, my 5.5.0/zooz system is now reporting in Farenheit, so it is behaving as if there is a time lag between the parameter being written and the AC updating (I had previously tried many queries, and that had not caused a change, so strange behavior for sure.)...My 5.5.3/ZMatter system continues to report in celsius. I'll post back if this changes after more time passes.

I've been waiting for Michel or someone else at UD to respond and answer my question. I know they are busy with IoX 5.5.0 migration plans, but I am asking something that I think is something important that others would like clarification on, so In the interest of potentially helping others, I will comment with some further information while we wait for the official word. The Zooz ZST10 700 has never had a backup/restore capability provided by the Admin Console (AC). An AC backup/restore feature was present up to and including the 500 Zwave option, so this is a feature that was lost when moving to Polisy and the Zooz stick. There is Windows software that Silicon Labs provides called Simplicity Studio which has a backup and restore function for the Zooz. This is the method brians is referring to above. Simplicity Studio is a large software package that has a lot of functionality in addition to the backup and restore. It is neither lightweight nor simple to use, but with a little persistence it can be installed and learned. Once UD has the ZMatter migration software perfected, it will be possible to directly backup from Zooz and restore to ZMatter. My previously stated question was asking if there will also be a backup from Zooz and restore to Zooz available. My guess is that the answer is no. That being the case, if you want the protection of having a Zooz backup you have to use Simplicity Studio. The reason you would want a Zooz backup is to protect against either the Zooz stick failing before you attempt migration to ZMatter, or a worst case scenario of something going wrong with the migration process that corrupts the Zooz stick (before you unplug it for the final time). I had a Zooz stick fail after only 7 months, and from what I read elsewhere, I'm not the only one that has had an early life failure.

@brians , I understand that the current v5.5.0 release is not working as intended with ZMatter. I also understand that one of the things that is not currently working is migration from Zooz to ZMatter. I have read everything that anyone has posted with regard to ZMatter in the last several days, and my questions are still valid. I want to know what UD intends when things are working, and I want to know for certain. I have had to rebuild my Zwave network from scratch once in the past month, and I do not intend to have to do it again, so I want to know exactly how UD intends that backup is going to work. I will attempt to further clarify what I originally asked: @Michel KohanimDoes UD intend to provide a backup and restore capability for Zooz ZST10 700, independent of the migration path from Zooz to ZMatter? If YES, in what version of IoX is this capability planned to first be present? If NO, that implies that only a 1 way migration path from Zooz ZST10 700 to ZMatter will be supported, correct?

For IoX 5.4.5, does backup/restore include Zooz ZST10 700? (Please do not answer unless you are certain of your reply. "I think so", "I hope so", etc. are not useful. Ideally someone from UD can reply with 100% certainty.) This part of the "IoX Release v5.5.0 Is Now Available" directions implies that ZWave is included, but I want to be absolutely certain: When IoX restarts, all existing Z-Wave nodes from the old installation are removed Note: The only way to go back is to restore a backup that was made prior to moving to ZMatter Z-Wave+ OR Does the snippet above imply that ZWave backup/restore for Zooz ZST10 700 is present only starting with IoX 5.5.0, BUT will be available only prior to pressing the Move to ZMatter Z-Wave button?

Are you looking at the directions in the Polisy User Guide under "Migrating from 994 to Polisy" ? If so, the zwave backup utility that those directions refer to apply only to the 994.

I initially tried to connect the wires with the ZMatter board plugged into the mPCIe connector, and I struggled with this as well. I ended up removing the board from the connector, attaching the wires, and then plugging the board back into the connector.

It turns out that I actually experienced the (quite unlikely) occurrence of my zooz zwave dongle going bad at the same time that I updated PG3. I opened a ticket and worked with the UD folks to confirm that is in fact what happened....As Michel has stated elsewhere, there is a backup functionality for the zooz dongle that is going to be present in ISY code that is going to be released very soon.

Michel made this post on 5/22 (post in "how to update zooz zst10 700 stick" thread 1. We are working on a combined Z-Wave/Matter board that gets installed inside + antennas coming out from the sides:- It will be field upgradable (so you won't need Studio etc.)- Z-Wave will have many diagnostics features + S2 2. We will have a utility that will backup your Zooz dongle:3. You can restore the Zooz backup into the new dongle4. For those who purchased Zooz from us, the total cost of the Zooz dongle will be discounted from the new dongle

Thanks for the update....There have been many, many soft and hard reboots done as myself and the UD folks have tried to debug the problem. No luck so far. Current theory is that the Zooz 700 is corrupted in some way.

I already have the ZMatter board on pre-order, meanwhile I will have to replace the Zooz 700, and potentially rebuild my zwave network.

@bpwwer, AC was reporting IoP version 5.4.4 before I did the update packages. The IoP AC is reporting "zwave dongle not responding" when the Z-Wave menu pulldown is selected. The UD folks spent several hours debugging my polisy box remotely today. The current best theory is that the Zoos 700 stick is corrupted somehow, and yes the symptoms started concurrent with my upgrade to PG3 3.1.12, so if the theory turns out to be correct, then this is a very unlikely (but real) coincidence. I tried updating the Zoos 700 firmware using the Simplicity Studios software on my windows laptop. It seemed to update correctly per what Simplicity Studios reported, but made no difference in the polisy box behavior. I am going to continue to work with the UD folks to debug further.

@asbril, did you ever get resolution of your problem? I am experiencing a complete loss of ZWAVE communication after having upgraded to PG3 3.1.12 . I have tried power several soft reboots, and a power cycle reboot of the polisy box to no avail.

I updated to PG3 3.1.12 using the "Upgrade Packages" button in IoP. After the install completed, and the polisy box rebooted, the node servers seem fine, but I can not communicate with any of my existing zwave devices. I have tried additional reboots of polisy and IoP to no avail. For instance, when I attempt to query a zwave light switch, I get a pop up window which states "Could not open config file to read" [./FILES/CONF/INSTENG.OPT] and "Could not open file" [./FILES/CONF/INSTENG.OPT] On the face of it, it makes no sense that updating PG3 would cause a loss of communication with all the zwave devices, but that is what happened. I have opened a ticket. I'll post back once the issue is resolved.