Guy Lavoie

I just upgraded my three test Polisys to 6.0.5 (yup I have three of them now, I'm a sucker for punishment!). All were at 6.0.4. Polisy 1 is running the Elk plugin in demo mode. Plugin came right up fine after reboot Polisy 2 is set up with the Zooz zwave dongle, with a test device (Jasco zwave plug in module). That came right back up and the device functional Polisy 3 is set up with the ZMatter dongle, with a Zigbee test device that I added earlier today(Jasco zigbee plugin module), The two node screens came up blank in admin console after the upgrade. I right clicked on the module and did Zigbee -> Synchronize -> Update with interview, and that brought back the module controls, and they worked fine. Polisys 2 and 3 are the ones I was using to test Zooz to ZMatter migrations earlier this week (and failed). The release notes didn't mention anything about zwave but it might be worth retrying following this upgrade. I'll wait a bit for more feedback from others before upgrading my eisy. My IoX finder is set up with the actual IP addresses for each controller. I had no need to do any java cache clearing or anything. It would be interesting to have a bit more information about some of the items mentioned in the release announcement: "Support for manual static ip config" is static IP configuration back? I'm not seeing it in the Configuration screen. "Improved Matter support" what exactly? Reliability? Better device interview results? Minimum previous version 5.9.1 What does someone do if they have a lower version? It's not like the isy994i where you can download older versions.

Interesting: Today I just tried the Zigbee functionality on my test Polisy and I added a Jasco Enbrighten on/off plug in module, which also lists power monitoring as a feature. IoX only shows it as an on/off device. Sounds like it might be based on the same chipset.

I guess you mean the value of a variable. For that, use REST commands, sent by a network command. Go down to "variables": ISY Developers:API:REST Interface - Universal Devices, Inc. Wiki https://share.google/QXVb7N3fCS9GVj5cc

I have two T7900's and one T5800 with the wifi dongle. I've never had the T5800 show up in the plugin. But they work fine with skyport. One of the T7900's has always been hard to get to connect to skyport. Works for a while, but if power cycled, won't reconnect. I've never had an over the air firmware upgrade work. Venstar sent me a SD card with the upgrade files on it, which I keep preciously for that purpose, since the card must not exceed a certain capacity that is now largely outdated.

At the risk of hijacking @whywork 's thread... I've also had varying success with Matter. But it's getting better. My only Thread device has been the Nanoleaf bulb, and it has been far from consistent. It's still working with the eisy, though there are often delays with status updates showing in admin console. Make sure you have the latest firmware in the bulb. For Cync, I have a Cync bulb and also a Cync smart plug. These are wifi Matter devices. Both work with the eisy, though status update in admin console has sometimes been intermittent (often delayed) with them, but turn on and off reliably. The bulb also responds nicely to the color setting commands. In all cases, I had to add them to another platform first (Google home) and then share them to the eisy. Directly commissioning with the eisy hasn't worked. Ikea Matter devices haven't arrived at Ikea in my area. I look forward to trying them.

Well it would make sense for this largely integrated region to all have the same time. At least Ontario and Quebec. Eastern time is pretty well the the de facto time zone for things happening in North America. Both national capitals, the largest business cities other than those in California, NASA, etc.

That's one thing you need to be careful about: the actual terms. Thread doesn't run over wifi, it runs over zigbee. Home Assistant is purely software. If it's interacting with the Ikea switch ok, then it's talking to it though something. You would need to tell us what that is. If it's a regular IP network connection (wifi or ethernet) then you must have a border router in your setup. If not, do you have a zigbee device that Home Assistant is going through? If you do have a border router, then you should be able to add it to your Polisy with a share code as you described. On the other hand, if Home Assistant is using a zigbee interface of some kind, then this won't work as things currently stand. Despite it's name, the ZMatter board isn't yet involved with supporting Matter. The Matter functionality of a Polisy or eisy is currently by the IP network connection only. The ZMatter board is a zwave/zigbee board, but UDI doesn't yet support sending Matter commands over the zigbee interface. Until they do, the way to do this is by having a border router in your setup that will bridge the IP/zigbee networks.

I had some time this afternoon, and now that I basically recreated my zwave setup from scratch due to not having a working Zooz to ZMatter migration, well my Zooz dongle was now free for testing. That plus the fact that I have a spare ZMatter dongle allowed me to try migrations from Zooz to ZMatter using two test Polisys. Polisy A has the Zooz 700 series dongle and no devices. Polisy B has the ZMatter dongle and also no devices. The first test was with a Weiser HomeConnect 620 lock, thinking that maybe the issue was with the S2 security that's supported by UDI with the ZMatter dongle but not implemented for the Zooz dongle (though the dongle itself supports S2). Added the lock to Polisy A, verified it was working fine. Then did the migration backup, restored that backup on Polisy B, which prompts for a reboot due to migration backup being restored. Nope, all I get are placeholder nodes, though all six nodes for the lock get created with their proper names. If I delete the placeholder nodes, do an exclude on the lock, and directly add the lock to Polisy B (entering the PIN code for S2 security), the lock adds and works perfectly. The second test was with simpler devices, two Jasco zwave appliance modules. Again starting with two blanked Polisys and factory reset of both dongles, I added the two modules to Polisy A, tested them ok, made a migration backup. Restored the migration backup on Polisy B, which reboots it at the end. Same result: placeholder nodes for the two modules. Deleting them and directly adding the two modules works fine. So there is something seriously broken with Zooz to ZMatter migrations. I forgot to mention, if I try to run an interview on the placeholder devices, it fails:

Some other places like Saskatchewan have been on constant standard time since the 1960's. Adjustments are already being made for zones that are exceptions. It's just a question of making sure any rule changes are kept up to date. But I think that the trend (especially towards constant daylight saving time) will only pick up over the next few years.

I'm only guessing, but in another automation controller I've used, some things like sunrise and sunset times are calculated at midnight, when the date rolls over. Any changes would then be seen at the following midnight. It might be something similar.

Well it only rolls back the configuration from using the ZMatter dongle to generic Zooz. Let us know what UDI says about the Zooz 800 dongle.

Have you tried the deactivate url? If that doesn't help, you might need to open a ticket and ask if the Zooz 800 dongle is supported.

Another thing: does your Configuration screen show a "Migrate to ZMatter Z-Wave" button? It should if it's configured to use a Zooz dongle. If not, try doing this from a browser: http://<your_IP_address>:8080/rest/zmatter/zwave/deactivateZMatterZWave Then restart IoX

Do you know for a fact if the Zooz 800 series dongle is supported by UDI? I know the 700 is. Also, have you tried actually powering off the eisy (instead of just rebooting) after configuring zwave to on in the menu and inserting the dongle?

An often mentioned suggestion for the isy994i with problems is to power it off, take out the SD card, and clean the contacts with an eraser, then put it back in and power it back up.

Just to be sure: the components you need to get for a full functionality are the eisy itself, the ZMatter board for zwave (or a Zooz 700 series dongle if you don't ever think you'll need or want zigbee) ZMatter is the better option, and a serial to USB adapter for your Insteon PLM if you're keeping your existing PLM.

If your isy994i has a 500 zwave board in it (not a 300) there is a migration procedure for it, though that doesn't always go smoothly. Otherwise if you only have a few locks it might not be so bad to just recreate them, and their related programs. Is your isy994i running a release 5.x x of IoX?

UD Mobile is the free phone app that goes with the eisy. It has many features. Do you have only Insteon or do you also have zwave devices on your isy994i?

Have you tried a reboot of your controller?

Can you get to the controller with admin console or eisy-ui?

If you factory reset the PLM even before doing the migration, then you already had need to do some kind of PLM restore. Ideally you want to simply backup on the original eisy and restore on the new one, and keep the PLM intact. But that doesn't explain why the PLM isn't being recognized. Did you check that Insteon was enabled in the Configure screen? It would be now if the USB PLM is recognized. Right now I'd try to figure out why it's not working right with the new USB PLM. As a new, blank system. Just trying to add a new switch or module.

So you're saying that the same original PLM and serial adapter that worked fine with the original eisy isn't seen by the new one? And works fine when put back on the original? That does look like some kind of unusual problem with USB communications. On the v2 unit, you connected the power to the designated USB C power port (next to a hdmi port), right? Have you tried the power supply of your original eisy on it too?

That's the problem with status-only devices. Using a variable allows you to convert it to a control type event by having the status change set a state variable, wait a few seconds, then reset it. Like this: If Status = true Then set s_event_variable = 1 Wait 5 seconds set s_event_variable = 0 Then your other program can look for the variable = 1 AND time = xxx to yyy

Ah yes, I call these "latent triggers", when the time interval test becomes the trigger instead of just a static condition you want to "And" against. I usually use a variable as @DennisC suggests. It would be nice if there was a way to make time intervals optionally work like integer variables, to not trigger.

Have you tried going into the Alexa app on seeing if the device already exists? If yes, try deleting it, then add it back through the portal.