Hey Aarti,
Sorry, I should have called out the link to the webinar better (its hard to see in the above post). Its probably nothing particularly different from what I’ve written above, but maybe provides some different emphasis. Affordability of Appliances Webinar Efficiency for Access Design Challenge - YouTube
One of the fastest ways to get manufacturer feedback and direct involvement might be just to directly encourage proposals and edits of the Nexus Channel Core “resource models”. These are the foundation upon which application-layer device interoperability is being built up, and capture ‘what’ might be valuable to share info about with other devices (e.g. battery) and what attributes, specifically, should/could be shared (capacity? voltage? low battery alarm threshold? etc).
The larger question is ‘what application level use cases are actually valuable when talking about sharing resource state between devices?’, which drives what resource models actually need to exist (instead of us just copying every existing OCF/ISO standard resource model out there). For instance, if no one actually cares about monitoring or controlling a fridge/freezer setpoint remotely, does it make sense to ‘standardize’ a fridge resource model with that attribute? etc.
I noticed that there is another thread open about how to make that process better/more streamlined as well: An RFC process to improve Open Source for Energy Access materials
I suspect the connector interoperability discussion is already going on via GOGLA, but I’m not involved at that level personally.