Hi, have installed the latest version of HA os. There seems to be nowhere I can set an external url anymore - all i can do is configure local or enable nabu.
What’s going on here? Am I missing something really obvious.
1 post - 1 participant
↧
External URL option missing in config?
↧
Deregistering Alexa's removes automation actions?
So i deregistered my alexa’s in the hope’s of fixing audio sync problems (skipping on everywhere group etc).
Now the automations i had, seem to (at least in the gui) not fully exist anymore. The yaml code is still intact though. Is there any way of fixing these or do i need to go through all my automations again to resolve…
1 post - 1 participant
↧
↧
Capture Still Image From Ring On Motion
Hi, this question has been asked before but not really answered.
Does anyone know how to capture an image from a Ring Doorbell and save it locally?
I came across a post that did the following but I’m unsure where the IP address comes from?
service: downloader.download_file
data_template:
url: http://172.16.50.124{{ state_attr('camera.front_door', 'entity_picture') }}
subdir: camera_front_door
filename: front_door.jpg
overwrite: true
2 posts - 2 participants
↧
Alert when power draw stops
Hi, I’m new to home assistant but think it’s probably the best way to achieve my goal.
How would I go about getting an alert if the power usage from an appliance stops? Ultimately I want to get it to sound a siren or the house alarm.
Thanks in advance.
2 posts - 2 participants
↧
Sonoff ZB Dongle Plus as Router No Working
I flashed my spare Sonoff ZB Dongle Plus with the Router Firmware. After that I paired it with my ZB Coordinator (My main Sonoff ZB Dongle Plus). Then when I try to use “Connect Devices via this Device” option by going to the ZB Dongle Plus (Newly added Router) menu, it doesn’t add my ZB device (Sonoff ZB Switch; which was in pairing mode) via this router. It adds the device via my Coordinator. Can someone please tell me how I can add devices via my ZB Dongle Plus Router? FYI I am using ZHA.
1 post - 1 participant
↧
↧
KNX expose Time not working
Hello there,
I’m trying to figure out how to expose time or date to knx because my Meteodata Weatherstation has no internal clock and needs this information to determine the elevation and azimut of the sun, so it can calculate the correct position of the covers. It is possible to tell the device to send a bit to a specific adress to get a the current time. Unfortunately the device does not simply ask on the adress of the time object 1/0/10 via GroupValueRead like other KNX devices.
My Hardware configuration is as follows:
- HA running on a raspberry 4b (Home Assistant Operating System)
- Home Assistant 2022.4.6
- supervisor-2022.04.0
- Elsner KNX PS640-IP
- Theben Meteodata 140 S 24V
- Logging for knx is enabled (and working):
logger:
default: critical
logs:
xknx.telegram: debug
This is what i tried before posting my question:
At first, simply following the documentation: https://www.home-assistant.io/integrations/knx/#exposing-entity-states-entity-attributes-or-time-to-knx-bus
My entry in configuration.yaml:
knx:
expose:
- type: date #also tried datetime
address: "1/0/11"
- type: time
address: "1/0/10"
This has no effect, neither in the HA serverlogs nor in ETS Groupmonitor there is any entry for date or time. As I read in other threads, there should be one entry on startup and one entry every hour.
Then i tried to set the Date and Time manually in ETS, output in Groupmonitor:
Unfortunately there is no entry in the HA logs after this step.
My next try was to figure out if i could set up an automation to send any time to knx bus. This seems to be impossible as there is no 3byte DPT in HA.
So I went the other way round and set up an automation which requests the time every 5 minutes (for test purposes only) and triggers Homeassistant to answer:
alias: KNX Uhrzeit senden
description: >-
Schickt an 1/0/10 und 1/0/11 ein Groupvalueread damit Homeassistant mit Zeit
und Datum antwortet.
trigger:
- platform: time_pattern
minutes: '5'
condition: []
action:
- service: knx.read
data:
address: 1/0/10
- service: knx.read
data:
address: 1/0/11
mode: single
The Log entry is as follows:
2022-04-24 12:05:00 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Outgoing" source_address="0.0.0" destination_address="1/0/10" payload="<GroupValueRead />" />
2022-04-24 12:05:00 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Outgoing" source_address="0.0.0" destination_address="1/0/11" payload="<GroupValueRead />" />
2022-04-24 12:05:00 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Outgoing" source_address="1.1.237" destination_address="1/0/10" payload="<GroupValueResponse value="<DPTArray value="[0xec,0x5,0x0]" />" />" />
2022-04-24 12:05:00 DEBUG (MainThread) [xknx.telegram] <Telegram direction="Outgoing" source_address="1.1.237" destination_address="1/0/11" payload="<GroupValueResponse value="<DPTArray value="[0x7a,0x4,0x18,0xec,0x5,0x0,0x21,0x80]" />" />" />
Obviously this is working as excpected, Homeassistant can get triggered by itself…
Needless to say this has no effect in the world of KNX, knx telegram is not showing up in Groupmonitor, the time on the Meteodata remains not defined.
It seems there is no communication between HA and KNX when time or date should be sent.
Now i’m stuck, i have no idea what i could possibly try or what i could have missed out.
All other KNX Devices (about 200 Groupadresses or more, sensors, binary sensors, switches, covers) work properly within Homeassistant (both directions). Before moving to Homeassistant i used FHEM, there was a simple oneliner tor configure sending time every hour.
Does anybody have an idea what to try or where i made a mistake?
1 post - 1 participant
↧
What is the minimum backup for HA and addons to work?
i dont know how my HA backups ballooned from MB to GB. and this 39GB was partial too!
what is taking up all that space? what should i backup so that i can restore HA up and running with all the Add-ons configuration? I dont need past records/events… just the bare essentials for them to be up and running.
1 post - 1 participant
↧
Zigbee dongle after migration
Hi everyone,
I’ve used to have HA OS installed on PI3 board. But as I’ve got some more spare time I wanted to tinker with docker and some microservices, so I’ve made a backup, but then uninstall HA OS and flashed the microSD with Ubuntu Server.
I’ve created myself docker compose file to spin up home assistant but the zigbee dongle TI CC2531 USB CDC is not found at /dev/ttyACM0 nor ACM1.
Does anyone know what to do? How much I am doomed?
Thanks
1 post - 1 participant
↧
Recorder domain exclude not working as expected
I have many of these type of logs in my state_attributes table:
{"type":"browser_mod","last_seen":"2022-04-23T21:44:48.128091","deviceID":"07c1ac69-44667gh77","path":"/lovelace/upstairs","visibility":"visible","userAgent":"Mozilla/5.0 (Linux; Android 7.1.2; Fire Build/NJH47F; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/80.0.3987.132 Safari/537.36","currentUser":"xxx","fullyKiosk":false,"width":1103,"height":689,"battery_level":23,"charging":true,"darkMode":false,"userData":{"id":"62df499525574a619ee6254448b84b85","name":"xxx","is_owner":true,"is_admin":true,"credentials":[{"auth_provider_type":"homeassistant","auth_provider_id":null}],"mfa_modules":[{"id":"totp","name":"Authenticator app","enabled":false}]},"config":{"command":"update","name":"upstairs","camera":true}}
And I am trying to exclude them from saving to the DB since they are useless and grow my DB by a few MB per day.
However my exclusion doesn’t work as it still logs these:
db_url: !secret mariaDBurl
purge_keep_days: 7
exclude:
domains:
- browser_mod
Can anyone see anything wrong here?
1 post - 1 participant
↧
↧
Energy Meter not working
Dear community,
I was following this discussion Sonoff POW R2 - how to know how I consumed in a day or month and then realized, that as of Version core-2022.4.6, this can be done much more easy and within the UI.
I have a fridge in the basement [1] and a machine to dry the air [2]. Each is powered via a Sonoff Pow2.
So, in HomeAssistant, I added two “Helpers”. One is converting the “Power” to kWh, the other is the Metering Utility, which I wanted to add to the Energy Dashboard.
For the fridge (“Gefrierschrank”) it works as expected, for the drying machine, there are values available, but I am not able to add the sensor to the Energy Dashboard. How do I trouble shoot this?
Any help is very much appreciated.
1 post - 1 participant
↧
ZWA039 Aeotec Ltd. / aërQ Temperature and Humidity Sensor v2.0 Configuration
New with Home Assistant. Here what I got:
Home Assistant Core
Installed version: 2022.4.5
Z-Wave JS Add-on
Current version: 0.1.56
I was able to add the ZWA039 Aeotec Ltd. / aërQ Temperature and Humidity Sensor v2.0 but not sure how to add the entities. (https://devices.zwave-js.io/)
Has anyone configured one of these before?
1 post - 1 participant
↧
Cannot change Area for one Hue device
I have one Phillips Hue device that will not allow changing its area.
The device was originally assigned to the living room likely due to the Hue hub having it there.
I changed the Hue hub location to Office and tried to assign the area in HA to Office yet the Dashboard still lists the device in the Living Room card.
I’ve restarted HA but cannot get this device to move. Further I have an Insteon device for my Garage door and have it assigned to a Garagr area yet the area does not show on the dashboard.
1 post - 1 participant
↧
Combining two entities?
I have two LightwaveRF wall switches (called, eg, Door A & Door B) that control the same central light - and this produces two Entities.
If I tap on the Door A or Door B entity within Lovelace, or turn on one of the wall switches the light turns on and the relevant icon changes colour BUT the other entity does not change.
Whilst I understand why this might be so, I would like to create a third entity that combines the two - so that whichever physical switch is turned on, the third icon changes colour to reflect the change in state. I would also like this third icon to turn the light on & off.
How might I best achieve this? Do I need to use a Lighting Group, or perhaps a Helper?
TIA
1 post - 1 participant
↧
↧
On condition blinking box shadow of entities card
I have following conditional card:
- type: conditional
conditions:
- entity: input_boolean.pool
state: 'on'
card:
type: entities
style: |
ha-card {
background: none;
font-variant: small-caps;
}
entities:
!include templates/cards/pool_timer.yaml
I would like to have animated (blinking) entities box shadow on condition - either sensor or input_boolean state.
Any advice pls?
1 post - 1 participant
↧
X10 Config via Insteon Integration
When configuring X10 in the Insteon integration, I’m wondering what parameter the last field is supposed be? It’s not labelled. In this screenshot, 5, the pulldown menu range is 1-254.
1 post - 1 participant
↧
How to sent a critical notification with the alert Domain?
How do I sent a critical notification with the alert domain to an iOS device with the home assistant App installed?
2 posts - 2 participants
↧
GoodWe inverter measurments to Energy panel
Hi
I’m new here and I don’t really know how to ask the question, but I’ll try.
I have a GoodWe solar inverter and I want to include the energy management into the Energy Panel of HA. I tried the official integration GoodWe Inverter and stopped working a few moments later. So I decided to give a try to the HACS integration SEMS Portal.
I now can have the current generation of my Solar Panels, in W. But I can’t add this measure to the Energy Panel… On the “Add generation” part, I have to enter a state with kWh.
Firstly. I don’t understand why I have to put it in kWh because my inverter gives me W in real time.
So, I did this:
template:
- sensor:
- name: "Solar Generation"
unit_of_measurement: "kWh"
state_class: total_increasing
device_class: energy
state: "{{ states('sensor.inverter_inversor')|float / 1000}}"
Now I can add this to the Energy Panel, but it does something very strange:
And this is impossible. I don’t produce 7,21kW. I want the graphic and data to be realistic and I don’t know what am I doing wrong.
I don’t know either how can I extract my consumption information from that integration.
Any help will be appreciated.
Thanks in advance
PD. Sorry for my bad English.
2 posts - 1 participant
↧
↧
Scratching my head over this automation with event_data
Hello great people!
I have an automation for my a Ring keypad I use for my alarm that has been running pretty well.
Thing is I am now trying to implement a new user (so a new password) and every single thing I tried on that automation have failed miserably. I get HA to send an visual error (red ring) to the keypad when the user types a wrong code:
alias: Send red ring if wrong pin
description: Keypad gets a red ring if pin is wrong
trigger:
- platform: event
event_type: zwave_js_notification
event_data:
node_id: 51
event_type: 5
data_type: 2
- platform: event
event_type: zwave_js_notification
event_data:
node_id: 70
event_type: 5
data_type: 2
condition:
condition: template
value_template: >
{{ trigger.event.data.event_data != '1111' }}
This works very well, if I type the right code, it’s all good, if it’s the wrong code, it sends the red ring. Problem is that if I try to add a new code so:
- id: send_red_ring_if_wrong_pin
alias: Send red ring if wrong pin
description: Keypad gets a red ring if pin is wrong
trigger:
- platform: event
event_type: zwave_js_notification
event_data:
node_id: 51
event_type: 5
data_type: 2
- platform: event
event_type: zwave_js_notification
event_data:
node_id: 70
event_type: 5
data_type: 2
condition:
condition: template
value_template: >
{{ trigger.event.data.event_data != '1111 }} or
trigger.event.data.event_data != '2222' }}
The automation still runs (and sends the red ring) even though the password is incorrect. I also tried to write it with “condition: or” but the same thing still happens.
What am I doing wrong? 
Any help is appreciated.
1 post - 1 participant
↧
Help me understand why this doesn't trigger
I have an automation that is doing all the actions from my interactions with an NS-panel.
This is the trigger:
trigger:
- platform: numeric_state
entity_id: sensor.ns_panel_last_click_va
above: '150'
below: '500'
id: color_temp
and the action is:
- choose:
- conditions:
- condition: trigger
id: color_temp
sequence:
- service: light.turn_on
data:
color_temp: '{{ states("sensor.ns_panel_last_click_va") | int }}'
target:
entity_id: '{{ states("input_text.ns_panel_kitchen_selected_device") }}'
default: []
input_text.ns_panel_kitchen_selected_device has the state light.kokslampa and is set previously.
(The state is cleared when I release the screen. If I change it to keep the state then I can trigger the above in services and it works fine)
This is what the trace looks like after I try to change the color temp, notice the time.
Yet I have an state update:
That should have triggered the automation (?).
This is the complete automation (it’s rather big).
It’s the last trigger, and the last choose that should have been triggered.
alias: ns panel kitchen actions
description: ''
trigger:
- platform: template
value_template: '{{ states(''sensor.ns_panel_last_click_va'') is match("\d+,\d+,\d+") }}'
id: color change
- platform: template
value_template: >-
{{ states('sensor.ns_panel_last_click_va') is
match("light.*|switch.*|climate.*") }}
- platform: state
entity_id: sensor.ns_panel_current_display_page
to: '13.00'
id: thermostat
- platform: state
entity_id: sensor.ns_panel_brightness_slider
id: brightness change
- platform: template
value_template: >-
{{ states('sensor.ns_panel_last_click_va') != "" and
states('sensor.ns_panel_last_click_va') != "newtxt"}}
for: '00:00:02'
id: long
- platform: numeric_state
entity_id: sensor.ns_panel_last_click_va
above: '150'
below: '500'
id: color_temp
condition: []
action:
- choose:
- conditions:
- condition: state
entity_id: sensor.ns_panel_current_display_page
state: '2.00'
sequence:
- service: homeassistant.toggle
data: {}
target:
entity_id: '{{ states(''sensor.ns_panel_last_click_va'') }}'
default: []
- choose:
- conditions:
- condition: state
entity_id: sensor.ns_panel_current_display_page
state: '8.00'
sequence:
- service: homeassistant.toggle
data: {}
target:
entity_id: '{{ states(''sensor.ns_panel_last_click_va'') }}'
default: []
- choose:
- conditions:
- condition: state
entity_id: sensor.ns_panel_current_display_page
state: '13.00'
sequence:
- choose:
- conditions:
- condition: state
entity_id: sensor.ns_panel_last_click_va
state: climate.vardagsrum
sequence:
- service: input_text.set_value
data:
value: climate.vardagsrum
target:
entity_id:
- input_text.ns_kitchen_temp
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.kitchen.pic=43
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.matilda.pic=51
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.david.pic=49
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.sovrum.pic=47
default: []
- choose:
- conditions:
- condition: state
entity_id: sensor.ns_panel_last_click_va
state: climate.matilda
sequence:
- service: input_text.set_value
data:
value: climate.matilda
target:
entity_id:
- input_text.ns_kitchen_temp
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.kitchen.pic=42
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.matilda.pic=50
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.david.pic=49
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.sovrum.pic=47
default: []
- choose:
- conditions:
- condition: state
entity_id: sensor.ns_panel_last_click_va
state: climate.david
sequence:
- service: input_text.set_value
data:
value: climate.david
target:
entity_id:
- input_text.ns_kitchen_temp
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.kitchen.pic=42
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.matilda.pic=51
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.david.pic=48
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.sovrum.pic=47
default: []
- choose:
- conditions:
- condition: state
entity_id: sensor.ns_panel_last_click_va
state: climate.sovrum
sequence:
- service: input_text.set_value
data:
value: climate.sovrum
target:
entity_id:
- input_text.ns_kitchen_temp
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.kitchen.pic=42
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.matilda.pic=51
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.david.pic=49
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.sovrum.pic=46
default: []
- choose:
- conditions:
- condition: state
entity_id: sensor.ns_panel_last_click_va
state: script.ns_kitchen_temp_up
sequence:
- service: script.ns_kitchen_temp_up
data: {}
default: []
- choose:
- conditions:
- condition: state
entity_id: sensor.ns_panel_last_click_va
state: script.ns_kitchen_temp_down
sequence:
- service: script.ns_kitchen_temp_down
data: {}
default: []
- choose:
- conditions:
- condition: state
entity_id: sensor.ns_panel_last_click_va
state: script.ns_kitchen_temp_boost
sequence:
- service: script.ns_kitchen_temp_boost
data: {}
default: []
default: []
- choose:
- conditions:
- condition: trigger
id: thermostat
sequence:
- choose:
- conditions:
- condition: state
entity_id: input_text.ns_kitchen_temp
state: climate.vardagsrum
sequence:
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.kitchen.pic=43
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.matilda.pic=51
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.david.pic=49
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.sovrum.pic=47
default: []
- choose:
- conditions:
- condition: state
entity_id: input_text.ns_kitchen_temp
state: climate.matilda
sequence:
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.kitchen.pic=42
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.matilda.pic=50
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.david.pic=49
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.sovrum.pic=47
default: []
- choose:
- conditions:
- condition: state
entity_id: input_text.ns_kitchen_temp
state: climate.david
sequence:
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.kitchen.pic=42
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.matilda.pic=51
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.david.pic=48
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.sovrum.pic=47
default: []
- choose:
- conditions:
- condition: state
entity_id: input_text.ns_kitchen_temp
state: climate.sovrum
sequence:
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.kitchen.pic=42
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.matilda.pic=51
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.david.pic=49
- service: esphome.ns_kitchen_send_command
data:
cmd: Thermostat.sovrum.pic=46
default: []
default: []
- choose:
- conditions:
- condition: trigger
id: long
sequence:
- choose:
- conditions:
- condition: template
value_template: >-
{{ states('sensor.ns_panel_last_click_va') in
['light.davids_lampa', 'light.matildas_lampa',
'light.skapen', 'light.kokslampa'] }}
sequence:
- service: esphome.ns_kitchen_send_command
data:
cmd: >-
Colorwheel.vprevpage.val="{{
states('sensor.ns_panel_current_display_page') |
replace(".00","") }}"
- service: input_text.set_value
data:
value: '{{ states(''sensor.ns_panel_last_click_va'') }}'
target:
entity_id: input_text.ns_panel_kitchen_selected_device
- service: esphome.ns_kitchen_set_page
data:
page: 14
- choose:
- conditions:
- condition: template
value_template: >-
{{ states("sensor.ns_panel_last_click_va") in
['light.davids_lampa', 'light.matildas_lampa',
'light.skapen'] }}
sequence:
- service: esphome.ns_kitchen_send_command
data:
cmd: vis h1,0
- service: esphome.ns_kitchen_send_command
data:
cmd: vis p0,0
default:
- service: esphome.ns_kitchen_send_command
data:
cmd: vis colorWheel,0
- service: esphome.ns_kitchen_send_command
data:
cmd: vis h1,1
- service: esphome.ns_kitchen_send_command
data:
cmd: vis p0,1
- service: esphome.ns_kitchen_send_command
data:
cmd: >-
h1.val={{state_attr(states('sensor.ns_panel_last_click_va'),
'color_temp')}}
- service: esphome.ns_kitchen_send_command
data:
cmd: >-
h0.val={{state_attr(states('sensor.ns_panel_last_click_va'),
'brightness')}}
default: []
default: []
- choose:
- conditions:
- condition: trigger
id: color change
sequence:
- service: light.turn_on
data:
rgb_color: '{{ states("sensor.ns_panel_last_click_va").split(",") }}'
target:
entity_id: '{{ states("input_text.ns_panel_kitchen_selected_device") }}'
default: []
- choose:
- conditions:
- condition: trigger
id: brightness change
sequence:
- service: light.turn_on
data:
brightness: '{{ states("sensor.ns_panel_brightness_slider") }}'
target:
entity_id: '{{ states("input_text.ns_panel_kitchen_selected_device") }}'
default: []
- choose:
- conditions:
- condition: trigger
id: color_temp
sequence:
- service: light.turn_on
data:
color_temp: '{{ states("sensor.ns_panel_last_click_va") | int }}'
target:
entity_id: '{{ states("input_text.ns_panel_kitchen_selected_device") }}'
default: []
mode: single
2 posts - 2 participants
↧
Help with "Invalid config" Error Notification
This morning I started getting a notification about an automation config error.
Just before the error occurred, I removed a couple old zigbee devices that were no longer in use. There were a couple automations that had references to those devices, so I deleted those with no resolution. Otherwise, my config file passes the config check, and things are working normally.
Below is a copy of the log. Would anyone be willing to point me in the right direction on this?
Logger: homeassistant.config
Source: config.py:454
First occurred: 12:52:00 (1 occurrences)
Last logged: 12:52:00
Invalid config for [automation]: Invalid trigger configuration. Got OrderedDict([('default_config', {}), ('automation', [OrderedDict([('id', '1648675356840'), ('alias', 'Notify When Backups Stale'), ('description', ''), ('trigger', [OrderedDict([('platform', 'state'), ('entity_id', 'binary_sensor.backups_stale'), ('from', 'off'), ('to', 'on')])]), ('condition', []), ('action', [OrderedDict([('service', 'notify.persistent_notification'), ('data', OrderedDict([('message', 'Home Assistant backup failed. Fix it!')]))]), OrderedDict([('service', 'notify.home_assi.... (See /config/configuration.yaml, line 7).
There is a reference, at the end of the error, to line number 7 of the config.yaml. That part of the code is as follows:
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Text to speech
tts:
- platform: google_translate
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
1 post - 1 participant
↧