Is it possible ti edit the YAML of a helper created in the UI ?

Looked everywhere I can think of and cant seem to figure out how to do it…

1 post - 1 participant

Read full topic

I´m running HA in a VM on my Synology and a HomematicCCU on a raspi. The new custom Homematic integration is working very well and everything should be fine. But there is one thing, i can´t get runnig anymore (did it before, but now it seems to be impossible):

I want to use the homematic.keypress event to trigger an automation. When i look at the event-listener results, the event-data is comming in correctly:

Ereignis 13 ausgelöst 19:53:

{
    "event_type": "homematic.keypress",
    "data": {
        "interface_id": "RaspberryMatic-HmIP-RF",
        "address": "00085BE9A3B1BA",
        "type": "press_long",
        "subtype": 2,
        "device_id": "e0f97bd899ae24d7c3cc36511a05f61c"
    },
    "origin": "LOCAL",
    "time_fired": "2022-04-25T17:53:05.258336+00:00",
    "context": {
        "id": "4d566eea0e1300be5d35bc87eb2e1645",
        "parent_id": null,
        "user_id": null
    }
}

The trigger-part in my automation looks like this:

trigger:
  - platform: event
    event_type: homematic.keypress
    event_data:
      name: 00085BE9A3B1BA
      param: press_long
      channel: 2

I tried nearly everything as “name” in the trigger: the adress, the device_id, the interface_id, all possible names… nothing. The automation isn´t starting.

There is one thing, I recognized: in all the other topics, where the homematic.keypress-event is comming in correctly in HA, in the “data”:-section is a “name”-value and not “adress” like in mine. Is it possible, that there were changes in Rasperrymatic, that the data doesn´t fit anymore? Because I had that automation working for month, and suddenly, a few weeks ago, it stopped working, without changing anything. Now I did a complete new HA installation from the scratch, but still no chance to get it work. Hope someone can help me. Thanx in advance!

1 post - 1 participant

Read full topic

Hello everyone ,
I have an issue connecting Home Assistant to a TLS enabled Mosquitto MQTT server.
I am using linuxserver/homeassistant and eclipse-mosquitto docker containers.

On the MQTT server I have:

1. Configured the broker to use TLS security [ref]
2. Added a user in password_file [ref]
3. Tested the setup using MQTT.fx 1.7.1 (properly connects using TLS usind the above created .ca certificate file)

On the Home-Assistant server I have:

1. Added the certificate path to configuration.yaml [ref]

The MQTT server is discovered and I am configuring the integration but the connection fails.

The MQTT container log:

1650914314: New connection from 10.0.3.1:41787 on port 8883.
1650914314: OpenSSL Error[0]: error:1404A3F2:SSL routines:ST_ACCEPT:sslv3 alert unexpected message
1650914314: Client <unknown> disconnected: Protocol error.
1650914317: Client connection from 10.0.3.1 failed: error:02FFF020:system library:func(4095):Broken pipe.

1 post - 1 participant

Read full topic

Looks like my browser cache cleared and my lovelace bacame broken because of “Custom element doesn’t exist: hui-horizontal-stack-card.”

It was working fine, no reconfiguration was done, but at some point the custom card stopped to work, and while in cahce was still working. Also I cannot find it in HACS to reinstall it. Is it from card-mod?

It loads after few mions and gives error in logs:

Logger: frontend.js.latest.202203012
Source: components/system_log/__init__.py:190
First occurred: 22:53:01 (1 occurrences)
Last logged: 22:53:01

https://xxxxxxxxxxx.duckdns.org/frontend_latest/app.b83d2076.js:850:0 Error: Failed to execute 'define' on 'CustomElementRegistry': the name "mod-card" has already been used with this registry

1 post - 1 participant

Read full topic

I using Zwave JS at HA , but how can i get to the parameters of the switch (fibaro motion sensor)itself
I thought :configuration > Devices/service > Z-wave JS > select the device > CONFIGURE DEVICE

but it is not entering its menu, waiting waiting . nothing happonds
What im am doing wrong?

Normally i could change color of LED and timing, triggers etc

1 post - 1 participant

Read full topic

I have been playing with some templating for making a sensor who tells me what time the electricity cost is lowest of the day.

in the developer I can get this code to work but not sure about the syntax for putting this in a sensor.

{% set l=state_attr('sensor.nordpool_kwh_dk1_dkk_3_10_025', 'raw_today')|sort(attribute='value') %}
cheapest kl. {{l[0].start.hour}}-{{l[0].end.hour}}

I get this result

cheapest
kl. 1-2

this is working but can not get it working in a template sensor can someone point me the right syntax for this to work ?

1 post - 1 participant

Read full topic

Hello Community,

I´m a zero coder so I have no clue how I can achieve my request.
I want to count all power sockets which are ON and have a special entitiy_id containing “switch.steckdose_”.

All my power plugs are named with the same schema steckdose_ so I believe thats the only way to sort it out.

For my lights I found something to count all lights, which are not groups - but I have no idea how the syntax is working or at least how I can get out from developer tools the infos I need:
{{ states.light | selectattr(‘state’,‘eq’,‘on’) | rejectattr(‘attributes.entity_id’, ‘defined’) | list|count }}

Thanks in advance for your help.

Greetings
Electro

1 post - 1 participant

Read full topic

Now that you can easily add a Nest Protect to Home Assistant, I am looking at creating an automation if it detects smoke.

The automation will unlock 2 doors, turn on all lights and I have a few air purifurers around the house, I am not sure if I should turn these off or set them full.

What other automation have people done with their smoke alarms

3 posts - 3 participants

Read full topic

Need help solving a problem.

Background:
I have built a DIY tipping bucket rain gauge. I have an Aqara door/window sensor that registers the tippings. When it tips over, the sensor goes from open, passing closed and tips over to open on the other side. Going from closed to open is one tip.
I’m using History Stats sensor to count every time the state is ON (open). I have done many testings and it works perfect.
However, yesterday it saw that it had register a few tippings although it was standing on a shelf indoors. I checked the logs and saw that the sensors state had been “unknown” for some seconds and then came back to ON and that, off course, also counts as one tip.

Now to my question:
Is there a way templating History Stats so that it only counts when it goes from OFF to ON and not just register ON? That would exclude the unknown state.
I’m thinking like the State trigger in an automation where you can set both the from- and to-state.

Many thanks!

1 post - 1 participant

Read full topic

Anyone getting odd icon behavior in the latest release?

A number of my icons have suddenly resized themselves, or in some cases moved themselves. I thought it was restricted to icons created by the button_card mod, but my HACS icon (in the sidebar) just grew substantially.

A quick test reveals DIFFERENT behavior in Chrome. Anyone else seeing this?

-J

2 posts - 2 participants

Read full topic

I’m trying to download the log of a history sensor I created in an effort to get a log and statistics on how much time I spend at work per day. The sensor code is below, now I’m having trouble exporting this data out of home assistant.

sensor:
  - platform: history_stats
    name: Time At Work
    entity_id: person.jack
    state: "Work"
    type: time
    start: "{{ now().replace(hour=0, minute=0, second=0) }}"
    end: "{{ now() }}"

1 post - 1 participant

Read full topic

Was hoping someone could school me on the right way to implement this.

Today, in my configuration.yaml, i have a

sensor: 
  !include sensor.yaml

In that sensor.yaml file, I have a bunch of sensors organized by platform type.

- platform: feedparser
    name: Politico
    feed_url: https://www.politico.com/rss/politicopicks.xml
    date_format: '%a, %d %b %Y %H:%M:%S %Z'
    scan_interval:
      hours: 3
 - platform: sonarr_upcoming_media
    api_key: 9ecd0e7ca7ee41db9d127a2bc090ee35
    host: 192.168.7.95
    port: 8989
    days: 7
    max: 10 
  - platform: template
    sensors:
      cleaner_days:
        friendly_name: "Days till Cleaners"
        value_template: >-
              {{ state_attr('sensor.cleaners','days') }}
      hvac_action:
        friendly_name: "hvac_action"
        value_template: "{{ states.climate.home.attributes.hvac_action }}"

This template sensor is where i have a problem.

I saw another example of working with templates that looks like this:

template:
  - sensor:
      friendly_name: "Echo Show Timer"
      icon: mdi:timer
      state: >-
        {% set entity = 'sensor.family_room_echo_next_timer' %} 
        {% if state_attr(entity,'status') == 'ON' %} active
        {% else %} inactive
        {% endif %}
      attribute: 
        remaining: >-
          {% set entity = 'sensor.family_room_echo_next_timer' %} 
          {% if state_attr(entity,'status') == 'ON' %}
            {% set duration = ((state_attr(entity, 'sorted_active')|from_json)[0][1].originalDurationInMillis/ 1000)| round(0) %}
            {{duration//3600}}:{{(duration%3600)//60}}:{{((duration%3600)%60)}}
          {% endif %}
      end_time: >-
        {% set entity = 'sensor.family_room_echo_next_timer' %} 
        {% if state_attr(entity,'status') == 'ON' %}
          {{ states(entity) }}
        {% endif %}   

The problem i have is that in my sensor.yaml file, I get the “sensor.state is not supported error.” how do i fold this latter example into my sensor.yaml file. Do i need to rewrite all my template sensors (there are lots!)

2 posts - 2 participants

Read full topic

I cannot get my ConBeeII stick to connect to network. I was working a week ago. I am running the latest HA 2022.4.7. My HA is running in a VM on unraid. It sees the Dresden USB stick but fails to connect to Network. Here are my log files.

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] firmware.sh: executing... 
[18:12:45] INFO: GCFFlasher V3_17 (c) dresden elektronik ingenieurtechnik gmbh
Path             | Vendor | Product | Serial     | Type
-----------------+--------+---------+------------+-------
/dev/ttyACM0     | 0x1CF1 | 0x0030  |            | ConBee II 
/dev/ttyACM1     | 0x1CF1 | 0x0030  | DE2495005  | ConBee II 
[cont-init.d] firmware.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] novnc.sh: executing... 
[cont-init.d] novnc.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[18:12:45] INFO: Websockify waiting for VNC to start
[services.d] done.
[18:12:45] INFO: Running the deCONZ OTA updater...
[18:12:45] INFO: Running the OSRAM LEdvance OTA updater...
[18:12:45] INFO: Running the IKEA OTA updater...
[18:12:45] INFO: Starting VNC server (local/yes)...
[18:12:46] INFO: Starting websockify...
WebSocket server settings:
  - Listen on 127.0.0.1:5901
  - Flash security policy server
  - Web server. Web root: /usr/share/novnc
  - No SSL/TLS support (no cert file)
  - proxying from 127.0.0.1:5901 to 127.0.0.1:5900

18:05:36:427 DDF: doc:path: samsung/samjin_button_switch.md
18:05:36:427 DDF: manufacturername: $MF_SAMJIN
18:05:36:427 DDF: md:known_issues: 
18:05:36:427 DDF: modelid: button
18:05:36:427 DDF: product: Samsung Button (IM6001-BTP01)
18:05:36:427 DDF: schema: devcap1.schema.json
18:05:36:427 DDF: status: Silver
18:05:36:428 DDF: subdevices: 
18:05:36:428 DDF: loaded resource item descriptor: attr/lastseen
18:05:36:428 DDF: loaded resource item descriptor: attr/manufacturername
18:05:36:428 DDF: loaded resource item descriptor: attr/modelid
18:05:36:428 DDF: failed to load resource item descriptor: attr/mode
18:05:36:428 DDF: loaded resource item descriptor: attr/name
18:05:36:428 DDF: loaded resource item descriptor: attr/swversion
18:05:36:428 DDF: loaded resource item descriptor: attr/type
18:05:36:428 DDF: loaded resource item descriptor: attr/uniqueid
18:05:36:428 DDF: loaded resource item descriptor: config/battery
18:05:36:428 DDF: loaded resource item descriptor: config/on
18:05:36:428 DDF: loaded resource item descriptor: config/pending
18:05:36:428 DDF: loaded resource item descriptor: config/reachable
18:05:36:428 DDF: loaded resource item descriptor: state/lastupdated
18:05:36:428 DDF: loaded resource item descriptor: state/buttonevent
18:05:36:428 DDF: loaded resource item descriptor: attr/lastseen
18:05:36:428 DDF: loaded resource item descriptor: attr/manufacturername
18:05:36:428 DDF: loaded resource item descriptor: attr/modelid
18:05:36:428 DDF: loaded resource item descriptor: attr/name
18:05:36:428 DDF: loaded resource item descriptor: attr/swversion
18:05:36:428 DDF: loaded resource item descriptor: attr/type
18:05:36:428 DDF: loaded resource item descriptor: attr/uniqueid
18:05:36:428 DDF: loaded resource item descriptor: config/battery
18:05:36:428 DDF: loaded resource item descriptor: config/offset
18:05:36:428 DDF: loaded resource item descriptor: config/on
18:05:36:428 DDF: loaded resource item descriptor: config/reachable
18:05:36:428 DDF: loaded resource item descriptor: state/lastupdated
18:05:36:428 DDF: loaded resource item descriptor: state/temperature
18:05:36:447 parent process s6-supervise
18:05:36:447 gw run mode: docker/hassio
18:05:36:447 GW sd-card image version file does not exist: /data/.local/share/dresden-elektronik/deCONZ/gw-version
18:05:36:449 DB sqlite version 3.27.2
18:05:36:449 DB PRAGMA page_count: 42
18:05:36:449 DB PRAGMA page_size: 4096
18:05:36:449 DB PRAGMA freelist_count: 0
18:05:36:449 DB file size 172032 bytes, free pages 0
18:05:36:449 DB PRAGMA user_version: 8
18:05:36:449 DB upgrade to user_version 9
18:05:36:487 DB write sqlite user_version 9
18:05:36:501 DB PRAGMA user_version: 9
18:05:36:501 DB cleanup
18:05:36:501 DB create temporary views
18:05:36:506 Started websocket server on 0.0.0.0, port: 8081
18:05:36:507 [INFO] - Found file containing button maps. Parsing data...
18:05:36:511 [INFO] - Button maps loaded.
18:05:36:512 found node plugin: libde_rest_plugin.so - REST API Plugin
18:05:36:512 found node plugin: libde_signal_plugin.so - Signal Monitor Plugin
18:05:37:286 OTAU: create 1189-003C-01056400.zigbee
18:05:37:300 OTAU: create 1189-003C-01056400.zigbee
18:05:37:309 OTAU: create 1189-0034-01056400.zigbee
18:05:37:317 OTAU: create 1189-0034-01056400.zigbee
18:05:37:325 OTAU: create 1189-0034-01056400.zigbee
18:05:37:333 OTAU: create 1189-0033-01056400.zigbee
18:05:37:341 OTAU: create 1189-0033-01056400.zigbee
18:05:37:368 OTAU: create 1189-00A0-02146550.zigbee
18:05:37:386 OTAU: create 1189-008C-02056550.zigbee
18:05:37:388 found node plugin: libstd_otau_plugin.so - STD OTAU Plugin
18:05:37:531 dlg action: Read binding table
18:05:38:417 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2495005-if00 / serialno: , ConBee II
18:05:38:460 Skip idle timer callback, too early: elapsed 927 msec
18:05:39:000 device state timeout ignored in state 2
18:05:40:159 device state timeout ignored in state 2
18:05:40:319 device state timeout ignored in state 2
18:05:40:478 device state timeout ignored in state 2
18:05:40:639 device state timeout ignored in state 2
18:05:40:798 device state timeout ignored in state 2
18:05:40:959 device state timeout ignored in state 2
18:05:41:119 device state timeout ignored in state 2
18:05:41:279 device state timeout ignored in state 2
18:05:41:438 device state timeout ignored in state 2
18:05:41:599 device state timeout ignored in state 2
18:05:41:781 device state timeout (handled)
18:05:41:859 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
18:05:41:859 device state timeout ignored in state 1
18:05:42:509 Announced to internet https://phoscon.de/discover
18:05:44:909 DEV Tick.Init: booted after 8000 seconds
18:05:51:935 GW update firmware found: /usr/share/deCONZ/firmware/deCONZ_ConBeeII_0x26660700.bin.GCF
18:05:56:426 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2495005-if00 / serialno: , ConBee II
18:05:57:426 start reconnect to network
18:05:57:999 device state timeout ignored in state 2
18:05:58:158 device state timeout ignored in state 2
18:05:58:319 device state timeout ignored in state 2
18:05:58:479 device state timeout ignored in state 2
18:05:58:638 device state timeout ignored in state 2
18:05:58:799 device state timeout ignored in state 2
18:05:58:959 device state timeout ignored in state 2
18:05:59:119 device state timeout ignored in state 2
18:05:59:278 device state timeout ignored in state 2
18:05:59:439 device state timeout ignored in state 2
18:05:59:598 device state timeout ignored in state 2
18:05:59:758 device state timeout (handled)
18:05:59:839 void zmMaster::handleStateIdle(zmMaster::MasterEvent) not connected goto OFF state
18:05:59:839 device state timeout ignored in state 1

1 post - 1 participant

Read full topic

I’m trying to troubleshoot some intermittent issues with some of my zigbee devices, and I suspect it’s a sometimes-malformed message. However, I’m having a lot of trouble reproducing it because it seems to happen at random (or at least hard-to-predict) times.

The easiest way to test this would be to see a playbook of the log that I get when I go to Developer tools->Events, and fill in “zha_event” and hit “start listening”. If I could just get that for ~1 day in some sort of log format without needing to keep a browser window open, that would be perfect. Is there any way to do this with home assistant, or am I stuck trying to hack together something that acts like the dev tools javascript?

1 post - 1 participant

Read full topic

Hello -

I have recently started with HA and installed HACS and then Grocy.

Use case - I want to track chores around the home and update them using a telegram notification response and/or NFC tag. This means If I scan the NFS tag the chore should be considered done, same with the telegram bot’s actionable notification. I have come so far with half of it only but ended with the below issues.

My system info -

Version 	core-2022.4.7
Installation Type 	Home Assistant OS
Development 	false
Supervisor 	true
Docker 	true
User 	root
Virtual Environment 	false
Python Version 	3.9.9
Operating System Family 	Linux
Operating System Version 	5.15.32

Issue1 :

After the restart of HA , I immediately started seeing these logs. gone through the documentation and I see no info on how to use this add-on now.

How should I proceed and what are my options?

2022-04-25 02:18:58 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration grocy which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-04-25 02:18:58 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-04-25 02:19:03 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that uses str for device registry entry_type. This is deprecated and will stop working in Home Assistant 2022.3, it should be updated to use DeviceEntryType instead. Please report this issue.
Stack (most recent call last):
File "/usr/local/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/local/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/usr/src/homeassistant/homeassistant/__main__.py", line 203, in <module>
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/__main__.py", line 191, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 119, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.9/asyncio/base_events.py", line 629, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.9/asyncio/base_events.py", line 596, in run_forever
self._run_once()
File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1890, in _run_once
handle._run()
File "/usr/local/lib/python3.9/asyncio/events.py", line 80, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 501, in _async_add_entity
device = device_registry.async_get_or_create(**processed_dev_info) # type: ignore[arg-type]
File "/usr/src/homeassistant/homeassistant/helpers/device_registry.py", line 369, in async_get_or_create
report( # type: ignore[unreachable]
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 74, in report
_LOGGER.warning(msg, stack_info=True)

Issue2:

I went ahead and proceed to create sensors to test, surprisingly after every restart sensors are behaving weird, for a while I see all the created sensors, and then after a restart one of the sensors shows unavailable.

Here is my sensor config (somehow the formatting isn’t looking good , but this is valid configuration, which I tested with “check configuration” )

---

platform: rest

name: water plants outside

resource: http://192.168.50.77:9283/api/chores/1

method: GET

value_template: "{{ (((as_timestamp(value_json.next_estimated_execution_time))-as_timestamp(now())) | int /60/1440) | round(0) }}"

json_attributes:

  - last_tracked

  - estimated_execution_time

headers:

  Accept: application/json

  Content-Type: application/json

  GROCY-API-KEY: !secret grocy_api

unit_of_measurement: "days"

platform: rest

name: water plants inside

resource: http://192.168.50.77:9283/api/chores/2

method: GET

value_template: "{{ (((as_timestamp(value_json.next_estimated_execution_time))-as_timestamp(now())) | int /60/1440) | round(0) }}"

json_attributes:

  - last_tracked

  - estimated_execution_time

headers:

  Accept: application/json

  Content-Type: application/json

  GROCY-API-KEY: !secret grocy_api

unit_of_measurement: "days"

and also I see few logs like this , I believe there are just warning and can ignore for now.

2022-04-25 02:18:58 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/integrations/../sensors/Grocy/grocy.yaml contains duplicate key "platform". Check lines 3 and 17

2022-04-25 02:18:58 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/integrations/../sensors/Grocy/grocy.yaml contains duplicate key "name". Check lines 4 and 18

2022-04-25 02:18:58 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/integrations/../sensors/Grocy/grocy.yaml contains duplicate key "resource". Check lines 5 and 19

2022-04-25 02:18:58 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/integrations/../sensors/Grocy/grocy.yaml contains duplicate key "method". Check lines 6 and 20

2022-04-25 02:18:58 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/integrations/../sensors/Grocy/grocy.yaml contains duplicate key "value_template". Check lines 7 and 21

2022-04-25 02:18:58 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/integrations/../sensors/Grocy/grocy.yaml contains duplicate key "json_attributes". Check lines 8 and 22

2022-04-25 02:18:58 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/integrations/../sensors/Grocy/grocy.yaml contains duplicate key "headers". Check lines 11 and 25

2022-04-25 02:18:58 WARNING (SyncWorker_0) [homeassistant.util.yaml.loader] YAML file /config/integrations/../sensors/Grocy/grocy.yaml contains duplicate key "unit_of_measurement". Check lines 15 and 29

so, bottom line it seems either there is some issue with Grocy app with the latest version of OS or I am overlooking something here.

can someone help me on this issue and/or is there an easy alternate solution to achieve to track chores.

1 post - 1 participant

Read full topic

I installed Home Assistant Windows Portable on my PC to support my Insteon Devices. It works great. However, my PC shut down and I had to reinstall and load the devices again. I’m sure that was not right. Does anyone know how to restart the HAWP program when that happens?

1 post - 1 participant

Read full topic

I’m trying to figure out if is it possible to combine some of my automations to simplify things. For example I have an automation that sends a notification when someone arrives to a zone:

alias: arrival home notification
description: ''
trigger:
  - platform: zone
    entity_id: person.ignacio,person.emilie,person.stroller
    zone: zone.home
    event: enter
condition: []
action:
  - service: notify.mobile_app_ignacio_s_phone
    data:
      message: '{{ trigger.to_state.name }} is arriving home'
mode: queued
max: 3

My problem is that I have to create one for notification for entering and one for leaving, and then do the same for each zone. Is there a way to do this more programmatically so I have a single automation for entering, and leaving different zones?

Thanks!

1 post - 1 participant

Read full topic

Logger: homeassistant.helpers.frame
Source: helpers/frame.py:74
First occurred: 12:39:17 PM (10 occurrences)
Last logged: 12:39:24 PM

Detected code that uses str for device registry entry_type. This is deprecated and will stop working in Home Assistant 2022.3, it should be updated to use DeviceEntryType instead. Please report this issue.

I’d love to report it, but to who?

EDIT: never mind, it comes from a custom component grocy and is in their issues list deprecated code warning in HA 2022.3.8 · Issue #197 · custom-components/grocy · GitHub

1 post - 1 participant

Read full topic

I’m a newb to Home Assistant having been cast aside by Insteon! I’ve got all my non Insteon stuff working a treat through Home Assist and wish I’d done this years ago!
Anyway - here’s the issue and wondered if anyone had seen this before.
I have several Insteon Dimmer switches. I can switch them off via the app, and voice cloud, but if I use voice, or the Home Assist UI to bring them on, they show “on” in the UI but do not light up in reality. That said…if I turn them on via the UI by setting a brightness value, or by using voice command: “Set Dining Room to 75%” everything works perfectly.
Is this a known integration issue? Has anyone come up with a work around to have the UI interpret “Turn On” to equate to “Set to 100%”?
Thanks so much!

1 post - 1 participant

Read full topic

hi, I connected Aqara light bulb to zigbee2mqtt however it does shown in to the home assistant

under integration - Mosquitto broker it also doesn’t show x devices y entities.

may I know how to solve this ?

3 posts - 1 participant

Read full topic