vwt12eh8

`became unavailable` means that the connection to the device has been lost. Unlike `undetected`, it does not mean that the input is turned off. I'm sure I've fixed the problem...

Yes, When there is really no input, the state should be `off`, not `unavailable`.

Are you sure you didn't set the warning condition to `state ! = 'on'`? To make it work correctly, you need to set either `state == 'off'` or `state !...

Perhaps that device trigger internally uses `state ! = 'on'` and not expecting `unavailable`. It's a bit more challenging, but I think you can ignore `unavailable` by setting the trigger...

Note that a device is considered disconnected when it has not sent any data for 15 consecutive seconds.

related #58

@GCustom Thank you. Later, we will publish a special branch that will parse the received data and include it in the diagnostic information, so please report back with the results...

A branch with additional diagnostic codes is now available. If you would like to help, please try the following and provide diagnostic information as a result. https://github.com/vwt12eh8/hassio-ecoflow/tree/serial-diagnostics ### Warning. -...

@lwsrbrts Thanks for providing the data. As far as I checked, it seems that only one of the batteries was notifying the serial number. If possible, could you also try...

I still can't seem to get any info on the battery on port 2... It seems to be difficult to manage devices by serial number...