Quantcast
Channel: Configuration - Home Assistant Community
Viewing all 106310 articles
Browse latest View live

General question about configuration.yaml

$
0
0

Dear Forum,

I think, I do have a general understanding-issue of how the “configuration.yaml” has to look like:

I already have added some sensors, which are working fine. But now I am trying to implement SNMP and am struggeling

my file looks like this:

# 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

template:
  - sensor:
    - name: "Verlustleistung_WR"
      unique_id: "VerlustleistungWR"
      unit_of_measurement: 'W'
      state_class: "measurement"
      device_class: power
      state: >
          {{ (float(states("sensor.solax_pv_power_total")))
           + (float(states("sensor.solax_grid_import")))
           - (float(states("sensor.solax_house_load"))) 
           - (float(states("sensor.solax_battery_power_charge"))) }}
               
########### other Sensors are implemented here #########

       - name: "Niro_rekuperierte_Energie_total_kwh"
         unique_id: "NiroRekuperierteEnergieTotalKwh"
         unit_of_measurement: 'kWh'
         state_class: "measurement"
         device_class: power
         state: >
         {{ ((float(states("sensor.niro_total_energy_regeneration"))) /1000)  | float | round(2) }} 

Now I am trying to implement the SNMP like this:

  - platform: snmp
       name: "WuT Web Thermometer"
       host: "192.168.2.152"
       community: public
       baseoid: .1.3.6.1.4.1.5040.1.2.8.1.3.1.1.1
       unit_of_measurement: '°C'
       scan_interval: "60" 
       device_class: 'temperature'
       state_class: 'measurement'

But WHERE in the file do I have to place this? Because I am always getting the error

I have no Idea, how to fix this

Thanks for any help
Holger

3 posts - 2 participants

Read full topic


Fast modbus sensor for automations/Node-RED and slow for statistics, how to do it?

$
0
0

Hi,
What is the best way to achieve this?
I need a fast read of modbus values 1s for automations/Node-RED to react reasonably fast
But I do not want to display or store this amount of history. I want to have about 5- 10 seconds of interval for the GUI and History.
Should I create two sensors or is there a better way?

1 post - 1 participant

Read full topic

PROBLEMI smlight SLZB-06M con 2mqtt

$
0
0

buongiorno a tutti sono nuovo in HA e spero di scrivere nel posto corretto.
ho appena installato un’antenna smlight SLZB-06M ma continua a darmi questi errore negli script. Ho provato di tutto seguendo vari tutorial ma niente.
Aiuto…GRAZIE

‘’‘[18:34:11] INFO: Preparing to start…
[18:34:11] INFO: Socat not enabled
[18:34:12] INFO: Starting Zigbee2MQTT…
Starting Zigbee2MQTT without watchdog.
[2025-03-02 18:34:14] info: z2m: Logging to console, file (filename: log.log)
[2025-03-02 18:34:14] info: z2m: Starting Zigbee2MQTT version 2.1.3 (commit #unknown)
[2025-03-02 18:34:14] info: z2m: Starting zigbee-herdsman (3.2.7)
[2025-03-02 18:34:15] error: z2m: Error while starting zigbee-herdsman
[2025-03-02 18:34:15] error: z2m: Failed to start zigbee-herdsman
[2025-03-02 18:34:15] error: z2m: Check Zigbee2MQTT fails to start/crashes runtime | Zigbee2MQTT for possible solutions
[2025-03-02 18:34:15] error: z2m: Exiting…
[2025-03-02 18:34:15] error: z2m: Error: USB adapter discovery error (No valid USB adapter found). Specify valid ‘adapter’ and ‘port’ in your configuration.
at discoverAdapter (/app/node_modules/.pnpm/zigbee-herdsman@3.2.7/node_modules/zigbee-herdsman/src/adapter/adapterDiscovery.ts:523:15)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at Function.create (/app/node_modules/.pnpm/zigbee-herdsman@3.2.7/node_modules/zigbee-herdsman/src/adapter/adapter.ts:68:33)
at Controller.start (/app/node_modules/.pnpm/zigbee-herdsman@3.2.7/node_modules/zigbee-herdsman/src/controller/controller.ts:132:24)
at Zigbee.start (/app/lib/zigbee.ts:69:27)
at Controller.start (/app/lib/controller.ts:142:13)
at start (/app/index.js:161:5)
[2025-03-02 18:34:15] error: z2m: If this happens after updating to Zigbee2MQTT 2.0.0, see Z2M 2.0.0: `USB adapter discovery error (No valid USB adapter found)` · Koenkk/zigbee2mqtt · Discussion #24364 · GitHub ‘’’

3 posts - 2 participants

Read full topic

Architecture guidance

$
0
0

Hi folks,

I am quickly finding that what I want to do in HA needs the use of code. For context about me, I am not a programmer by profession, but I have for instance created a custom types in PowerShell exposing the native C interface of a Windows dll so that I can call those functions. Advapi32.dl LsaEnumerateAccountsWithUserRight for instance. But that is absolutely the limit of the sort of thing I am capable of. Mostly I have written fairly small self-contained scripts for work [1000 lines is normal] in PowerShell using .net runtime natively [not powershell commandletts “too slow”]. Some scripts might have a few . sourced sections to make the editing manageable and modular. Because in a Powershell script everything is global or local in a function scopes are quite simple to deal with. Mapping my level into HA is confusing.

I am struggling [and here is the rub as always in technology] to know what I don’t know, so please bear with as I am not clear WHAT questions I should be asking to get me to the answers I need. I am not clear whether I should be creating template helpers [other helpers], automations, functional UI code in lovelace – etc. or, just be writing my own custom components entirely from scratch and am worried about investing time in the wrong direction.

My problem centres [I think] on how things interact with each other, I don’t mean devices, I mean architectural elements of the code I produce in the HA system. Where are globals, locals, array’s, boolean’s all specified, how do they work. Do we do this in the UI code itself or write automations that can be triggered from the UI? Specify static functions in the config yaml. What are the helpers for, I am using these to expose elements that I can glue together with code elsewhere but is that “right” ?? Not sure.

It is confusing because it’s like a ginormous leggo set with no pictures. The way these things are stuck together isn’t the focus of the documentation that I have found so far. The developer documentation guidance for HA explicitly prohibits the use of example code beyond the most basic required artefacts for the integration, so that code can be copied and pasted and I understand why. I need to get into the level above the basic but below development and I am not asking the right questions to hit those resources on my own. I need information on how to structure my approach in the “right way”. Info on different approaches would be good too !
What I am worried about is misusing the functional architecture and ”doing it wrong” and then find out my way is being “deprecated” or is glitchy or buggy / slow at a later stage of development “coz I done it wrong”.

So I am asking for the charity of the community to reach down a hand into the newbie pit and hold up an arrow for me to follow please.

If you’ve read this far, thank you. Because the above is a broad ask, the below is cobbled together in a few hours to try to understand the system [unsuccessfully] to work out what is going on.
It all focuses around the climate domain and here is one entity which has been deconstructed from the way climate presents it, into what I need via helper templates at the bottom.

This is the YAML for that UI above:

type: vertical-stack
cards:
  - show_name: true
    show_icon: false
    type: button
    tap_action:
      action: toggle
    name: Previous Temperature Value
    show_state: true
    entity: sensor.back_door_prv_temp
  - show_name: true
    show_icon: false
    type: button
    tap_action:
      action: toggle
    name: Previous Temperature Time
    show_state: true
    entity: sensor.back_door_this_temp_time
  - show_name: true
    show_icon: false
    type: button
    tap_action:
      action: none
    hold_action:
      action: none
    entity: sensor.back_door_mode
    show_state: true
    name: Mode
  - show_name: true
    show_icon: false
    type: button
    tap_action:
      action: none
    hold_action:
      action: none
    entity: sensor.back_door_now_temp_value
    show_state: true
    name: OverRide Temp
  - type: custom:slider-entity-row
    entity: climate.back_door
    max: 21
    min: 5
    step: 0.5
    toggle: false
    hide_state: false
    hide_when_off: false
    full_row: false
    show_icon: false
    name: Over-Ride Temp
  - type: custom:time-picker-card
    entity: input_datetime.evohome_override_time
    initial: "{{ now().strftime('%H:%M') }}"
    name: Override Until
    Hour_mode: 24
    tap_action: none
    hour_mode: 24
    layout:
      embedded: true
  - show_name: true
    show_icon: false
    type: button
    tap_action:
      action: none
    hold_action:
      action: none
    entity: sensor.back_door_temp_until_time
    show_state: true
    name: OverRide Until
  - show_name: true
    show_icon: false
    name: Clear Override
    type: button
    tap_action:
      action: perform-action
      perform_action: evohome.clear_zone_override
      target: {}
      data:
        entity_id: climate.back_door
    hold_action:
      action: perform-action
      perform_action: evohome.clear_zone_override
      target: {}
      data:
        entity_id: climate.back_door
  - show_name: true
    show_icon: false
    show_state: false
    entity: sensor.back_door_temperature
    type: button
    tap_action:
      action: perform-action
      perform_action: evohome.set_zone_override
      target: {}
      data:
        entity_id: climate.back_door
        setpoint: 12 # should be read from custom:slider-entity-row
        duration: 578 # should be read from custom:time-picker-card
    name: Set Override
    hold_action:
      action: none
  - show_name: true
    show_icon: false
    type: button
    tap_action:
      action: toggle
    name: Next Temperature Time
    show_state: true
    entity: sensor.back_door_next_temp_time
  - show_name: true
    show_icon: false
    type: button
    tap_action:
      action: toggle
    name: Next Temperature Value
    show_state: true
    entity: sensor.back_door_nxt_temperature

and these are the helpers which enable those distinct data pieces to be retrieved from the climate domain for the entity.

      {"created_at":"2025-03-01T08:26:11.447395+00:00","data":{},"disabled_by":null,"discovery_keys":{},"domain":"template","entry_id":"01JN8D07KQXJ5XEPD07E1FHH4P","minor_version":1,"modified_at":"2025-03-01T10:18:50.934716+00:00","options":{"device_class":"temperature","name":"Back Door Temperature","state":"{{ state_attr('climate.back_door', 'current_temperature') | float }}","state_class":"measurement","template_type":"sensor","unit_of_measurement":"°C"},"pref_disable_new_entities":false,"pref_disable_polling":false,"source":"user","title":"Back Door Temperature","unique_id":null,"version":1},
      {"created_at":"2025-03-02T20:27:37.645518+00:00","data":{},"disabled_by":null,"discovery_keys":{},"domain":"template","entry_id":"01JNC8NY9D86G93S018PMZRVW7","minor_version":1,"modified_at":"2025-03-02T20:27:37.645521+00:00","options":{"name":"Back_Door_mode","state":"{{ state_attr('climate.back_door', 'status').setpoint_status.setpoint_mode}}","template_type":"sensor"},"pref_disable_new_entities":false,"pref_disable_polling":false,"source":"user","title":"Back_Door_mode","unique_id":null,"version":1},
      {"created_at":"2025-03-02T20:38:35.472723+00:00","data":{},"disabled_by":null,"discovery_keys":{},"domain":"template","entry_id":"01JNC9A0PGG29DFQC3AVEV23FW","minor_version":1,"modified_at":"2025-03-02T20:51:51.902301+00:00","options":{"device_class":"temperature","name":"Back_door_prv_temp","state":"{{ state_attr('climate.back_door', 'status').setpoints.this_sp_temp }}","template_type":"sensor","unit_of_measurement":"°C"},"pref_disable_new_entities":false,"pref_disable_polling":false,"source":"user","title":"Back_door_prv_temp","unique_id":null,"version":1},
      {"created_at":"2025-03-02T20:52:57.893710+00:00","data":{},"disabled_by":null,"discovery_keys":{},"domain":"template","entry_id":"01JNCA4AX5ZRX5N0C7XNWF9RK5","minor_version":1,"modified_at":"2025-03-02T20:52:57.893713+00:00","options":{"device_class":"temperature","name":"Back_Door_nxt_temperature","state":"{{state_attr('climate.back_door', 'status').setpoints.next_sp_temp}}","template_type":"sensor","unit_of_measurement":"°C"},"pref_disable_new_entities":false,"pref_disable_polling":false,"source":"user","title":"Back_Door_nxt_temperature","unique_id":null,"version":1},
      {"created_at":"2025-03-02T20:54:29.197719+00:00","data":{},"disabled_by":null,"discovery_keys":{},"domain":"template","entry_id":"01JNCA742DS9SQPCH6AXZYMHFX","minor_version":1,"modified_at":"2025-03-02T20:54:52.741944+00:00","options":{"name":"Back_door_Next_Temp_time","state":"{{ as_timestamp(state_attr('climate.back_door', 'status').setpoints.next_sp_from) | timestamp_custom('%I:%M:%S %p') }}","template_type":"sensor"},"pref_disable_new_entities":false,"pref_disable_polling":false,"source":"user","title":"Back_door_Next_Temp_time","unique_id":null,"version":1},
      {"created_at":"2025-03-02T20:56:28.413197+00:00","data":{},"disabled_by":null,"discovery_keys":{},"domain":"template","entry_id":"01JNCAARFX18TQ2D79H14DX7Q1","minor_version":1,"modified_at":"2025-03-02T20:56:28.413199+00:00","options":{"name":"Back_door_This_Temp_time","state":"{{ as_timestamp(state_attr('climate.back_door', 'status').setpoints.this_sp_from) | timestamp_custom('%I:%M:%S %p') }}","template_type":"sensor"},"pref_disable_new_entities":false,"pref_disable_polling":false,"source":"user","title":"Back_door_This_Temp_time","unique_id":null,"version":1},
      {"created_at":"2025-03-02T21:02:33.100059+00:00","data":{},"disabled_by":null,"discovery_keys":{},"domain":"template","entry_id":"01JNCANWMCQ5VPGFG4M3J5NFJ4","minor_version":1,"modified_at":"2025-03-02T21:02:33.100061+00:00","options":{"name":"Back_door_temp_until_time","state":"{{ as_timestamp(state_attr('climate.back_door', 'status').setpoint_status.until) | timestamp_custom('%I:%M:%S %p') }}","template_type":"sensor"},"pref_disable_new_entities":false,"pref_disable_polling":false,"source":"user","title":"Back_door_temp_until_time","unique_id":null,"version":1},
      {"created_at":"2025-03-02T21:04:13.292654+00:00","data":{},"disabled_by":null,"discovery_keys":{},"domain":"template","entry_id":"01JNCARYFCDWJAEJ3FW4TVS3CA","minor_version":1,"modified_at":"2025-03-02T22:43:16.828140+00:00","options":{"device_class":"temperature","name":"Back_door_now_temp_value","state":"{{ state_attr('climate.back_door', 'status').setpoint_status.target_heat_temperature | float }}","template_type":"sensor","unit_of_measurement":"°C"},"pref_disable_new_entities":false,"pref_disable_polling":false,"source":"user","title":"Back_door_now_temp_value","unique_id":null,"version":1}

The thing I am worried about is that doing it this way I will need 163 helpers – just for this and this is just the climate, never mind the 35 smart plugs lights etc.
Surely this is not he right way, is it ?
Mabbe I should be developing a custom card and then I can just re-use that ?

Secondly, which goes back to my initial paragraphs:

HOW – do I start declaring variables and referencing these, passing in arguments to other functions, you know normal programming, in HA, this is what I am missing.
Otherwise my UI code is going to end up enormous as opposed to a few functions I can re-use with pointers to structures and data types of interest.
If someone points to the basic documentation to answer this, I am going to die of embarrassment !

Thanks.

2 posts - 2 participants

Read full topic

Configure own sensors

$
0
0

Hi,

New to Home Assistant but I’m trying to get my home battery in the Energy dashboard.

Modified the configuration.yaml as following:

# 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
sensor: !include sensors.yaml

Made a sensors.yaml file with the following:

template:
  - sensor:
      - name: Battery Charge Power
        state_class: measurement 
        device_class: power
        unit_of_measurement: W
        state: >
         {% if states('sensor.battery_power') | float(0) >= 0 %}
         {% set gridout = (states('sensor.battery_power') |float |abs) %}
         {% else %}
         {% set gridout = 0 %}
         {% endif %}
         {{ gridout }}
        availability: "{{ has_value('sensor.battery_power') }}"
        
      - name: Battery Discharge Power
        state_class: measurement 
        device_class: power
        unit_of_measurement: W
        state: >
         {% if states('sensor.battery_power') | float(0) <= 0 %}
         {% set gridout = (states('sensor.battery_power') |float |abs) %}
         {% else %}
         {% set gridout = 0 %}
         {% endif %}
         {{ gridout }}
        availability: "{{ has_value('sensor.battery_power') }}"

When I try the code above in the developer tools → template it works.
If I restart HA I always get this message, and the sensors aren’t created:

ERROR (MainThread) [homeassistant.config] Invalid config for ‘sensor’ at configuration.yaml, line 12: required key ‘platform’ not provided, please check the docs at Sensor - Home Assistant

Help would be appreciated :slight_smile:

3 posts - 3 participants

Read full topic

Why cant i delete tuya?

$
0
0

i spent the last two hours trying to delete, disable then delete, enable then delete, and between every attempt do a full reboot of the system. tuya is still there. what the hell man…

3 posts - 2 participants

Read full topic

All Z2M lights are suddenly unknown

$
0
0

Hello there,

From yesterday to today, I had to restart HA (an upgrade to Alexa Media Player integration).

Since this restart, all my lights from zigbee2mqtt are like this

Cette entité n’est plus fournie par l’intégration mqtt. Si l’entité n’est plus utilisée, supprimez-la depuis les paramètres.

This entity is no longer provided by the mqtt integration. If the entity is no longer used, delete it from the parameters.

All other stuffs are working as expected (switches, smoke detectors, water leak detectors, door sensors) but not the lights

I’ve tried the obvious already: restart mqtt integration, restart mosquitto, restart zigbee2mqtt, restart HA and even restart my RPi, nothing is working.

Please help :cry:

2 posts - 1 participant

Read full topic

Unable to start zigbee2mqtt - Sonoff Zigbee 3.0 USB Dongle-E V2

$
0
0

Hello, I am trying to configure the Zigbee Dongle without success.
So my Z2M version is: 2.1.3-1
I did flash firmware to: ncp-uart-hw-v7.4.5.0-zbdonglee-230400 by website with success.
my config:

Socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: “-d -d”
log: false

MQTT:
server: mqtt://core-mosquitto:1883
user: mqtt-user
password: xxxxxxxxx

Serial:
port: >-
/dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_6a1e78b8284bef11a714c0a079f42d1b-if00-port0
adapter: ember

Logs from Z2M:

[2025-03-03 13:47:52] error: 	**z2m: Error while starting zigbee-herdsman**
[2025-03-03 13:47:52] error: 	**z2m: Failed to start zigbee-herdsman**
[2025-03-03 13:47:52] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-03-03 13:47:52] error: 	z2m: Exiting...
[2025-03-03 13:47:52] error: 	z2m: **Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.**
    at EmberAdapter.initEzsp (/app/node_modules/.pnpm/zigbee-herdsman@3.2.7/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:670:19)
    at EmberAdapter.start (/app/node_modules/.pnpm/zigbee-herdsman@3.2.7/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1536:24)
    at Controller.start (/app/node_modules/.pnpm/zigbee-herdsman@3.2.7/node_modules/zigbee-herdsman/src/controller/controller.ts:136:29)
    at Zigbee.start (/app/lib/zigbee.ts:69:27)
    at Controller.start (/app/lib/controller.ts:142:13)
    at start (/app/index.js:161:5)

ZHA seemed to be disable and when I plug in dongle I click ignore when device is detected by ZHA.
I tried to use adapter: ezsp but didn’t help.

1 post - 1 participant

Read full topic


Howto shutoff heat pump when LWT

$
0
0

This is somewhat complex so I am hoping we have a guru on the community !

Question: How might I automate turning off a heat pump when leaving water temperature minus the leaving water offset demand is less than 30?

Issue
I am using HA to modulate heating because the madoka room thermostat is not as responsive as my custom room sensors and also because there are limitations on the number of API calls the Oneta app can invoke over a 24 hour period (so updating the madoka values from cloud interface). The Daikin system obtains a Leaving Water Temperature (LWT) from the weather curve set in the MMI, then my HA automation applies an offset value (range -10 to +10) to the LWT value, to modulate the system as a complex but now fully working hysteresis that is not available in HA generic thermostat etc. Indeed there are 5 different thresholds that increase or decrease the offset in different time frames , to maintain the house temp - which is does perfectly, around 20C. So I do not want to change any of this - thank you for understanding.

Help needed
As I throttle the LWT My Daikin Air Heat Pump cycles rapidly causing wear & tear and increased maintenance costs when the LWT is less than 30C. I need some way to ensure that for negative offset values, when deducted from the current LWT, the resultant value is >= 30. Similarly for positive offsets, when added to the current LWT, the resultant value is => 30.

Setup:
I use the Onecta integration downloaded today, I have a number of sensors and climate devices.
What I really need is the LWT value from the weather curve that the system is using, if that is >=30 then turn pump on, if on the other hand deducting -ve offsets takes it below 30 then turn off the pump. But that curve value is not available - I note on Github users are requesting it but I think Daikin do not provide an API wrapper for this so it cannot be made available.

The only two useful exposed entities are:

climate.heating_leaving_water_offset which has state HEATING or OFF, and its associated attribute target_temperature which is a integer value from -10 to +10 (for simplicity here lets call this offset)

and

sensor.heating_climatecontrol_leaving_water_temperature which has a numeric state of 0 to 50. (for simplicity here lets call this lwt)
… but lwt isnt helping me as that is the current leaving water temperature and not the target lwt.
Ideally as above, if we had the weather curve value then this is the target lwt rather than actual lwt, and we could just simply do:

IF target-lwt + offset < 30 # check if target lwt with offset applied is < 30
THEN
    # lwt with negative offset would be less than 30
    # or
    # lwt with positive offset would be less than 30
    << turn off pump >>
ENDIF

I want to turn off the pump (climate.heating_leaving_water_offset HVAC mode set to OFF) when negative offsets applied to lwt is < 30. Lwt will always reduce for negative offsets. So this side of automation seems doable.

However the upward increasing side is more complex. If LWT + positive offset is < 30 then pump should stay off but then of course the pump will not run so LWT will never increase and so the pump will always be off once LWT has gone below 30. Mmmm.

Maybe my logic/algorithm is wrong here, but I don’t know what more I can do with the limited entities exposed through the Daikin Onecta integration.

This is complicated - is anyone understanding this and if so can you suggest a solution.

1 post - 1 participant

Read full topic

JupyterLab not wanting to start

$
0
0

Hey fellow JupyterLab enthusiasts using it under Home Assistant! I’m reaching out for some help and guidance.
I’m having a bit of trouble getting JupyterLab to start, and I was hoping someone might be able to lend a hand.
I’ve included the logs below - I’d be super grateful if someone could take a look and offer some insight.
I’ve tried a few troubleshooting steps already, but I’m stumped. Here are the logs:


s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
 Add-on: JupyterLab
 Create documents containing live code, equations, visualizations, and explanatory text
-----------------------------------------------------------
 Add-on version: 0.15.9
 You are running the latest version of this add-on.
 System: Home Assistant OS 14.2  (amd64 / qemux86-64)
 Home Assistant Core: 2024.12.5
 Home Assistant Supervisor: 2025.02.4
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[15:12:02] INFO: Configuring timezone (Europe/Bucharest)...
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-system-packages: starting
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-jupyter: starting
s6-rc: info: service init-system-packages successfully started
s6-rc: info: service init-nginx successfully started
s6-rc: info: service init-jupyter successfully started
s6-rc: info: service init-notebooks: starting
s6-rc: info: service jupyter: starting
s6-rc: info: service jupyter successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
[15:12:02] INFO: Starting the Jupyter server...
[15:12:02] WARNING: Not updating Home Assistant notebook!
[15:12:02] WARNING: You have made local changes, which we will not overwrite.
fatal: cannot change to '/config/notebooks//bokeh-examples': No such file or directory
fatal: cannot change to '/config/notebooks/bokeh-examples': No such file or directory
s6-rc: warning: unable to start service init-notebooks: command exited 128
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service nginx: stopping
[15:12:02] INFO: Service NGINX exited with code 256 (by signal 15)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service jupyter: stopping
s6-rc: info: service init-nginx successfully stopped
[15:12:02] INFO: Service JupyterLab exited with code 256 (by signal 15)
s6-rc: info: service jupyter successfully stopped
s6-rc: info: service init-system-packages: stopping
s6-rc: info: service init-jupyter: stopping
s6-rc: info: service init-system-packages successfully stopped
s6-rc: info: service init-jupyter successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-timezone: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-timezone 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

Thanks in advance for your help and expertise - I really appreciate it!

1 post - 1 participant

Read full topic

Stuck on getting sensor value out of an array

$
0
0

I have searched around the forum, and I can’t find anything that works for me. I have this code in Node-RED:

msg.topic = kjede + ' ' + navn;
msg.payload['pris'] = msg.payload.prices.B95.price;
msg.payload['tid'] =  timer +':'+minutter;

The array looks like this:

(Price of 95 octane gasoline, and it was updated 1 hour and 48 minutes ago.)

Then I have created a sensor in configuration. yaml:

mqtt:
  - sensor:
    - name: "Bensinpris på Valand"
      state_topic: "Driv Valand"
      unique_id: bensinpris-driv-valand
      force_update: true
      value_template: "{{ payload_json['pris'] }}"

    - name: "Bensinpris oppdatert på Valand"
      state_topic: "Driv Valand"
      unique_id: bensinpris-oppdratert-driv-valand
      force_update: true
      value_template: "{{ value_json.payload.tid }}"

But none of those versions (or a few others I have tried) work. They keep saying variants of

Template variable error: ‘dict object’ has no attribute ‘payload’ when rendering ‘{{ value_json.payload.tid }}’

Depending on which version I try. Can somebody please tell me what I’m doing wrong here?

1 post - 1 participant

Read full topic

Tplink switchs - can i disable error individually for module query 'get_matter_setup_info

$
0
0

hi i got these new Kasa Tplink Matter Switchs dimmers…

1st question why did i need an account to set them up?
and 2nd i get these errors… i have the internet shut off to the IoT devices and i turned off cloud diagnostic. as i dont want it connecting to the internet

but i seeing these errors any way i can fix it?

Logger: kasa.smart.smartdevice
Source: components/tplink/coordinator.py:78
First occurred: March 2, 2025 at 7:29:56 PM (22 occurrences)
Last logged: 2:12:07 AM

Error querying 192.168.20.162 individually for module query 'get_matter_setup_info' after first update: ('Unable to query the device: 192.168.20.162: ', TimeoutError())
Error querying 192.168.20.162 for modules 'Time, Cloud, DeviceModule, LightPreset, LightTransition, Matter' after first update: ("Device connection error: 192.168.20.162: Cannot connect to host 192.168.20.162:80 ssl:<ssl.SSLContext object at 0x7f659ac4b140> [Connect call failed ('192.168.20.162', 80)]", ClientConnectorError(ConnectionKey(host='192.168.20.162', port=80, is_ssl=False, ssl=<ssl.SSLContext object at 0x7f659ac4b140>, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(113, "Connect call failed ('192.168.20.162', 80)")))
Error querying 192.168.20.162 individually for module query 'get_device_time' after first update: ("Device connection error: 192.168.20.162: Cannot connect to host 192.168.20.162:80 ssl:<ssl.SSLContext object at 0x7f659ac4b140> [Connect call failed ('192.168.20.162', 80)]", ClientConnectorError(ConnectionKey(host='192.168.20.162', port=80, is_ssl=False, ssl=<ssl.SSLContext object at 0x7f659ac4b140>, proxy=None, proxy_auth=None, proxy_headers_hash=None), OSError(113, "Connect call failed ('192.168.20.162', 80)")))
Error querying 192.168.20.162 individually for module query 'get_device_usage' after first update: Error querying device: 192.168.20.162: TIME_ERROR(-1601) for method: get_device_usage (error_code=TIME_ERROR)
Error processing Time for device 192.168.20.162, module will be unavailable: get_device_time for Time (error_code=INTERNAL_QUERY_ERROR)
Logger: homeassistant.components.tplink.coordinator
Source: helpers/update_coordinator.py:412
integration: TP-Link Smart Home (documentation, issues)
First occurred: March 2, 2025 at 7:30:20 PM (10 occurrences)
Last logged: 2:19:41 AM

Error fetching 192.168.20.200 data: Unable to communicate with the device update: Unable to connect to the device: 192.168.20.200:9999: [Errno 111] Connect call failed ('192.168.20.200', 9999)
Error fetching 192.168.20.254 data: Unable to communicate with the device update: Unable to connect to the device: 192.168.20.254:9999: [Errno 111] Connect call failed ('192.168.20.254', 9999)
Error fetching 192.168.20.237 data: Unable to communicate with the device update: Unable to connect to the device: 192.168.20.237:9999: [Errno 111] Connect call failed ('192.168.20.237', 9999)
Error fetching 192.168.20.162 data: Unable to communicate with the device update: get_device_info not found in {'get_device_time': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_device_info': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_device_usage': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, 'get_matter_setup_info': <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>} for device 192.168.20.162
Error fetching 192.168.20.195 data: Unable to communicate with the device update: Unable to connect to the device: 192.168.20.195:9999: [Errno 111] Connect call failed ('192.168.20.195', 9999)

or is it a mistake to gottten the kasa tplink matter switchs?
or is there a way to disable the error from coming up etc

1 post - 1 participant

Read full topic

Howto add a toggle-switch button to a card

$
0
0

Hell everyone,

This is picture of a native entities card with a toggle-switch button. The kind of toggle-switch that is used everywhere in Home Assistant :

Is there an easy way to include such a toggle-switch button in a Tile card, or mushroom template or even bubble-card ?

I must miss something as all my tries end-up with lots of card_mod CSS tweaks. It seems an overkill.
Thanks for your help & ideas

1 post - 1 participant

Read full topic

Issues with setting up rtl_433(next) and rtl_433 Auto discovery (next)

$
0
0

I have installed these two add-ons and am succesfully receiving data from my oil sensors which i can see in MQTT Explorer and am displaying on my dashboard. This is without any specific configuration in the options section of the rtl_433 (next add-on)


in the rtl_433 autodiscovery (next) addon, i have my mqtt date as follows:

If, within the rtl_433 (next) add-on, i change the entry as follows:

rtl_433_conf_file: ""
retain: true
frequency: 433.92M, 433.905M, 431.837M, 868.30M, 868.268M -s 1024k
hop_interval: 20
rtl433_flags: "-vv -F log"

No changes can be seen in the log tab even after restarting. no hopping of frequencies, no added logging data etc.

So it seems to me the add-on is not reading this code for some reason.
In Studio Code Server, i have looked through all teh HA files and see nothing relevant other than the rtl_433 directory which only contains the rtl_433.conf.template file with contents starting with: “this is an empty template file…”

Could anyone help and tell me where i can add options so that:
A) i can see any frequency hopping,debug and scanning data in the log?
B) scan frequency 433.92M (as it is already succesfully doing by default it seems)
plus
frequency 868.30M
frequency 868.268M
I have tried uninstalling the add-on and deleting its data and reinstalling, that made no difference. I have spent a day searching through the forum as well as trying co-pilot (very frustrating) but seem stuck.

Many thanks!

1 post - 1 participant

Read full topic

Midea AC Attributes not updating

$
0
0

Hello all,

I’ve successfully configured the Midea AC Lan HACS integration with a static IP, etc. I can control AC via my Home Assistant.

However, some attributes (so far I think it is just the fan_mode) don’t update. I can succesfully change the fan speed between auto, low, med, high; but the associated attribute remains on “auto”. So by looking on Home Assistant, the fan speed always says its on auto.

image

Anyone else encounter something similar, or is there something I’ve missed for setting it up?

Many thanks!

P.S. changing the fan speed, while it does indeed change it on the device, HA doesn’t show the command in the logbook

1 post - 1 participant

Read full topic


Negative houseload

$
0
0

Hello, I shut down my HA server today to build on the server. When I booted it up, I now have negative house power consumption. Resetting to a backup didn’t work. All settings on the Solax inverter seem to be as usual

3 posts - 2 participants

Read full topic

Energy directly used from solar

$
0
0

I am trying to make a sensor which gives my the number off directly consumed energy from my Envoy Solar panels. Having a Homewizard P1 meter gives me p1.meter.import and p1.meter.export. The Envoys give me production today and total production.
In the energy dashboard distribution image total usage is displayed and also what i am returning to the grid en consuming from the grid but not what i am consuming myself from he solar panels.
In the printscreen beneth the -name eigen verbruik zonnepanelen should give me that number but instead gives me a number which does not is the actual returned energy to the grid.

Is it correct to say when choosing a helper: nuts (i believe it is called utility) and then choose p1 meter.export (that shows the total export of energy) choose month and reset yes it must show me the energy consumed for this month?

template:

  • sensor:
    • name: “Eigen Verbruik Zonnepanelen”
      unique_id: “eigen_verbruik_zonnepanelen”
      unit_of_measurement: “kWh”
      state: >-
      {{
      (states(‘sensor.envoy_122132012200_energy_production_today’)|float(0) -
      states(‘sensor.p1_meter_energie_export’)|float(0)) | round(2)
      }}

1 post - 1 participant

Read full topic

Add-on MariaDB has been removed from the repository

$
0
0

I run 3 different HA instances. One of them started reporting the need for repairs - that MariaDB was no longer in the repository and needs to be removed. Same error for Mosquito MQTT, File Editor, and Matter. Seems like my instance is no longer getting correct list of official addons. Any suggestions on where to look?

1 post - 1 participant

Read full topic

Wyoming discovery fails not sure why

$
0
0

piper whisper and speech_to_phrase are all installed, their logs say
discovery has been notified.

Discovery is enabled in configuration.yaml

on reboot I get this log entry for wyoming.

Logger: homeassistant
Source: components/wyoming/config_flow.py:75
First occurred: 9:02:31 AM (1 occurrences)
Last logged: 9:02:31 AM

Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/discovery_flow.py", line 137, in _async_start
    await gather_with_limited_concurrency(FLOW_INIT_LIMIT, *init_coros)
  File "/usr/src/homeassistant/homeassistant/util/async_.py", line 114, in gather_with_limited_concurrency
    return await gather(
           ^^^^^^^^^^^^^
    ...<2 lines>...
    )
    ^
  File "/usr/src/homeassistant/homeassistant/util/async_.py", line 112, in sem_task
    return await task
           ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1309, in async_init
    flow, result = await self._async_init(flow_id, handler, context, data)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1344, in _async_init
    result = await self._async_handle_step(flow, flow.init_step, data)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 490, in _async_handle_step
    result: _FlowResultT = await getattr(flow, method)(user_input)
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/wyoming/config_flow.py", line 75, in async_step_hassio
    entry.data[CONF_HOST] == uri.hostname
    ~~~~~~~~~~^^^^^^^^^^^
KeyError: 'host'

1 post - 1 participant

Read full topic

AEG (Electrolux) washing machine integration

$
0
0

Dear community,

I recently got a new washing machine with wifi integration from AEG (Electrolux). As this device has a wifi connection I was curious to integrate it into my HA for some automations.

However, I am struggling to find the right integration for this device. I am running Home Assistant Core 2025.2.5 with OS version 14.2 on a Raspberry 4.

I saw that back in 2022 there has been a feature request regarding this topic, but the git link is not available anymore. Hence, I don’t really know if there is an integration by now or at least a known way on how this integration can be done.

I’d very much appreciate if someone could help me with this.
Thanks,
Christian

1 post - 1 participant

Read full topic

Viewing all 106310 articles
Browse latest View live