Hello,
I started today using Home Assistent and found an issue with Shelly Plug S Gen3.
In Shelly Cloud they are named with some readyble names.
After adding them to Home Assistent they were shown with “shelly[some iD]”, so I renamed them. But on Dashboard still the first name is used:
1 post - 1 participant
I’ve done some reading on this and the search results that came back, of which there were plenty, seem to go around a little… so I thought I’d ask because I’m scratching my head a little and some of my assumptions could be wrong.
Firstly, I’m running on a Pi5. I believe that HA is running in a container, even on the Pi. I’ve checked the network options and for fixed IP, there is no entry for NTP. I’ve SSH’d to the box but being in a container I need to get to the underlying OS. Typing login results in being asked for a user name and password, but I’m not sure what to use as I only gave a password to the HA installation.
There is a plugin called Chrony but I’d like to get this sorted on the Pi host if possible because I’m presuming that Chrony won’t be able to get to the underlying OS.
Grateful for advice please.
EDIT - The Pi does have access to time.cloudflare.com but I’m presuming this is only done at boot time?
1 post - 1 participant
Hello everybody,
I have an Amazon Ring device connected to Home Assistant through the related integration, and I wanted to setup an automation to send a notification on my phone everytime someone rings the doorbell.
I created an automation which reacts on the Ding event of the Ring device, and that is configured as follows:
alias: Ring - Notification
description: ""
triggers:
- trigger: state
entity_id:
- event.door_ding
conditions: []
actions:
- action: notify.mobile_app_my_iphone
metadata: {}
data:
message: Someone rang the doorbell
title: Doorbell
mode: single
This automation is correctly triggered when someone rings my doorbell, however it is also unexpectedly triggered in other cases like:
I already searched in the forum as well as in the github issues but I was not able to find something useful on this topic. Did someone experience the same issue as I’m having? Can my automation be improved to avoid being triggered multiple times like I reported above?
Thanks!
1 post - 1 participant
Selecting all the devices you want to share over HomeKit bridge to Apple home is a mess. Just a long long jumble of devices that you have to select from.
Please add keyword support support, so I can export e.g. every device that I have tagged ForHomekit
Simple?
2 posts - 2 participants
When I open scenes I see Create your First Scene. I create scene and save it.When I exit editor new scene is not found. If I open scenes.yaml the code is there.
1 post - 1 participant
Need some help with this. I’m trying to set up control logic for a bathroom exhaust fan, with multiple triggers to turn the fan on/off based on various criteria (humidity, switch, timer, etc)
The first 4 triggers work and will initiate a trace. However, the timer.finished trigger isn’t working.
alias: Olive's Bathroom - Fan Logic
description: ""
triggers:
- type: turned_on
device_id: 4579fb219e9e7cd038941647d543e26d
entity_id: 5c7e78855b7f6a476a52a07819f173e5
domain: switch
trigger: device
id: Fan Switch Turned On
- type: turned_off
device_id: 4579fb219e9e7cd038941647d543e26d
entity_id: 5c7e78855b7f6a476a52a07819f173e5
domain: switch
trigger: device
id: Fan Switch Turned Off
- type: humidity
device_id: 88c8f6cdc6de52211e65a6c5e0d582e4
entity_id: 4bde3d33b2aca0f8660f799c7fafa8e7
domain: sensor
trigger: device
id: High Humidity
above: 65
- type: humidity
device_id: 88c8f6cdc6de52211e65a6c5e0d582e4
entity_id: 4bde3d33b2aca0f8660f799c7fafa8e7
domain: sensor
trigger: device
id: Normal Humidity
below: 65
- trigger: event
event_type: timer.finished
id: Fan Timer Finishes
event_data:
entity_id: timer.olive-bathroom-fan
conditions: []
actions:
- choose:
- conditions:
- condition: trigger
id:
- Fan Switch Turned On
sequence:
- action: input_boolean.turn_on
metadata: {}
data: {}
target:
entity_id: input_boolean.olive_bathroom_fan_helper
- action: timer.start
metadata: {}
data: {}
target:
entity_id: timer.olive_bathroom_fan_timer_helper
- conditions:
- condition: trigger
id:
- Fan Switch Turned Off
sequence:
- action: input_boolean.turn_off
metadata: {}
data: {}
target:
entity_id: input_boolean.olive_bathroom_fan_helper
- action: timer.cancel
metadata: {}
data: {}
target:
entity_id: timer.olive_bathroom_fan_timer_helper
- conditions:
- condition: trigger
id:
- Fan Timer Finishes
- type: is_temperature
condition: device
device_id: 88c8f6cdc6de52211e65a6c5e0d582e4
entity_id: 026b56c8b41b43919fbc84842eb6a86d
domain: sensor
below: 65
sequence:
- action: input_boolean.turn_off
metadata: {}
data: {}
target:
entity_id: input_boolean.olive_bathroom_fan_helper
- conditions:
- condition: trigger
id:
- High Humidity
sequence:
- action: input_boolean.turn_on
metadata: {}
data: {}
target:
entity_id: input_boolean.olive_bathroom_fan_helper
- action: timer.cancel
metadata: {}
data: {}
target:
entity_id: timer.olive_bathroom_fan_timer_helper
- conditions:
- condition: trigger
id:
- Normal Humidity
sequence:
- action: input_boolean.turn_off
metadata: {}
data: {}
target:
entity_id: input_boolean.olive_bathroom_fan_helper
mode: single
2 posts - 2 participants
Hello, sorry if this isn’t in the right place. I have spent all days watching videos, trying different blueprints and reading other people posts. My problem might be that I’m still struggling with the actions and building blocks. I know this is probably so simple.
My Objective: I have a door lock that I want to turn the light on when I unlock it. all this I can set up fine. but I want the light to turn off after 1 minute and this is where I’m struggling. the blueprints I tried don’t work for "lock’ or “unlock” just “on/off” or motion. I feel as though what I’ve done is correct but the light won’t turn off. a little guidance would be really appreciated! here’s what the yaml file says.
alias: Front Lock Light On
description: “”
triggers:
again any help would be appreciated.i would like to know what I did wrong in the ui too so I can learn from my mistake… thanks!!
1 post - 1 participant
I need a flag to change the icon color for a custom button. If state.water_heater.snst081556q_oven and sensor.snst081556q_cook_mode both equal off, the stove is all off. I am getting the below errors in-spite of the fact in the editor I get the green check-mark. Help appreciated, thanks in advance, Anthony Baker
- sensor:
- name: 'StoveOff'
state: >
"{% is_state('state.water_heater.snst081556q_oven', 'Off') and is_state('sensor.snst081556q_cook_mode', 'Off') %}"
Logger: homeassistant.config
Source: config.py:357
First occurred: 4:17:02 PM (19 occurrences)
Last logged: 6:58:52 PM
Invalid config for 'template' at templates.yaml, line 24: required key 'state' not provided Invalid config for 'template' at templates.yaml, line 25: 'state' is an invalid option for 'template', check: state
Invalid config for 'template' at templates.yaml, line 25: invalid template (TemplateSyntaxError: Encountered unknown tag 'is_state'.) for dictionary value 'sensor->0->state', got "{% is_state('state.water_heater.snst081556q_oven', 'Off') and is_state('sensor.snst081556q_cook_mode', 'Off') %}\n"
Invalid config for 'template' at templates.yaml, line 24: invalid template (TemplateSyntaxError: Encountered unknown tag 'is_state'.) for dictionary value 'sensor->1->state', got "{% is_state('state.water_heater.snst081556q_oven', 'Off') and is_state('sensor.snst081556q_cook_mode', 'Off') %}\n"
Invalid config for 'template' at templates.yaml, line 24: invalid template (TemplateSyntaxError: Encountered unknown tag 'is_state'.) for dictionary value 'sensor->1->state', got "{% is_state('water_heater.snst081556q_oven', 'Off') and is_state('sensor.snst081556q_cook_mode', 'Off') %}\n"
Invalid config for 'template' at templates.yaml, line 25: invalid template (TemplateSyntaxError: Encountered unknown tag 'is_state'.) for dictionary value 'binary_sensor->0->state', got "{% is_state('state.water_heater.snst081556q_oven', 'Off') and is_state('sensor.snst081556q_cook_mode', 'Off') %}\n"
- sensors:
time_templated:
# value_template: "{{ now().strftime('%X') }}"
value_template: "{{ now().strftime('%H:%M:%S') }}"
friendly_name: ''
icon_template: 'mdi:clock'
date_templated:
value_template: "{{ now().strftime('%d %B, %Y') }}"
friendly_name: ''
icon_template: 'mdi:clock'
weekday_templated:
value_template: "{{ now().strftime('%A') }}"
friendly_name: ''
icon_template: 'mdi:clock'
- sensor:
- name: 'Lights On'
icon: mdi:lightbulb-group-on
state: "{{ states.light
| rejectattr('entity_id', 'in', ['light.master_bedroom_ceiling_fan', 'light.reolink_video_doorbell_wifi_infra_red_lights_in_night_mode'])
| selectattr('state', 'eq', 'on')| list | count + states.input_boolean
| selectattr('state', 'eq', 'on') | list | count}}"
- sensor:
- name: 'StoveOff'
state: >
"{% is_state('state.water_heater.snst081556q_oven', 'Off') and is_state('sensor.snst081556q_cook_mode', 'Off') %}"
- sensor:
##### Low Battery list ##################################
- name: "Low Battery Devices"
unique_id: ba292875-ae67-480d-9867-29cdb20afaea
icon: >
mdi:battery-low
state: >
{% set threshold = states('input_number.battery_threshold') | int %}
{%- set ns = namespace(sensors=[]) -%}
{%- for state in states.sensor
| selectattr('attributes.device_class', 'defined')
| selectattr('attributes.state_class', 'defined')
| selectattr('attributes.device_class', '==', 'battery')
| selectattr('attributes.state_class', '==', 'measurement')
| selectattr('state', 'is_number') -%}
{%- if state.state | int <= threshold -%}
{% set ns.sensors = ns.sensors + [dict(name = state.name | replace(' battery', '') | replace(' Battery', ''), state = state.state | int)] %}
{%- endif -%}
{%- endfor -%}
{%- set batt = ns.sensors | sort(attribute='state') %}
{%- set ns = namespace(batt='') -%}
{%- for state in batt -%}
{% set ns.batt= ns.batt + (state.name ~ ' (' ~ state.state ~'%)' ~ "\n") %}
{%- endfor -%}
{% if ns.batt | count > 0 %}
{{ ns.batt | truncate(255, true, '...') }}
{% else %}
{{ 'unavailable' }}
{% endif %}
##----------------------------------------------------------------------------------------------------------------------
##
## Unavailable Devices Sensor
##
## 05-Feb-2024 | Andy Symons | created
## 16-May-2024 | mr_roboto | updated to track unavailable device count rather than entities
##
## Credit: based loosely on https://github.com/jazzyisj/unavailable-entities-sensor/blob/main/README.md
##
## The sensor provides lists related to real devices, not internal entities, helpers, automations etc.,
## Entities with state 'unknown' are not counted, because it is possible for a device to have a sub-entity that is
## unknown while the device itself is available.
##
## The STATE simply gives the count of unavailable entities.
## The long results have to be attributes because the state cannot contain more than 255 characters:
## ATTRIBUTE 'entity_id_list' contains a list of unavailable entities using their entity ids, which may or may not have been set by the user.
## ATTRIBUTE 'entity_name_list' contains a list of unavailable entities using their friendly names as assigned by the user.
## ATTRIBUTE 'device_name_list contains a list of the devices that are unavailable, which is to say having one or more entities that are unavailable,
## using their friendly names as assigned by the user.
##
##----------------------------------------------------------------------------------------------------------------------
- sensor:
name: "Unavailable Devices"
unique_id: unavailable_devices
icon: "{{ iif(states(this.entity_id)|int(-1) > 0,'mdi:alert-circle','mdi:check-circle') }}"
state_class: measurement
unit_of_measurement: devices
# The entity state is the count of unavailable devices.
state: >
{{ states
| selectattr('domain','in',['binary_sensor', 'climate', 'light', 'sensor', 'switch'])
| selectattr('state', 'in', ['unavailable'])
| map(attribute='entity_id')
| map('device_attr', 'name_by_user')
| reject('match', 'None')
| unique
| list
| count
}}
# The long results have to be attributes because the state cannot contain more than 255 characters.
attributes:
## A list of the devices that are unavailable, using their friendly names as assigned by the user.
device_name_list: >-
{{ states
| selectattr('domain','in',['binary_sensor', 'climate', 'light', 'sensor', 'switch'])
| selectattr('state', 'in', ['unavailable'])
| map(attribute='entity_id')
| map('device_attr', 'name_by_user')
| reject('match', 'None')
| unique
| list
| sort
| join('\n')
}}
## A list of unavailable entities using their friendly names as assigned by the user.
entity_name_list: >-
{{ states
| selectattr('domain','in',['binary_sensor', 'climate', 'light', 'sensor', 'switch'])
| selectattr('state', 'in', ['unavailable'])
| map(attribute='entity_id')
| map('state_attr', 'friendly_name')
| reject('match', 'None')
| list
| sort
| join('\n')
}}
## A list of unavailable entities using their entity ids (which may or may not have been set by the user).
entity_id_list: >-
{{ states
| selectattr('domain','in',['binary_sensor', 'climate', 'light', 'sensor', 'switch'])
| selectattr('state', 'in', ['unavailable'])
| map(attribute='entity_id')
| reject('match', 'None')
| list
| sort
| join('\n')
}}
# HOW THE ATTRIBUTE TEMPLATES WORK
# -- Taking device_name_list as an example...
#
# {{ states -- all the states (entities) in the system
# | selectattr('domain','in',['binary_sensor', 'climate', etc. -- filter only the entities for real devices
# | selectattr('state', 'in', ['unavailable']) -- filter only entities that are unavailable
# | map(attribute='entity_id') -- get the entity id from the record
# | map('device_attr', 'name_by_user') -- map the entity id onto the device name
# | reject('match', 'None') -- take out names 'None' (meaning there is no name, so not a device)
# | unique -- take out duplicates (devices usually have several entities)
# | list -- make into a list (in the template sense)
# | sort -- put them in alphabetical order
# | join('\n') -- take out extraneous punctuation for a tidy output
# }}
2 posts - 2 participants
Hi Everyone
I have ZHA setup with HASS OS. I have about 6 of these Zigbee plugs. Everything works just fine. I want to use one of these plugs on my desktop computer.
How do I configure these things to always switch following a ac power outage? Of the 8 or so that I have, 3 always turn back on when the power comes back, but the others do not.
I know its possible because years ago, I recall finding some instructions on some website on how to do it. It involved sending raw commands to the device but I can’t seem to locate it currently.
1 post - 1 participant
Hi, hoping someone can help.
I’ve setup my nanoleaf lines, they’ve been detected by Home Assistant. I get a message to press and held the power button for 5 seconds… but there is no power button.
I’ve connected them before but I can’t remember how.
Any ideas?
Thanks…
1 post - 1 participant
Hi, I am trying to implement my Yale YRL210 Lever Lock via zwave. This is the older yale lock with zwave dongle (pre-azure line).
The device has the follwoing IDs:
ManufactureID ProductType-ProductID
0x0129 0x0003-0x0000
however, the ZWave Config DB only has
0x0129 0x0003-0x0409
I installed ZWave JS UI
so I downloaded and modified the config file and added it to my store/config dir, but when I re-interview the device (I tired to restart too), It still shows up as unknown product, what am I doing wrong?
FROM:
{
"manufacturer": "Yale",
"manufacturerId": "0x0129",
"label": "YRL210",
"description": "Push Button Lever Lock",
"devices": [
{
"productType": "0x0003",
"productId": "0x0409"
}
],
TO:
{
"manufacturer": "Yale",
"manufacturerId": "0x0129",
"label": "YRL210",
"description": "Push Button Lever Lock",
"devices": [
{
"productType": "0x0003",
"productId": "0x0409"
},
{
"productType": "0x0003",
"productId": "0x0000"
}
],
I have a PR open with ZWaveJS too, but not sure when it will be merged, so I’d like to test it
5 posts - 3 participants
Hiya Geniuses!
I’ve been struggling for a bit to try and get a Sonoff RF Bridge device running ESPHome firmware. I’ve successfully flashed the hardware and all the sensors work, but I’m not seeing the RF-Bridge.
I’m following the quite comprehensive guide provided at - https://www.irrgang.dev/how-to-flash-the-sonoff-rf-bridger2-with-esphome/
Looking at the ESPHome device, it is active and I’m seeing a bunch of things under the Diagnostic heading.
But compared to the screen shot in the post, there should also be something labelled as rf-bridge.
esphome:
name: rf-bridge-1
friendly_name: RF Bridge 1
esp8266:
board: esp01_1m
# Enable logging
logger:
baud_rate: 0
api:
encryption:
key: !secret api_encryption_key
services:
- service: send_rf_code
variables:
sync: int
low: int
high: int
code: int
then:
- rf_bridge.send_code:
sync: !lambda 'return sync;'
low: !lambda 'return low;'
high: !lambda 'return high;'
code: !lambda 'return code;'
- service: learn
then:
- rf_bridge.learn
rf_bridge:
on_code_received:
then:
- homeassistant.event:
event: esphome.rf_code_received
data:
sync: !lambda 'return format_hex(data.sync);'
low: !lambda 'return format_hex(data.low);'
high: !lambda 'return format_hex(data.high);'
code: !lambda 'return format_hex(data.code);'
ota:
platform: esphome
password: !secret ota_password
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
button:
# Restart the ESP
- platform: restart
name: "Restart"
uart:
tx_pin: 1
rx_pin: 3
baud_rate: 19200
# Sensors for ESP version and WIFI information
text_sensor:
# ESPHome version
- platform: version
hide_timestamp: true
name: "ESPHome Version"
# IP address and connected SSID
- platform: wifi_info
ip_address:
name: "IP Address"
icon: mdi:wifi
ssid:
name: "Connected SSID"
icon: mdi:wifi-strength-2
sensor:
# WiFi signal
- platform: wifi_signal
name: "WiFi Signal"
update_interval: 120s
- platform: uptime
name: Sonoff RF Bridge Uptime
binary_sensor:
- platform: status
name: Sonoff RF Bridge Status
light:
- platform: status_led
name: "Switch state"
pin: GPIO13
I’m assuming if I’d done something really basic like screwing up the indents, then the ESPHome compile would fail?
Appreciate anyone who can nudge me in the right direction. Thanks
1 post - 1 participant
I gotta problem. Faulty hardware results in an integration spewing gigabytes of log messages per day, not to mention a notification every 38 seconds. The notifications finally enraged me to the point where I eliminated them by commenting out a line of integration code. But I’ve wasted a week trying to quell the log messages, and i’ve failed miserably.
Here’s my config,yaml, as of tonight. I believe it’s straightforward, except for the last two lines.
++++++++++++++++++++++++++++++++++++++++
default_config:
frontend:
themes: !include_dir_merge_named themes
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
logger:
default: fatal
+++++++++++++++++++++++++++++++++++++++++
My understanding is that inclusion of the final two lines will result in no log message with an error level lower than “fatal” appearing in the log. And if I omit the last two lines, anything lower than a “warning” message will be omitted. (My information was extracted from Logger - Home Assistant ). Why, then, am I seeing this?
As long as I’m here, here are two other questions, related to some ineffectual lines which were deleted from config.yaml yesterday.
+++++++++++++++++++++++++++++++++++++++++++++
logger:
logs:
homeassistant.components.hubspacediscovery: warning
homeassistant.components.ocpp: warning
homeassistant.components.wiz: warning
+++++++++++++++++++++++++++++++++++++++++++++
1] Why must “homeassistant.” be specified? Is there another possibility?
2] Same question for “components.”. What else might it be?
1 post - 1 participant
Hi everyone.Not sure if this is the right place here. I’m currently working on an epaper display with esphome showing some weather data, washing machine state, garbage days and calendar events. Now I got a little bit of stuck, because I’m new to HomeAssistant, also new to python, new to yaml (and also basically new to c++). I have only some experience in some other programming languages some time ago.
Long topic and 3 questions waiting for an answer.
So, the ePaper itself is not the problem. Working great. My issue is the preparation of the data in the template.yaml for the sensor attributes, which are send to the esp. Here are the code snippets, how it works now:
- service: calendar.get_events
target:
entity_id:
- calendar.fxx
- calendar.kxx
- calendar.jxx
- calendar.exx
data:
start_date_time: "{{ now().strftime('%Y-%m-%d 00:00:00') }}"
end_date_time: "{{ (now() + timedelta(days=14)).strftime('%Y-%m-%d 00:00:00') }}"
response_variable: calendar_events
and this is, how the attributes are created:
event_count: >
{% set all_events = calendar_events['calendar.fxx'].events + calendar_events['calendar.kxx'].events + calendar_events['calendar.jxx'].events + calendar_events['calendar.exx'].events %}
{{ all_events | count() }}
event_summary1: >
{% set all_events = calendar_events['calendar.fxx'].events + calendar_events['calendar.kxx'].events + calendar_events['calendar.jxx'].events + calendar_events['calendar.exx'].events %}
{% if (all_events | count()) >0 %}
{{ (all_events|sort(attribute='start'))[0].summary }}
{% endif %}
event_startdate1: >
{% set all_events = calendar_events['calendar.fxx'].events + calendar_events['calendar.kxx'].events + calendar_events['calendar.jxx'].events + calendar_events['calendar.exx'].events %}
{% if (all_events | count()) >0 %}
{{ ((all_events|sort(attribute='start'))[0].start|as_datetime|as_local).strftime("%d.%m.%Y") }}
{% endif %}
event_starttime1: >
{% set all_events = calendar_events['calendar.fxx'].events + calendar_events['calendar.kxx'].events + calendar_events['calendar.jxx'].events + calendar_events['calendar.exx'].events %}
{% if (all_events | count()) >0 %}
{{ ((all_events|sort(attribute='start'))[0].start|as_datetime|as_local).strftime("%H:%M") }}
{% endif %}
event_tag1: >
{% set all_events = calendar_events['calendar.fxx'].events + calendar_events['calendar.kxx'].events + calendar_events['calendar.jxx'].events + calendar_events['calendar.exx'].events %}
{% if (all_events | count()) >0 %}
{% set wochentag = ["Mo", "Di", "Mi", "Do", "Fr", "Sa", "So"] %}
{% if ((all_events|sort(attribute='start'))[0].start|as_datetime|as_local).strftime("%H:%M") == "00:00" %}
{% set calday = as_timestamp((all_events|sort(attribute='start'))[0].start|as_datetime|as_local) | timestamp_custom('%w',false) | int %}
{% else %}
{% set calday = as_timestamp((all_events|sort(attribute='start'))[0].start|as_datetime|as_local) | timestamp_custom('%w',false) | int -1 %}
{% endif %}
{{ wochentag[calday] }}
{% endif %}
event_summary2: >
{% set all_events = calendar_events['calendar.fxx'].events + calendar_events['calendar.kxx'].events + calendar_events['calendar.jxx'].events + calendar_events['calendar.exx'].events %}
{% if (all_events | count()) >1 %}
{{ (all_events|sort(attribute='start'))[1].summary }}
{% endif %}
As you can see, in every attribute there are some procedures repeated again and again for each attribute. Eg. adding the events togther to get them sorted. This can’t be the way to do it. There has to be a way to do that somewhere above in the yaml file and then just access the variable again and again in each attribute. Due to my missing experience in Python an yaml, I didn’t find a way to do this. I can’t access a variable which is set in another attribute before. How to do this? Were to place the code in the yaml file?
I add the events in nr. 1 together in one big array of events to be able to sort them by the startdate. I am not sure, wether this is the best way to do it, but the bigger problem of this is, that the information from which calendar/person the event is from gets lost. Is there a way to add a new field to each event with the name like in a for-loop before all the events are added together?
Which book or source of knowledge to use to learn Python and the Home Assistant Yaml the right way?
Thx and best regards
1 post - 1 participant
I started just a few weeks ago, and this happened before a few times, then it got resolved by power off - power on.
My installation: raspberry pi 5 with a SDD card, wired ethernet on a switch. Original power supply, one aeotec dongle for zwave, one sonoff dongle for zigbee.
3 posts - 2 participants
Hello,
I have my Reolink WIFI doorbell with Frigate and the Frigate card with 2-way audio running. It works. I have two questions about this:
homeassistant:/config# cat frigate.yml
mqtt:
enabled: true
host: 172.30.32.1
user: admin_mqtt
password: Marlies(12)
topic_prefix: frigate
# Optional: client id (default: shown below)
# WARNING: must be unique if you are running multiple instances
client_id: frigate
# Optional: interval in seconds for publishing stats (default: shown below)
stats_interval: 30
objects:
track:
- person
- car
filters:
person:
min_area: 5000
max_area: 100000
go2rtc:
streams:
front_doorbell:
- rtsp://admin:Marlies(12)@192.168.130.143:554/Preview_01_main#backchannel=0
- rtsp://admin:Marlies(12)@192.168.130.143:554/Preview_01_sub
- ffmpeg:front_doorbell#audio=opus#hardware
front_doorbell_sub:
- rtsp://admin:Marlies(12)@192.168.130.143:554/Preview_01_sub
- ffmpeg:front_doorbel_sub#audio=opus#hardware
webrtc:
candidates:
- 172.30.32.1:8555
- stun:8555
cameras:
front_doorbell:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/front_doorbell?video=copy&audio=aac
input_args: preset-rtsp-restream-low-latency
roles:
- record
- path: rtsp://127.0.0.1:8554/front_doorbell_sub?video=copy&audio=aac
input_args: preset-rtsp-restream-low-latency
roles:
- detect
- audio
detect:
width: 1280
height: 720
fps: 5
snapshots:
enabled: true
record:
enabled: true
retain:
days: 7
events:
retain:
default: 14
version: 0.14
Frigate card
type: custom:frigate-card
cameras:
- camera_entity: camera.front_doorbell
live_provider: go2rtc
go2rtc:
modes:
- webrtc
menu:
buttons:
microphone:
enabled: true
alignment: matching
timeline:
enabled: false
cameras:
enabled: false
frigate:
enabled: false
download:
enabled: false
media_player:
enabled: false
mute:
enabled: true
alignment: opposing
camera_ui:
enabled: false
style: outside
position: right
button_size: 66
alignment: right
live:
controls:
thumbnails:
mode: none
auto_mute: all
preload: false
dimensions: {}
media_gallery:
controls:
thumbnails:
size: 140
show_favorite_control: false
show_timeline_control: false
show_download_control: false
filter:
mode: none
I would be happy to receive further support.
Greetings from Stefan Harbich
Doorbell Firmware: Firmware: v3.0.0.4110_2410111119
Frigate Version: 0.14.1
Frigate Card Version: 6.0.0
Frigate Home Assistant Integration Version: 5.5.1
1 post - 1 participant
Hi everyone,
I have an automation with this condition:
conditions:
- condition: state
entity_id: input_boolean.holiday_mode
state: "on"
The automation should start only if the button is active.
Why I got the error:
Translation error: INVALID_ARGUMENT_TYPE
Thanks
1 post - 1 participant
Added z-wave js ui, finds node and everything looks fine.
But can’t find devices when I search for a thermostat example.
(Smartthing finds the device)
Tried several times to include and exclude and reset the device.
I have Silicon Labs controller 700, with verson v.7.21.5.
I have tried:
-Extension cable
Stuck… any suggestions? 
3 posts - 2 participants
Have a device here and I did ask the manufacturer how they would update the device, the answer is that they dont have anything to do with it, it was running CSA standard firmware.
Is matter so standardised that it have common firmware for devices?
The device is a Mill heater so its a thermostat and I’m hoping for support for energy monitoring an a few other things.
1 post - 1 participant
Hi,
I am using device_tracker presence detection entity that was created by the HA android app in my automation. However I am finding that overnight it will start to “flip flop” between the home and away states causing the automation to run when it shouldn’t.
The time highlighted by the red box the phone was at home the entire time but it has flipped to away status multiple times!
Any pointers on how I can debug this?
Thanks.
1 post - 1 participant
