If I get some time, yes, but the docs are very easy to update for even a novice githubber. Every page has an edit on github button. Just follow this guide:
This change should go to the climate component page and possibly the customize page.
Ok will do that. It’s just that it is only one of the parameters. Any others can be customized?
I’m glad I found this thread! I set up an ESP8266 MQTT gateway on the weekend and couldn’t work out how to get the HVAC control working.
I’ll work through the solutions presented here and will report back.
All entity state attributes can be customized, but some don’t make sense to customize cause they are just info for the user or part of the sensor report, and some are hidden by default so can be hard to find out about.
Can I use just the temperature setpoint without fan speed etc? Just got this in mysensors.json:
"131": {
"sensor_id": 131,
"children": {
"1": {
"id": 1,
"type": 29,
"description": "Thermostat Biuro",
"values": {
"45": "14.0",
"2": "0"
}
}
But there is no entity that corresponds to it. I was thinking this will make a thermostat faceplate anyway, but this is not the case.
Well summer time. And aircons don’t work anymore. I can switch on|off. But for example speed control is not working anymore. Same for temp change. Temp change is even more interesting. Set it from lets say 18 to 20 and than it just reverts back. Seems a lot of changes have been done from last summer
Mysensors.json of node in question
"41": {
"sensor_id": 41,
"children": {
"0": {
"id": 0,
"type": 29,
"description": "",
"values": {
"0": "24.8",
"44": "18",
"21": "CoolOn",
"22": "Max"
}
},
"2": {
"id": 2,
"type": 7,
"description": "",
"values": {
"1": "43.1",
"0": "1102525219"
}
},
"3": {
"id": 3,
"type": 6,
"description": "",
"values": {
"0": "24.8",
"32": "25.3",
"4": "16.100"
}
},
"4": {
"id": 4,
"type": 22,
"description": "",
"values": {
"45": "87.0",
"37": "269.0"
}
},
"5": {
"id": 5,
"type": 24,
"description": "",
"values": {
"45": "00A0604702",
"37": "160.62"
}
},
"136": {
"id": 136,
"type": 8,
"description": "",
"values": {}
},
"110": {
"id": 110,
"type": 7,
"description": "",
"values": {}
},
"16": {
"id": 16,
"type": 0,
"description": "",
"values": {}
},
"218": {
"id": 218,
"type": 1,
"description": "",
"values": {}
},
"164": {
"id": 164,
"type": 32,
"description": "",
"values": {}
},
"148": {
"id": 148,
"type": 38,
"description": "",
"values": {}
},
"254": {
"id": 254,
"type": 19,
"description": "",
"values": {}
},
"85": {
"id": 85,
"type": 4,
"description": "45470FE7F8",
"values": {}
}
},
"type": 7,
"sketch_name": "MYS Zal",
"sketch_version": "2.1",
"battery_level": 0,
"protocol_version": "1.4",
"heartbeat": 0
},
Any errors in your Home Assistant log?
Thanks for asking. Actually quite some. Didn’t notice. Seems several HA upgrades broke the MYS integration
Logger: mysensors.sensor
Source: /usr/local/lib/python3.8/site-packages/mysensors/sensor.py:141
First occurred: 8 июля 2021 г., 19:26:44 (5 occurrences)
Last logged: 8 июля 2021 г., 19:27:16
* Invalid <Message data="41;0;1;0;44;18">: Not valid message sub-type: 44 for object value @ data['sub_type']. Got 44 not a valid value for object value @ data['payload']. Got '18'
* Invalid <Message data="41;0;1;0;22;Max">: value must be either 0 or 1 for object value @ data['payload']. Got 'Max'
* Invalid <Message data="41;0;1;1;22;Auto">: value must be either 0 or 1 for object value @ data['payload']. Got 'Auto'
* Invalid <Message data="41;0;1;1;22;Min">: value must be either 0 or 1 for object value @ data['payload']. Got 'Min'
* Invalid <Message data="41;0;1;1;44;20.0">: Not valid message sub-type: 44 for object value @ data['sub_type']. Got 44 not a valid value for object value @ data['payload']. Got '20.0'
I’d open an issue on github about it.
Sorry for replying to this old topic, is this one resolved?? I get exactly the same issue as @moskovskiy82