-
Notifications
You must be signed in to change notification settings - Fork 35
Description
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:
- The specification should be improved so the UX only allows pairing that can potentially be used together
- The specification should include a further compatibility state that has to be presented in the UI by using
NodeManagementDetailedDiscoveryData
andNodeManagementUseCaseData
responses and presenting this in an end-user friendly way - A UX guideline should be provided that covers all the possible scenarios the devices UX should cover to allow a seamless setup process.
- A public up to date website should be established which contains a list of the supported UseCases and Features and their respective role, and which are required on the other end. So planning and purchasing can be made transparent