I would like to start using floorplans/maps with various device actions on them. This means I need locally stored images, that can be seen over the network.
I managed to upload images to HA, but as they need to be accessed with a token, I either need to refresh the token every day (no), or have an image with a long-lived token (also not a good idea).

How have other people done things?
Is it worth spinning up an http image host?
Or maybe throwing files into an nginx folder inside HA?

Thoughts on a postcard :)

Oh my Jesus, can we just renationalise them already?

'We can only squeeze money out of this debt strangled utility if you exempt us from liability, particularly the executives in charge'

What a load of horseshit.

As I'm currently doing a re-wire, it's a great opportunity for me to put some metering in the house.
I'm single-phase, but I plan to monitor multiple sections of the house, which are each wired for 100A independently.

I'm currently eyeing up either the Shelly Pro 3EM – 120A or the 50A.
As it will fit nicely in the consumer unit, and supports Ethernet.

I previously looked at the Aeotec clamp devices, but they seem to be difficult to find with multiple 100A connectors.

Emporia Vue was also a consideration, but I'm always a little hesitant to buy products that require custom firmware to even work properly, when others are available. And I'd also like to avoid using 2.4Ghz wifi for connectivity.

I'd love to hear any experiences people have had with similar devices, good or bad. And how the integration with HA went.

I guess they kinda have to do this, or you'd have to keep the same person on breakfast until they retired.

I always found it a little bit comfy that BBC pipelined a lot of the flagship presenters.
Steve Wright going from Radio 1, to Radio 2 as the listeners aged, for example.

This was very much a me mistake, so apologies from me.

The long story short, is that we were migrating the domain between accounts.

As the previous DNS records would be wiped during transfer, we made backups, and started the process.
This morning, the "approve transfer" button was lit.
A sensible person would have gone "perfect, lets get this scheduled".
Instead, I just pressed the button.

Unfortunately, when you transfer, and are keeping continuity, you should always make sure the receiving account is ready to re-apply the settings.
I didn't, and the receiving account owner was happily asleep. 100% my bad!

All sorted now (hopefully).
There might be some weirdness while DNS updates propagate through the various caches.

I think the lessons learned are pretty obvious:

• Consider how noticeable downtime will be, and schedule with this in mind.
• Check that your counterpart is online when transferring a domain.
• Always schedule a maintenance window, even if you get excited when the button activates.

Apology from me. We're moving some things around on the back end, and my non-thinking brain didn't think to check another admin was online before handing over control of a system to them.

Hopefully, feddit.uk will be back up before the end of the day, assuming nothing horrid happens.