-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenADR3.0 support? #160
Comments
OpenADR 3.0 looks like a big step forward for ease of use and modernity. I have no plans at the moment to integrate it into the existing OpenLEADR library because the two are so different that it would make much more sense to create a separate OpenADR 3.0 library for the new stuff. I currently don't have enough time to get started on this, but I'm happy to work with others to build a package for OpenADR 3. If this is something that you'd like to collaborate on, please let me know. I think the included Swaggerdoc should get you up and running in the programming language of your choice pretty quickly, but I'm sure there is room for a dedicated implementation like OpenLEADR has provided for the 2.0 version. Let me know your thoughts! |
@stan-janssen @jamesharrow I believe we can start supporting OpenADR 3.0 via a new dedicated set of repositories to that version. I agree that 2.0 and 3.0 are very different. We should continue to support in parallel the Open ADR 2.0 as it is widely adopted. |
Hi, I would love to have access to an OpenADR 3.0 implementation. I can contribute to the development of the project. However, I do not know where to start. Will it be possible to use the LFE to share this message worldwide to find people/organizations interested in developing the OpenADR 3.0 development support? @stan-janssen @axmsoftware @jamesharrow how could we proceed? |
It looks like OpenADR3.0 has been published now and uses WebSockets and JSON instead of SimpleHTTP and XML.
Are there any plans to extend this to support OpenADR3.0?
https://www.openadr.org/openadr-3-0
Thanks
The text was updated successfully, but these errors were encountered: