thermostat_mode
doesn’t seem to be a valid capability
I did I by creating from a new device and added capability thermostat.
And also a lot of others like current, power, energy, text etc. After creating a new device. I could use the advanced topics to setup all my mqtt topics and used the example from post 116 to create a custom picker. Made me sweat whole day but it’s working so far.
So it’s working now?
The issue is this part:
“capability”: “enum”,
You have to select a valid capability that offers the needed events.
“thermostat_mode”: {
“capability”: “thermostat_mode”,
Yes working great. Thanks!
I have a problem getting values updated. I connected a water meter to MQTT and i can see that it regulary reports values. When i create a new device, based on MQTT Hub it seems to work.. .but it never gets any update. At the moment i add a 2nd device for the exact same topic the new device gets the current value and the old stuck one gets updated too.
Thats a test… before updateing the left one showed 0.021 although there was other values reported to MQTT in between.
I was always watching MQTT with MQTT Explorer:
So im 100% sure, that there was updates which did not hit the device in Homey…
The devices are configured as sensor with this topic:
{
"meter_water": {
"capability": "meter_water",
"stateTopic": "shellyplusuni-wasser-wm/watermeter/m3",
"template": "{{ value | float }}",
"displayName": "Water meter"
}
}
What could be the reason, that these devices are working for a short time and then stop updateing the values from MQTT Server?
Can you check if MqttClient app is restarted in between?
In this case, the topic registration gets lost.
New test version 4.5.0:
- adapted device settings for HomeyEnergy to new SDK options
- possibility to add energy settings for home battery, ev charger and electric car.
For home battery:
- set device option to “home battery”
- add
measure_power
(positive/negative value dependent on charge/discharge). - add
meter_power.charged
andmeter_power.discharged
(you can use other names) - insert these capabilities in device settings into corresponding fields
For ev charger:
- use
measure_power
andmeter_power
capability and set device option to “EV charger”. - If you are using V2G (vehicle top grid), you can set the meter power imported/exported capability
For electric car:
- set device option to “electric car”
- add
measure_battery
andev_charging_state
capability
Im trying to add a device with multiple utilization and one temperature topic.
The device is sensor… i was a bit playing and came to that config:
{
"measure_temperature": {
"capability": "measure_temperature",
"stateTopic": "home/system/temp",
"valueTemplate": "{{value}}",
"displayName": "CPU Temperature"
},
"measure_humidity": {
"capability": "measure_humidity",
"stateTopic": "home/system/cpu",
"valueTemplate": "{{value}}",
"displayName": "CPU Usage (%)"
},
"measure_luminance": {
"capability": "measure_luminance",
"stateTopic": "home/system/ram",
"valueTemplate": "{{value}}",
"displayName": "RAM Usage (%)"
},
"measure_pressure": {
"capability": "measure_pressure",
"stateTopic": "home/system/disk",
"valueTemplate": "{{value}}",
"displayName": "Disk Usage (%)"
}
}
i had to use different types, because it seems only to accept one topic per type…
The result shows the correct values, but very strange:
Is there a way to show multiple utilization percentages with correct unit and a more generic icon?
You are using different standard capabilities. Using subcapabilities you can add a capability sevreal times.
And the app offers 2 custom capabilities: measure_number
and measure_string
for generic values.
Example:
{
"measure_temperature": {
"capability": "measure_temperature",
"stateTopic": "home/system/temp",
"valueTemplate": "{{value}}",
"displayName": "CPU Temperature"
},
"measure_number.cpu": {
"capability": "measure_number.cpu",
"stateTopic": "home/system/cpu",
"valueTemplate": "{{value}}",
"displayName": "CPU Usage (%)",
"unit": "%"
},
"measure_number.ram": {
"capability": "measure_number.ram",
"stateTopic": "home/system/ram",
"valueTemplate": "{{value}}",
"displayName": "RAM Usage (%)",
"unit": "%"
},
"measure_number.disk": {
"capability": "measure_number.disk",
"stateTopic": "home/system/disk",
"valueTemplate": "{{value}}",
"displayName": "Disk Usage (%)",
"unit": "%"
}
}
The units should work, too (not tested). But the icons are predefined for the capability and not changeable.
I hope the example is working for you