-
Notifications
You must be signed in to change notification settings - Fork 61
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
Node type specification #152
Comments
See #38 and the linked PR and so on. I had proposed to have this as extension but at that time there was no extension mechanism in place. |
Would this really be an extension? |
It is about the values :) |
Has any work been done on specifying a core set of device/node/property types? |
Would it be better to have a device $type topic rather than a node $type? |
@mjcumming I think there is a good argument for both. |
Probably we should come up with some use cases to try and vet out the best approach. My thoughts are that any further development along these lines is to allow controllers to have a functional understanding of Homie devices. Arguably, we need to start with properties and define additional properties (or behavior of existing). Ie. the OpenHAB implementation uses a Boolean for representing a switch or contact. That is fine but it should be defined somewhere. I use OpenHAB as an example and my guess is it is the most use controller for Homie devices. I am not a big fan of the use of the car example. Its just not a home automation use case. I also don't really see the purpose of Nodes. Its nice on paper as a way to structure devices but in any of the 100 Homie devices I have connected to OpenHAB, the Node has no real functionality. I don't see where a controller needs to know anything about Nodes. But since we have Nodes I am not suggesting we change or remove that. But I (from my use) don't understand their purpose. |
My mistake on hitting close.... |
I am going to close this so we can keep all discussion in this thread. |
I propose adding a set of predefined node types with required properties to improve the handling of devices by controllers.
We already have a required topic $type for each node, I think it would be a really good idea to define a set of types which require, but are not limited to certain properties. An example is given:
A "lamp" should have at least the following properties:
A "dimmable-lamp" should at least have:
The text was updated successfully, but these errors were encountered: