This PR will remove the handling of HEMS and EEBUS devices because the API does not provide any features or data points.
The Functionality of managing the Vitocharge VX3 is not affected, the HEMS and EEBus devices are separate devices, which I accidentally messed up in my last PR
The handling of the E3_TCU unit will be changed to a gateway, like mentioned by @CFenner in PR #318
Maybe in the future there will be more possibilities to manage, for example Vehicle Charging Stations (VCS).
The devices are already listed, but we cannot access features or data points.
Sadly, I cannot test the TCU data point for Wi-Fi strength because my TCU is connected via Ethernet. There is a documented data point for Ethernet gateway.ethernet.config, but this also somehow doesn't show up on my TCU, so I can't implement this currently.
This PR will remove the handling of HEMS and EEBUS devices because the API does not provide any features or data points. The Functionality of managing the Vitocharge VX3 is not affected, the HEMS and EEBus devices are separate devices, which I accidentally messed up in my last PR The handling of the E3_TCU unit will be changed to a gateway, like mentioned by @CFenner in PR #318 Maybe in the future there will be more possibilities to manage, for example Vehicle Charging Stations (VCS). The devices are already listed, but we cannot access features or data points.
Sadly, I cannot test the TCU data point for Wi-Fi strength because my TCU is connected via Ethernet. There is a documented data point for Ethernet
gateway.ethernet.config
, but this also somehow doesn't show up on my TCU, so I can't implement this currently.