Sorry, I forgot about this thread, but I was reminded today when I saw the new bug. The issue that originally affected me was https://github.com/home-assistant/core/issues/103208. It broke Xbee users, so not everyone. My Zigbee integrations didn’t work after the update so I had to roll back to a backup for my first time with HA. A patch was developed, but it didn’t get integrated into any of the 2023.11.x releases, which I found kind of frustrating but I figured I’d wait it out and eventually there would be a version that works again.

Fortunately I held off on 2023.12, because according to https://github.com/home-assistant/core/issues/105344 a bunch of people are having problems with this release too.

The last update broke zigbee for a month, so forgive me if I don’t jump on this bandwagon.

My town doesn’t allow polymeric sand so I have to use regular masonry sand. It hasn’t affected the stability of the pavers, but pulling weeds all summer is kind of annoying.

Maybe you use plain sand now and come back and do it when it’s warm.

It’s a little confusing. Nextion makes “HMI displays”. It’s an integrated module that runs its own software, draws the UI, processes events, etc. It’s a black box that just reports back to the processor “button 3 on page 1 has been pressed”. You design the interface with that ugly Windows app and upload it to the display, but there is no direct access to the screen.

To make use of the Nextion display, you need something connected to it, and that’s where the ESP32 comes in. It receives those “button 3 pressed” events and handles them, but crucially, it does not have raw access to the screen, so you can’t just draw your own widgets on it like you’d be able to do on an ordinary display.

There are other projects to build your own controller with a touch screen and a microcontroller; the appeal of the NSPanel is that it’s basically an ESP32 and a Nextion display conveniently prebuilt, has decent hardware and aesthetics, and it isn’t hard to reflash it with ESPHome. Replacing the Sonoff firmware on the ESP32 doesn’t change the limitations of the Nextion display.

I haven’t seen that software, but it doesn’t look like it can be used with Nextion screens, which are totally proprietary.

The way I use them is to reflash the firmware with ESPHome, at which point they have nothing to do with Sonoff. I got really into these things when they came out and made a video about the process: https://youtu.be/Kdf6W_Ied4o?si=4nh7kP28IglwVHBx. There are a bunch of different ways to use them including retaining the original software, but I kind of stopped paying attention when I got mine working.

It’s worth noting that they have two different products. The “NSPanel Pro” is completely different, I think it runs Android. I haven’t played with that at all.

I have one Kindle Fire using the Fully Kiosk Browser and a wall mount with a hidden power cord (https://a.co/d/05GVxVP). It uses the camera to turn on when you walk up to it. It’s ok, but I installed it 3 years ago and never really finished making a dashboard for it. In practice, we control the vast majority of stuff by voice with the Google/Nest Home integration, or switches. The big control panel thing doesn’t hold enough interest to even bother putting controls on it, and I mainly leave it showing air quality graphs.

Of more practical use are smaller panels for area-specific uses. I mainly standardized on NSPanel, because I was experimenting with them and ended up with a bunch. Example: https://youtu.be/DBzg7v1Q5Zo. I have a short attention span and tend to stop when it’s 90% good enough. I also have in other places a DIY HA SwitchPlate, and HASPone on a Lanbon L8.

I suppose that’s true. Rereading my comment, it’s a bit over the top. If I pretend now I don’t know anything and start at http://home-assistant.io, it’s not that hard to scroll down, see the thing, and buy it. I don’t know exactly how I got so off-track when I tried. Probably I knew “a little too much”, as in the words “home assistant blue” in the back of my head, Googled for that and got distracted by “I need to understand why there are two boxes and one isn’t for sale anymore, so exactly what is the difference is between them?”.

Coming back to that naive journey, though, I could see how someone could end up buying Green with no wireless dongle or Yellow with no CM4 (especially since you can’t get one).

I still think that for the limited size of this ecosystem, choosing a box shouldn’t be confusing. I can now understand where it came from, though, once I realized that HA Yellow was designed around a Raspberry Pi board that became unobtainable, so they had to go with a different architecture.

I have a friend who bought a new house and wanted to do some automation with the lights. While my HA is a total DIY setup, I thought maybe I’d suggest he get one of these boxes I was vaguely aware they sell. I went to the web site and first of all couldn’t find them from home-assistant.io (I see they’re on the front page at least now, but I swear it was harder to find when I looked the other day). Then I got lost trying to understand what the actual box was… yellow, blue, some third party odroid thing? Didn’t matter, everything was out of stock anyway. Now there’s a green one. I’m not sure this is actually making it easier to get started. I’m somewhat of an expert and I gave up.

There are several. I have one as I mentioned in my comment: it’s called a Phyn Plus. It works with and without sensors. I have some in strategic places like under the water heater.

It actually caught a leak, although it wasn’t from the plumbing. It was rain getting into the chimney and dripping into a puddle in the boiler room that set off one of the sensors. I like the cable-style sensor they have – it’s like a 4-foot-long headphone cord, but the whole length is a water sensor, so if any part gets wet it goes off.

Cutting a pipe and adding a valve is a really simple thing and should only be expensive to the extent that any plumbing job is expensive.

I would specifically ask for a quality 1/4 turn ball valve - there’s no point in cheaping out on that part when you’re mostly paying for labor. And as long as you’re doing that, you probably want two of them. For the same reason the city doesn’t want you touching theirs, you should have a shutoff that you actually use when you need to do plumbing work in the house, and one before that that you never touch unless it’s an emergency and you can’t shut off the other one.

For a bit more expense, you could consider an automatic shutoff leak detector. I have one called Phyn that keeps track of water usage, tests for pressure drops every night, and detects unusual flow patterns and can automatically shut it off.