ve6rah

I think the basic issue here is that mount points in haos need to be read only until something is actually mounted on them. This way you would get an...

After a LOT of digging, and no thanks at all to OpenEVSE's lack of logging/troubleshooting ability, I discovered that it seems to be a DNS issue. I have no idea...

I tried multiple reboots, I tried a factory reset, no luck. It's obviously having DNS issues, but I don't know where to go from here.

DNS servers are local to my network. Or at least that is what the DHCP server is serving, without any form of diagnostics, I can't see if OpenEVSE is trying...

Right now my short-term fix is to ignore DNS, and put everything in by IP. However it seems like we've at least figured out why this is happening. Sounds like...

The names I'm trying to resolve are both internal to my network. One is the MQTT server, the other is the NTP server. I don't allow IoT devices to connect...

The domain names in question are FQDN. They are part of my registered domain, however only served locally.

> tls_insecure has to be true for the add-on, because it's connecting to the IP not the FQDN in the certificate. Just for anyone else reading this thread. That will...

No offense, but that solution is not at all what this issue was about. Home assistant has a protocol for MQTT discovery. The MQTT device publishes information to a specific...

That's one option, the other I have off the top of my head is to mathematically subtract the information from the charge chart