jec6613

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.