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

Doorbird on Android TV

$
0
0

Hello everybody!

I have an Android TV and a doorbird video intercom. i wish that when someone rings, everything shows on my tv exactly like on the phone but unfortunately there is no doorbird app on android tv. Has anyone done something like this before? Do you have any ideas to make this possible?

I thank you in advance :wink:

Cordially,

Raz

1 post - 1 participant

Read full topic


Many interuptions of nabu casa

Home Assistant and Google assistant : how to link HA butons and Google automation

$
0
0

Hello,
I have created buttons in HA that are associated to a MQTT platform for the activation of a pool filtration pump.

button:
  - platform: mqtt
    name: "Pump activation"
    command_topic: "CMD/PUMP"
    qos: 0
    retain: false
    payload_press: "ON"

I have also completed the integration of Google Home in HA.
Then I have created an automation in Google Home that can successfully activate the pump with a voice command because Google home recognizes my HA buttons as actionable actions.

I would like now to create a button that could send sensor information through a voice message on Google assistant and that could be triggered by an incoming voice message recognized by my Google assistant.
I first tried with a button card on the GUI.

type: button
icon: mdi:gesture-tap-button
show_state: true
name: Test
hold_action:
  action: none
tap_action:
  action: call-service
  service: tts.google_translate_say
  service_data:
    entity_id: media_player.chromecast_de_beatrice
    message: >-
      Le niveau de CO2 est {{ states('sensor.netatmo_maison_nancras_indoor_co2')
      }} ppm ! La température extérieure est de {{
      states('sensor.netatmo_maison_nancras_indoor_exterieur_temperature') }}
      degré'Bonsoir: ceci est un nouvel essai..'
    language: fr
  target: {}

The button is working fine from HA GUI but is not recognized by home assistant as an action.
I have also tried also to declare a button inside the configuration file but didn’t find the correct syntax.

How can I declare in the configuration.yaml file, a button similar to my “MQTT” button but associated to the service “google_translate_say” and not to a MQTT topic ?

1 post - 1 participant

Read full topic

Help to use a attribute as trigger

$
0
0

I have a sensor for my electricity price for my home. I want to check the price level and if the price is high, I will turn off the heater to my Spa (small swimming pool).

One attribute in the sensor is called “price_level”. If state is_not “very_expencive” on pric level I want the heator to be on.

I have wrote this but it don´t work.

- alias: Spa
  trigger:
    - platform: template
      entity_id: sensor.electricity_price_rydbovagen_16
      value_template: "{{ not is_state('price_level', 'very_expencive') }}" # Heater and pump starts if attribute is_not "very_expencive"

  action:
    service: homeassistant.turn_on
    entity_id: 
         - switch.pump_spabad          # turn on pump and heater

Skärmklipp

3 posts - 3 participants

Read full topic

Help with conbee 2 passthrough to zigbee2mqtt docker

$
0
0

Hi!
Iam running Unraid server.
I run HA in VM (used JuanMTech on youtube guide to get started.
and it works fine.
i have also installed a mosquitto docker container without problems.
Now iam trying to setup a docker container with zigbee2mqtt with my conbee2 stick.
but i get this error all the time.

e[31mZigbee2MQTT:errore[39m 2022-01-16 16:27:04: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2475097-if00'

This is my z2m configuration file:

homeassistant: false
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://192.168.1.243:1883
  user: xxxx
  password: xxxx
serial:
  port: >-
    /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2475097-if00
  adapter: deconz
frontend:
  port: 8080
advanced:
  pan_id: 18424
  ext_pan_id:
    - 221
    - 221
    - 221
    - 221
    - 221
    - 221
    - 221
    - 221
  channel: 11

And this is my docker settings:

What am i doing wrong?
I figured maybe when i installed the HA on the VM i choosed to passthrough my conbee2 stick to the vm so its “locked” to the VM and not usable/visable to the docker container?
If this is the case, how can i “delete” the device from the VM setting template?
This is the VM template

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm'>
  <name>Home Assistant</name>
  <uuid>07b9dd51-e098-7b0e-c4d3-6c4037f28ec5</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Linux" icon="/mnt/user/domains/home_assistant/icon/hass.png" os="linux"/>
  </metadata>
  <memory unit='KiB'>2097152</memory>
  <currentMemory unit='KiB'>2097152</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>2</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-5.1'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/07b9dd51-e098-7b0e-c4d3-6c4037f28ec5_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none' migratable='on'>
    <topology sockets='1' dies='1' cores='2' threads='1'/>
    <cache mode='passthrough'/>
  </cpu>
  <clock offset='utc'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='writeback'/>
      <source file='/mnt/user/domains/home_assistant/haos_ova-7.0.qcow2'/>
      <target dev='hdc' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x11'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x13'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0x14'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:72:27:92'/>
      <source bridge='br0'/>
      <model type='virtio-net'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='4'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x0403'/>
        <product id='0x6001'/>
      </source>
      <address type='usb' bus='0' port='1'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x0658'/>
        <product id='0x0200'/>
      </source>
      <address type='usb' bus='0' port='2'/>
    </hostdev>
    <hostdev mode='subsystem' type='usb' managed='no'>
      <source>
        <vendor id='0x1cf1'/>
        <product id='0x0030'/>
      </source>
      <address type='usb' bus='0' port='3'/>
    </hostdev>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
</domain>

I have also tried using the "Libvirt Hotplug USB plugin in unraid to detach the usb stick and tried starting the zigbee2mqtt docker but with the same result.
Could this be a permission issiue or something?

Thnx in advance

1 post - 1 participant

Read full topic

Help setting up device energy monitoring

$
0
0

I have been trying for the last week to get this working but no success.

I have 3 power monitoring plug sockets that give power in watts, I have also added 3 extra devices to show roughly the power used. I followed this guide Energy monitoring in Home Assistant - with or without power meters

The problem is that the nas and the tv do not show any energy consumption but do show power. The others do show energy but what it shows does not look right to me, not sure if I have set watts, watt-hour, kilowatt or kilowatt-hour

Any help would be appreciated.

configuration.yaml

  customize: !include customize.yaml
  customize_glob:
    sensor.kettle_energy:
      last_reset: '1970-01-01T00:00:00+00:00'
      state_class: measurement
      device_class: energy
      unit_of_measurement: Wh
    sensor.monitors_energy:
      last_reset: '1970-01-01T00:00:00+00:00'
      state_class: measurement
      device_class: energy
      unit_of_measurement: Wh
    sensor.wifi_plug_energy:
      last_reset: '1970-01-01T00:00:00+00:00'
      state_class: measurement
      device_class: energy
      unit_of_measurement: Wh
    sensor.desktop_energy:
      last_reset: '1970-01-01T00:00:00+00:00'
      state_class: measurement
      device_class: energy
      unit_of_measurement: Wh
    sensor.main_tv_energy:
      last_reset: '1970-01-01T00:00:00+00:00'
      state_class: measurement
      device_class: energy
      unit_of_measurement: Wh
    sensor.bathroom_light_energy:
      last_reset: '1970-01-01T00:00:00+00:00'
      state_class: measurement
      device_class: energy
      unit_of_measurement: Wh
    sensor.my_nas_energy:
      last_reset: '1970-01-01T00:00:00+00:00'
      state_class: measurement
      device_class: energy
      friendly_name: NAS
      unit_of_measurement: Wh
    sensor.metered_devices_daily_energy:
      last_reset: '1970-01-01T00:00:00+00:00'
      state_class: measurement
      device_class: energy
      friendly_name: Daily Energy
      unit_of_measurement: Wh
    sensor.metered_devices_monthly_energy:
      last_reset: '1970-01-01T00:00:00+00:00'
      state_class: measurement
      device_class: energy
      friendly_name: Monthly Energy
      unit_of_measurement: Wh

utility_meter:
  monitors_daily_energy:
    source: sensor.monitors_energy
    cycle: daily
  monitors_monthly_energy:
    source: sensor.monitors_energy
    cycle: monthly
  wifi_plug_daily_energy:
    source: sensor.wifi_plug_energy
    cycle: daily
  wifi_plug_monthly_energy:
    source: sensor.wifi_plug_energy
    cycle: monthly
  kettle_daily_energy:
    source: sensor.kettle_energy
    cycle: daily
  kettle_monthly_energy:
    source: sensor.kettle_energy
    cycle: monthly
  desktop_daily_energy:
    source: sensor.desktop_energy
    cycle: daily
  desktop_monthly_energy:
    source: sensor.desktop_energy
    cycle: monthly
  bathroom_light_daily_energy:
    source: sensor.bathroom_light_energy
    cycle: daily
  bathroom_light_monthly_energy:
    source: sensor.bathroom_light_energy
    cycle: monthly
  my_nas_daily_energy:
    source: sensor.my_nas_energy
    cycle: daily
  my_nas_monthly_energy:
    source: sensor.my_nas_energy
    cycle: monthly
  main_tv_daily_energy:
    source: sensor.main_tv_energy
    cycle: daily
  main_tv_monthly_energy:
    source: sensor.main_tv_energy
    cycle: monthly
  metered_devices_daily_energy:
    source: sensor.metered_devices_power
    cycle: daily
  metered_devices_monthly_energy:
    source: sensor.metered_devices_power
    cycle: monthly

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

sensors.yaml

- platform: template
  sensors:
    bathroom_light_power:
      friendly_name: "Bathroom Light Power"
      attribute_templates:
        last_reset: '1970-01-01T00:00:00+00:00'
        state_class: measurement
        device_class: power
      unit_of_measurement: 'W'
      value_template: >
        {% if is_state('switch.bathroom_light', 'on') %}
          15
        {% else %}
          0
        {% endif %}
    my_nas_power:
      friendly_name: "NAS Power"
      attribute_templates:
        last_reset: '1970-01-01T00:00:00+00:00'
        state_class: measurement
        device_class: power
      unit_of_measurement: 'W'
      value_template: >
        {% if is_state('device_tracker.homeserver', 'home') %}
          200
        {% else %}
          0
        {% endif %}
    desktop_power:
      friendly_name: "Computer Power"
      attribute_templates:
        last_reset: '1970-01-01T00:00:00+00:00'
        state_class: measurement
        device_class: power
      unit_of_measurement: 'W'
      value_template: >
        {% if is_state('device_tracker.desktop', 'home') %}
          150
        {% else %}
          0
        {% endif %}
    main_tv_power:
      friendly_name: "Living Room TV"
      attribute_templates:
        last_reset: '1970-01-01T00:00:00+00:00'
        state_class: measurement
        device_class: power
      unit_of_measurement: 'W'
      value_template: >
        {% if is_state('media_player.str_dn1080_e30a1f', 'on') %}
          300
        {% else %}
          0
        {% endif %}
    metered_devices_power:
      friendly_name: "Current Usage"
      attribute_templates:
        last_reset: '1970-01-01T00:00:00+00:00'
        state_class: measurement
        device_class: power
      unit_of_measurement: 'W'
      icon_template: mdi:speedometer
      value_template: "{{ (states('sensor.monitors_power') | float + 
        states('sensor.bathroom_light_power') | float +
        states('sensor.my_nas_power') | float +
        states('sensor.main_tv_power') | float +
        states('sensor.desktop_power') | float +
        states('sensor.wifi_plug_power') | float +
        states('sensor.kettle_power') | float) | round(2) }}"


- platform: integration
  source: sensor.monitors_power
  name: monitors_energy
  unit_prefix: k
  unit_time: h
  round: 2

- platform: integration
  source: sensor.my_nas_power
  name: my_nas_energy
  unit_prefix: k
  unit_time: h
  round: 2

- platform: integration
  source: sensor.wifi_plug_power
  name: wifi_plug_energy
  unit_prefix: k
  unit_time: h
  round: 2

- platform: integration
  source: sensor.kettle_power
  name: kettle_energy
  unit_prefix: k
  unit_time: h
  round: 2

- platform: integration
  source: sensor.main_tv_power
  name: main_tv_energy
  unit_prefix: k
  unit_time: h
  round: 2

- platform: integration
  source: sensor.desktop_power
  name: desktop_energy
  unit_prefix: k
  unit_time: h
  round: 2

- platform: integration
  source: sensor.bathroom_light_power
  name: bathroom_light_energy
  unit_prefix: k
  unit_time: h
  round: 2

1 post - 1 participant

Read full topic

Zwave-js installation on HA core

$
0
0

Hi,
I recently migrated my home assistant (core) from z-wave to z-wave.js. It was in the end not difficult but in the end it never is of course. I got information from a number of sources and grouped info on how I did it at this page. Maybe it will be useful to somebody.

1 post - 1 participant

Read full topic

Using Siri Shortcuts in automations?

$
0
0

I have an idea for an automation I’ve been trying to get working for a few days now:
Essentially, I’d like to trigger music from an Apple Music playlist to start playing when I enter a room. So far I have both the HA and Apple side of things working independently, but I can’t get them to talk to each other in the way I want.

To handle the playing of the music I’ve built a siri shortcut that finds my playlist, shuffles the songs, connects to my smart speakers (google minis exposed via the Aircast integration), sets the proper volume, and starts playing. Triggering this on my phone works like a charm. On the HA side, I have an input boolean to track presence in a room that is controlled by a motion sensor.

Ideally, this would be a completely hands-free automation. No voice control, no tapping on my phone. So far the closest I’ve gotten is to use a push notification that sends a shortcut service call when tapped.

I’m wondering if it’s possible to fire a Siri Shortcut without any kind of intervention from the user at all?

1 post - 1 participant

Read full topic


Logitech hub harmony alternative?

$
0
0

Hi, I use the smart hub a lot with HA… It works great… but it when it dies ( let’s hope not) , is there a good alternative with a remote where you can define also activites and custom commands with a good integration in HA?

Thnx

1 post - 1 participant

Read full topic

Homekit MQTT cover state problem

$
0
0

Hey,

I would like add my custom window opener system to homekit (arduino with mqtt). There isnt position or tilt funtion just open and close. The state can be “open, opening, close, closing”. It is working fine with home assistant, but I have two problem with homekit:

  1. I set device_class to “window” in configuration.yaml into mqtt section, but in home app I get “shutter” icon and I cannot change it to window.

  2. In Home app the “state” is not working fine. The HA showing all state (close, closing, open, opening), but I have only two state in Home App: “open” and “closed”.

Thank you your help!

My config:

cover:
  - platform: mqtt
    unique_id: Bedroom_Window_01
    name: "Bedroom - Window 01"
    device_class: window
    command_topic: "Indoor/Bedroom/Window/01/Set"
    state_topic: "Indoor/Bedroom/Window/01/State"
    payload_open: "1"
    payload_close: "0"
    state_opening: "opening"
    state_open: "open"
    state_closing: "closing"
    state_closed: "closed"
    optimistic: false
    qos: 2

1 post - 1 participant

Read full topic

Homematic IP HmIP-RC8 event fires no action in automation

$
0
0

Hi,
my setup:
HA on RPI3 with Raspberrymatic addon.
I managed to get setup running, paired new devices and got the HmIP firing up events on eventbus:
{
“event_type”: “homematic.keypress”,
“data”: {
“name”: “Remote”,
“param”: “PRESS_SHORT”,
“channel”: 1
},
“origin”: “LOCAL”,
“time_fired”: “2022-01-16T16:57:19.717826+00:00”,
“context”: {
“id”: “501ccf7ecec13b492dd27fbe5927e94f”,
“parent_id”: null,
“user_id”: null
}
}
BUT, i can’t get a automation running reacting on that event !!
I read all possible working solutions i found, but it doesn’t work for me.
My automation:
alias: wled
description: ‘’
trigger:

  • event_data:
    channel: 1
    param: PRESS_SHORT
    address: Remote
    event_type: homematic.keypress
    platform: event
    action:
  • type: toggle
    device_id: a102057dd7a1182b9836d9914fb00711
    entity_id: light.wled
    domain: light
    mode: single

The action works if if try from automations window.
Perhaps someone can help me out :wink:
regards, Peter

1 post - 1 participant

Read full topic

How to integrate devices in 3d floorplan in home assistant

$
0
0

Hi

I have built a 3d floorplan, i would like to know how to integrate it in home assistant to display the devices in the room, lit the room when lights are on, etc…

Is there any guide about how to do this?

Thanks

1 post - 1 participant

Read full topic

Stupid newbie question re ethernet/vs wifi

$
0
0

Sorry to bother the community. I have HA up and running and connected to the internet via an ethernet cable. Generally I like to connect my RPI’s via wifi. I can’t seem to find how to do that. I would expect it to be under configuration, but I can’t find it.
Txs

1 post - 1 participant

Read full topic

Zwave-js sensors for Kwikset 914 lock...missing?

$
0
0

Previously I was using the alarm type, alarm level, and some other sensors to trigger events with the old zwave integration and it seems like for some reason Zwave-js doesn’t have them. Has anyone figured out a way to get them, or a workaround?

I’m also now using keymaster for lock codes and user management and without these sensors, the functionality is much more limited.

2 posts - 2 participants

Read full topic

Kasa smart plug goes to "unavailable" state

$
0
0

I have an automation that is triggered by Kasa smart plug’s current consumption - basically when it goes below certain value.

The behavior I see is that sometime this automation is wrongly triggered. I looked in the trace logs and I see this:

trigger:
  id: '0'
  idx: '0'
  platform: device
  entity_id: sensor.washer_plug_current_consumption
  below: 2
  above: null
  from_state:
    entity_id: sensor.washer_plug_current_consumption
    state: unavailable
    attributes:
      state_class: measurement
      unit_of_measurement: W
      friendly_name: Washer plug Current Consumption
      device_class: power
    last_changed: '2022-01-16T04:35:48.388935+00:00'
    last_updated: '2022-01-16T04:35:48.388935+00:00'
    context:
      id: 99aa4d6cb49984eec14ce4e5424def29
      parent_id: null
      user_id: null
  to_state:
    entity_id: sensor.washer_plug_current_consumption
    state: '0.3'
    attributes:
      state_class: measurement
      unit_of_measurement: W
      friendly_name: Washer plug Current Consumption
      device_class: power
    last_changed: '2022-01-16T04:36:08.376758+00:00'
    last_updated: '2022-01-16T04:36:08.376758+00:00'
    context:
      id: 1462744b1b3bb8830e1999cdb3b547da
      parent_id: null
      user_id: null

So basically sometimes the smart plug is unavailable, what causes the automation to be triggered.

How can I configure the trigger so that it will basically ignore when the plug goes temporarily into unavailable state?

Thanks!

1 post - 1 participant

Read full topic


How to add "running hours" to long-term statistics

$
0
0

I’m still a bit confused with the long-term statistics.

Some pumps and several heating devices I’m tracking the amount of usage. For this I created some history_stats sensors. For example “stats_pump1_today” counts the amount of time the pump was running today. I would like to include these values in the long term statistics to enable to trend usage over longer periods of time. I checked the long-term statistics page but it seems there is no one for time/running time. Is it possible to enable this?

Also, the long term stats are stored in the database but discards the purge period (of course), but is it ever purged? And is it possible to trend this data with other (custom) cards, so far I only had success with the default history-stats card. I would really like an equivalent to the energy dashboard with date selectors, week/month totalizers, etc…

1 post - 1 participant

Read full topic

Addon Updates Stuck

$
0
0

My HA instance gets stuck at every addon update. When I press an addon to update it gets the looping circle forever. If I refresh the page it seems that the addon updated itself. Is anyone else getting this strange behaviour ? Any ideas why ? This has begun at some point on the latest updates of HA. I am on a NUC supervised on Debian 11.

1 post - 1 participant

Read full topic

Person entity just disappeared

$
0
0

Hi,

Very strange thing is going on on my HA right now. When im reying to set a new automation and add a condition based on zone I cant find my person entity in the options list no only that can’t find my person entity, I actually can’t find any entity at all. What the hell is going on here?

The text in this screenshot is in Hebrew because I’m from Israel, but I believe you can guess what is written there

1 post - 1 participant

Read full topic

Set netatmo thermostat true temperature

$
0
0

Hi

is there a way to set the true temperature (current_temperature) of my netatmo thermostat from home assistant?

thanks !

1 post - 1 participant

Read full topic

Modbus challenge

$
0
0

I’m trying to tie a modbus PLC into HA for monitoring inside a brewery. We’re using a Solo SL-4848. I need to be able to reset the SV (set point) if needed. According the the docs, the SV register decimal address is 44098.

But the modbus service appear to only accept 0-255) for the address. I admit I’m a complete modbus n00b.
image
Here’s tje base config. My testing is with the Dev tools at this point.

  - name: hub3
    type: serial
    baudrate: 9600
    bytesize: 7
    method: ascii
    parity: E
    port: /dev/ttyUSB3
    stopbits: 1

1 post - 1 participant

Read full topic

Viewing all 106397 articles
Browse latest View live