How to apply EEBUS use cases on the device / gateway side?

[memory-hws]

In my usage scenario, the device acts as a gateway: it collects data from inverters, batteries, and other components, and then reports this data to an EEBUS controller. However, I could not find any use case implementations related to this role. So I don't know how to report device data through the EEBUS protocol.

All the use case related code I have found so far appears to be written from the controller perspective. I am not sure whether my understanding is incorrect, or if the use case logic for the device/gateway side is expected to be implemented by integrators themselves.



Could you please explain how this is intended to work? Any guidance would be greatly appreciated.

[andig]

I guess you should read up on the EEBUS Use Case documentation: https://www.eebus.org/wp-content/uploads/2023/04/20221222-EEBUS-Overview-Use-Cases-v1.7.pdf

[memory-hws]

Thank you very much for your help, but I still don't know how to implement data reporting. For example, the following is the code implemented in the device-app to monitor battery data.

However, I don't know how to implement the corresponding code in HEMS to report data to the device-app. If I register the same use case, the device app will definitely not receive data. So how should I solve this problem?