I used to use a custom DNS solution using Amazon Route 53 (which I already used for my websites) and a Let’s Encrypt certificate. It worked ok but was pretty technical to set up.

Then I switched ISP and the new one doesn’t allow incoming connections by default so I use Nabu Casa. It was super simple to set up and works perfectly and, imo, well worth the cost.

The one thing that was a misstep on my docker journey was that the original tutorials that I followed installed them using the command line. It’s much better to do it using a docker compose file.

I guess that my message wasn’t clear but by “component” I meant a home automation component.

I have the following containers in my HA installation:

• Home assistant
• Node red
• MQTT
• Zigbee2mqtt
• Esphome

And maybe others that I have forgotten.

Each had to be installed manually by adding it to my docker compose file, mapping drives, and editing config files.

Most, if not all, of them (except HA) can be installed from within HA if you’re using HAOS.

It can also be installed using docker containers but that is more difficult to manage as you have to install every component manually.

My tank came with a mounting point on the top of it where you can fit an ultrasonic sensor. You just configure it with the depth of your tank and that’s it. I have a unit inside that shows how much oil I have left.

Apparently, it uses an RF protocol that can be intercepted and interpreted in HA with the right dongle but I haven’t done that.

Edit: mine looks like this although with different branding.

Downgrading to 1.31.1 fixed it. Thanks a lot.

Ok, thanks. I’ll have a look at switching to an older version.

I have the older SONOFF stick.

I’m pretty sure that I have tried that. The kind of sure that means I’m going to have to try it again. 😀

I have thanks. I have tried just doing the basic setting of ‘true’ and the more advanced options with no joy.