jec6613

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.

I'm sure I'm not the only one who got the email about using AI camera detection to use lights and sounds to scare off predators. Which given how brazen the coyotes have been this year (and unfortunately got some smaller dogs in my town), sounds excellent! However, we have black bears around as well, and camera AI helpfully identifies one of these goofballs as a bear about 2% of the time. Helpfully, he also makes coyotes rethink their life choices the few times they've approached his yard (Labrador Retriever for scale)

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.

No, but the Home Assistant minimums assume you're running, "On the Iron," so it's loading up a bunch of drivers - virtualized, its memory needs are more modest.

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!

Yes, they all are - i3, s9, and four m6's.

Discovery on initial startup isn't working, and I've tested on both an eisy and a polisy, both with PG3x, seeing the same log entries. Anybody run into anything similar? 2024-02-09 08:24:17,704 Thread-1 udi_interface INFO roomba-poly:start: Roomba node server starting 2024-02-09 08:24:17,772 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with result code 0 (Success) 2024-02-09 08:24:17,774 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:60:46_24 - MID: 2 Result: 0 2024-02-09 08:24:17,818 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Succesfully for Message ID: 2 - QoS: (0,) 2024-02-09 08:24:17,893 MQTT udi_interface.interface INFO interface:_message: custom data response {'customparamsdoc': '<h3>Roomba robots are auto discovered</h3>\n\n<p>If no robots are configured when starting, the node server will start the discovery process.\nThis will look for Roomba devices on the network. For each device found, you will then have\nto manually put the Roomba in to a mode that allows the node server to query the authentication\ninformation from the device. You will be prompted via a notice when this is required.</p>\n\n<p>The discovered Roomba deivces are then saved so that future starts can skip the discovery process.</p>\n\n<p>If you need to re-discover devices, use the "Discover" button in the UI to start the discovery\nprocess. This will clear any exising devices and start from an empty list.</p>\n'} 2024-02-09 08:24:17,933 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customparamsdoc 2024-02-09 08:24:18,014 Thread-3 udi_interface INFO roomba-poly:handleRobotData: Loading saved robots {'robots': {}} 2024-02-09 08:24:18,018 Thread-3 udi_interface INFO roomba-poly:handleRobotData: We have restored the saved robot list 2024-02-09 08:24:18,021 Thread-3 udi_interface INFO roomba-poly:handleRobotData: Finished with handleRobotData 2024-02-09 08:24:18,054 MQTT udi_interface.interface INFO interface:_message: Profile installation finished 2024-02-09 08:24:18,125 Thread-5 udi_interface INFO roomba-poly:handleConfigDone: No saved robots... 2024-02-09 08:24:18,126 Thread-5 udi_interface INFO roomba-poly:discover: Attempting to discover Roombas 2024-02-09 08:24:18,129 Thread-5 udi_interface INFO roomba-poly:_get_response: Comparing irobotmcs with irobotmcs 2024-02-09 08:24:25,142 Thread-5 udi_interface ERROR roomba-poly:_get_response: Socket timeout while waiting for response 2024-02-09 08:24:26,207 Thread-5 udi_interface INFO roomba-poly:_get_response: Comparing irobotmcs with irobotmcs 2024-02-09 08:24:33,227 Thread-5 udi_interface ERROR roomba-poly:_get_response: Socket timeout while waiting for response 2024-02-09 08:24:34,244 Thread-5 udi_interface INFO roomba-poly:_get_response: Comparing irobotmcs with irobotmcs 2024-02-09 08:24:41,258 Thread-5 udi_interface ERROR roomba-poly:_get_response: Socket timeout while waiting for response 2024-02-09 08:24:42,265 Thread-5 udi_interface INFO roomba-poly:_get_response: Comparing irobotmcs with irobotmcs 2024-02-09 08:24:49,269 Thread-5 udi_interface ERROR roomba-poly:_get_response: Socket timeout while waiting for response 2024-02-09 08:24:50,273 Thread-5 udi_interface INFO roomba-poly:_get_response: Comparing irobotmcs with irobotmcs 2024-02-09 08:24:57,355 Thread-5 udi_interface ERROR roomba-poly:_get_response: Socket timeout while waiting for response 2024-02-09 08:24:58,371 Thread-5 udi_interface ERROR roomba-poly:discover: Failed to discover any Roomba robots 2024-02-09 08:24:58,372 Thread-5 udi_interface.custom INFO custom:_save: Sending data customdata to Polyglot. 2024-02-09 08:24:58,373 Thread-5 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2024-02-09 08:24:58,456 Thread-6 udi_interface INFO roomba-poly:handleRobotData: Loading saved robots {'robots': {}} 2024-02-09 08:24:58,458 Thread-6 udi_interface INFO roomba-poly:handleRobotData: We have restored the saved robot list 2024-02-09 08:24:58,461 MQTT udi_interface.interface INFO interface:_message: Successfully set key = customdata 2024-02-09 08:24:58,461 Thread-6 udi_interface INFO roomba-poly:handleRobotData: Finished with handleRobotData 2024-02-09 08:24:58,541 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2024-02-09 08:25:02,878 Thread-1 udi_interface INFO roomba-poly:addNodes: addNodes: Discovery fround 0 robots!

No, your Eisy came with a thermal pad to use the external case as a heatsink.

So is mine, I used sudo

sudo vm poweroff -f homeassistant And then backup everything in /storage, and you should be able to boot from the NVME and put everything back. Edit: doesn't seem the case, but this is BSD, I'm sure there's a method of doing it, you just may be restricted in storage space for the backup.

I actually already have a headless Celeron based Nuc for that already. It's also a jump box for all sorts of network management, and it is indeed very handy. I'm not sure if a VNC connection would be nearly as effective as RDP though, if I could even get it running on Polisy.

What OS are you on? On Windows, I've always gotten this nice big + sign:

@theitprofessor Just because they have field upgradeable firmware doesn't mean it will be frequent, or that it exists at all right now. in Z-Wave land, a few devices get a few firmware updates, but it's still fairly rare except for right after new chipset releases. Given the new company direction, if there were any updates I think we'd have heard of them by now in their periodic updates - and if they do occur, I hope UD has the time to add in that capability as well. If it does require a hub and it's an important update, I'll probably pick one up, join the devices to it for a firmware update, then just hit restore device in the AC once the firmware update is done.

@theitprofessor I wonder if just doing a device restore would you get to the same place for the dimmer, as IoX would re-write every setting to match what's in the database.