Skip to content
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

Present child sensor capabilities #356

Open
pj-r opened this issue Jan 18, 2016 · 2 comments

Comments

Projects
2 participants
@pj-r
Copy link

commented Jan 18, 2016

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:

  • 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.

Discussion about this on mysensors forum

@pj-r pj-r changed the title Present child sensor values Present child sensor capabilities Jan 18, 2016

@pj-r

This comment has been minimized.

Copy link
Author

commented Mar 16, 2016

Another thread from Domoticz forums
There is also example how this functionality could be used.

@pj-r

This comment has been minimized.

Copy link
Author

commented Mar 21, 2016

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..

@fallberg fallberg added this to To do in 2.4.0 via automation Feb 25, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.