Seth

I spent a bunch of time with another user of my Home Assistant integration trying to figure out a similar issue, and the only thing we could come up with...

False alarm on the no logs thing; I had to power cycle the BLE proxies under 2024.5.1 first. I am letting it run a bit to collect logs.

``` 2024-05-05 17:26:02.068 WARNING (MainThread) [aioesphomeapi.connection] olimex-bluetooth-proxy-2898a8 @ 10.0.0.158: Connection error occurred: [Errno 104] Connection reset by peer 2024-05-05 17:26:02.205 INFO (MainThread) [backoff] Backing off _request_http(...) for 0.3s (pyopensprinkler.OpenSprinklerConnectionError: Cannot...

It eventually locks up the BT proxies and requires them to be power cycled. Waiting to install 2024.5.2 to see if that changes things.

I am still seeing it as well. The proxies need to be rebooted to recover.

EV charger appears to present as an inverter based on the sunspec ident block.

Maybe making it look like an inverter would let it reuse modbus definitions without SolarEdge having to support new types, but also if it looks like an inverter it wouldn't...

I can find modbus data about Keba P30 but not about P40. If SolarEdge is just using the P40 rebranded and the P30 modbus still works with the P40, I...

I can't use the UDP guide unfortunately, it needs to be modbus through the SolarEdge inverter bus to work with this integration.

No, I do not have an EV charger on my system. There are various modbus scanning utilities that might be able to help. This one is cross platform: https://github.com/SciFiDryer/ModbusMechanic