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
Functionality for presenting sensors capabilities would help the contoller software to build automatically hvac switches for example.
For example:
gw.presentcaps(childId, listOfValues) (user could define names for these in the controller)
or even better: gw.presentcaps(childId, listOfKeys) (in this case values would be from 0 to count of list but names are provided automatically)
or the best: gw.presentcaps(childId, listOfValues, listOfKeys). The contoller could buid up the switch from this info.
One design question: Would this be called after or would it be alternative for gw.present(...)?
Keys would be used in UI of contoller and values(list of 8 bit int?) are what is transferred in messages.
For example my air source heat pump has only V_HVAC_MODE modes "Off", "HeatOn", "CoolOn". Values for these could be 0, 1 and 2.
Another idea: present these values in loop:
presentcap(uint8_t childSensorId, uint8_t sensorType, char *valueName, uint8_t value)
Would it be easier to implement in library side?
I think we also have to have this sensorType defined in call since there can be multiple sensors/actuator within the same child: V_HVAC_FLOW_STATE, V_HVAC_FLOW_MODE, V_HVAC_FLOW_SPEED..
There is now new switch type(SELECTOR) presented in Domoticz. With that its now possible to handle with V_HVAC enum switches.
Functionality for presenting sensors capabilities would help the contoller software to build automatically hvac switches for example.
For example:
One design question: Would this be called after or would it be alternative for gw.present(...)?
Keys would be used in UI of contoller and values(list of 8 bit int?) are what is transferred in messages.
For example my air source heat pump has only V_HVAC_MODE modes "Off", "HeatOn", "CoolOn". Values for these could be 0, 1 and 2.
Discussion about this on mysensors forum
The text was updated successfully, but these errors were encountered: