jec6613

If I had to hazard a guess, it wasn't selling as well as the other i3 devices simply because they already had a really good paddle switch and dimmer.

It doesn't persist, and there's no way to programmatically set it. Either would fix the issue.

Yes, this exactly!

With eisy-ui coming along and the Admin Console going away eventually, I figured now would be a good time to ask about this. I have a number of scenes where I update the action response to battery operated motion sensors, so on every boot of IoX (or ISY from 5.x onward, this worked without issue in 4.x) I have to go in and manually disable automatic writes to battery powered devices, otherwise over the course of a week or so the performance goes off a cliff due to all of the pending writes. Does anybody have a way of doing this using a program? The option isn't in the eisy-ui at all, and frankly after years of this it's getting old and I want to remove one more, "After power loss.." things from my life.

Didn't realize that had changed, apparently with the 6.0.0 release - go figure. My polisy got turned into a backup router after an SSD failure (and a second eisy as a backup controller).

The only big difference at this point is that the eisy supports eisy-ui, a new web-based GUI, which while it doesn't fully replace the Java admin console yet, it will be in the future. From an automation perspective, they're identical, as is the new eisy V2, including Z-Wave handling. Though I will note that because the Z-Wave is external in the eisy, you can relocate it to a more advantageous location.

I think you mean bridge mode, not broadcast mode, but, yes, Optimum does that to reduce their own support calls.

As others have said - filters. If you need more than 10A, an ordinary X10 noise filter does about 90% of the job of the Insteon FilterLinc, and are available at 20A and more.

Quite a bit later, but on a related topic I really wish that the UD Mobile favorites config could just be a bunch of XML or similar so I could just edit it with a keyboard.

So, shocker, Wi-Fi 7 does make a difference for home automation. There's an update in the spec where devices can sleep and be woken, unlike on previous versions where every device constantly sent beacons and filled up the airwaves. This lets you put more HA devices onto Wi-Fi. But the Wi-Fi 6 in the current eisy only runs at Wi-Fi 5 anyway.

Since Wi-Fi 5 barely has support in FreeBSD 15, we're probably 3-4 years away at least until either of these changes make a difference in how the device behaves. However, if it really bugs you, you can always just take the WiFi card out of the old eisy and put it in the new one, it's just an E-key M.2 card if memory serves.

Very much seems like MeLE stopped making the old hardware, so just pick and validate a new one. It's a big advantage of moving off of the ISY994 and later apu2 (Polisy) hardware, it's quite easy to move to a new platform as hardware ages. The CPU is of course tons faster in IPC (the N150 has a new core design from Alder Lake), so that's a good thing, as is lower power consumption from the new process node.

I haven't checked the portal UUID or looked at what the UID coming to my DHCP server is since I changed the reservation, but yes I can confirm that I have an IPv4 address.

It's sending a unique ID, not its MAC address, to supported servers. This has been the new standard for a few years now to support IPv6 - that unique ID is not dependent on the NIC but is for the entire system, so a well designed system can multi-path over multiple NICs with multiple IPv6 addresses.

I had the same issue - see my post earlier about DHCP changes with the OS update.

I just checked my DHCP server, was much the easiest. It's standard BSD though so I'm sure you can find it via ssh as well.

After the upgrade, it's no longer sending the MAC to a router but a DHCP UID number (which is much longer) - anybody with DHCP reservations be sure to update them!

Z-wave also runs into network contention on big networks, so I find them less than ideal with a big install. However, Z-Wave offers higher security and some interesting devices that do not exist in Insteon, so along with me 150+ Insteon devices I have 50 or so Z-Wave as well. All of the ISY variants allow them to work seamlessly together.

Dome sold Z-Wave ones years ago, I have about 5 of them in high-risk areas, maintain them once a year and don't need to worry about checking snap traps in the attic. If they catch a mouse, the cheap snap traps come up to make sure I get them all!

Yeah, announced right after the US tariffs. It's not really clear what will be taxed coming into Canada because you import so much from us that can't be sourced elsewhere (photographic and motion picture film, for instance), but this is really (on the US side anyway) mostly about killing the de minimis loophole that allows Shein and Temu to operate from Canada's free trade zones and skip the pre-existing tariffs on Chinese goods entering the US. It's a right old mess.

Ditto, it appears to roll it back.

In most cases, there should be a screw hole in the back of the box, you can pick up a bag of green grounding screws to give a positive connection to the conduit system.

Couldn't that just be accomplished by poking a firewall hole? I do understand wanting to have PG3x on an IoT VLAN in order for some functionality to work at all because of broadcast domain issues, though I solved that by using my old Polisy as a PG3x head-end in that VLAN, and an above mentioned firewall hole, but you can already slice up the internal NIC to two virtual NICs, so doing VLAN magic seems pretty trivial after that.

One thing about Wi-Fi is it's not like Z-Wave or Insteon or Zigbee. While the above three provide the full stack of OSI layer 1-7. Wi-Fi is only OSI layers 1-2, basic connectivity only. It still needs TCP/IP to handle layers 3 and 4, as well as the rest of the application stack (5-7) to make it useful. Protocols like Matter look to fill that gap with something that's standards complaint for home automation devices, but right now on Wi-Fi, or TCP/IP generally, it's individual per vendor, requiring the use of a Polyglot plugin as @dbwarner5 describes. To complicate matters further, many devices using Wi-Fi for their connectivity only communicate to a cloud server, and do not permit you, on your local LAN, to access the device directly. Others lock down the communication to only their smartphone app via cryptography, and still others allow you to access it locally without issue. And one thing to keep in mind as you add Wi-Fi devices, is that they have a hidden node problem that leads to your network slowing down as you add more devices, with each associated device taking about 1% of your total Wi-Fi bandwidth even when it's doing nothing - and even with multiple APs to mitigate this, there are still only three clear Wi-Fi channels in the 2.4 GHz ISM band, leading to a practical maximum of about 300 devices connected in a standard home with normal business-grade equipment (note: this can be overcome, but as with most problems it's solved by throwing money at it). Unless your Wi-Fi network is already significantly overbuilt, you'll need to budget for a large expansion.

Update: there was a connectivity issue where a firewall rule was eating ICMP packets - put an allow rule in and things started working, thanks for putting me on the right track!