incomplete HVAC switch mysensors

[diamantmatch]

Hello,

i was recently building a new HVAC node wich can send IR commands to my wall mounted air conditioning.
fortunately mysensors has several variables implemented so that i can send several values over to the node.
S_HVAC is the switch wich has the following variables:
V_HVAC_SETPOINT_HEAT this is a heat setpoint
V_HVAC_SETPOINT_COLD this is a cold setpoint
V_HVAC_FLOW_STATE this defines if it is cooling, heating, off or automatic
V_HVAC_FLOW_MODE this is a mode for sleeping of always on
V_HVAC_SPEED this mode defines the speed for the fan; FAN_1, FAN_2, FAN_3 or FAN_AUTO


unafortunately when i tried presenting the node to domoticz it was not recognised.
after some tips i tried sending back some values in the hope that a device would be created. but all i got in the log was the following:

Code: Select all

16-08-29 11:22:34.763 (mysensor) Temp (Baro Temp)
2016-08-29 11:22:34.772 (mysensor) General/Barometer (Baro)
2016-08-29 11:22:35.059 MySensors: Node: 12, Sketch Version: 1.0
2016-08-29 11:22:35.099 Error: MySensors: Unhandled sensor (sub-type=22), please report with log!
2016-08-29 11:22:35.108 Error: MySensors: Unhandled sensor (sub-type=21), please report with log!
2016-08-29 11:22:35.115 (mysensor) Thermostat (Setpoint Heat)
2016-08-29 11:22:35.298 (mysensor) Temp (Baro Temp)

since this moment i realized that maybe domoticz doesnt have all the variables for S_HVAC but only a temperature setpoint.

after another tip someone showed me the sourcecode and indeed, there is only a temperature setpoint variable listed under the S_HVAC.
https://github.com/domoticz/domoticz/bl ... Base.h#L53

maybe someone could explain me why the rest is missing or is it just left out for some reason?

[pj-r]

Yes, no one has implemented functionality for these "enum" switches yet:
- V_HVAC_FLOW_STATE
- V_HVAC_FLOW_MODE
- V_HVAC_SPEED

Selector switch type that makes possible implementing functionality for these came bit after these were added to mysensors.

There is one workaround:
You cant create three dummy selectors and specify all the needed values for those. Then you add three dimmers in your sketch. Hide those dimmers from domoticz UI. Can be done by adding $ in then begining of device name. Then in lua or blocky "link" these dummy selectors and dimmers together. So when dummy selector is changed in UI -> change value of dimmer in blocky or lua -> handle dimmer change in mysensors node(send message to heat pump). And same in opposite way.

[diamantmatch]

There is one workaround:
You cant create three dummy selectors and specify all the needed values for those. Then you add three dimmers in your sketch. Hide those dimmers from domoticz UI. Can be done by adding $ in then begining of device name. Then in lua or blocky "link" these dummy selectors and dimmers together. So when dummy selector is changed in UI -> change value of dimmer in blocky or lua -> handle dimmer change in mysensors node(send message to heat pump). And same in opposite way.

awesome! i am experimenting with this selector switch and it look pretty promising.
there is one thing i dont understand though, maybe you could enlighten me on this.

when i am writing a script in blockly i need to adress the mysensors node, but how do i handle the dimmer change and send something to an not exisistant ( according to domoticz ) child node?

[pj-r]

when i am writing a script in blockly i need to adress the mysensors node, but how do i handle the dimmer change and send something to an not exisistant ( according to domoticz ) child node?

Where do you handle dimmer change? Think there is bit of misunderstanding now.

In domoticz your create dummy selector and in mysensors S_DIMMER/V_DIMMER

You should be handling selector change and update the dimmers in mysensors node. And in mysensors node: instead of: V_HVAC_FLOW_STATE, V_HVAC_FLOW_MODE or V_HVAC_SPEED use V_DIMMER.

Then use blocky to "link" these two together. If the dimmer wont show up in domoticz try to send something random for example from present method.