Guy Lavoie

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.

Try powering off your eisy for a few minutes, then turn it back on. Then log back in and see if the PLM now shows as responding ok.

If it's like for a few of us, just rebooting your controller might automatically upgrade it to 6.0.4 (if your current version is 6.0.0 or higher). If you get the eisy-ui login screen and log in with your portal credentials, don't be surprised if the screen is just blank. Just do a browser refresh.

I'm guessing that "That that has stooped on have of the device insteon devices woek" means half of the devices work? If so, are the non working ones battery powered devices, like leak detectors or open close sensors? If that's the case, you might need to relink those manually.

As you might have seen in other threads in this section, I have had difficulty with migrating from a Zooz stick to ZMatter on my eisy, and essentially reinstalled all my Zwave devices manually. One particularly difficult part was adding back Weiser locks. I have 5 of them, plus a spare that I use for testing. Doing the add Zwave device routine and pressing the button on the lock would often only add a single generic device node, or two nodes. This might vary for other locks but a proper add of a Weiser lock will usually give 5 or 6 nodes (depending on if it's a Smartcode 10 or Smartcode 620). In the US, these are often known by the Kwikset name. Each time I needed to do a Zwave exclude and retry the add. Bringing the lock closer to the controller would improve chances of success, but still usually required multiple retries. Taking the lock off the door isn't exactly fun either. In Zwave discussions on the forum, I would often see a suggestion to bring the device closer to the controller, so it wasn't just me either. In observing the add process, it's the "interview" process that seems to be the failure point. In checking out settings under the "Z-Wave" menu, I noticed Network -> Interview Timeout. So I bumped it up to the maximum of 3 minutes, and tried the Nth add of a lock that wasn't adding correctly for over an hour. Poof, added perfectly on the first try! There were short pauses during the interview progress indication, but it carried on to completion. And this lock was sitting on my desk to be closer to the controller. Well I had one last lock to add (of the five, the first two added back in-place, the third by bringing it close, and then the frustrating one I just described). This last lock is the farthest away, on a separate garage behind the house. I used the UD Mobile feature to go out, exclude it, and add it back. Came back in the house to see the 6 nodes added perfectly, on first try! Dumb luck? Twice? When thinking about the notion of bringing the device closer for adding it, the only real justification for that seems to be to reduce the need to go through the mesh network, which can only add delays. It would seem that making the timeout delay more tolerant is a much easier way of doing this. Let me know what you think, and if you do try this yourself, how it works out.

The common denominator seems to be the battery powered devices. Locks are also battery powered. Though there might still be a difference because locks need to be able to receive commands so they're always awake, while sensors usually only send out data. Do the sensors appear at all in your device list? Or are they there but showing only as placeholder nodes with no controls? If they do appear, try right clicking on the device: Z-Wave -> Synchronize -> Update with Interview. You might try waking up the device first, if there is a way to so that. I'll actually be experimenting a bit with migrations once I'm certain that I've manually reconfigured everything correctly to ZMatter on my eisy.. Then I'll be able to reset the Zooz stick and try things with it. I have Polisys as test controllers, and I've just acquired one that has a ZMatter board in it. I'll create a small setup with one lock and a zwave appliance module with the Zooz stick on a Polisy, and try migrating that to the ZMatter Polisy.

Migrating from a ISY994i to a eisy? Is it just Insteon devices or also Zwave? Did you keep the same PLM, using a serial to USB adapter?

With 6.0.3 you should already have eisy-ui installed. Have you tried accessing it? Just browse to your controller's IP address, with no port number (default 80).

I just couldn't get the zwave migration to work. I ended up adding back each device manually (exclude or reset, then add). Thankfully I only have about a dozen zwave devices, none of which are wall switches. But for a few of the locks, I needed to remove them from the door and bring them closer to the ZMatter dongle to properly add them. These are Weiser locks. I'm thinking that their greater number of features and nodes might have been a factor. To make reconfiguring devices easier, I had the restored migration backup running on a test controller (Polisy) and my actual setup with the new dongle on my eisy, and ran two admin console sessions running side by side on two monitors, so I could easily see what the old device names were, and search the programs where they were referenced. I'd then replicate that on the eisy.