I currently use a button to trigger my TV Room to be set up when I’m done with dinner.

During dinner, I have my tablet sitting in a generic stand on the table to manage the music that’s being played, to follow the lyrics, etc.

What I want to achieve is the following:
When I move the tablet from the table into the charging stand, I want an existing script to be triggered - the one that I’m currently triggering by pushing a separate physical button. The script is all set up and working fine.

The tricky part is that when I put the tablet into the charger, the charger_type sensor changes to ‘wireless’ but it also does that every few minutes for a few seconds while the tablet is in the stand, so a simple to: wireless is not going to cut it. I need to filter out the cases where the sensor turns to wireless after it’s been on none for a few seconds.

Any idea how to template a filter that achieves that?

BTW:
Yes, there are other sensors, e.g. binary_sensor.drdashboard_is_charging, but they have the same issue.

1 post - 1 participant

Read full topic

Is anyone else getting an unhashable type: 'dict' error when clicking on the prev and next track buttons on the media player card for a Denon AVR integration? Here’s the full error:

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:245
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 5:33:20 PM (2 occurrences)
Last logged: 5:47:42 PM

[140265772236032] Unexpected exception
[140265772221344] Unexpected exception
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2795, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2838, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1006, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
        hass, entity, func, data, call.context
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1078, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/denonavr/media_player.py", line 176, in wrapper
    return await func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/denonavr/media_player.py", line 443, in async_media_next_track
    await self._receiver.async_next_track()
  File "/usr/local/lib/python3.13/site-packages/denonavr/denonavr.py", line 584, in async_next_track
    await self.input.async_next_track()
  File "/usr/local/lib/python3.13/site-packages/denonavr/input.py", line 1124, in async_next_track
    await self._device.api.async_post(
        self._device.urls.command_netaudio_post, data=body
    )
  File "/usr/local/lib/python3.13/site-packages/denonavr/api.py", line 219, in async_post
    return await self.httpx_async_client.async_post(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<6 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/denonavr/decorators.py", line 82, in wrapper
    return await cached_func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/asyncstdlib/_lrucache.py", line 428, in __call__
    key = CallKey.from_call(args, kwargs, typed=self.__typed)
  File "/usr/local/lib/python3.13/site-packages/asyncstdlib/_lrucache.py", line 318, in from_call
    return cls(key)
  File "/usr/local/lib/python3.13/site-packages/asyncstdlib/_lrucache.py", line 277, in __init__
    self._hash = hash(values)
                 ~~~~^^^^^^^^
TypeError: unhashable type: 'dict'

1 post - 1 participant

Read full topic

The new graphs introduced in 2025.2 look nice.
But I have a couple of sensors which report about each 1…2 seconds. When i open the default chart (just click on the entity history button), then it’s veery slow, and if I try to click… 8t’s freezing. The same on the mobile…

I can make a video if it is helpful.

1 post - 1 participant

Read full topic

• Core 2025.2.0
• Supervisor 2025.02.0
• Operating System 14.2
• Interface utilisateur 20250109.2

Hi,

I’m trying to set the automatic backup but when I want to confirm it, I have erros like these:

[547922093408] Error handling message: expected a dictionary for dictionary value @ data[‘schedule’]. Got ‘daily’ (invalid_format) XXXX from XXX.XXX.XXX.XXX (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36 Edg/132.0.0.0)

[547922093408] Error handling message: expected a dictionary for dictionary value @ data[‘schedule’]. Got ‘mon’ (invalid_format) XXXX from XXX.XXX.XXX.XXX (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36 Edg/132.0.0.0)

I found a previous topic about problems with an empty YAML, but I don’t see empty files.

QuickTurtle

3 posts - 2 participants

Read full topic

Sorry, a bit late coming back here. (See referenced post)

I’m using this solution widely where I trigger on an event (or in my case often many) and then in a choose look at the event_type.

On a restart (or, for example, restarting the zwave integration), I get events fired. I assume that is so that listeners could update the state at startup. The result is things get turned on that should not have been – the scene controller button wasn’t pushed.

The trigger data has this from_state that includes restored: true. I couldn’t find docs on that, but I assume that I can check that in a condition to test if the event is from a restart and not an actual button pushed on a scene controller.

trigger:
  id: '0'
  idx: '0'
  alias: null
  platform: state
  entity_id: event.bar_ceiling_light_scene_001
  from_state:
    entity_id: event.bar_ceiling_light_scene_001
    state: unavailable
    attributes:
      restored: true
      event_types:
        - KeyHeldDown
        - KeyPressed
        - KeyPressed2x
        - KeyPressed3x
        - KeyPressed4x
        - KeyPressed5x
        - KeyReleased
       ...

So, specifically something like this:

conditions:
  - condition: template
    value_template: "{{ not trigger.from_state.attributes.restored }}"

1 post - 1 participant

Read full topic

Hi,

After finally getting H.A to work in a VMM on Synology I decided to automate some outdoor lights (18 of), which I did not think would be that hard!

All I am trying to achieve is that the all the lights come on, dim in stages & switch off at the following times:-

16:00 ON @100% brightness
00:00 ON but dim to 50%
02:00 ON but dim to 20%
08:00 OFF

to be done each day for ever more.

I have tried setting up automation using delays of hours between events. Sometimes they come off but not come and vice versa. They all work fine when manually triggered to do so.

All I really need to do is

Current time between 16:00 & 00:00 set lamp ON & brightness 100%
Current time between 00:00 & 02:00 set lamp ON & brightness 50%
Current time between 02:00 & 08:00 set lamp ON & brightness 20%

and monitor constantly.

Am I best achieving this via a script or another way?

Regards
Steve

4 posts - 3 participants

Read full topic

Hi All,

I have a Dome Z-Wave motion sensor at the bottom of my basement stairs that has been connected to my HUSBZB-1 stick (Only using Z-Wave on this) for years without issues. A few days ago I started having issues with this motion sensor, It seemed to be erratic so as I have never replaced the battery that is the first thing I did. If I put it in the hallway outside the room my HSUSBZB-1 is it works without issues. If I put it back in the place it has been forever what I noticed is that in my dashboard it is constantly detecting motion. I can move it too the top of the basement stairs and after about 30 seconds it stops detecting motion and works properly.

I have excluded it and factory reset it but still the same thing happens, I also had a Leviton zwave plug that also gave me issues recently so I removed it and replaced it with a Tradfri Zigbee plug as I had another one of these that went bad last year but now I am wondering if something else is going on.

Could something be going on with my Zwave stick ? I have 4 Schlage Zwave locks on the main floor that are all working perfectly. I am running Zwave JS btw. Not sure if this is related to a zwave JS update recently as I have had zero issues with my small network for years.

Really scratching my head with this one and would love to hear any thoughts on this.

1 post - 1 participant

Read full topic

Hello -
Hoping someone can help me. I have an annoying log entry that doesn’t seem to be causing any issues but I can’t track it down. It’s referencing a device that’s been off the system for a number of weeks. I recently finally moved off of Vera and removed the integration. (It left a few devices behind that I can’t remove but that’s a different problem and this device doesn’t show up in Entities).

I have no templates that I know of. No dashboards calling this. Any idea where I can look?

Logger: homeassistant.helpers.event
Source: helpers/template.py:645
First occurred: 10:07:49 PM (3 occurrences)
Last logged: 10:52:25 PM

Error while processing template: Template<template=({{ states('sensor.office_temperature_398')| round(1)}}°F) renders=2>
Error while processing template: Template<template=({{ states('sensor.office_temperature_398')| round(1)}}°F) renders=6>
Error while processing template: Template<template=({{ states('sensor.office_temperature_398')| round(1)}}°F) renders=10>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1940, in forgiving_round
    value = round(float(value), precision)
                  ~~~~~^^^^^^^
ValueError: could not convert string to float: 'unknown'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 643, in async_render
    render_result = _render_with_context(self.template, compiled, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2745, in _render_with_context
    return template.render(**kwargs)
           ~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 1295, in render
    self.environment.handle_exception()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.13/site-packages/jinja2/environment.py", line 942, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 1, in top-level template code
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1945, in forgiving_round
    raise_no_default("round", value)
    ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1921, in raise_no_default
    raise ValueError(
    ...<2 lines>...
    )
ValueError: Template error: round got invalid input 'unknown' when rendering template '{{ states('sensor.office_temperature_398')| round(1)}}°F' but no default was specified

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 760, in async_render_to_info
    render_info._result = self.async_render(  # noqa: SLF001
                          ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
        variables, strict=strict, log_fn=log_fn, **kwargs
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 645, in async_render
    raise TemplateError(err) from err
homeassistant.exceptions.TemplateError: ValueError: Template error: round got invalid input 'unknown' when rendering template '{{ states('sensor.office_temperature_398')| round(1)}}°F' but no default was specified

3 posts - 2 participants

Read full topic

Please help. I’ve been trying to find a solution for 5 days. I’ve tried a thousand different things. I went back to my first attempt and ask someone to please point me in the right direction.

The first sensor (sensor.nws_daily_forecasts) works perfectly. The second sensor (sensor.current_forecast) just needs its state value to equal the value of the first sensor’s first attribute (forecast_0).

Here is the template sensor:

template:
  - trigger:
      - platform: time_pattern
        minutes: "/15"
    action:
      - service: nws.get_forecasts_extra
        data:
          type: twice_daily
        target:
          entity_id: weather.klqk_daynight
        response_variable: daily_forecast
    sensor:
      - name: "NWS Daily Forecasts" 
        unique_id: nws_daily_forecasts 
        state: "{{ now() }}"
        attributes:
          forecast_0: "{{ daily_forecast.forecast[0].detailed_description }}"
          forecast_1: "{{ daily_forecast.forecast[1].detailed_description }}"
          forecast_2: "{{ daily_forecast.forecast[2].detailed_description }}"
          forecast_3: "{{ daily_forecast.forecast[3].detailed_description }}"

      - name: "Current Forecast"
        unique_id: current_forecast
        state: "{{ daily_forecast.forecast[0].detailed_description }}"

No matter what I have tried, I always get ‘unknown’ on the second sensor.

Thanks…

1 post - 1 participant

Read full topic

I have created an automation that I want to trigger with a helper button: input_button.office_light_flash

I can run the automation and it works, but when I press the button it does not trigger. What am I missing?

alias: Flash Office Lights
description: Flash Office Lights
triggers:
  - entity_id: input_button.office_light_flash
    from: "off"
    to: pressed
    trigger: state
conditions: []
actions:
  - variables:
      original_brightness: "{{ state_attr('light.floor_lamp', 'brightness') | default(0) }}"
      target_state: |
        {% if original_brightness <= 128 %}
          255
        {% else %}
          64
        {% endif %}
  - repeat:
      count: 3
      sequence:
        - choose:
            - conditions:
                - condition: template
                  value_template: "{{ original_brightness == 0 }}"
              sequence:
                - target:
                    entity_id: light.floor_lamp
                  action: light.turn_off
                  data: {}
            - conditions:
                - condition: template
                  value_template: "{{ original_brightness > 0 }}"
              sequence:
                - target:
                    entity_id: light.floor_lamp
                  data:
                    brightness: "{{ target_state | int }}"
                  action: light.turn_on
        - delay: "00:00:00.5"
        - choose:
            - conditions:
                - condition: template
                  value_template: "{{ original_brightness == 0 }}"
              sequence:
                - target:
                    entity_id: light.floor_lamp
                  action: light.turn_off
                  data: {}
            - conditions:
                - condition: template
                  value_template: "{{ original_brightness > 0 }}"
              sequence:
                - target:
                    entity_id: light.floor_lamp
                  data:
                    brightness: "{{ original_brightness | int }}"
                  action: light.turn_on
        - delay: "00:00:00.5"
  - target:
      entity_id: input_button.sam_office_light_flash
    action: input_button.press
    data: {}
mode: single

2 posts - 2 participants

Read full topic

During backup configuration I removed config/.storage/backup.
Now, trying to configure it again HA doesn’t offer to use network storage for backup location.

How to fully reset backup configuration or how to understand why HA doesn’t see network backup location?

1 post - 1 participant

Read full topic

Have a strange issue, I setup a calendar with repeat events for my bin collections. As you can see today from the main calendar view that it’s “Household” day today, however in my button on my dashboard it’s reading as Recycling? I only have 1 calendar set up, I’ve removed it and re-added it, created all the events again?

Bit of a funky one! Any ideas?

5 posts - 2 participants

Read full topic

Hi, I have a zigbee switch managed through Z2M. For some reasons, at some times the switch switches on automatically. I narrowed it down to it to happen when one member of the family switches to home. However, I have double-checked both node-red and HA automation and I could not find anything related to it.

Is there a way to know which component caused the switch to switch on? In the log I simply see “Supervisor”

2 posts - 2 participants

Read full topic

Hi!

I have sauna and would like to know when it was turned on. I have a temperature sensor in the sauna and configured a trend sensor, but it look like it is not working as intended.

The trend sensor should be turned on, if the temperature within the sauna has risen by 5°C within the last 10 minutes. The temperature sensor is a Aqara Temperature sensor and it appears to update the temperature every 10-15 seconds, if it changed meaningfully. Right now it appears to turn on randomly, can someone please guide me towards a correct solution?

I switched to absolute temperature values to check whether it is on/off, but this is suboptimal due to different base values in summer and winter.

Graphs with temperature values & trend:

Sauna temperature trend sensor configuration:

1 post - 1 participant

Read full topic

Hi everybody,

is there a (somewhat simple) way to create an image (png/jpeg) of ones current position? When running, I have a shortcut on my phone that will send a notification home when triggered; the notification includes my current estimated address, distance to home, and estimated time I should arrive home.

While this is not really important, I thought it’d be nice to include an image of a map that shows my position. I know that this position can be shown in Home Assistant (and it is), but I would like to include it directly in the notification message, so that even people that don’t use Home Assistant (but might be notified via Signal or similar) would be able to see it.

Thank you for your ideas

1 post - 1 participant

Read full topic

Hello I am already reading data from ems-esp (heating system) to homeassistant via moqitto.
Now I would like to transfer data from mosqitto to influxdb2 via Telegraf.
Basically Telegraf is working already but only once. The service runs on influxdb but only transfers data on the first start.

Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Loading config: /etc/telegraf/telegraf.conf
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Starting Telegraf 1.33.1 brought to you by InfluxData the makers of InfluxDB
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Available plugins: 236 inputs, 9 aggregators, 33 processors, 26 parsers, 63 outputs, 6 secret-stores
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Loaded inputs: mqtt_consumer
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Loaded aggregators:
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Loaded processors:
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Loaded secretstores:
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Loaded outputs: file influxdb_v2
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Tags enabled: host=influxdb
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! [agent] Config: Interval:10s, Quiet:false, Hostname:"influxdb", Flush Interval:10s
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z D! [agent] Initializing plugins
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z D! [agent] Connecting outputs
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z D! [agent] Attempting connection to [outputs.file]
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z D! [agent] Successfully connected to outputs.file
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z D! [agent] Attempting connection to [outputs.influxdb_v2]
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z D! [agent] Successfully connected to outputs.influxdb_v2
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z D! [agent] Starting service inputs
Feb 07 11:02:04 influxdb systemd[1]: Started telegraf.service - Telegraf.
░░ Subject: A start job for unit telegraf.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit telegraf.service has finished successfully.
░░ 
░░ The job identifier is 1401.
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! [inputs.mqtt_consumer] Connected [tcp://192.168.10.146:1883]
Feb 07 11:02:14 influxdb telegraf[775]: mqtt_consumer,host=influxdb,topic=ems-esp/solar_data turnondiff=10,cylpumpmod=0,solarpumpmod=0,collectortemp=31.3,energytoday=15459,pumpminmod=5,heatcnt=0,climatezone=90,pumpworktime=83801,cylmaxtemp=60,m1worktime=0,collectormintemp=20,turnoffdiff=5,pump2worktime=0,energytotal=3312.1,collector1area=7,collectormaxtemp=120,energylasthour=0,solarpump2mod=0,cylbottomtemp=52.8 1738922524200126227
Feb 07 11:02:14 influxdb telegraf[775]: mqtt_consumer,host=influxdb,topic=ems-esp/boiler_data pumpmodmax=100,boil2hyston=0,pumpdelay=10,burnminperiod=10,burnmaxpower=100,burn2workmin=0,heatingpumpmod=0,boil2hystoff=0,selflowtemp=5,burnminpower=0,boilhyston=-6,maintenancetime=6000,heatingtemp=82,burnworkmin=194452,outdoortemp=19.8,curburnpow=0,curflowtemp=26.5,heatworkmin=168918,servicecodenumber=203,boilhystoff=6,selburnpow=0,heatstarts=9535,ubauptime=896104,burnstarts=12008,flamecurr=0,pumpmodmin=10 1738922524200210183
Feb 07 11:02:14 influxdb telegraf[775]: mqtt_consumer,host=influxdb,topic=ems-esp/boiler_data_ww wwcurtemp2=54,wwstarts=2473,wwsettemp=50,wwseltemp=50,wwmaxpower=100,wwstoragetemp2=54,wwhystoff=0,wwdisinfectiontemp=70,wwworkm=25534,wwcurtemp=54,wwflowtempoffset=40,wwcurflow=0,wwhyston=-5 1738922524200281498
Feb 07 11:02:14 influxdb telegraf[775]: mqtt_consumer,host=influxdb,topic=ems-esp/thermostat_data_hc1 maxflowtemp=48,comforttemp=22,remoteseltemp=0,tempautotemp=-1,targetflowtemp=0,manualtemp=30,reducetemp=0,minflowtemp=25,offsettemp=0,roominflfactor=4,fastheatup=0,noreducetemp=-31,nofrosttemp=5,summertemp=15,curroominfl=0,seltemp=22,designtemp=45,roominfluence=0,ecotemp=21 1738922524200336601
Feb 07 11:02:14 influxdb telegraf[775]: mqtt_consumer,host=influxdb,topic=ems-esp/thermostat_data intoffset=0,wwsettemplow=45,wwextra1=0,wwsettemp=60,dampedoutdoortemp=19.9,wwdisinfecttime=120,floordrytemp=0,wwchargeduration=60,minexttemp=-10 1738922524200386862
Feb 07 11:02:14 influxdb telegraf[775]: 2025-02-07T10:02:14Z D! [outputs.file] Wrote batch of 5 metrics in 194.489µs
Feb 07 11:02:14 influxdb telegraf[775]: 2025-02-07T10:02:14Z D! [outputs.file] Buffer fullness: 0 / 10000 metrics
Feb 07 11:02:14 influxdb telegraf[775]: 2025-02-07T10:02:14Z D! [outputs.influxdb_v2] Wrote batch of 5 metrics in 12.645894ms
Feb 07 11:02:14 influxdb telegraf[775]: 2025-02-07T10:02:14Z D! [outputs.influxdb_v2] Buffer fullness: 0 / 10000 metrics
Feb 07 11:02:24 influxdb telegraf[775]: 2025-02-07T10:02:24Z D! [outputs.influxdb_v2] Buffer fullness: 0 / 10000 metrics
Feb 07 11:02:24 influxdb telegraf[775]: 2025-02-07T10:02:24Z D! [outputs.file] Buffer fullness: 0 / 10000 metrics
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Loading config: /etc/telegraf/telegraf.conf
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Starting Telegraf 1.33.1 brought to you by InfluxData the makers of InfluxDB
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Available plugins: 236 inputs, 9 aggregators, 33 processors, 26 parsers, 63 outputs, 6 secret-stores
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Loaded inputs: mqtt_consumer
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Loaded aggregators:
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Loaded processors:
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Loaded secretstores:
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Loaded outputs: file influxdb_v2
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! Tags enabled: host=influxdb
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! [agent] Config: Interval:10s, Quiet:false, Hostname:"influxdb", Flush Interval:10s
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z D! [agent] Initializing plugins
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z D! [agent] Connecting outputs
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z D! [agent] Attempting connection to [outputs.file]
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z D! [agent] Successfully connected to outputs.file
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z D! [agent] Attempting connection to [outputs.influxdb_v2]
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z D! [agent] Successfully connected to outputs.influxdb_v2
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z D! [agent] Starting service inputs
Feb 07 11:02:04 influxdb systemd[1]: Started telegraf.service - Telegraf.
░░ Subject: A start job for unit telegraf.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit telegraf.service has finished successfully.
░░ 
░░ The job identifier is 1401.
Feb 07 11:02:04 influxdb telegraf[775]: 2025-02-07T10:02:04Z I! [inputs.mqtt_consumer] Connected [tcp://192.168.10.146:1883]
Feb 07 11:02:14 influxdb telegraf[775]: mqtt_consumer,host=influxdb,topic=ems-esp/solar_data turnondiff=10,cylpumpmod=0,solarpumpmod=0,collectortemp=31.3,energytoday=15459,pumpminmod=5,heatcnt=0,climatezone=90,pumpworktime=83801,cylmaxtemp=60,m1worktime=0,collectormintemp=20,turnoffdiff=5,pump2worktime=0,energytotal=3312.1,collector1area=7,collectormaxtemp=120,energylasthour=0,solarpump2mod=0,cylbottomtemp=52.8 1738922524200126227
Feb 07 11:02:14 influxdb telegraf[775]: mqtt_consumer,host=influxdb,topic=ems-esp/boiler_data pumpmodmax=100,boil2hyston=0,pumpdelay=10,burnminperiod=10,burnmaxpower=100,burn2workmin=0,heatingpumpmod=0,boil2hystoff=0,selflowtemp=5,burnminpower=0,boilhyston=-6,maintenancetime=6000,heatingtemp=82,burnworkmin=194452,outdoortemp=19.8,curburnpow=0,curflowtemp=26.5,heatworkmin=168918,servicecodenumber=203,boilhystoff=6,selburnpow=0,heatstarts=9535,ubauptime=896104,burnstarts=12008,flamecurr=0,pumpmodmin=10 1738922524200210183
Feb 07 11:02:14 influxdb telegraf[775]: mqtt_consumer,host=influxdb,topic=ems-esp/boiler_data_ww wwcurtemp2=54,wwstarts=2473,wwsettemp=50,wwseltemp=50,wwmaxpower=100,wwstoragetemp2=54,wwhystoff=0,wwdisinfectiontemp=70,wwworkm=25534,wwcurtemp=54,wwflowtempoffset=40,wwcurflow=0,wwhyston=-5 1738922524200281498
Feb 07 11:02:14 influxdb telegraf[775]: mqtt_consumer,host=influxdb,topic=ems-esp/thermostat_data_hc1 maxflowtemp=48,comforttemp=22,remoteseltemp=0,tempautotemp=-1,targetflowtemp=0,manualtemp=30,reducetemp=0,minflowtemp=25,offsettemp=0,roominflfactor=4,fastheatup=0,noreducetemp=-31,nofrosttemp=5,summertemp=15,curroominfl=0,seltemp=22,designtemp=45,roominfluence=0,ecotemp=21 1738922524200336601
Feb 07 11:02:14 influxdb telegraf[775]: mqtt_consumer,host=influxdb,topic=ems-esp/thermostat_data intoffset=0,wwsettemplow=45,wwextra1=0,wwsettemp=60,dampedoutdoortemp=19.9,wwdisinfecttime=120,floordrytemp=0,wwchargeduration=60,minexttemp=-10 1738922524200386862
Feb 07 11:02:14 influxdb telegraf[775]: 2025-02-07T10:02:14Z D! [outputs.file] Wrote batch of 5 metrics in 194.489µs
Feb 07 11:02:14 influxdb telegraf[775]: 2025-02-07T10:02:14Z D! [outputs.file] Buffer fullness: 0 / 10000 metrics
Feb 07 11:02:14 influxdb telegraf[775]: 2025-02-07T10:02:14Z D! [outputs.influxdb_v2] Wrote batch of 5 metrics in 12.645894ms
Feb 07 11:02:14 influxdb telegraf[775]: 2025-02-07T10:02:14Z D! [outputs.influxdb_v2] Buffer fullness: 0 / 10000 metrics
Feb 07 11:02:24 influxdb telegraf[775]: 2025-02-07T10:02:24Z D! [outputs.influxdb_v2] Buffer fullness: 0 / 10000 metrics
Feb 07 11:02:24 influxdb telegraf[775]: 2025-02-07T10:02:24Z D! [outputs.file] Buffer fullness: 0 / 10000 metrics

Can somone help me to get the data into influxdb?
Do I have to adjust something in mosquitto to be able to read from homeassistant and from Telegraf?

1 post - 1 participant

Read full topic

With YAML frontend I have created a bunch of dashboards containing declutter-cards.
My problem is that I want to also be able to have “dynamic” dashboards so that they can populate their cards with entities given as input parameters.

Why? Well I have quite small on-wall Android screens that can only show 2x3 small cards. A tap on a card that represents a dimmable lamp should open up a full screen control of that dimmable entity to be easily viewed and adjusted. Then that control should be able to be close, showing the initial dashboard where the lamp card was.

I was able to make a card tap triggered popup with some card_mod stuff but the not-so-fancy Android screen is just too slow with updating that popup and doing all the DOM modification stuff.

So I tried out a full screen dashboard instead and that rendered much faster. The problem with that dashboard is that the cards will have “hard coded” entities. Instead I would like to have the entity ID as input variables.

Example of declutter-like non-working code:
Navigation from tapping a card

        tap_action:
          action: navigate
          navigation_path: /wall-panels/dimmable_lamp
          variables:
            - name: Livingroom
            - entity: light.livingroom_dimmer_lamp

Navigated dashboard

- title: '[[name]]'
  path: dimmable_lamp
  subview: true
  badges: []
  cards:
    - type: button
      show_name: false
      show_icon: true
      tap_action:
        action: toggle
      entity: '[[entity]]'
    - type: custom:mushroom-light-card
      entity: '[[entity]]'
      show_brightness_control: true
      collapsible_controls: true

Is there a way to achieve what I want with a “dynamic” dashboard?

2 posts - 1 participant

Read full topic

Hello all,

I have this recurrent issue for years… I wonder if I’m the only one or if someone has found a fix.

The issue:
My Yeelight LED bulbs 1S (YLDP13YL) all stop responding from HA after about ~1200h uptime.
A bit less actually, but I never managed to pinpoint the exact time. I would say between 1100h and 1200h, but every time I see it, it is close to 1200h.

I tried to restart HA, force wifi disconnection, disabling then enabling again LAN control on the bulbs, no luck.
The only “fix” is to power cycle the bulb.
It happens with all of them.
I’m running FW 2.1.7_0039.

Note: when it happens, it is still working more or less from Yeelight or Mi Home app, but it is slow and after a while, I lose control too from the app.

I’ll open a thread on yeelight forum too but if you have any clue or idea, I’ll be happy to read you

Thanks

1 post - 1 participant

Read full topic

I have this graphic on my front end that shows the contents of LPG gas bottles and which bank is in use.

I was using six images to show content based on rough consumption calculations.

I now have a 0-100% sensor, the value of which I’d like to use to show the bottles emptying over time.

Essentially, I suppose this amounts to a custom gauge with a coloured rectangle that increases in height with the sensor value. I can mask the rectangle to get the shape.

I can handle the graphics, but I need help creating the gauge without resorting to 100 images.

Is it possible to create such a thing?

Where can I start?

3 posts - 2 participants

Read full topic

Hi, I’m using a Tuya thermostat flashed with ESPhome and MQTT. This part works great and I can control the thermostat from the lovelace UI.
However, the thermostat has a problem by which Home assistant doesn’t know the current state of the thermostat (whether it is heating or not). This menas that the “heating” status is unreliable and uninformative.

To solve that I have a workaround: When the thermostat turns to heating it closes a contact. This contact is connected to another ESPhome device. This is the entity “termostat calefaccio”

Question is, how do I do this?

1 post - 1 participant

Read full topic