Hi! I successfully added custom font in resources and changed font in the theme’s yaml file.

Here is the code of the theme for fonts:

  # Font
  primary-font-family: 'Tektur'
  paper-font-common-base_-_font-family: "var(--primary-font-family)"
  paper-font-common-code_-_font-family: "var(--primary-font-family)"
  paper-font-body1_-_font-family: "var(--primary-font-family)"
  paper-font-subhead_-_font-family: "var(--primary-font-family)"
  paper-font-headline_-_font-family: "var(--primary-font-family)"
  paper-font-caption_-_font-family: "var(--primary-font-family)"
  paper-font-title_-_font-family: "var(--primary-font-family)"
  ha-card-header-font-family: "var(--primary-font-family)"

I can give a full code of the theme if it is necesarry.
I know, that theme’s font not applying for all cards, but I want to be sure, that it was applied for everything it can be.

1 post - 1 participant

Read full topic

I have a sensor set up that shows my room, but I want to turn that into a device tracker that I can attach to a Person so i can tell if the house is occupied.

I’ve seen other solutions that use the sensors and groups in automations but it would be nice to use the native HA Person object to do it. I want to be able to look at a panel and see who is home and who is away at a glance too.

I have this as an attempt at a device_tracker config in my config.yaml:

  device_tracker:
    - platform: mqtt
      name: stuarts_iphone_at_home
      state_topic: "espresense/devices/espresence_stuarts_iphone/+"
      source_type: bluetooth
      value_template: "{{ topic.split('/')[-1] }}"
      expire_after: 60

but I don’t see a device tracker of that name available after a restart.

device_tracker doesn’t support template as a platform which is a shame because that would work a treat.

This config for the sensor works as expected:

sensor:
    - platform: mqtt_room
      device_id: espresence_stuarts_iphone
      name: ESP Stuarts iPhone
      state_topic: espresense/devices/espresence_stuarts_iphone
      timeout: 60
      away_timeout: 120
      unique_id: espresence_stuarts_iphone

1 post - 1 participant

Read full topic

I have configured a history stat senor to track the lifespan of a UV water sanitation bulb. I have an input_button configured that I can press when I have replaced the buld and the sensor should fall back to 0:

Start:

{% set start = states('input_button.uv_lamp_reset_reset') %}
{{ iif(start in ['unknown','unavailable'],now(),start|as_datetime) }}

End:

{{ now() }}

The sensor is set up to track the state “On” of a shelly switch:

This is the state of the input button:

The sensor just remains at 0 no matter how long the bulb switch is in “On” state.

Weird thing is that I have the exactly same configuration for another maintenance tracker (burntime of a wood heating system) and that one is working perfectly fine! ojnly difference is, only difference I can think of ist taht in the case of the UV Buld tracker HA somehow added the new sensor to the Shelly device it depends on, while the heating tracker was treated as an independent senor because it relies on a state generated by a template sensor. (Even if I try skipping the dialog box where HA asks me about adding the sensor to a device, it will still do it no matter what…)

Searched around the interwebs for answers but to no avail. Tried to ask ChatGPT about it, but that was useless as expected.

Why is this not working / what am I doning wrong?
Thanks in advance for your inputs!

2 posts - 2 participants

Read full topic

time=2025-06-06T06:40:51.517-05:00 level=WARN source=ggml.go:152 msg="key not found" key=general.alignment default=32
[GIN] 2025/06/06 - 06:40:51 | 400 |   80.018179ms |      10.71.1.15 | POST     "/api/chat"

Ollama uses the /api/generate endpoint, not chat.

2 posts - 2 participants

Read full topic

Hi. I created an automation whereby when I turn on my Xbox, or more specifically when the Xbox logs into my account, the light turns on 3o minutes before sunset. I don’t know what’s going on, but it’s not working. The light itself works fine and is made with ESP32+LEDs – WLED. If you have a moment, could you take a look at my blueprint and see where the error is?

alias: Xbox On
description: “”
triggers:

• type: turned_on
  device_id: 7d2de328eccbb2533a3f0239a1163ee3
  entity_id: bff9ac68eea494aaf0b4252aafeb40fd
  domain: binary_sensor
  trigger: device
  conditions:
• condition: sun
  after: sunset
  before: sunrise
  before_offset: “-00:30:00”
  actions:
• data:
  brightness_pct: 40
  rgb_color:
  - 120
  - 0
  - 255
  effect: Solid
  action: light.turn_on
  target:
  entity_id: light.wled
  mode: single

2 posts - 2 participants

Read full topic

Hi, I’ve read the docs and various posts but everything I try doesn’t work. I can install the SNMP tools from CLI and then SNMP command works fine to the switch (enable/disable a port) but from the switch config in configuration.yaml the switch just reverts to it’s previous state with nothing in the logs ?

I’m relatively new to HA, but used it for a while, just new to heavy custom things in it.

What am I doing wrong, it’s driving me nuts. Below is my YAML

switch:

• platform: snmp
  name: “Zyxel Sw P4 (Reo)”
  host: 192.168.1.2
  version: 2c
  community: DLpublic
  baseoid: 1.3.6.1.2.1.2.2.1.7.4
  payload_on: 1
  payload_off: 0

1 post - 1 participant

Read full topic

As I have a growing need to regularly change “Volume Limit” settings across my Sonos devices I have been looking for an easier way to do this than one by one through the app. Unfortunately it does not seem like Sonos allows manipulating this setting through the exposed API, so I am thinking that I might need to look into reverse engineering the app traffic for this and then program something “the hard way” (if at all possible).
However before I get into this, is there anybody out there who might already have tried this approach or found any other way to do something like this?

(And FYI, I have already scripted automations where Home Assistant turns the volume down automatically if it is increased above certain limits at the wrong time of the day, but as this allows the music to run on high volumes for a few seconds before being turned down, this in not a good enough option for me in this case unfortunately.)

1 post - 1 participant

Read full topic

I need to run a webhook sending the image to it. However I cant seem to receive any picture. I believe the error was on the image location. Anyone will to assist?

shell_command:
  encode_snapshot: "base64 /media/tmp/snapshot_garage.jpg > /config/encoded_image.txt"

rest_command:
  send_base64_to_n8n:
    url: "http://192.168.x.x:xxxx/webhook-test/hass"
    method: POST
    headers:
      Content-Type: application/json
    payload: >
      {
        "image_base64": "{{ states('sensor.encoded_image') }}"
      }  

shell_command:
  send_base64_snapshot: >
    curl -X POST -H "Content-Type: application/json"
    -d '{"image_base64":"'"$(base64 /media/tmp/snapshot_garage.jpg)"'"}'
    http://192.168.x.x:xxxx/webhook-test/hass

4 posts - 2 participants

Read full topic

How to set the voice assistant to Portuguese? Every tutorial say that I need to select the main language on the top to view the available options for stt/tts for that language but I only see these options:

What am I missing here?

Thank you

1 post - 1 participant

Read full topic

Hello,

I need to register two (manual inputs) values throughout the day and display the history of the two to compare them.

I can’t get them automatically, so I have to input them manually.

1. The first one is a value that can go from -10 to 10, ideally it should be a slider or something I can easily choose the value rather than writing it (on mobile), it would then register the new state (value).

2. The second one, probably the easier, is a datetime. I need to be able to push a button “now”, it would register the current datetime. I currently do that with a button that trigger an automation like this:

   action: input_datetime.set_datetime
   metadata: {}
   target:
     entity_id: input_datetime.XXX
   data:
     datetime: "{{ now().strftime('%Y-%m-%d %H:%M:%S') }}"
   

Then, I’d like to put a graph that shows the evolution of the first value throughout the day, and highlight on the graph the value it was each time I pressed the “now” button. It can be “two” separate graph (as long as the axis are in sync), but I’d prefer if it was on the same.

I’m a little confused between using a input_stats or counter for (1) and how should I approach the input method for that value

Thanks in advance for your recommandations

1 post - 1 participant

Read full topic

I’ve tried to integrate Google Nest into HA. I believe I’ve filled the instructions to the letter. Paid the $5 fee. It’s only when I get to the party where I have to go to an external website. I get the following error. “Can’t link to My First Google Project”. Could it be I have wait a few hours to be able to link my project. Any thoughts?

7 posts - 2 participants

Read full topic

I’m attempting to set an automation or find a blueprint that will take into account weather outside and if there is solar gain from the sun, ie cloudy weather would adjust the air conditioning differently than the extra heat through the windows when the sun is out. Primarily upstairs.

We have in our home a large central air heat pump that is connected to a wifi programable thermostat from Honeywell. It is either in heat mode or cool mode depending on the season, but I would like to make the unit “smart” via automations in HA. We keep our home at around 21C in the summer and winter.

The issue I’m trying to solve from the “set the schedule and forget” of the current thermostat is the variations in comfort upstairs when it’s summer and the sun is out. It can be 21C on the main level and 24C upstairs at night during sunny hot days outside. What I’d like to have set up or find in a blueprint, the state of the weather outside, (maybe with a combination of temp sensors on exterior cameras) temperature and variable cloud cover and apply that to the thermostat temperature setting. Making it a degree or two cooler starting at mid day to counter the solar gain effects probably coming in through the attic into the late evening. I keep the curtains and blinds closed which helps, but this is something I do manually in the summer, and would be great to automate it to keep the family discomfort of the heat at bedtime to a minimum. Or vice versa a particular damp, cool day, shift the Honeywell to heat mode.

The blueprints I’ve seen so far haven’t an adjustment for this variation of direct sun with weather conditions. At least not that I’ve explored yet.

3 posts - 2 participants

Read full topic

I’ve been using SambaNAS to record in Frigate to a secondary drive on my HA host for some time now. I have an automation which added a bit of a delay to allow SambaNAS to startup before Frigate which was working great. Lately however, it seems that HAOS supervisor isn’t updating that SambaNAS is running for quite a few minutes after HA start-up. What’s the best way to speed this up? Or should I try something else to trigger it?

I’ve been trying various different things as I’d like Frigate to start as soon as SambaNAS does thus minimising my camera’s down time. I also want it to not start Frigate if for any reason there’s an issue with the drive as I don’t want to fill the system drive.

I’ve tried forcing HA to reload the supervisor info for SambaNAS but sometimes I think this happens too soon so it doesn’t happen any quicker than it normally does. Also sometimes it will reload it so fast that the next trigger in the sequence has already happened.

- alias: Frigate - Delay start for media mount
  id: Frigate - Delay start for media mount
  description: ""
  mode: single
  trigger:
    - trigger: homeassistant
      event: start
  condition:
    - condition: state
      entity_id: binary_sensor.frigate_full_access_running
      state: "off"
  action:
#    - wait_for_trigger:
#        - platform: state
#          entity_id: sensor.home_assistant_supervisor_cpu_percent
#      timeout: "00:05:00"
    - delay: "00:01:00"
    - action: homeassistant.reload_config_entry
      target:
        device_id: a5be72009fab739c9228879709344c38 #reloads HA Supervisor SambaNAS integration
#    - wait_for_trigger:
#        - platform: state
#          entity_id: binary_sensor.samba_nas_running
#          to: "on"
#      timeout: "00:05:00"
    - action: homeassistant.reload_config_entry
      target:
        device_id: 29dc09920ca372becfbda88d481063b0 #reloads HA System Monitor integration for sensor.disk_use_percent_frigate
    - delay: "00:00:05"
    - choose:
        - conditions:
            - condition: state
              entity_id: binary_sensor.samba_nas_running
              state: "on"
            - condition: numeric_state
              entity_id: sensor.disk_use_percent_frigate
              above: 0
          sequence:
            - service: hassio.addon_start
              data:
                addon: ccab4aaf_frigate-fa
        - conditions:
            - condition: state
              entity_id: binary_sensor.samba_nas_running
              state: "on"
            - condition: state
              entity_id: sensor.disk_use_percent_frigate
              state: "unavailable"
          sequence:
            - service: notify.mobiles
              data:
                title: "Frigate Startup Failure"
                message: "Frigate disk mount has failed"
                data:
                  ttl: 0
                  car_ui: true
                  channel: "Important"
                  priority: high
#            - service: notify.gmail
#              data_template:
#                title: "Frigate Startup Failure"
#                message: "Frigate disk mount has failed"
            - stop: "Frigate disk mount has failed"
        - conditions:
            - condition: state
              entity_id: binary_sensor.samba_nas_running
              state: "off"
            - condition: state
              entity_id: sensor.disk_use_percent_frigate
              state: "unavailable"
          sequence:
            - service: notify.mobiles
              data:
                title: "Frigate Startup Failure"
                message: "Frigate disk mount has failed"
                data:
                  ttl: 0
                  car_ui: true
                  channel: "Important"
                  priority: high
            - stop: "Frigate disk mount has failed"

1 post - 1 participant

Read full topic

I use some precense decetion per room in order to controll the lights. This seems a threat to the WAF (Waife Acceptance Factor). Because my wife keeps turning off bluetooth and wifi. I fixed precense detection at home level by using a doorsensor at the front door (when you leave and lock the house, we use the front door). After experimenting with the app as tracker (that generates notifications on her phone and after a while gets disabled), I ended up with the network scanner integration looking for the mac adress (that I have configured to be stable in the phone).

However, for a room, this is not usefull, so I use PIR sensors (Zwave Fibaro and NeoCool) , combined PIR radar devices ( Zigbee Battery Powered Presence Sensor ZG-204ZM) and some esp32 based mmWave presence detectors. PIR sensors work most of the time, but seem not allways reliable. The mmwave radar detect someone sitting still, but not allways. (for example; I mounted a mmwave esp in front of me at my desk, to avoid the lights going off when I sitting still at the desk. I also noticed the quality of the devices may vary; some of the neo coolcams seems less stable than fibaro. Philio PST02B seems the most stable Pir sensor.

What are you experiences?

I have set the time that the sensor to report motion ‘on’ for a pretty pretty short time (1 min) and used an automation triggered by the sensor ‘on’ to start a timer. At the timer off event it gets triggered again and turns off the light. The time-out is dynamicly configurable this way. I can set the ‘on’ time dynamically (shorter when at night or when a certain scene is active for example) and it is persistant when HA reboots.

Looking for suggestions to get this rock sollid and reliable enough to survive the WAF.
For example; is there a esp32 solution for using noise detection in addition? has anyone experience? (Ohh I do not install these google or other 3party mics in my home), just pure local stuff

1 post - 1 participant

Read full topic

How do I actually add my family to Home Assistant? Should I add them as persons or users? I am not sure when to use one or the other, the docs left me a bit confused…

1 post - 1 participant

Read full topic

I switched over a Zwave switch from Home Seerer to Home Assistant (HA). It went well. I added two new Zwave switches to HA. I also added two new Govee (GV) Lights to my system, but only one to HA.

These new lights (and on Fan) would come on and off at random times (10+ times a day/night). It took me a long time to figure out what was doing it. I noticed That the GV light not in HA was turning on too. that and the logs lead me to Alexa as my ghost. I wrote an automation to turn off some of these when they turn on with no Presence detected. I also removed the GV lights from Alexa and that stopped them from random on/off.

So does anyone know why Alexa is doing this?

Also I have a lot of duplicates in Alexa. Example, some from GV, then duplicated from HA. Should I remove the ones added by Govee or delete the HA version? What is best practice for HA and Alexa (and Alexa skills)?

6 posts - 3 participants

Read full topic

Hi everyone,

I’d like to request native support in ZHA for virtual button press events from the Aqara H1 EU wall switch (lumi.switch.l1aeu1) when it’s in decoupled mode.

Current Behaviour

When using this switch with the ZHA integration:

I can successfully enable decoupled mode via Zigbee cluster 0xFCC0, attribute 0x0200.

However, no zha_event or any other event is fired when the button is pressed in this mode.

There are also no entities or triggers exposed in Home Assistant when in decoupled mode.

This makes it impossible to use the switch as a wireless button unless it’s controlling the relay directly, which defeats the purpose of using it with smart bulbs or virtual automations.

Expected Behaviour

When in decoupled mode, the switch should:

Fire a zha_event (or similar) on button press.

Include basic metadata like:

{
“device_id”: “…”,
“command”: “single_press”
}

Allow users to use the switch purely as a scene controller or trigger, as supported in Zigbee2MQTT.

Additional Notes

This is currently fully supported in Zigbee2MQTT via custom converters.

There is a partial workaround using custom quirks that map cluster 0xFCC0 to XiaomiOppleCluster, which exposes a raw attribute_updated event, but:

This is not user-friendly

Not documented or intuitive

Lacks clean event names like single_press, double_press, etc.

Why This Matters

The H1 EU is one of the most popular and widely available Zigbee wall switches in the EU. Many users want to:

Use it as a wireless scene trigger

Avoid toggling the relay when using smart bulbs

Use ZHA without having to switch to Zigbee2MQTT

This feature would greatly increase the flexibility and usability of ZHA for users in Europe.

Happy to provide logs, test devices, or help with development if needed!
Thanks a lot in advance

1 post - 1 participant

Read full topic

Hello.
I have a question about the mqtt discovery mechanics.
Maybe you find my question naive, but I would like to ask before I opt for changing the code (a script provided by the Shelly)

Here is the situation.
The script I’m working with reports all or selected device sensors as a single json. Here is the complete content:

{
  "pid": 1,
  "battery": 88,
  "illuminance": 0,
  "window": 0,
  "rotation": 82.8,
  "rssi": -69
}

In certain situations, however, it reports only some of them, for example

{
  "pid": 1,
  "battery": 88,
  "rssi": -69
}

Please note, in the second message, there is the window attribute missing.
The device issue sensor configuration for the discovery as:

{
  "device": {
    "name": "macxxxxx",
    "identifiers": [
      "macxxxxx"
    ],
    "manufacturer": "Shelly",
    "model": "Door/Window BLU"
  },
  "name": "window",
  "stat_t": "blegateway/macxxxxx/telemetry",
  "uniq_id": "macxxxxx-window",
  "state_class": "measurement",
  "dev_cla": "window",
  "pl_on": 1,
  "pl_off": 0,
  "value_template": "{{ value_json.window }}"
}

During normal HA operation, the disappearance of the window attribute does not matter, which is a bit surprising to me, making me write this post.
So both messages above can follow each other, making the related binary sensor remain in a closed state.

The situation changes on HA restart. Because value_json.window refers to a nonexistent value, the sensor becomes unavailable.

I can change the way how data are reported to mqtt, making them independent from each other, thus making the window attribute always available in mqtt.

But before I do it, I would like to ask whether there is a discovery built-in option, ensuring that the state of the sensor survives HA restart.

My guess is, there is no such option. But then it leads me to question: how is it possible that making value_json.window unavailable in runtime doesn’t turn into sensor unavailability?

1 post - 1 participant

Read full topic

I’m not sure where to post this, but I think it would be a great addition to HA. I know there are other ways of doing this like using the scheduler or boolean automation but the process is not straightforward at all. Having the options under visibility would help a lot.

Days:
Checkboxes for: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday

Maybe have boxes for Weekdays / Weekends

Timeframe: 6:00am to 8:00am

An example use for this would be displaying the Time to Work and traffic map on my wife’s dashboard for her drive to work. It doesn’t need to be displayed at all times.

Or if you have buttons or scenes that you only want displayed during the day or evening.

2 posts - 2 participants

Read full topic

Hello everyone…

I am using the said integration and i had an issue a few days back where it had to unplug the usb leading to the Bluetooth dongle and accidentally plugged it back to different port…2 days later i realized and fixed it and the USB dongle is recognized again and bluetooth things do work again, besides all my Passive BLE monitor xiaomi temp/humidity sensors…flashed with the ATC firmware…i deleted one to see if it is re-finding it, but unfortunately not…
Can someone tell me how i get those back to work? I reloaded the integration, i went through the configure part…but no auto detect as they were originally.
Thx alot for any hint

1 post - 1 participant

Read full topic