These have the following entries: Dimmer switch; scene button 1; scene button 2; SC basic asssoc 2; and SC basic assoc 3.

I have been renaming the "dimmer switch" part from "ZY 025 dimmer switch" to "Bedroom fan" (or whatever) and using that to work with ISY portal. That SEEMs to work, in that I can use an echo to turn this on/off, and also select low or high speeds (I remember there's no "middle", so you have to say 50% power).

Is there a better way to do this?

Also, I end up with extra elements. Should I also name with with the "Bedroom Fan" or just leave them?

The successful devices are:

Kajplats E26 1100 lumen bulb: I added it to Apple Home and then use the sharing code to add it to Amazon Alexa and then used another Apple Home sharing code to add it to UD mobile. I had to start with a factory reset bulb and then worked quickly to add it to the 3 systems.

Grillplats mini smart plug: used same technique as above.

Unsuccessful devices:

Billresa switch: above technique added it to Apple Home and Amazon Alexa but can't add to UD mobile. Just times out.

MYGGSPRAY motion sensor: added to Apple Home and Alexa but UD mobile says can’t find thread border router. Tried sharing codes from Apple Home and Alexa.

Anyone else have luck with these devices?

Zigbee checkbox is checked in IOX. Worked great for a year.

I have Upgraded packages, unplugged and replugged dongle, and rebooted.

Any clues before I open ticket?

I use and enjoy my ISY devices every day. I have a Polisy Pro running 6.04 with the internal zwave/zigbee matter dongle.

Background:

I am looking to replace a couple of aging Remotelinc 2s. IKEA is now selling a matter capable Bilresa two button switch for $6. I got a couple and I think they are nice.

I have a matter network with thread over wifi running in my house with Home Assistant. The Bilresa switches pair/add to matter OK on Home Assistant.

I have Zwave and Zigbee devices paired with my Polisy. I have never tried to use matter on my Polisy; no devices added.

I understand that to add an already paired matter device to an additional matter "server" is not just scanning the original QR code but requires getting a new pairing code for the matter device from the first/existing matter "server".

I am unable to get my Polisy to pair with the Bilresa switch. I have tried several ways.

Open Home assistant, ask to share Bilresa, get pairing code. Open UD mobile, verify Matter is enabled. Ask UD mobile to add new (this would be first matter device on Polisy) matter device. UD Mobile asks for pairing code - I enter the sharing/pairing code from home assistant. After several minutes the request times out. Bilresa not added. I have tried adding Bilresa using both UD mobile on android Pixel phone and on iOS iPad. Bilresa does not add. Tried with Bilresa within inches of Polisy. No Bilresqa added.

At a different location I have successfully added/shared a different matter Bilresa to two matter "servers" ((Nest hub and Home Assistant) on the same network. Bilresa is seen and works with both matter "servers."

Is Matter really running on my Polisy? What other ways should I try adding/sharing Bilresa to my Polisy?

Any suggestions?

Thank you for you advice.

My controller appears LR-aware internally and I am able to add using DSK value, but I don’t see any user-facing way to enable or verify LR. Is LR currently supported on eisy, and if not, is it planned? I have a single device that would benefit.

TY

Trying to jump ahead . I have a silos 800 zwave antenna, but this system is not just plug-and-play . Has anyone else

done this ? If so, what was your procedure? Thanks !

Per instructions, I added the device to my Eisy (version 5.8.4). Once added, per instructions, I set parameters 2 and 3 to 10 and parameters10 and 11 to 0. Then executed an exclude and include again. The unit comes back with the S1 relay containing the expected new child entry. Nothing new for the S2 relay, but that seems to be a known issue with the ZEN17.

I then test the new entry with a low voltage transformer and it recognizes the on and off status. But once I power down the ZEN17 and power it back up again, the new child does not work anymore. I can't query it and the on/off status never shows up again. I have tried this with two separate ZeN17 units and the results are the same. I have excluded/included and interviewed many times and nothing seems to solve the issue.

At this point, I am going another direction using an Aeotec sensor and an AC current switch.

But I would like to know if anyone else seen behavior like this with the ZEN17? Any thoughts or ideas?

I think that the time has finally come, and I am ready to replace my ISY994 with eisy.
But the availability (lack of it) of ZMATTER dongle is a showstopper for me.

I have mostly Insteon devices, but also few Z-Wave locks, so Z-Wave feature is a must for me.

Any info where it will be available again?

Reason is that I just bought the Zooz Titan valve actuator to turn the water supply on and off and need to figure out how to connect to it. I am a TOTAL Z-wave newbie and dont recall anymore if the EISY came with Z-wave.

Thanks and be patient with a Zwave newbie

Anyway, when I would attempt to add, the log would show an interview start and then the messages ZBEE-Log Terminating, then ZMATTER-Log terminating, then the whole system would freeze. I waited about a half hour once for it to unfreeze and it didn't so every time after that I've tried forcing it to reboot by pulling the power, because once this happens the whole thing freezes. Also, the ZWave and Matter menus show not available even though the Zigbee menu is still present (doesn't respond to anything you click).

At this point I'm not sure how to proceed next. I'm considering doing a factory reset on the EISY and starting over. I still have access to my Polisy.

Suggestions?

I'm looking to add automated window shades to my house and need to choose the type of motor (Zigbee, ZWave, Matter over Thread).

I'm leaning toward Matter over Thread for the shades. I don't have Zigbee, ZWave or Matter/Thread in the house right now.

I'd like to control these from my EISY rather than adding HA to the mix (probably through a bhyve VM).

Would an Aqara Hub M3 theoretically work with the EISY Matter Beta support? Since it would plug into my network, the EISY would need to find it that way. Of course I can fix the IP address and specify if needed.

I installed a couple of devices a few weeks back, out in the back yard, close to each other and farther from the house (but still within range of a few other devices). Before that I set them up (added them to Polisy) at my desk.

I looked at the data.neighbours table today and it shows a lot of neighbors within the house, but not neighbors of each other, which I assume they should be (since they're the closest two devices to each other).

They will respond to Polisy commands but sometimes are slow, so I know they are somewhat within range but believe they can be better.

I've heard that the ZWave devices are "self-healing" but it's been a few weeks now and am wondering if I should do something to make them rebuild the neighbor tables.

Thankfully restoring from the pre-upgrade backup and plugging the Zooz dongle back in works, but I'd like to be able to complete this migration. Any hints as to what might be wrong? I've gone through the whole process twice, with the same results.

Retesting the ZMatter dongle with the Polisy works fine, so it's functional.

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.