fensoft
(Fensoft)
1
Hello
I’m trying to use discovery for MQTT but I can’t make device works.
Here is my config:
"~": "maxcube2mqtt/valve/Bureau_Valve",
"unique_id": "maxcube_valve_Bureau_Valve",
"name": "Valve Bureau / Valve",
"temp_cmd_t": "~/setpoint/set",
"temp_stat_t": "~/setpoint",
"curr_temp_t": "~/temp",
"min_temp": "12",
"max_temp": "25",
"temp_step": "0.5",
"device": {
"manufacturer": "ELV",
"model": "valve",
"name": "Valve Bureau / Valve",
"identifiers": [
"maxcube_08289d"
],
"connections": [
[
"mac",
"08289d"
]
]
},
"origin": {
"name": "maxcube"
}
}
It’ s written here that I need connection
(and not connections
, typo ?) + identifiers
and name
.
Am I missing something else ?
francisp
(Francis)
2
This is one of mine, I don’t even use connections
{
"unit_of_measurement": "°C",
"device_class": "temperature",
"value_template": "{{value_json.TEMP}}",
"state_class": "measurement",
"state_topic": "rflink/Xiron-3201",
"name": "eetkamer_temperature",
"unique_id": "eetkamer_temperature",
"device": {
"identifiers": [
"xiron_3201"
],
"name": "xiron_3201",
"model": "Digoo temp & humidity sensor",
"manufacturer": "Digoo"
}
}
petro
(Petro)
3
well for 1, that’s not a valid mac address. If you don’t want it to show up in other device pages from other integrations, don’t use connections.
If the origin is the device, also omit that.
fensoft
(Fensoft)
4
I’ ve tried with this:
{
"~": "maxcube2mqtt/valve/Bureau_Valve",
"unique_id": "maxcube_valve_Bureau_Valve",
"name": "Valve Bureau / Valve",
"temp_cmd_t": "~/setpoint/set",
"temp_stat_t": "~/setpoint",
"curr_temp_t": "~/temp",
"min_temp": "12",
"max_temp": "25",
"temp_step": "0.5",
"device": {
"manufacturer": "ELV",
"model": "valve",
"name": "Valve Bureau / Valve",
"identifiers": [
"maxcube_08289d"
]
}
}
But still no “go to device” in the entity:
petro
(Petro)
5
Clear your cache and refresh the page.
fensoft
(Fensoft)
6
still the same problem. no linked device to the entity nor device in the device list
francisp
(Francis)
7
And you see the correct discovery message in e.g. MQTT Explorer ?
fensoft
(Fensoft)
8
in fact i’ve dumped this message from mqttexplorer itself from topic = homeassistant/climate/Bureau - Valve/config.
The entity itself works.
Don’t you need state_topic
in your payload for a device to be discovered, or am I confusing that with autodiscovery?
fensoft
(Fensoft)
10
climate entities doesn’t have “state_topic”.
fensoft
(Fensoft)
11
found a workaround: reboot homeassistant. maybe it’s a bug ?