Quantcast
Channel: Configuration - Home Assistant Community
Viewing all 106223 articles
Browse latest View live

How to view dismissed notifications during HomeKit (bridge) install?

$
0
0

Total noob here. Testing HA via Synology on a point-and-click docker install. I’m going through the HomeKit installation and I’ve gotten the QR codes, however, I hit “dismiss” on some of them accidentally. How do I view my previous notifications (specifically the ones with the QR codes, but the general question stands)?

1 post - 1 participant

Read full topic


Camera Stream troubleshooting help please

$
0
0

I’m trying to get any of my camera to stream to a Nest Hub with no luck. I’ve selected Arlo cams, Wyze cam, and Nest Hello (doorbell) with same results in automation. I can view them fine in frontend, so I know it’s not the camera’s picture.

alias: Test
description: ''
trigger: []
condition: []
action:
  - service: camera.play_stream
    data:
      media_player: media_player.kitchen_max
    target:
      entity_id: camera.aarlo_front_porch
mode: single

I get the attached on the Nest hub. It’s just the streaming logo. No sound or picture from camera

1 post - 1 participant

Read full topic

Lovelace-layout-card not working or installing?

$
0
0

I have tried to install lovelace-layout-card using the HACS install from a custom repository as I cannot find it anywhere on the system. I enter in the repository field:

For the category I choose Lovelace. Click on [Add] and get:

image

Well I cannot find it anywhere and every time I try anything from the various pages I get the error “Custom element doesn’t exist:”

My directory structure looks like:

image

Note NO local folder. config/www/community I have:

image

I’m not seeing errors that seem to say I am using it wrong. All the errors are “Custom element doesn’t exist:”

So it reports it exist in the “store”, yet I search and it’s not found? What do they mean by “the store”?

1 post - 1 participant

Read full topic

Issue with an Automation

$
0
0

Would someone be kind enough to look over this automaiton?

The lights come on, some on at the requested brightness, others at full. The double plug switch option never comes on. The lights do not turn off after any amount of time, I have to manually turn them off.

- id: '1640321742258'
  alias: Front Door Triggered Lights
  description: Turn on most lights after 2045
  trigger:
  - type: opened
    platform: device
    device_id: 67c71e4256c239940d1ce93d2dea9cba
    entity_id: binary_sensor.front_door
    domain: binary_sensor
  condition:
  - condition: time
    after: '20:45:00'
  action:
  - service: light.turn_on
    target:
      entity_id:
      - light.hallway
      - light.livingroom
      - light.pc
    data:
      brightness_pct: 30
  - delay:
      hours: 0
      minutes: 5
      seconds: 0
      milliseconds: 0
  - service: light.turn_off
    target:
      entity_id:
      - light.hallway
      - light.livingroom
      - light.pc
  - service: switch.turn_on
    target:
      entity_id: switch.double_plug_left
  - delay:
      hours: 0
      minutes: 3
      seconds: 0
      milliseconds: 0
  - service: switch.turn_off
    target:
      entity_id: switch.double_plug_left
  mode: single

1 post - 1 participant

Read full topic

Control LED strip brightness through MQTT with automation

$
0
0

Hi,

First of all Merry Christmas to everyone who celebrates it!
These forums have helped me a numerous times, but I can’t seem to find a solution for my current problem. I’m starting to think that I’m overthinking something, so just tell me if this is the case.
I have a LED strip connected to an arduino nano, which has mysensors (fastled library) sketch flashed. The arduino is connected to a Pi with a USB cable. Pi is running HA in a python venv. This works fine.
I also have mqttstatestream set up so I can control all my HAs running a separate Pis (one per each room)
mqttstatestream in general also works fine.
I can turn the LED strip on/off, can set the color. The issue is only with setting the brightness of the LED strip from the master HA.
Now the code:
Light config on the master HA:

  - platform: mqtt
    name: TK Lampa
    command_topic: "beosztottak/szulotv/mqttstates/light/tklampa_0_15/set_status"
    state_topic: "beosztottak/szulotv/mqttstates/light/tklampa_0_15/V_STATUS"
    state_value_template: "{{ value }}"
    brightness_command_topic: "beosztottak/szulotv/mqttstates/light/tklampa_0_15/set_percent"
    brightness_state_topic: "beosztottak/szulotv/mqttstates/light/tklampa_0_15/V_PERCENTAGE"
    brightness_value_template: "{{ ((value | float / 100) * 255) | int }}"
    rgb_command_topic: "beosztottak/szulotv/mqttstates/light/tklampa_0_15/set_rgb"
    rgb_state_topic: "beosztottak/szulotv/mqttstates/light/tklampa_0_15/V_RGB"
    rgb_value_template: "{{ value }}"
    payload_on: "ON"
    payload_off: "OFF"
    optimistic: true
    qos: 2

Automations on the slave HA:

- id: '1619194286185'
  alias: TK_lampa_fel
  description: ''
  trigger:
  - platform: mqtt
    topic: beosztottak/szulotv/mqttstates/light/tklampa_0_15/set_status
    payload: 'ON'
  condition: []
  action:
  - service: homeassistant.turn_on
    data: {}
    entity_id: light.tklampa_0_15
  mode: single

- id: '1619201591539'
  alias: TK_lampa_BRGHT
  description: ''
  trigger:
  - platform: mqtt
    topic: beosztottak/szulotv/mqttstates/light/tklampa_0_15/set_percent
  condition: []
  action:
  - service: homeassistant.turn_on
    data: {}
    entity_id: light.tklampa_0_15
  - service: light.turn_on
    target:
      entity_id: light.tklampa_0_15
    data:
      brightness: '{{ states.sensor.sen_tk_lampa_brght_korr.state }}'
  mode: single

- id: '1619202719976'
  alias: TK_lampa_color
  description: ''
  trigger:
  - platform: mqtt
    topic: beosztottak/szulotv/mqttstates/light/tklampa_0_15/set_rgb
  condition: []
  action:
  - service: light.turn_on
    target:
      entity_id: light.tklampa_0_15
    data:
      rgb_color: '{{ states.sensor.tk_lampa_set_rgb.state }}'
  mode: single

- id: '1619203224641'
  alias: TK_lampa_LE
  description: ''
  trigger:
  - platform: mqtt
    topic: beosztottak/szulotv/mqttstates/light/tklampa_0_15/set_status
    payload: 'OFF'
  condition: []
  action:
  - service: homeassistant.turn_off
    data: {}
    entity_id: light.tklampa_0_15
  mode: single

and the config for the MQTT sensors set up on the slave:

  - platform: mqtt
    name: TK_lampa_set_percent
    state_topic: "beosztottak/szulotv/mqttstates/light/tklampa_0_15/set_percent"
    #value_template: "{{ ((value | float / 255) * 100) | int }}"
    value_template: "{{ value }}"
    qos: 0

  - platform: mqtt
    name: TK_lampa_set_rgb
    state_topic: "beosztottak/szulotv/mqttstates/light/tklampa_0_15/set_rgb"
    qos: 0

  - platform: mqtt
    name: TK_lampa_set_status
    state_topic: "beosztottak/szulotv/mqttstates/light/tklampa_0_15/set_status"
    qos: 0

  - platform: template
    sensors:
      sen_tk_lampa_brght_korr:
        value_template: '{{ ((states("sensor.tk_lampa_set_percent") | float / 255) * 100) | round(0) }}'

I know that the other automations are not needed for the issue, I just pasted them to show that I’m trying to do something similar to them.
I think I understand the issue: HA is sending a value between 0-255 and the V_PERCENTAGE in mysensors is a 0-100 value.
I have found some posts regarding similar issues, that’s where I’ve got the formula form for sen_tk_lampa_brght_korr, but none of them seems to help me.

What I know until now.

  • On the master you need to have separate MQTT topics for command and state
  • These separate topics need to use the same value range (eg.:0-255), otherwise the brightness slider “jumps” around when changing it.
  • Any math in the “brightness” field of the automation on the slave does not work. That’s why I’ve created sen_tk_lampa_brght_korr sensor
  • I’ve also tried to put an attribute to the “brightness” field of the automation on the slave, like “states.light.tklampa_0_15.attributes.brightness” without luck.

The only thing I don’t understand is why doesn’t the value change in sen_tk_lampa_brght_korr change the brightness of the LEDs.

I’m not sure if any logs are needed in this case, because in general things work, so it’s only my way of thinking that needs to be adjusted…

Thanks for the help!

1 post - 1 participant

Read full topic

Genie client

$
0
0

I followed the guide here:

The server itself is working but I am unable to get any clients to connect.

Any tips on how to triage or fix? or has anyone got the Genie client working?

genie::WebServer-**Message**: 23:02:06.816: Web UI listening on port 8000

genie::state::State-**Message**: 23:02:06.816: ENTER state Sleeping

PulseAudio connection established

genie::conversation::Client-**Message**: 23:02:06.960: Sent access token request to Home Assistant, got HTTP 8

(genie-client:19714): genie::conversation::Client-**WARNING** **: 23:02:06.960: Failed to get access token from Home Assistant: (null)

genie::conversation::Client-**Message**: 23:02:09.964: Requesting Home Assistant session token from http://xxxx:443/api/hassio/ingress/session

genie::conversation::Client-**Message**: 23:02:09.981: Sent access token request to Home Assistant, got HTTP 8

(genie-client:19714): genie::conversation::Client-**WARNING** **: 23:02:09.982: Failed to get access token from Home Assistant: (null)

1 post - 1 participant

Read full topic

Float expected?

$
0
0

There are strange things going on… Just to make it easier, I reduced a script to makes this test.

Here is the simple script

alias: 'Switch : Airco float'
fields:
  temperature:
    description: The temperature to set the airco at
    default: 19
    example: 21
sequence:
  - service: climate.set_temperature
    data:
      temperature: '{{ temperature }}'
    target:
      entity_id: climate.airco_gang
description: Set airco temperature
mode: single

Calling this script from a button like this works fine

type: button
tap_action:
  action: call-service
  service: script.switch_airco_float
  service_data:
    temperature: 20
  target: {}
name: Test gang

Replacing the 20 degrees by a helper gives me an error about “float expecting” ?

type: button
tap_action:
  action: call-service
  service: script.switch_airco_float
  service_data:
    temperature: '{{ states(''input_number.temperatuur_airco_gang'')|float}}'
  target: {}
name: Test gang

Schermafbeelding 2021-12-28 082523

1 post - 1 participant

Read full topic

Pulse counter - from energy to power

$
0
0

Hi there,

I have a pulse counter connected to an rpi zero which sends its values via MQTT to home assistant running on another hardware component. The MQTT messages look like this:

{
    "fields": {
        "nstime": 1640676204429749500,
        "pulse": 3911667,
        "uptime": 11280557.66
    },
    "name": "s0meter",
    "tags": {
        "host": "s0pi",
        "path": "/home/pi/s0readings/sensorlog-current.txt"
    },
    "timestamp": 1640676204
}

The ‘nstime’ and ‘pulse’ fields are the most important ones:

  • pulse: the current pulse amount, my s0 meter gives 1000 pulses per kWh
  • nstime: the epoch at the time of the pulse

This gives me energy, not power. According to Pulse counter to current usage I should be able to use the derivative component (Derivative - Home Assistant) to calculate power.

However, I have the impression the derivative function will use the time that HA received the MQTT message. This is incorrect in my case: it should use the epoch mentioned in the MQTT message (nstime).

Is there a way to calculate the power manually, using e.g. a template? I guess it should be something like:
W = 1Wh / ( epoch(last_pulse) - epoch(previous_pulse) / 3600 )

1 post - 1 participant

Read full topic


Show water usage as a bar chart for a selectable period

$
0
0

What are at the moment the options to show the water usage in a chart for a selectable period?

I know that there are some discussions about adding it to the Engery Dashboard. But for what I have seen so far is that is not added at this time.

1 post - 1 participant

Read full topic

Entity card showing monthly electricity cost of 2 plugs

$
0
0

I use this code to track the combined kWh energy usage of 2 sonoff s31 plugs, then I calculate the electricity cost. But I can’t figure out how to display the sum of the last 30 days electricity cost in an entity card

sensor:
  - platform: integration
    source: sensor.sonoff_10014f7842_power
    name: grow_tent1_kWh
    unit_prefix: k
    unit: kWh
    round: 2


      all_grow_tent_kwh_cost:
        friendly_name: "Total electricity cost (Grow tents)"
        unit_of_measurement: '$'
        value_template: "
        {{ 
            ( float(states('sensor.grow_tent1_kwh')) + float(states('sensor.grow_tent2_kwh')) ) * 0.09502
        }}
        "

1 post - 1 participant

Read full topic

Windows in Alexa & Nabu Casa

$
0
0

Hi,

I was used to set my windows as Covers in exporting entities to alexa through Nabu Casa.
I see here: Link display entities categories changed (I believe).

I suspect this is more due to Alexa/Amazon than Nabu Casa itself, but I was wondering what is the right category now for “windows”.

2 posts - 2 participants

Read full topic

Add Danalock V3 in Z Wave JS

Map card - exclude family members from bounds when they're interstate?

$
0
0

Hi Team,

In the event that one of the family are interstate I’d like to exclude them from the map view so that I can get a more meaningful view of who is in the same city. I’ve been fumbling through the code and thought that putting “fitZones: false” in the config might do the trick but no luck. I’m now wondering if my best bet is to do this using leaflet javascript after the fact.

Before I go too far down the road does anyone have any advice?

Thanks,
Dim

1 post - 1 participant

Read full topic

Calculated temperature sensor

$
0
0

Hello,

I want to setup a “virtual” sensor that is the difference between two measured temperatures that I would use for controlling a circulation pump in my heating system.

What I would like to do is ad sensor A that presents a temperature that is sensor X – sensor Y as an example.

Believe it or not I have tried to search for an answer but haven’t been able to find it.

Could someone point me in the right direction?

Kind regards,

Fredrik Mörner

1 post - 1 participant

Read full topic

Template sensor with discrete string values

$
0
0

I have created a multiline-if template sensor that combines few other sensor values and generates a human friendly ouput for the status of my heat pump.

The template sensor is defined like this:

template:
  - sensor:
      - name: "Nilan_CompactP"
        state: >
          {% if is_state('binary_sensor.nilan_compactp_compressorstate', 'off') %}
            off
          {% elif is_state('binary_sensor.nilan_compactp_deicingheatexchanger', 'on') or is_state('binary_sensor.nilan_compactp_deicingheatpump', 'on') %}
            defrosting
          {% elif is_state('binary_sensor.nilan_compactp_heatvalve', 'on') and is_state('binary_sensor.nilan_compactp_fourwayvalve', 'off') %}
            heating
          {% elif is_state('binary_sensor.nilan_compactp_heatvalve', 'on') and is_state('binary_sensor.nilan_compactp_fourwayvalve', 'on') %}
            cooling
          {% elif is_state('binary_sensor.nilan_compactp_hotwatervalve', 'on') and is_state('binary_sensor.nilan_compactp_fourwayvalve', 'off') %}
            hot water production
          {% else %}
            unknown
          {% endif %}
        state_class: measurement

The sensor itself works OK, meaning that it outputs the correct string value. The issue is with the history card in the GUI - it wants to plot a chart, but obviously fails since there are no numeric values.

I would like to have a discrete history chart, similar to the weather integration:
image

Question: How can I define a custom “enum” for my sensor?

1 post - 1 participant

Read full topic


Rest sensor unavailable; logfile full of errors

$
0
0

Hi, probably the solution is simple, but cannot figure this out, how to prevent many error messages.

I read a JSON from a REST sensor, and merge them in multiple sensors and binary_sensors.

Sometimes the REST fails, and the sensor will give “unavailable” for all other sensors and binary_sensors.
When this happens, the log is flooded with errors;

ERROR (MainThread) [homeassistant.helpers.event] Error while processing template: Template("{{ state_attr('sensor.laadpaal_straat_sensors', 'evses')[0]['status'] == 'Occupied' }}")
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 406, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1771, in _render_with_context
    return template.render(**kwargs)
  File "/usr/local/lib/python3.9/site-packages/jinja2/environment.py", line 1291, in render
    self.environment.handle_exception()
  File "/usr/local/lib/python3.9/site-packages/jinja2/environment.py", line 925, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/local/lib/python3.9/site-packages/jinja2/sandbox.py", line 303, in getitem
    return obj[argument]
jinja2.exceptions.UndefinedError: None has no element 0

Binary_sensor:

  - platform: template
    sensors:
      laadpaal_po_l:
        device_class: occupancy
        friendly_name: "EV charger links"
        value_template: >-
          {{ state_attr('sensor.laadpaal_straat_sensors', 'evses')[0]['status'] == 'Occupied' }}
        icon_template: >
          {% if state_attr('sensor.laadpaal_straat_sensors', 'evses')[0]['status'] == 'Occupied' %} mdi:car-electric
          {% elif state_attr('sensor.laadpaal_straat_sensors', 'evses')[0]['status'] == 'Available' %} mdi:car-electric-outline
          {% else %} mdi:alert-circle-outline
          {% endif %}

Any help or suggestion is welcome!

1 post - 1 participant

Read full topic

Zigbee2MQTT addon

$
0
0

I want to use the Zigbee2MQTT addon. This addon is not visible in the Add-on store, neither in the Official add-ons nor in the Home Assistant Community Add-ons. I can add it by coupling a repository in Github, but why is it not available in the Add-on Store? Is it in beta, or not yet certified or is there a different reason why it is not in the Add-on Store? A comparable add-on for Z-Wave is available in the Add-on store, so why not for Zigbee?

1 post - 1 participant

Read full topic

Automation for humidifier

$
0
0

Automation for humidifier

I suggest that those who are not indifferent share their options for automating the humidifier, sensors, and also share cards. Each of us can do something interesting and your idea may be useful.

Smartmix Evaporative Humidifier Humidifier added through this integration xiaomi airpurifier

My automation option is like this. I am using a humidity sensor and have created an auxiliary number element for the target humidity. I made a difference between them so that the fan speed was adaptive and depended on the difference between the humidity sensor and the auxiliary number element. Thus, if the room humidity and the target humidity will have more than the specified, then the fan speed will be high, but as the difference between the humidity sensor and the auxiliary number element decreases, the fan speed will decrease, and when the specified humidity reaches, the speed will be minimal.

Sensor

sensor:
  - platform: template
    sensors:
      livingroom_airhumidifier_auto_speed:
        friendly_name: "Living Room: Humidifier. Auto speed"
        value_template: >
            {% set tiv_humidity = states("sensor.livingroom_tiv_humidity") %}
            {% set target_humidity = states("input_number.livingroom_humidifier_target_humidity") %}
            {% set sum = target_humidity|int - tiv_humidity |int  %}
            {% if sum < 0 %} Silent
            {% elif sum >= 0 and sum < 4.8 %} Silent
            {% elif sum > 4.9 and sum < 9.8 %} Medium
            {% elif sum > 9.9 %} High
            {% endif %}

Automation

alias: 'Living Room: Humidifier. Automatic ventilation speed'
description: >-
  The fan speed is determined by the difference between the target and room
   humidity
trigger:
  - platform: state
    entity_id: sensor.livingroom_airhumidifier_auto_speed
    id: 'Humidifier: Auto speed'
  - platform: state
    entity_id: input_boolean.livingroom_humidifier_auto_power_on_off
    from: 'off'
    to: 'on'
    id: 'Humidifier: Auto speed enabled'
  - platform: state
    entity_id: fan.gostinaia_uvlazhnitel_xiaomi_evaporative
    from: 'off'
    to: 'on'
    id: Humidifier included
condition:
  - condition: state
    entity_id: input_boolean.livingroom_humidifier_auto_power_on_off
    state: 'on'
  - condition: state
    entity_id: fan.gostinaia_uvlazhnitel_xiaomi_evaporative
    state: 'on'
action:
  - service: fan.set_preset_mode
    target:
      entity_id: fan.gostinaia_uvlazhnitel_xiaomi_evaporative
    data:
      preset_mode: '{{states("sensor.livingroom_airhumidifier_auto_speed")}}'
mode: single

Card

image

To create this card, I used integration multiple entity row and group

type: entities
entities:
  - entity: fan.gostinaia_uvlazhnitel_xiaomi_evaporative
    type: custom:multiple-entity-row
    name: Humidifier
    toggle: false
    state_color: true
    show_state: false
    secondary_info:
      attribute: water_level
      name: Water level
      unit: '%'
    entities:
      - entity: group.livingroom_airhumidifier_info_and_menu
        name: Menu
        state_color: true
        icon: mdi:information-outline
        styles:
          width: 40px
      - entity: sensor.gostinaia_tiv_humidity
        name: Humidity
        unit: '%'
        styles:
          width: 55px
      - entity: sensor.livingroom_airhumidifier_speed
        secondary_info: false
        name: Speed
        styles:
          width: 55px
      - entity: input_boolean.livingroom_humidifier_auto_power_on_off
        name: Auto
        toggle: true
        state_color: true
        styles:
          width: 55px
  - type: section
title: Humidifier

Текст на русском (Text in Russian) (click for more details)

1 post - 1 participant

Read full topic

KNX configuration issu

$
0
0

Hi!

Trying to connect HA to my Logicmachine.
The IP of LM is 192.168.10.165
HA:

My ETS connect fine to LM, but HA doesnt. They are on the same network…

1 post - 1 participant

Read full topic

Please Best of the best. Config fan tuya flash do tasmota

$
0
0

Hello.
We will deal with this aroma diffuser.

I have successfully loaded the tasmota firmware. There is no problem here.
However, the moment I started configuring the device and Tasmota, the problems began.

I set up the Tasmota template, and I found that there was an error in it.

{"NAME":"YX-088","GPIO":[0,2272,0,2304,0,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":54,"CMND":"TuyaMCU 11,1|TuyaMCU 61,2|TuyaMCU 62,3|TuyaMCU|12,5|TuyaMCU 63,6|TuyaMCU 21,7|TuyaMCU 24,8|TuyaRGB 3|DimmerRange 1,255|TuyaEnumList 1,2|TuyaEnumList 2,2|TuyaEnumList 3,1"}`

There is one vertical character " | " In the command :

TuyaMCU|12,5

I fixed that and continued.
I put Rule1 in the tasmota console with my own specific /%topic%/

Rule1
on power1#state=0 do publish stat/%topic%/fanmode none endon
on tuyareceived#dptype5id9 do publish stat/%topic%/error %value% endon 
on tuyareceived#dptype4id2==0 do publish stat/%topic%/fanmode medium endon
on tuyareceived#dptype4id2==1 do publish stat/%topic%/fanmode low endon
on tuyareceived#dptype4id2==2 do publish stat/%topic%/fanmode high endon
on tuyareceived#dptype4id3==0 do publish stat/%topic%/timer 2h timer endon
on tuyareceived#dptype4id3==1 do publish stat/%topic%/timer 4h timer endon
on tuyareceived#dptype4id3==2 do publish stat/%topic%/timer timer off endon
on tuyareceived#dptype4id6==0 do publish stat/%topic%/colormode solid endon
on tuyareceived#dptype4id6==1 do publish stat/%topic%/colormode cycle endon
on event#fanmode==-1 do power1 0 endon
on event#fanmode!=-1 do backlog power1 1; tuyaenum1 %value% endon
on event#solid do tuyaenum3 0 endon
on event#cycle do tuyaenum3 1 endon

I also noticed %value% in two lines
I left it unnoticed

Label web UI buttons:

Backlog WebButton1 Fan; WebButton2 Light; FriendlyName1 Diffuser Fan; FriendlyName2 Diffuser Light

OK, I thought.
But I started configuring the fan in Home Assistant and found other writing errors

fan:
  - platform: mqtt
    name: "Diffuser"
    icon: "mdi:smoke"
    state_topic: "stat/%topic%/RESULT"
    state_value_template: "{% if value_json.POWER1 is defined %}{{ value_json.POWER1 }}{% endif%}"
    command_topic: "cmnd/%topic%/POWER1"
    preset_modes:
      - "2h timer"
      - "4h timer"
      - "timer off"
    preset_mode_state_topic: "stat/%topic%/timer"
    preset_mode_command_topic: "cmnd/%topic%/tuyaenum2"
    preset_mode_command_template: >-
      {% if value == "2h timer" %}
        {{ 0 }}
      {% elif value == "4h timer" %}
        {{ 1 }}
      {% else %}
        {{ 2 }}
      {% endif %}
    percentage_state_topic: "stat/%topic%/fanmode"
    percentage_value_template: >-
      {% if value == "low" %}
        {{ 1 }}
      {% elif value == "medium" %}
        {{ 2 }}
      {% elif value == "high" %}
        {{ 3 }}
      {% else %}
        {{ 0 }}
      {% endif %}
    percentage_command_topic: "cmnd/%topic%/event"
    percentage_command_template: >-
      {% if value == 1 %}
        {{ 'fanmode=1' }}
      {% elif value == 2 %}
        {{ 'fanmode=0' }}
      {% elif value == 3 %}
        {{ 'fanmode=2' }}
      {% else %}
        {{ 'fanmode=-1' }}
      {% endif %}
    speed_range_max: 3
    availability_topic: "tele/%topic%/LWT"
    payload_available: "Online"
    payload_not_available: "Offline"
    unique_id: "fan-diffuser"

select:
  - platform: mqtt
    name: "Diffuser Color Mode"
    command_topic: "cmnd/%topic%/event"
    state_topic: "stat/%topic%/colormode"
    options:
      - "solid"
      - "cycle"
    availability:
      - payload_available: "Online"
        payload_not_available: "Offline"
        topic: "tele/%topic%/LWT"
    unique_id: "select-livingroom-diffueser-color-mode"

binary_sensor:
  - platform: mqtt
    name: "Difuser Error"
    state_topic: "stat/%topic%/error"
    value_template: "{{ 'ON' if value != '0X00' else 'OFF' }}"
    device_class: problem
    availability_topic: "tele/%topic%/LWT"
    payload_available: "Online"
    payload_not_avail: "Offline"
    unique_id: "binary-diffueser-error"

And here is my end.
Home Assistant hardly communicates with the diffuser.
In fact, it communicates, but insufficiently. I can choose any combination of preset and speed and send it to the diffuser, but the attributes of the fan entity never change.
I intended to use a fan card in the hunt, but it doesn’t work.

Please nice, would anyone be willing to check the configuration and compatibility for HA?
The author of the template does not communicate.

I’m sorry, and I ask for help again.

1 post - 1 participant

Read full topic

Viewing all 106223 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>