if I change:
configuration.yaml
#mqtt: !include mqtt.yaml
and mqtt.yaml
mqtt:
sensor:
- name: weather_station_outtemp_c
unique_id: uniqueid__weather_outtemp_c
icon: mdi:thermometer
state_topic: "weather/outTemp_C"
value_template: "{{ value | round(1) }}"
unit_of_measurement: "°C"
- name: weather_station_intemp_c
unique_id: uniqueid__weather_intemp_c
icon: mdi:thermometer
state_topic: "weather/inTemp_C"
value_template: "{{ value | round(1) }}"
unit_of_measurement: "°C"
- name: weather_station_extratemp1_c
unique_id: uniqueid__weather_extratemp1_c
icon: mdi:thermometer
state_topic: "weather/extraTemp1_C"
value_template: "{{ value | round(1) }}"
unit_of_measurement: "°C"
no errors
MQTT integration create 3 entities
but value is "Unknown"
Il giorno sabato 10 febbraio 2024 alle 07:40:42 UTC+1 Claudio ha scritto:
> tanks Peter,
> i add in configuration.yaml the line
> mqtt: !include mqtt.yaml
> i create in /packages file mqtt.yaml
>
>
> but a have this error
> Configuration errors
> Error loading /config/configuration.yaml: in "/config/configuration.yaml",
> line 31, column 7: Unable to read file /config/mqtt.yaml.
>
> this is my configuration.yaml file
> ----------------
>
> # Loads default set of integrations. Do not remove.
> default_config:
>
> # Example configuration.yaml entry
>
>
> # Load frontend themes from the themes folder
> frontend:
> themes: !include_dir_merge_named themes
>
> automation: !include automations.yaml
> script: !include scripts.yaml
> scene: !include scenes.yaml
>
> http:
> ssl_certificate: /ssl/fullchain.pem
> ssl_key: /ssl/privkey.pem
>
> homeassistant:
> packages: !include_dir_named packages
>
> # Example configuration.yaml entry
> evohome:
> username: "xxxxxxxxxxx"
> password: "xxxxxxxxxxx"
>
> # Example configuration.yaml entry
>
>
> mqtt: !include mqtt.yaml
> -------
>
> where am I wrong?
>
>
> Il giorno venerdì 9 febbraio 2024 alle 23:31:28 UTC+1 Vetti52 ha scritto:
>
>> It is easier to keep the mqtt data in a separate file.
>> So just add in your configuration.yaml the line
>>
>> mqtt: !include mqtt.yaml
>>
>> and create a separate mqtt.yaml file containing the data, you have
>> exported from weewx into your mqtt broker.
>> My mqtt.yaml looks like (be careful with the indentations!):
>>
>> sensor:
>> - name: weather_station_outtemp_c
>> unique_id: uniqueid__weather_outtemp_c
>> icon: mdi:thermometer
>> state_topic: "weather/outTemp_C"
>> value_template: "{{ value | round(1) }}"
>> unit_of_measurement: "°C"
>> - name: weather_station_intemp_c
>> unique_id: uniqueid__weather_intemp_c
>> icon: mdi:thermometer
>> state_topic: "weather/inTemp_C"
>> value_template: "{{ value | round(1) }}"
>> unit_of_measurement: "°C"
>> - name: weather_station_extratemp1_c
>> unique_id: uniqueid__weather_extratemp1_c
>> icon: mdi:thermometer
>> state_topic: "weather/extraTemp1_C"
>> value_template: "{{ value | round(1) }}"
>> unit_of_measurement: "°C"
>>
>> This is just the top of the file. There are a lot more of state/topics,
>> and they must meet those, which you have uploaded to the mqtt broker.
>> HTH
>> Peter
>> Claudio schrieb am Freitag, 9. Februar 2024 um 17:19:31 UTC+1:
>>
>>> import weewx data from mqtt to home assistant.
>>> I can't configure the configuration.yaml file, if I go to the mqtt
>>> component the weewx topic is visible but it doesn't create the entities for
>>> me and when it creates them it tells me that they are not active.
>>> Does anyone have an example of the configuration.yaml for me
>>>
>>> Thank you
>>> Claudio
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/2ee275d9-8703-42aa-ab09-ebd72a406512n%40googlegroups.com.
