I’ve been thinking about whether I want to start using labels by integrating them in automations.

I currently have a list of customized battery entities, where I add the type of battery as an attribute and an automation that sends me a notification, if any of those entities goes low. This also means that I have to edit both places for every new/removed battery device.

This is where labels or groups could come in and building the automation in a way that doesn’t require changes for new/removed devices. Same goes for stuff like lights etc. basically anything that would be grouped and used in an automation

How do you handle stuff like this? Do you use labels/groups or something else?

1 post - 1 participant

Read full topic

I have an SLZB-06 as my Zigbee coordinator, and HA and my Zigbee network are working fine. There are just a couple of things I’m curious about.

The SLZB-06 is running firmware 2.5.6 and I can see it with the SLZB-06 integration, as well as via its web interface. HA is up to date.

First, when I look at the web interface, the Mode selection looks like this:

Now, it’s working as the Coordinator, so why does it not show that turned on? Is it the case that since its default role is Coordinator, I didn’t need to turn it on here? Would it hurt anything if I did?

Second, in the integrations Configuration section, it shows the Zigbee firmware as unknown:

Is that normal? Would it appear if I turned the Coordinator switch on?

Again, everything is working so I don’t need to do anything, and I hesitate to make a change just to see what happens, as I don’t want to mess something up.

If anyone can enlighten me I’d appreciate it.

1 post - 1 participant

Read full topic

This binary sensor stopped working (judging by the developer tool) several months ago for some unknown reason. I tried to revive it by restarting HA’s docker container. It didn’t help. Then I removed the sensor and restarted the container again hoping it will be recreated upon reboot. It didn’t happen - how can I restore this binary sensor now (and preferably make it function)?

1 post - 1 participant

Read full topic

Everything has been working. Reboots haven’t helped. Now I can’t add any new devices. When I hit add device, I get

Add a Z-Wave device

The device could not be added.

Config entry 28e5d68105cce2e32d6e86adad45b8d1 not loaded

1 post - 1 participant

Read full topic

Hello!
I got this pesky problem - after an update in mid-2024, my Zigbee setup started experiencing serious problems. Most Zigbee devices stopped working, except for temperature sensors. I initially tried troubleshooting without success. The issues escalated to the point where I had to delete simple automations, like kitchen light control triggered by motion, because it completely stopped working overnight, and my family became very frustrated.

Months later, I attempted to reintroduce simple automation for hallway lights with a Zigbee button. It worked for a while till someday ago (2-3)
Now, I’m back to square one: Zigbee devices, like Sonoff buttons, enter an “unknown” state immediately after a reset. I see events fired, but right after, the state transitions to “identify button unknown.” The problem is consistent across two Sonoff buttons. I see the battery status displayed as 100%, but nothing else works.

My last environment: System: Raspberry Pi 3B, Core: 2024.12.3, Supervisor: 2024.11.4, Operating System: 14.0, User Interface: 20241127.8. Zigbee integration used Sonoff Zigbee 3.0 USB Dongle Plus

I have several attempts to reset a Sonoff Zigbee button but they enter “unknown state” immediately after reset and remain unusable. (also my sonoff power switch to fire light in my living room)
I’ve enabled debug logging, but I find it hard to interpret the results. I tested the same scenario with two separate Sonoff buttons, and both exhibit identical behavior.

The system ran stable before mid-2024. Some Zigbee devices like temperature sensors still work. Persistent issues make automations unreliable and unusable.

Please help, i am really missing gold ages of working things… (i am just a cm’s before trash all step…)

My core is 2024.12.3 and i am running Home Assistant OS

1 post - 1 participant

Read full topic

I have an ESPHOME device that sends Lat/Long information to my Home Assistant every few seconds.

What is the next step I need to undertake, to allow that information to display as an icon on the Map Card?

I see the entity “zone.home” (which does display) as a state and 8 attributes. However, my Lat & long entities as a much simpler structure of just state & 2 attributes.

How do I turn the two lat/long sensors into a zone?

Regards, Martin

1 post - 1 participant

Read full topic

I’m trying to add my first Matter device to HA (docker)

After scanning the QR-code the new Matter device was found and successfully connected.

But adding the Matter device to HA failed.

Does anyone have any idea what could be going wrong? Are there any log files that could be analyzed?

1 post - 1 participant

Read full topic

I have designed a control system for my in floor heat using some ESP sensors and a bunch of other components. It has worked flawlessly for about a year. I did some updates on home assistant yesterday and and woke up with the shop sitting at 5 degrees centigrade this morning. The temperature in the building had been steadily dropping for the last 24 + hours. I have a number of temperature sensors monitoring the various loops and outside temperature. based on the outdoor temperature I vary the cut in temperature for the boiler.
When below the set temperature I have an automation trigger the boiler, the boiler runs for 30 minutes, then the boiler shuts off and I continue circulation the glycol in the floor for 10 minutes then the pump turns off. If the boiler output line temperature is below the set point this should trigger the boiler to turn back on and repeat this cycle until the boiler output line stays above the set point… the set point is currently 15.1 degrees centigrade. by the time the last cycle ended the return line was at 11 degrees centigrade. for some reason the event will not trigger. I suspect it is due to the fact that the temperature is below the set point. All of the rest of the automations seem to be working as designed.
for the automation i have it built as follows.

• When ESP Boiler Monitor Sensor 1 - Boiler output is below input_number.start_temperature and if boiler run timer is idle and if the boiler idle timer is idle (this is where the pump continues circulating) then do Switch ‘Turn on’ on ESP Boiler Monitor Boiler switch.

2 posts - 1 participant

Read full topic

I installed a power socket, it is node11 on my z-wave network.
Ican ping it, all tests good normal, but from the devices interface switch, i cannot have it switch on our off

1 post - 1 participant

Read full topic

I am trying to assure a Sony Bravia TV is using its speakers rather than audio system prior to starting an automation action. The REST example came from: https://github.com/home-assistant/core/issues/88532 which was used to create a shell command that was added to configuration.yaml as:

#Exposes shell_command,sonytv_speakers shell_command: sonytv_speakers: curl -X POST \ http://xxx.xx.xx.xxx/sony/audio \ -H 'cache-control:no-cache' \ -H 'x-auth-psk:xxxx' \ -d '{"method":"setSoundSettings", "id":5, "params":[{"settings":[{"value":"speaker", "target":"outputTerminal"}]}], "version":"1.1"}'

The command works when entered directly in the terminal and there are no errors in the configuration.yaml file. (“xxxxxxxx” used in lieu of actual IP and PSK.)

However when envoked as a service call in an automation, for example:

action: shell_command.sonytv_speakers data: {}

nothing happens and the log error is:

``Logger: homeassistant.components.shell_command
Source: /usr/src/homeassistant/homeassistant/components/shell_command/init.py:129
integration: Shell Command (documentation, issues)
First occurred: 5:30:04 PM (1 occurrences)
Last logged: 5:30:04 PM

Error running command: curl -X POST \ http://xxx.xx.xx.xxx/sony/audio \ -H 'cache-control:no-cache' \ -H 'x-auth-psk:xxxx' \ -d '{"method":"setSoundSettings", "id":5, "params":[{"settings":[{"value":"speaker", "target":"outputTerminal"}]}], "version":"1.1"}', return code: 3
NoneType: None``

I would appreciate suggestions to make the automation work as planned.

3 posts - 3 participants

Read full topic

I am not an expert at YAML and lots of examples I query don’t tell me whether their code is a sensor or an automation or a script so my querys have not shown me a solution.

I just want to run a script that tells me how long all the switches and lights (that are currently on) have been on for.

I did set up the History_Stats but that ends up giving me a bar chart and how long a light has been on every day for the past week.

What I want to know is if a light has been running for hours, then I can track down problems. I will just run the script and get a notification on my iphone what lights are currently on and how long they have been on.

Can anyone assist me?

2 posts - 2 participants

Read full topic

I have the following: action in my blueprint:

variables:
  iDevs: !input notify_device
...
sequence:
  - alias: All Devs
    repeat:
      for_each: "{{ iDevs }}"
      sequence:
        - action: notify.mobile_app_sm_s918u
          data:
            title: "{{ title }}"
            message: "{{ message }}"
            data: 
              tts_text: "{{iPrefix}}{{data.tts_text}}"

I would like to determine the action based on the templated name repeat.item instead of the hardcoded “notify.mobile_app_sm_s918u”

2 posts - 2 participants

Read full topic

I have a helper number configured as min. value 0, max. value 3, step size 1. What determines the initial value?

I want to have an automation use the current value of this number to control the action taken, then increment the value (or wrap around to 0 if the current value has reached the maximum of 3 already). (So no user input nor direct control of the number.)

The automation is triggered by a button press, and then the number value is what controls the specific actions.

Is it possible to use a helper number this way, and if so how do I build that automation in the GUI editor exactly?

1 post - 1 participant

Read full topic

Hello,

I have some automations on many cameras. But some time i have to remove some camera from the automation.

There´s a way to create one helper that i can select one or many from a lista ? this list can be based on a entity filter, if so.

and in the automation code i can do this

"if “xxxx” in “helpder.myhelper” then …

Thanks

1 post - 1 participant

Read full topic

I have ChatGPT set up through the OpenAI integration, and I have Home Assistant assist set up as well. Both work fine. How can I store the responses? I want to display the text on my dashboard. There doesn’t appear to be any attributes from the conversation entities that would be helpful. I know about input_text, but I don’t know how to pass the data to it (plus the character limit is only 255, which isn’t ideal).

1 post - 1 participant

Read full topic

Hi all

I have a REST integration which calls Cloudflare’s GraphQL endpoint to get the number of requests to a specific zone (website) and the number of requests blocked.
My sensors however always return unknown.

Here are the tests I performed:

• Replaced all the !secret values with their actual hard coded values
• Replaced all Jinja templating stuff like the zoneTag or datetime_geq with actual hard coded values
• Tested this in Postman and Altair and both got a response
• Verified the JSON response in the Template section under Development tools to ensure it is correct, and all good.

rest:  
  - resource: !secret graphql_cloudflare_url
    scan_interval: 300
    method: POST
    headers:
      Content-Type: "application/json"
      Authorization: !secret graphql_cloudflare_bearer
    payload: >
      {
        "query": "{
          viewer {
            zones(filter: { zoneTag: \"{{ states('sensor.zone_tag') }}\" }) {
              httpRequestsAdaptiveGroups(
                limit: 10
                filter: { datetime_geq: \"{{ (now() - timedelta(hours=23)).isoformat() }}\" }
              ) {
                count
                dimensions {
                  securityAction
                }
              }
            }
          }
        }"
      }
    sensor:
      - name: "Normal Requests Count"
        value_template: >
          {{
            value_json['data']['viewer']['zones'][0]['httpRequestsAdaptiveGroups']
            | selectattr('dimensions.securityAction', 'equalto', 'unknown')
            | map(attribute='count') | sum
          }}
        unit_of_measurement: "requests"
      - name: "Blocked Requests Count"
        value_template: >
          {{
            value_json['data']['viewer']['zones'][0]['httpRequestsAdaptiveGroups']
            | selectattr('dimensions.securityAction', 'equalto', 'block')
            | map(attribute='count') | sum
          }}
        unit_of_measurement: "requests"

This is what the response looks like in Postman and Altair:
(The “unknown” securityAction in the response just means it was not blocked by the Cloudflare WAF)

{
  "data": {
    "viewer": {
      "zones": [
        {
          "httpRequestsAdaptiveGroups": [
            {
              "count": 1452,
              "dimensions": {
                "securityAction": "unknown"
              }
            },
            {
              "count": 44,
              "dimensions": {
                "securityAction": "block"
              }
            }
          ]
        }
      ]
    }
  },
  "errors": null
}

I have absolutely no idea why the values would always return “unknown”… Any assistance will be greatly appreciated.

1 post - 1 participant

Read full topic

i have bought my third zigbee ethernet coordinator
ZB-GW03-V1.4,
https://www.aliexpress.com/item/1005005959454155.html

i have 2 same ones which i have used successfully until today with my HA
I managed to configure this 3rd Z2M instance and it worked for 1 full day (i did have issues with at first - see post Help! zigbee ethernet g/w wont boot after wrong configuration ) but it was solved

then it disappeared from my LAN network, cant ping it and it wont show in the router DHCP client lists
i reset it to factory and tried again - it just wont show on my router

the red/green leds keeps blinking (cant upload video here)

i dont see its default Wifi network as well

any ideas?

1 post - 1 participant

Read full topic

So I have been struggling and almost lost all my configuration, fortunately I was able to restore backup which healed my network, however I’m still not able to migrate to SkyConnect-stick.

Here are the details:
I first tried the migrate radio without doing much research which involves some additional things to consider since I’m running Home Assistant in a docker container. This means that I have to plug both the new radio and the old radio in, before restarting the container.

This was successfull, old radio is /dev/ttyACM0 and the new Skyconnect is /dev/ttyUSB

I can see skyconnect as a newly found device discovered. This leads me to start migration. Beforehand I take a backup of HASS aswell as a manual backup of the radio. Then proceeding with the setup.

The migration takes a while and it says it is successfull. However nothing works, and I thought something was wrong because the new skyconnect stick still shows up as a new device under devices and the old zigbee-radio still says to be “Conbee 2”, however the network details have changed from deconz to skyconnect radio aswell as dev/ttyUSB0

I waited for some time but nothing reconnected. I thought, maybe the issue is that I didnt unplug the old radio according to the migrate radio wizard, however I took this litterally as it says “you can unplug your old radio now i you want to…” or something similiar.

So this led me down another rabbit hole where I tried to add a device to this reconfigured zha radio (skyconnect) and i was able to add two devices, this I thought was strange and I thought that maybe I was in deep trouble, my expectations was that I was not able to add any devices at all. Once added they were able to be controlled, but all other devices was still not functioning.

Long story short, before trying this again, I want to make sure I’m not doing anything wrong since I am a newbie, and hindsight, I should have installed HASS OS to not struggle with USB-devices, but whatever, I’m still learning and I think it is fun.

If someone has any recommendations other than the two other topics with regards to this would be appreciated, I believe this one is quite different as my HA is running in Docker, I might be wrong.

Best regards

1 post - 1 participant

Read full topic

I’m having trouble connecting a presence sensor to my HA server. I’ve tried both a Aqara FP2 and Everything One. Neither is visible when I try to add devices. I may have two different problems but I’m not sure.

I have a IoT guest network on my ASUS router with several devices connected including two ESP devices (two AirGradient sensors, two tablets as dashboards). I’m not having trouble with these devices. Always connecting to the network and always connected to HA. I’m trying to connect these two presence sensors to the IoT network and then to HA.

The FP2 is connected to the IoT network. HA does not see it. I can see it with the Aqara app on my iPhone (which is not on the subnet but on the main home network). This device does not appear on the Apple Homekit though an Aqara Hub does (it’s wired to the main network).

The Everything One appears on HA but only for a couple of hours then disappears. It only works when connected to my main PC for configuration (I tell it to connect to the IoT network and give it the password). It seems to connect because I see it on HA. If I move it to its intended permanent location, it’s lost on HA. If I leave it connected to the PC, it will become unavailable on HA in a few hours. Cycling the power has not effect. Only reconfiguring it using the website gets it to reconnect to HA. When connecting to HA, I see it connected to my IoT network.

I’m at a loss as to figure out the problems with these two sensors. Any suggestions?

1 post - 1 participant

Read full topic

Hello everyone,
lately, but I don’t know exactly from which version, telegram groups that have ID higher than “-100xxxxxx” do not work.
I have two groups, one with ID “-100xxxxxx” and another with ID “-90xxxxxx”.
The one with ID -90xxxxxx has stopped working in the sense that I no longer receive notifications.
While if I configure in yaml the group that has ID “-100xxxxxx” the notifications arrive correctly in that group.
Are there problems with IDs other than -100?
Thanks for the support

1 post - 1 participant

Read full topic