Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove HEMS an EEBus devices and change TCU handling to gateway #364

Merged
merged 10 commits into from
Apr 2, 2024

Conversation

Nibot1
Copy link
Contributor

@Nibot1 Nibot1 commented Mar 30, 2024

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.

Copy link
Member

@CFenner CFenner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -52,21 +52,12 @@ def __extract_devices(self):
for installation in self.installations:
for gateway in installation.gateways:
for device in gateway.devices:
if device.deviceType not in ["heating", "zigbee", "vitoconnect", "electricityStorage", "EEBus", "hems", "tcu", "ventilation"]:
if device.deviceType not in ["heating", "zigbee", "vitoconnect", "electricityStorage", "tcu", "ventilation"]:
continue # we are only interested in heating, photovoltaic, electricityStorage, hems and ventilation devices

if device.id == "gateway" and device.deviceType == "vitoconnect":
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably this is also no longer necessary.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes you are right, this is not necessary anymore.

@Nibot1
Copy link
Contributor Author

Nibot1 commented Mar 30, 2024

Sadly, I cannot test the TCU data point for Wi-Fi strength because my TCU is connected via Ethernet, but I will write a test for the Serial number

Copy link
Member

@CFenner CFenner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(self.asElectricalEnergySystem, r"E3_TCU10_x07", ["type:tcu"]),
(self.asElectricalEnergySystem, r"E3_EEBus", ["type:eebus"]),
(self.asElectricalEnergySystem, r"E3_VitoCharge_03", ["type:energy_storage"]),
(self.asGateway, r"E3_TCU10_x07", ["type:gateway;TCU300"]),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The TCU could probably also be ignored in the HA integration, right?

https://github.com/home-assistant/core/blob/dev/homeassistant/components/vicare/const.py#L18

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the TCU does not provide any information

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you create the PR in the Home Assistant Repo?

@woehrl01
Copy link
Collaborator

woehrl01 commented Apr 2, 2024

Thank you @Nibot1 lgtm

@woehrl01 woehrl01 merged commit f8d1b44 into openviess:master Apr 2, 2024
4 checks passed
@Nibot1 Nibot1 deleted the fix/e3_tcu-hems-eebus_handling branch April 2, 2024 19:42
@CFenner CFenner added the enhancement New feature or request label Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants