Guy Lavoie

Yes. Matter didn't really invent anything new. It uses existing technologies (IPv6 for networking, wifi/ethernet, and also zigbee for low power applications). The only real innovation is transmitting IPv6 over zigbee. It cuts down development costs. It's mostly software, for sharing devices across platforms. One other thing that UDI also hasn't implemented yet is device sharing. It accepts shares, but doesn't yet provide sharing to others. That's why you might want to keep the device configured on another platform like Alexa for now, If it exists only on your eisy and you'd want to share it to something else, you'd need to delete it, recommission it, reshare, etc.

I mean border router. The purpose of the border router is to bridge the two transport (layer) methods: ethernet/wifi, and zigbee (which Thread uses). The network layer is always IPv6. I don’t yet know how the border router "knows" what IPv6 traffic to route or not. There must be a scheme to that, more stuff to learn. Border routers have no configuration options, they just "do it". When UDI first implemented Matter, they had to implement IPv6 on the eisy and Polisy. It's still in development. As it currently stands, talking to a Thread device needs a border router because only the network interface is used. Ultimately, they'll hopefully implement talking to the zigbee (Thread) devices directly through the Zmatter dongle. Maybe the eisy could become a border router itself.

To my knowledge, the border router is "transparent" to the network. Any given controller (Alexa, eisy, Google home, etc) doesn't know if a device is Thread or ethernet. Once it knows about a device, it simply talks to it using IPv6, which gets routed over the router if needed.

Try moving the Repeat statement to the beginning of the action statements, like this: Garage Open - [ID 0005][Parent 0001] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Repeat 4 times Set 'Kitchen Ceiling - Dining Room' On Wait 3 seconds Set 'Kitchen Ceiling - Dining Room' Off Wait 3 seconds Set 'Kitchen Ceiling - Dining Room' On ,,,

If the M1 is being accessed by a plugin, the likely place would be as a custom parameter in polyglot, for that plugin. eg: log into polyglot, click on Dashboard and select the elk plugin, then click on Configuration to view and edit the custom parameters. One of those would likely be the ip address.

If the M1 is being accessed by a plugin, the likely place would be as a custom parameter in polyglot, for that plugin.

I have two Polisys happily running 6.0.4. It's your call. The update mostly addresses Matter functionaily, updates to polyglot, etc.

I have an Amazon Echo (not Echo dot) that does this. Here is a list of all devices that act as border routers: A complete list of Thread Border Routers on the market today | Matter Alpha https://share.google/T4JIypeoornYNxsIZ

Here is an example of what I mean: to copy a program, the program logic and reference type could be copied, and the actual reference be replaced by a placeholder. For example: Awning (unroll) - [ID 00B9][Parent 00B8] If 'IOL Awning Unroll Relay' Status is On And 's_Alarm_off' = 1 Then Set 'IOL Awning Rollup Relay' Off Wait 50 seconds Set 'IOL Awning Unroll Relay' Off Else - No Actions - (To add one, press 'Action') Would get pasted as: Awning (unroll) - <generated new id> If '<device status> ' Status is On And '<status variable>' = 1 Then Set '<device>' Off Wait 50 seconds Set '<device>' Off Else - No Actions - (To add one, press 'Action')

That's one thing that hasn't been discussed with the eventual move from the java based admin console to browser based eisy-ui: it should now be possible to access two (or more) controllers simultaneously. The ability to copy/paste things from one eisy-ui session to another would certainly be a welcome feature. The "by reference (id)" design of nodes, variables, programs, etc would make that somewhat difficult, but thought should be given to making at least some of that possible.

I'm still rather new at this (a year and a half) but the things that work for me: Put all programs related to a common function or area in distinct folders. So I have a folder for all shade related programs, another folder for water leak detection, another one for locks, etc. For device naming, I'll tend to name devices with a prefix for the type of device it is, so Leak_<name> for leak detectors, Motion_<name> for motion sensors, etc. IoX tends to do that by default too for devices like ZWave (ZW_<name>) Matter (ZM<name>. Of course you can rename them anything you want, but I like to keep that prefix. For light switches, well as an X10 user for the previous 25 years, I knew the rooms by their house/unit codes by heart, so I kept the naming scheme as a prefix: eg C4_living_room, B2_office, etc. They did have a natural progression throughout the house and each house code grouped something or a floor, so that remained meaningful. For variables, status variables get name s_<name> and integer variables as i_<name>. For Alexa, I keep the spokens to single words, for reliability ("living", not "living room"). Sounds a bit awkward sometimes.

You'll need to have it appear on your local network before thinking about seeing it in IoX finder or the portal. The first thing to try would be powering it off and then back on. Try that a couple of times, giving it a couple of minutes to reconnect. If that doesn't solve it, you might need to open a ticket, and be ready to have a hdmi moniter and keyboard attached.

I don't know how "scenes" work in Zwave, but with Insteon, you set up scenes that make the switches communicate directly with each other, so the eisy isn't involved in the actual communication between them, making for very fast response.

Does it appear in your router's connected devices table? If so, have you tried a ssh connection to it from your PC?

You could create a "all off" scene with everything you want turned off as responders.

There are both "All Units Off" and "All Lights Off" commands, depending on if you want to turn off all devices or just lights, on a given house code.

Well it sounds like he wants to run a Hue emulator on the eisy (there is a plugin called Hue Emulator). So access to the eisy and the Hue emulator would both be at the same IP address. If the IoX port could be changed to something else than 8080 then this could be a solution, but the ports number isn't currently editable in Configuration. So that's a good question.

I did experiment with triggering Alexa routines with a variable change in isy. It worked but indeed, there was a variable delay that would occur, sometimes 10 seconds or more.

Could something generating electrical noise be jamming the signals? Anything new added to the household?

I've kept all the spokens to single word names. That can get challenging when you're up to 50 devices but it seems to make things more reliable.

Speaking of backups, I also do the one I describe here:

Not all LED lights work well with dimmers, even if you don't dim them. Is the fixture itself rated as dimmable? Many aren't.

Did you ever figure out how to get the temperature device to be recognized as such by Alexa? Just wondering. Thanks.

The same thing happened with one of my Polisys, updating from 6.0.0 to 6.0.4, upon a reboot (which came after powering it up after I flashed it's SSD with a 6.0.0 image I had made in September). Looks like they're taking a page from Microsoft's playbook, doing upgrades on the fly upon a reboot. I'm guessing that they figured 6.0.0 wasn't stable enough to leave as-is on a running system.

It could just be going bad, such as a bad capacitor.