You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2024. It is now read-only.
I see you are implementing the SHIP protocol from EEBUS for usage with S2 standard. Is this an indication that you're planning on merging with EEBUS or reusing the EEBUS standard to a higher degree? From my very basic understanding the S2 standard and EEBUS is mostly targetting the same use cases already.
The text was updated successfully, but these errors were encountered:
@mansandersson Hi! No this is not the case. This repo was started as an exercise to understand the SHIP protocol better and to provide a working proof-of-concept. There are currently no plans to bring this repo further. The goal of this PoC was to see if S2 could also run on top of SHIP and if that is desirable. TNO is driving S2 design and I am currently not involved in that process.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I see you are implementing the SHIP protocol from EEBUS for usage with S2 standard. Is this an indication that you're planning on merging with EEBUS or reusing the EEBUS standard to a higher degree? From my very basic understanding the S2 standard and EEBUS is mostly targetting the same use cases already.
The text was updated successfully, but these errors were encountered: