-
Notifications
You must be signed in to change notification settings - Fork 6
Description
Hey there,
I'm working for Victron Energy. We built an S2 PoC together with TNO and are now in the process of adopting S2 for some of our products.
For us, CEM and RM's are located on the same device and we use D-Bus for interprocess communication. Things like discovery, encryption, etc. are not relevant in our context or already get handled by existing functionality. We would still like to (and currently do) use the S2 Python library to not reinvent the wheel regarding generating models as well as parsing and validating messages.
I have welcomed the fact that the websocket-related parts of the library have already been moved to an optional package and I would like to encourage you to keep it that way. On our OpenEmbedded based Linux hardware we deliberately do not use pip and choose each dependency very carefully due to space and security concerns.
Currently, the S2Connection class still is tightly coupled to websockets. What I would therefore like to see is a more generic S2Connection base class, which is independently of the communication protocol.
For the first steps, we derived our own connection class from S2Connection. If you are interested, I can create a PR with a proposal on how to achieve this more generic base class.