Skip to content

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

Description

@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.

Image 

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions