mqtt-hassio.cfg genaue Informationen

[sebska]

Hallo,

ich schreibe mal auf Deutsch, da ich da besser formulieren kann.

Ich glaube, das meine Konfiguration zwischen der 15.ctlv2.csv und dem HomeAssistant MQTT noch nicht vollständig ist.
Ich gehe davon aus, das ich noch weiter in der mqtt-hassio.cfg anpassen muss.

Es sind z.B die ganzen Z1Holidayxxxx (Datum und Zeit) nicht in HA vorhanden, ich sehe diese jedoch im MQTT-Explorer in HA.

Andere Werte z.B. die Z1QuickVetoDuration ist nur lesbar zu sehen.

Kann mir jemand erklären, was ich in der mqtt-hassio.cfg anpassen muss? Oder gibt es eine bessere Erklärung des Files (aus den Texten im File wierde ich nicht abschließend schlau) als Text, das ich es mir selber erarbeiten kann?

Viele Grüße Sebastian

[JonesGW-MGD]

Did you do this? : #1446 (reply in thread)

Using this in the ebusd start as a command line parameter will allow writable values. They are disabled by default.

[sebska]

Yes, i did this.
I can write e.g. temperatures in HA.

But not all writable things are writable in HA. I can write Z1QuickVetoDuration with Putty via TCP. But in HA it is not writable, only a "sensor".
And the Z1Holiday... Start/End Date/Time only appear in Putty-TCP or in MQTT-Explorer within HA. Not in the MQTT-Section of HA. So I can not see (or write) them within HA.
And the same with Z1QuickVetoEnd... Date/Time. It seems, that Date- and Timevalues are not recognized by MQTT Auto-Discovery.
So there must be something within mqtt-hassio.cfg, I guess.

[JonesGW-MGD]

So if you go to HA>Developer Tools>Services, and >go to YAML mode and create something like this:
service: mqtt.publish
data:
qos: "1"
retain: true
topic: ebusd/basv/z1HolidayTemp/set
payload: 14

and in your case it won't the basv but maybe ctlv2 - whatever your MQTT topic is, and chose a payload that is different from whatever this parameter is currently set at - are you saying it doesn't change the value in the controller?

[sebska]

No, you got me wrong.

1. I can change all writable values via TCP.
2. I can change values with HA, when they are e.g. number entities. E.g. temperatures.

But: (my current problems)
3) Writabe values appear as sensor entities. I cannot write them in HA, but they are writable in TCP. They need to be number entities in HA.
4) Time and Date values do not appear in HA. But in TCP and (MQTT- Explorer in HA) i can see them.

So in my thinking I need to do something in mqtt-hassio.cfg:

a) change sensor to number? ( if they are writable in the csv): e.g. Z1QuickVetoDuration
b) make values appear in HA (time, date): e.g. Z1QuickVetoEndDate

[JonesGW-MGD]

OK apologies, I hadn't realised you could write some but not others. Your mqtt-hassio.cfg differs from mine -

from line 148 you have:

type_map-number = number
type_map-list = string
type_map-time = time
# HA integration: skip string/date/datetime types completely
type_map-string =
type_map-date =
type_map-datetime =

For the similar block, I have:

type_map-number = number
type_map-list = string
type_map-time = time
type_map-date = date
type_map-datetime = datetime

# HA integration: skip string types completely
type_map-string =

You also seem to be missing or have commented out:

# HA integration: the mapping list for (potentially) writable string entities containing a date value field type, message name+field name, and unit.
type_switch-w-date =
    text,,,date =

type_switch-date =
    sensor,,, =

# HA integration: the mapping list for (potentially) writable string entities containing a datetime value field type, message name+field name, and unit.
type_switch-w-datetime =
    text,,,datetime =

type_switch-datetime =
    sensor,,, =

I don't know to be honest if this is related to your issue as I don't have the same problem you do.

[martin8310]

Hallo, @sebska gibt es hierzu eine Lösung? Ich verzweifle auch an der Config von dem Teil.