-
Notifications
You must be signed in to change notification settings - Fork 21
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
Compatibility of EEBUS devices is not transparent #54
Comments
As both a software engineer and a user of multiple EEBus devices (washer, dryer, heatpump) and the SMA Home Manager: YES! |
@wimleers would you be interested in providing EEBUS data for your devices to https://github.com/enbility/devices ? Feel free to open a discussion in that Repo if so and you need help on how to do that |
Yes! On it! I have a Vaillant 75/5 and VR921 gateway since last week. I want:
I know this can be done using |
Did that: enbility/devices#2. |
Bringing this to Home Assistant would be really cool. It would be much more streamlined than messing around with ebusd |
Pairing is technically only a process for the two devices to be allowed to talk to each other. The UX for any user without this technical understanding has no idea about this, its implications and results in a bad experience.
An Elli wallbox can be paired with another Elli wallbox. Then nothing happens afterwards. There is no warning that nothing will happen or can happen.
A lot of users tried to pair the Elli wallbox with an SMA Home Manager 2.0 as both say they support EEBUS. Pairing worked and some people thought now charging is controlled by available PV surplus energy. Even though technically this can not work. The Elli wallbox limited the charging speed to 6A per phase and never changed it. The Elli wallbox doesn't even show an information or error message that the other device doesn't support required features and falls back to this charging mode. It only shows an yellow LED instead of a green LED.
Even electrical engineers setting up the devices do not have such an understanding and will not have sufficient understanding. It is just too complex and the varieties will only increase with more devices supporting EEBUS in the future.
Solutions:
NodeManagementDetailedDiscoveryData
andNodeManagementUseCaseData
responses and presenting this in an end-user friendly wayThe text was updated successfully, but these errors were encountered: