Hello dear community,

I have been migrating my Home Assistant (HASS) from my Intel MacBook Pro 2015 (VirtualBox VM) to a Mac Mini M4 (UTM VM) for several days.
Everything worked except for Deconz.
I have already tried many things, including the solutions from here: Move ConBee II to another host and reconfigure Home Assistant deCONZ integration

All devices are also displayed, both in Deconz and in Home Assistant. However, I cannot control the devices.

Here are a few excerpts from the logs:

08:47:24:341 /data/.local/share/deCONZ/config.ini exists and is writeable
08:47:24:341 /data/.local/share/deCONZ/zll.db exists and is writeable
08:47:24:345 COM: use stable device path /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2466425-if00
08:47:24:351 COM: /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2466425-if00 / serialno: DE2466425, ConBee II
08:47:24:351 ZCLDB init file /data/.local/share/deCONZ/zcldb.txt

Error: unable to open database "/data/.local/share/dresden-elektronik/deCONZ/zll.db": unable to open database file

08:47:59:951 SC state change failed: 38:5b:44:ff:fe:4e:a2:e2-01
08:47:59:951 SC state change failed: 38:5b:44:ff:fe:4e:a2:e2-01
08:47:59:951 SC state change failed: 38:5b:44:ff:fe:4e:a2:e2-01
08:47:59:951 SC state change failed: 38:5b:44:ff:fe:4e:a2:e2-01
08:47:59:987 Device protocol version: 0x010B
08:48:00:107 CTRL ANT_CTRL 0x03
08:48:00:161 Device protocol version: 0x010B
08:48:04:952 try to reconnect to network try=4
08:48:04:975 Device protocol version: 0x010B
08:48:05:104 CTRL ANT_CTRL 0x03
08:48:05:159 Device protocol version: 0x010B
08:48:09:948 try to reconnect to network try=5
08:48:09:978 Device protocol version: 0x010B
08:48:10:107 CTRL ANT_CTRL 0x03
08:48:10:159 Device protocol version: 0x010B
08:48:14:950 try to reconnect to network try=6
08:48:14:967 Device protocol version: 0x010B
08:48:15:131 CTRL ANT_CTRL 0x03
08:48:15:183 Device protocol version: 0x010B
08:48:15:952 SC state change failed: bc:02:6e:ff:fe:7c:e6:ba-01
08:48:15:952 SC state change failed: bc:02:6e:ff:fe:7c:e6:ba-01
08:48:15:952 SC state change failed: bc:02:6e:ff:fe:7c:e6:ba-01
08:48:15:952 SC state change failed: bc:02:6e:ff:fe:7c:e6:ba-01

08:50:08:033 0x943469FFFE250B8F seems to be a zombie recv errors 12
08:50:08:521 0x943469FFFE296495 seems to be a zombie recv errors 14

08:49:34:893 max transmit errors for node 0x54EF4410009A3C28, last seen by neighbors 130 s
08:49:34:917 max transmit errors for node 0x385B44FFFE7FA84F, last seen by neighbors 130 s
08:49:34:923 max transmit errors for node 0x54EF4410009A3C28, last seen by neighbors 130 s
08:49:34:942 max transmit errors for node 0x54EF4410009A3C28, last seen by neighbors 130 s
08:49:34:949 reconnect network done
08:49:34:966 max transmit errors for node 0x54EF4410009A3C28, last seen by neighbors 130 s
08:49:34:971 0x7CB03EAA0A0BF524 error APSDE-DATA.confirm: 0xD0 on task
08:49:34:989 max transmit errors for node 0x54EF4410009A3C28, last seen by neighbors 130 s
08:49:35:005 max transmit errors for node 0x54EF4410009A3C28, last seen by neighbors 130 s

I would be very grateful if someone could help me.

1 post - 1 participant

Read full topic

Hello, i am trying to get temperature values from this site Latest Conditions in Kozani
I am giving source this url, and css selector .realtime > div:nth-child(2) > div:nth-child(2) > span:nth-child(1)

I am testing the above in https://try.jsoup.org/ and they work fine.

Whatever css, the sensor created gives always unavailable.
Could someone help me? thank you

3 posts - 2 participants

Read full topic

Hello everyone,
I am trying to integrate the add-on MQTT Siemens S7 Connector and fail to load the configuration.
I have already tried the configuration in the following folders:

/homeassistant/addon_configs/xxxxxxxx_mqtt-s7-connector/config.yaml
/homeassistant/config.yaml
/homeassistant/config_files/config.yaml
/homeassistant/configfiles/config.yaml
/homeassistant/config/config.yaml

I always get an error that the configuration is not found.

What am I doing wrong here?

Please find attached the complete error message.

Add-on: MQTT Siemens S7 Connector

MQTT Siemens S7 connector to integrate Siemens PLC’s with Home Assistant

Add-on version: 1.0.8

You are running the latest version of this add-on.

System: Home Assistant OS 14.2 (amd64 / generic-x86-64)

Home Assistant Core: 2025.3.0

Home Assistant Supervisor: 2025.03.2

s6-rc: info: service base-addon-banner successfully started

s6-rc: info: service fix-attrs: starting

s6-rc: info: service base-addon-log-level: starting

s6-rc: info: service fix-attrs successfully started

Log level is set to WARNING

s6-rc: info: service base-addon-log-level successfully started

s6-rc: info: service legacy-cont-init: starting

s6-rc: info: service legacy-cont-init successfully started

s6-rc: info: service init: starting

s6-rc: info: service init successfully started

s6-rc: info: service legacy-services: starting

s6-rc: info: service legacy-services successfully started

s7-mqtt-connector@1.0.4 start

node index.js --addonversion 1.0.8 --config /config/config.yaml --loglevel=4

INIT ## log level is set to: 4

2025-3-8 9:13:57 ## ERROR ## Config file ‘/config/config.yaml’ not found

/usr/src/mqtt-s7-connector/service_functions.js:57

throw new Error(msg);

^

Error: Config file ‘/config/config.yaml’ not found

at Object.error (/usr/src/mqtt-s7-connector/service_functions.js:57:9)

at Object.config (/usr/src/mqtt-s7-connector/config_handler.js:40:20)

at Object. (/usr/src/mqtt-s7-connector/index.js:12:31)

at Module._compile (node:internal/modules/cjs/loader:1550:14)

at Object…js (node:internal/modules/cjs/loader:1702:10)

at Module.load (node:internal/modules/cjs/loader:1307:32)

at Function._load (node:internal/modules/cjs/loader:1121:12)

at TracingChannel.traceSync (node:diagnostics_channel:322:14)

at wrapModuleLoad (node:internal/modules/cjs/loader:219:24)

at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)

Node.js v23.2.0

s6-rc: info: service legacy-services: stopping

s6-rc: info: service legacy-services successfully stopped

s6-rc: info: service init: stopping

s6-rc: info: service mqtt-s7-connector: stopping

s6-rc: info: service init successfully stopped

s6-rc: info: service legacy-cont-init: stopping

s6-rc: info: service mqtt-s7-connector successfully stopped

s6-rc: info: service legacy-cont-init successfully stopped

s6-rc: info: service fix-attrs: stopping

s6-rc: info: service base-addon-log-level: stopping

s6-rc: info: service fix-attrs successfully stopped

s6-rc: info: service base-addon-log-level successfully stopped

s6-rc: info: service base-addon-banner: stopping

s6-rc: info: service base-addon-banner successfully stopped

s6-rc: info: service s6rc-oneshot-runner: stopping

s6-rc: info: service s6rc-oneshot-runner successfully stopped

1 post - 1 participant

Read full topic

Hi, is there any way to send media/recording files to OneDrive?

2 posts - 2 participants

Read full topic

Hi. This is my first post.

I have bought a 6 gang Moes switch:

https://a.aliexpress.com/_EGmgCWo

I want each switch to work as a scene. HA only allows 3 of the 6 switches to be scene switches?

So I then bought a Moes ZigBee Gateway. Through the Moes app, I can change all the switches to scene.

When the switch is now connected to the Moes gateway. I cannot connect to it using HA.

How can I get all 6 switches to be scene switches using HA?

Please help. Thanks.

1 post - 1 participant

Read full topic

Hi,

I am trying to run ollama (deepseek r1 14b) on my workstation and try to integrate it with home assistant which is hosted on a mini PC.

I have managed to create the voice assistant pipeline, but I am getting error “Unexpected error during intent recognition” every time I am trying to access the deepseek model.

Am I missing any settings setup? My goal is to use it to control my smart home and for local simple queries like (tell me a recepie of X, who was X, what is the weather like on Monday in X, etc.). I also have a voice assistant PE, but first I want to make it work from the browser/app.

Hope you can help.

Thank you!

1 post - 1 participant

Read full topic

Chaps; I had this working in configuration.yaml
and it created a sensor for me

command_line:
   - sensor:
       name: plex file history
       command: 'cat /config/bruce/file/plex.txt'

I’m trying to move this to sensor.yaml but I can’t get either the formatting correct or the syntax as it won’t create a sensor for me.

In configuration.yaml I have include

sensor: !include sensor.yaml

And my sensor.yaml is

- platform: command_line
  sensors:
    name: plex file history
    command: 'cat /config/bruce/file/plex.txt'

It passes Dev Tools / Check configuration with no errors but just doesn’t create the sensor
Please help, believe me I’ve trawled the forums but just can’t get this working.

1 post - 1 participant

Read full topic

Hello there.
I Know i Know … again such a topic…

We have a Dashboard where we would like to integrate Home assistent as a iframe.

Sounds Easy, right ? Rigth ? RIGHT ? – Not at all. The Issuse is, (beside the really overkomplicatet “enter some cryptic config in yaml whrere you enter username and ip blah blah”) - the Primary dashboard are allowing only https connections and the PI runns in kiosk “dont save cookie” mode.

Well other software fixes this issue with “add this 128 char string to your url and be happy”. that would be very easy and simple- Especialy when you have a number of potentialy Dashboards. but i can’t find any parameter for url or accesstoken

To be detailed. we use divera247 (it is a Alarm-app for Firefighters and other blue light organisations ) and potentialy every our persons could open this site from everywhere on this planet.

so, we need a possible way to:

• Show the Dashbard with a predifine api token or login token.
• Save the “Darkmode” and Dashboard in url with other configs
• hide other options for this user. (like map or other tabs9
• Site needs to be accessed via https/nabucasa

is there an option in home assistent ?

have a wonderful day

Thomas

1 post - 1 participant

Read full topic

Voice Assistant PE has been up and running for a couple of weeks now, without issues. This morning I’ve found that it’s not working (I was looking in the logs for something else), and I can’t find what the issue is. Device isn’t pingable, I’ve tried restarting it, resetting the integration but to no avail.

Log says this:
2025-03-08 10:36:20.623 WARNING (MainThread) [aioesphomeapi.connection] home-assistant-voice-092d71 @ 192.168.1.215: Connection error occurred: home-assistant-voice-092d71 @ 192.168.1.215: EOF received 2025-03-08 10:36:22.958 WARNING (MainThread) [homeassistant.components.esphome.manager] Home Assistant Voice 092d71: [W][micro_wake_word:375]: Wake word dection is already running

Prevously I was getting warnings about connection errors:

2025-03-08 09:08:20.642 WARNING (MainThread) [aioesphomeapi.connection] home-assistant-voice-092d71 @ 192.168.1.215: Connection error occurred: home-assistant-voice-092d71 @ 192.168.1.215: EOF received

Any ideas? Is it factory reset time?

1 post - 1 participant

Read full topic

Hey everyone, I’m looking for some assistance with a script. I have scripts that capture the current state of lights using scene.create then at the end of the script it fires that scene to restore the state of the lights and lastly deletes the scene it created. The issue I’m facing is if the lights were originally off in the captured state and say the script involved the flashing of lights. Home assistant will often see these lights as still in an on state, even after the restore scene has fired to turn them back off.

Has anyone else ran into this and found a solution?

1 post - 1 participant

Read full topic

Hello,

I’m new here and trying to setup my remote connection to my Home Assistant.
I have a domain name, A record has been setup in Cloudflare to my public IP.

Portforwarding on my router has been setup.
I could reach at some point my home assistant by public IP.
But the connection isn’t secure and i don’t want that.

I’m trying to alter my configuration in my HA.

# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

http:
  server_port: 8443
  use_x_forwarded_for: true

  trusted_proxies:
  
- 172.67.219.0/24 
- 104.21.86.0/24
- 188.114.97.0/24

Also in error log:

    )
homeassistant.exceptions.HomeAssistantError: The system cannot restart because the configuration is not valid: Invalid config for 'http' at configuration.yaml, line 13: some but not all values in the same group of inclusion 'proxy' 'http-><proxy>', got None

Any help is greatly appreciated!

Thanks,
Substar

1 post - 1 participant

Read full topic

Hi all,

I am new to home assist and have been scratching my head for the past few hours trying to figure out why this damn automation just doesn’t trigger automatically but when I force the temp sensors to change temps up or down the automation works perfectly. The same can’t be said about the organic automation, it doesn’t work most of the time. Here is my YAML config

alias: Turn on heater
description: ""
triggers:
  - alias: Digital Temp Sensor is below 70F
    type: temperature
    device_id: 4e0df00917394e026eed7c348edde5da
    entity_id: 0b0ff66ce72a91ada7bde2264d302d75
    domain: sensor
    trigger: device
    below: 70
    above: 50
  - alias: Wall Temp Sensor is below 68F
    type: temperature
    device_id: 7d2022e49e55e9a667d83d8fd0202cae
    entity_id: 6ceeed06f33d30c66bace280194359d5
    domain: sensor
    trigger: device
    below: 68
    above: 50
  - trigger: numeric_state
    entity_id:
      - sensor.temp_sensor_temperature
    below: 68
    above: 50
  - trigger: numeric_state
    entity_id:
      - sensor.digital_temp_sensor_temperature
    below: 70
    above: 50
conditions:
  - condition: time
    after: "04:30:00"
    before: "20:30:00"
actions:
  - type: turn_on
    device_id: da0a85a389b7bd3c2d4b62c8cb981a70
    entity_id: 2d750d8175ad3f0ba6642e58f888eb44
    domain: switch
  - alias: Wait for temp to change
    wait_for_trigger:
      - alias: Digital Temp sensor is above 70F
        type: temperature
        device_id: 4e0df00917394e026eed7c348edde5da
        entity_id: 0b0ff66ce72a91ada7bde2264d302d75
        domain: sensor
        trigger: device
        above: 70
      - alias: Wall Temp sensor is above 69F
        type: temperature
        device_id: 7d2022e49e55e9a667d83d8fd0202cae
        entity_id: 6ceeed06f33d30c66bace280194359d5
        domain: sensor
        trigger: device
        above: 69
  - type: turn_off
    device_id: da0a85a389b7bd3c2d4b62c8cb981a70
    entity_id: 2d750d8175ad3f0ba6642e58f888eb44
    domain: switch
mode: single

Thank you for all the help!

1 post - 1 participant

Read full topic

How can I track bluetooth devices that I can see at Advertisement Monitor page? I cannot see any of those devices in known_devices.yaml file.
bluetooth: configuration seam to expect real bth adapter. Is that using proxy devices?
Any suggestions?

1 post - 1 participant

Read full topic

Hello everyone, I’d love to be able to recreate (or find a template somewhere) of this mushroom based dashboard: https://community-assets.home-assistant.io/original/4X/9/4/7/947695cc6988303f25f8b0186dec0b8363c10a67.jpeg

What I don’t understand is how they made sections not follow the ZGrid pattern but rather a Z Mansonry one. Does anyone know how the default arrangement for sections can be changed? Thank you very much!

1 post - 1 participant

Read full topic

Hi,

I’ve read the following threads:

• Voice PE button press triggers Easter egg
• Trigger an automation on an event with no state change (Voice Assistant PE button)

However, I still can’t figure out how to create an automation trigger for the Voice PE button single/double or triple press. I can see the button press in the “Scene” section, but I’m not sure what changes to make or where to make them. If I need to edit a YAML file, could someone point me in the right direction?

I’m still new to Home Assistant, so any guidance would be really helpful. Thank you!

Firmware: 25.2.1 (ESPHome 2025.2.0)

1 post - 1 participant

Read full topic

Issue
My IKEA Tradfri bulbs are no longer showing color_temp in HA (but can still control)

HA: 2025.3.1
Z2MQTT: 2.1.3
IKEA Bulb Firmware: 3.0.23

I can see the color temp within Zigbee2mqtt

But in Home Assistant, its all reported as null

I can still control the color temperature via HA light card, but, once you navigate away and back again, there is no value on the slider

I’ve restarted both HA and Z2M. Logs show payload of color temp being sent within zigbee2mqtt (makes sense as I can control it). Not sure of what other logs and where I can be looking to further troubleshoot this issue. Thank you

1 post - 1 participant

Read full topic

The below automation, built in the UI, but in YAML edit mode, produces an error. The error is caused because the value of the lightset variable is empty when the automation attempts to call script.lightset_by_label_on. So this implies to me that the line:

lightset: "{{ trigger_label_map[s9_lightset] }}" is improperly configured.

Can someone help me figure this out? I’ve done a lot of searching about and this seems to be the syntax to use from what I can see.

AUTOMATION ====

alias: lightset | State Changed
description: ""
triggers:
  - trigger: state
    entity_id:
      - input_select.lightset_lset_app_test_set_state
    id: s9_lightset
conditions: []
actions:
  - variables:
      trigger_label_map:
        s9_lightset: Light Set - Lset App Test Light Set
        s1_lightset: Light Set - Day Dim - Kitchen
        s2_lightset: Light Set - Day Dim
      lightset: "{{ trigger_label_map[trigger.id] }}"
  - alias: Choose Action Using State
    choose:
      - conditions:
          - condition: template
            value_template: "{{ trigger.to_state.state == 'In Process - ON'}}"
            alias: IF State is In Process - On
        sequence:
          - alias: Turn on the Light Set
            action: script.lightset_by_lable_on
            metadata: {}
            data:
              lightset_label: "{{ lightset }}"
mode: single

ERROR ====

Executed: March 8, 2025 at 8:39:01 AM
Error: UndefinedError: 'dict object' has no attribute ''
Result:

params:
  domain: script
  service: lightset_by_label_on
  service_data:
    lightset_label: ''
  target: {}
running_script: true

child_id:
  domain: script
  item_id: lightset_by_label_on
  run_id: 53961bf797e8873358428f15c7a1b14a

CONTEXT ====

I am building a mini ‘application’ to manage several different sets of lights that I associate to three different ambient light sensors. A key function of this app is to sense when it is dim during the day, for example if it’s cloudy out the room will be dim, and control it’s associated light-set accordingly. I define each light set using Labels (easy way to add/remove lights from the different light sets). I have a reusable script that takes such a label as input and turns on all the lights in that light set (this script is well tested and works fine) - that’s the script the offending automation is trying to call.

The above automation is a starting point skeleton for what I intend to be a router or controller - it will trigger anytime the state of any of the light sets changes. Based on the state-change it will call an appropriate script to take the appropriate action. In the above I am at present simply trying to sense and call the ‘light set on’ action for my test light set.

The trigger_label_map: variable is meant to lookup the light set label associated to the helper that holds the given light set’s current state - i.e., those helpers, one for each light set, are the triggers for this automation.

No doubt there are other ways to do this and avoid the error I’m getting - but, fundamentally, why is the variable assignment failing?

1 post - 1 participant

Read full topic

Hello everyone,
I need your help configuring my Solax PV system on Home Assistant.

For now, while waiting for my Raspberry Pi 4 to arrive, I have installed Home Assistant on a Docker machine for testing purposes.

I’ve been trying to configure the Solax photovoltaic system via SolaX Inverter Modbus since this morning, without success. I also tried the SolaX Power integration, but I still can’t connect.

I have assigned a fixed IP to my inverter (192.168.1.104), and I can login via browser using my username and password.
My inverter model is X1-Hybrid-G4, and the WIFI dongle 3.0 is running firmware version 3.019.01.
I also have two batteries, one master and one slave.

The Modbus address of the inverter is 1, as verified in the advanced settings of the Solax application.
This is the configuration I’m using for SolaX Inverter Modbus (Should I select parallel Mode Master Slave)? :

But when I click Send, the configuration remain in initialization and it says configuration failed.

Looking at the logs this could be interesting:

2025-03-08 13:41:29.027 WARNING (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX: reading serial number from address 0x1a10 failed; other address may succeed
2025-03-08 13:41:29.027 ERROR (MainThread) [custom_components.solax_modbus.plugin_solax] SolaX: cannot find any serial number(s)
2025-03-08 13:41:29.028 ERROR (MainThread) [custom_components.solax_modbus.plugin_solax] unrecognized inverter type - serial number : unknown
2025-03-08 13:41:39.031 INFO (MainThread) [custom_components.solax_modbus] Inverter is not connected, trying to connect
2025-03-08 13:41:39.034 DEBUG (MainThread) [custom_components.solax_modbus] Trying to connect to Inverter at 192.168.1.104:502

Could someone help me?
Thanks

1 post - 1 participant

Read full topic

Hey there,

I am using the custom TP Link Deco integration and I was able to set it up correctly. The thing is that values that shows as Speed up and Speed down are much lower than what shows the Tp Link Deco Up.

Already checked measurements units. I am also looking at the main deco device.

What am I doing wrong here?

1 post - 1 participant

Read full topic

I changed my raspberry pi 3b+ by an identical one and moved SD and dongle to the new one, just to see if its possible to replace a pi in case of failure and have everything working without any worries.

The raspberry pi boots up, docker starts and launches HA, I can connect through the local IP (which changed because the router assigns IPs via the mac address), but I could not connect via Home Assistant Cloud.

I had to go there, turn off remote access and turn it on again.

Could this be fixed the next time? It would be much better if a raspberry pi could just be replaced without any worries

1 post - 1 participant

Read full topic