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

Losing Control of Music Assistant

$
0
0

I can’t seem to figure out why I’ll randomly loss control of music assistant. My speaker will continue to play music from my Youtube Music playlist but any attempt to control from MA results in a “Please call connect first” error message

2025-02-13 20:20:24.552 INFO (MainThread) [music_assistant.streams] Start Queue Flow stream for Queue Bedroom speaker - crossfade: False
2025-02-13 20:20:25.480 ERROR (MainThread) [music_assistant] Error doing task: Task exception was never retrieved
Traceback (most recent call last):
  File "/app/venv/lib/python3.12/site-packages/music_assistant/controllers/players.py", line 89, in wrapper
    await func(self, *args, **kwargs)
  File "/app/venv/lib/python3.12/site-packages/music_assistant/controllers/players.py", line 617, in play_media
    await player_prov.play_media(
  File "/app/venv/lib/python3.12/site-packages/music_assistant/providers/hass_players/__init__.py", line 302, in play_media
    await self.hass_prov.hass.call_service(
  File "/app/venv/lib/python3.12/site-packages/hass_client/client.py", line 178, in call_service
    raise NotConnected(msg)
hass_client.exceptions.NotConnected: Please call connect first.

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

Traceback (most recent call last):
  File "/app/venv/lib/python3.12/site-packages/music_assistant/controllers/players.py", line 91, in wrapper
    raise PlayerCommandFailed(str(err)) from err
music_assistant_models.errors.PlayerCommandFailed: Please call connect first.
2025-02-13 20:20:32.474 ERROR (MainThread) [music_assistant] Error doing task: Task exception was never retrieved
Traceback (most recent call last):
  File "/app/venv/lib/python3.12/site-packages/music_assistant/controllers/players.py", line 89, in wrapper
    await func(self, *args, **kwargs)
  File "/app/venv/lib/python3.12/site-packages/music_assistant/controllers/players.py", line 617, in play_media
    await player_prov.play_media(
  File "/app/venv/lib/python3.12/site-packages/music_assistant/providers/hass_players/__init__.py", line 302, in play_media
    await self.hass_prov.hass.call_service(
  File "/app/venv/lib/python3.12/site-packages/hass_client/client.py", line 178, in call_service
    raise NotConnected(msg)
hass_client.exceptions.NotConnected: Please call connect first.

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

Traceback (most recent call last):
  File "/app/venv/lib/python3.12/site-packages/music_assistant/controllers/players.py", line 91, in wrapper
    raise PlayerCommandFailed(str(err)) from err
music_assistant_models.errors.PlayerCommandFailed: Please call connect first.
2025-02-13 20:20:42.784 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play_pause: Please call connect first.
2025-02-13 20:20:44.955 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play_pause: Please call connect first.
2025-02-13 20:21:18.928 ERROR (MainThread) [music_assistant] Error doing task: Task exception was never retrieved
Traceback (most recent call last):
  File "/app/venv/lib/python3.12/site-packages/music_assistant/controllers/player_queues.py", line 570, in stop
    await player_provider.cmd_stop(queue_id)
  File "/app/venv/lib/python3.12/site-packages/music_assistant/providers/hass_players/__init__.py", line 242, in cmd_stop
    await self.hass_prov.hass.call_service(
  File "/app/venv/lib/python3.12/site-packages/hass_client/client.py", line 178, in call_service
    raise NotConnected(msg)
hass_client.exceptions.NotConnected: Please call connect first.
2025-02-13 20:21:22.479 ERROR (MainThread) [music_assistant] Error doing task: Task exception was never retrieved
Traceback (most recent call last):
  File "/app/venv/lib/python3.12/site-packages/music_assistant/controllers/players.py", line 89, in wrapper
    await func(self, *args, **kwargs)
  File "/app/venv/lib/python3.12/site-packages/music_assistant/controllers/players.py", line 617, in play_media
    await player_prov.play_media(
  File "/app/venv/lib/python3.12/site-packages/music_assistant/providers/hass_players/__init__.py", line 302, in play_media
    await self.hass_prov.hass.call_service(
  File "/app/venv/lib/python3.12/site-packages/hass_client/client.py", line 178, in call_service
    raise NotConnected(msg)
hass_client.exceptions.NotConnected: Please call connect first.

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

Traceback (most recent call last):
  File "/app/venv/lib/python3.12/site-packages/music_assistant/controllers/players.py", line 91, in wrapper
    raise PlayerCommandFailed(str(err)) from err
music_assistant_models.errors.PlayerCommandFailed: Please call connect first.
2025-02-13 20:21:23.601 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play_pause: Please call connect first.
2025-02-13 20:25:08.988 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play_pause: Please call connect first.
2025-02-13 20:25:10.676 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play_pause: Please call connect first.
2025-02-13 20:25:14.825 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/play_pause: Please call connect first.
2025-02-13 20:25:15.726 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/volume_set: Please call connect first.
2025-02-13 20:25:16.268 ERROR (MainThread) [music_assistant.webserver] Error handling message: players/cmd/volume_set: Please call connect first.

1 post - 1 participant

Read full topic


Define entity value so it only shows 2 decimal points instead of the 3

$
0
0

The following code, shows a BubbleCard with Entity name (Kettle) and then state being ON below, to the right it either shows current consumption for example 3,320.3 w or if its below 2 watts it just shows the daily consumption being ex. 1.2354 kWh, how do I get this value to show just 1.24 kWh instead?

type: custom:bubble-card
card_type: button
use_accent_color: true
show_state: true
show_last_changed: false
show_attribute: false
card_layout: normal
button_type: switch
slider_live_update: true
hold_action:
  action: toggle
double_tap_action:
  action: none
scrolling_effect: false
show_icon: true
icon: mdi:power
tap_action:
  action: none
grid_options:
  columns: 6
  rows: 1
button_action:
  tap_action:
    action: none
  double_tap_action:
    action: none
  hold_action:
    action: none
name: Kettle
show_name: true
styles: |-
  .bubble-button-background {
  background-color: ${state === 'on' ? '#282828' : "#ff0000"} !important;
  }
  .bubble-icon { color: ${state === 'on' ?  '#FFFFFF' : '#4C4C4C'} !important;
  }
entity: switch.sm06_kettle_7556
sub_button:
  - entity: sensor.sm06_kettle_7556_today_s_consumption
    state_background: false
    show_background: false
    show_name: false
    show_icon: false
    show_last_changed: false
    show_state: true
    visibility:
      - condition: and
        conditions:
          - condition: numeric_state
            entity: sensor.sm06_kettle_7556_current_consumption
            below: 2
          - condition: state
            entity: switch.sm06_kettle_7556
            state: "on"
card_mod:
  style: |
    ha-card {
      background-color: {% if states(config.sub_button[0].entity) | float > 5 %} #EE2722 {% else %} #282828 {% endif %} !important;
    }

3 posts - 2 participants

Read full topic

Tts.speak and tts.home_assistant_cloud volume issues

$
0
0

Im using a Sonos media player for my announcements in my place and find that the ha cloud responses are LOW in level compared to playing music.

The volume of the media player is already set to max

Any way of bumping it up???

  - action: media_player.volume_set
    metadata: {}
    data:
      volume_level: 1
    target:
      entity_id: media_player.lounge
  - action: tts.speak
    metadata: {}
    data:
      cache: false
      media_player_entity_id: media_player.lounge
      message: "{{ response.text }}"
    target:
      entity_id: tts.home_assistant_cloud

1 post - 1 participant

Read full topic

Commission matter devices to Home Assistant which runs on Raspberry PI locally using Postman client (REST API or WebSocket)

$
0
0

How to commission matter devices to Home Assistant which runs on Raspberry PI locally using Postman client (REST API or WebSocket) and How to control these devices from the same Postman client.

1 post - 1 participant

Read full topic

Connectivity Maintenance Dashboard

$
0
0

Two questions below - and thank you all for your help!

I have a huge number of sensors now in my home, and once every could of days I need to rejigger one or another thing to bring them back online or back to a properly functioning state.I would like to create a dashboard that shows a concise list (only out of a set of devices I wish to monitor, they are from different vendors) - of all those which are currently “unknown” or “unavailable”. This would be very handy to then be able to just at a glance know if anything needs attention. So here are my two questions -

As an exmple I do have for instance a sensor that shows (self explanatory):

#
# This binary sensor not only specifies if any entities in the integration are unavailable, but also if
# there are any unavailable, it will contain an attribute that is a list of the entities that are unavailable.
#
template:
  - binary_sensor:
      - name: "Any Shelly Unavailable"
        state: "{{ integration_entities('shelly') | select('is_state', 'unavailable') | list | count > 0 }}"
        attributes:
          entity_id: "{{ integration_entities('shelly') | select('is_state', 'unavailable') | list }}"
        unique_id: any_shelly_unavailable

  1. Can someone provide a sample or a template sensor or the like that I could use to figure out how to create, in one or more or a combination of (template?) sensors that would have a list of the devices and next to each, either the word unavailable or unkown and the time that it became that state?
  2. If it was done in the same manner as the above example, then how would I display attributes in a dashboard (if that is what would be needed)?

I don’t care if it is a lot of coding or if I have to type out the name of every saingle sensor in the code, once it is done then I am golden (it doesn’t need to be any kind of automatically generated list, because some I do not want to show that I would expect to be offline at certain times, etc.)…

I could create a dashboard with a gazillion cards and each card would represent a sensor and only be displayed if that sensor state is unknown or unavailable, but not only would it be ugly instead of a compact list, but I am sure there must be a more elegant way of handling this…

Thank you anyone who could help get me started or pointed in the right direction!

1 post - 1 participant

Read full topic

Drift in hue and saturation of Ikea Tradfiri bulb

$
0
0

I’ve written the following automation that generally works well for using a remote control with four buttons to control the hue and saturation of my Ikea Tradfiri color LED bulb. However, there seems to be some issue with round-trip conversion because when I repeatedly press the right/left buttons to change the hue, the saturation slowly decreases (e.g., it should remain at 100, but it slowly drops from 100 to 98.8 to 97.6 and so on each time the hue changes until the saturation gets close to 0). After doing some research, I believe this has to do with some rounding errors. Home Assistant maps hue and saturation to a narrower range of values than Zigbee’s color cluster. While this is not a show-stopper, it’s a bit annoying as I would like to be able to cycle through all the colors using the remote without the saturation dropping. Any thoughts on how I can fix this?

automation:
  - id: "nolan_light_color_cycle"
    alias: "Nolan reading light color"
    trigger:
      - platform: device
        device_id: 1f5b19e8dcb1889edffcadd2ab8b558c
        domain: zha
        type: remote_button_short_press
        subtype: left
        id: hue_down
      - platform: device
        device_id: 1f5b19e8dcb1889edffcadd2ab8b558c
        domain: zha
        type: remote_button_short_press
        subtype: right
        id: hue_up
      - platform: device
        device_id: 1f5b19e8dcb1889edffcadd2ab8b558c
        domain: zha
        type: remote_button_short_press
        subtype: turn_on
        id: sat_up
      - platform: device
        device_id: 1f5b19e8dcb1889edffcadd2ab8b558c
        domain: zha
        type: remote_button_short_press
        subtype: turn_off
        id: sat_down
      - platform: device
        device_id: 1f5b19e8dcb1889edffcadd2ab8b558c
        domain: zha
        type: remote_button_long_press
        subtype: dim_up
        id: sat_max
      - platform: device
        device_id: 1f5b19e8dcb1889edffcadd2ab8b558c
        domain: zha
        type: remote_button_long_press
        subtype: dim_down
        id: sat_min
    action:
      service: light.turn_on
      entity_id: light.nolan_reading_nook
      data:
        hs_color: >-
          {% set hue = int(state_attr('light.nolan_reading_nook', 'hs_color')[0]) %}
          {% set sat = int(state_attr('light.nolan_reading_nook', 'hs_color')[1]) %}
          {% if trigger.id == 'hue_down' %}
            {% set hue = (hue - 9) % 360 %}
          {% elif trigger.id == 'hue_up' %}
            {% set hue = (hue + 9) % 360 %}
          {% elif trigger.id == 'sat_up' %}
            {% set sat = min(sat + 5, 100) %}
          {% elif trigger.id == 'sat_down' %}
            {% set sat = max(sat - 5, 0) %}
          {% elif trigger.id == 'sat_max' %}
            {% set sat = 100 %}
          {% elif trigger.id == 'sat_min' %}
            {% set sat = 0 %}
          {% endif %}
          [{{ hue|int }}, {{ sat|int }}]

3 posts - 3 participants

Read full topic

Command Line sensor to report disk free space

$
0
0

I am trying to create a sensor that reports my free space on my frigate storage.
This command works from a command line:

➜ /bin/df -h | /bin/grep ‘/media/frigate’ | /usr/bin/awk ‘NR==1{print $3}’

114.3G

Here is how I define it in my commanline.yaml file (included from configuration.yaml)

- sensor:
    name: zeus_frigate_free_space
    command: "/bin/df -h | /bin/grep '/media/frigate' | /usr/bin/awk 'NR==1{print $3}'
"
    unit_of_measurement: "GB"

The sensor state is always “Unknown”. Am I using the awk command wrong? The output seems to have an extra line before the data.

1 post - 1 participant

Read full topic

Card layer level

$
0
0

Hello,

After several hours of troubleshooting with ChatGPT, I hope to have a bit more luck here because whatever ChatGPT tries, nothing works.
I just started creating a dashboard that is displayed on a tablet that I mounted on the wall, I use 3 main components at the moment, sidebar, bubble-card and weather card.

I made 2 pop-up buttons on the bottom of the screen, there is some gradient effect behind it, the issue is, this effect also goed over the sidebar and weather card, I would like to place the weather card on top of the bubble card so the gradient effect won’t effect weather card.

My code look likes this:

title: Home
sidebar:
  width:
    mobile: 0
    tablet: 20
    desktop: 17
  digitalClock: true
  date: true
  style: |
    :host {
        --sidebar-background: {{ 'black' if states('sun.sun') == 'below_horizon' else 'white' }}!important;
        --sidebar-text-color: {{ 'white' if states('sun.sun') == 'below_horizon' else 'black' }}!important;
        --face-color: {{ 'black' if states('sun.sun') == 'below_horizon' else 'white' }};
        --face-border-color: {{ 'black' if states('sun.sun') == 'below_horizon' else 'white' }};
        --clock-hands-color: {{ 'white' if states('sun.sun') == 'below_horizon' else 'black' }};
        --clock-seconds-hand-color: #FF4B3E;
        --clock-middle-background: {{ 'black' if states('sun.sun') == 'below_horizon' else 'white' }};
        --clock-middle-border: {{ 'white' if states('sun.sun') == 'below_horizon' else 'black' }};
    }
    .digitalClock {
      text-align: center;
      color: var(--sidebar-text-color)!important;
    }
    .date {
      font-size: 32px;
      text-align: center;
      color: var(--sidebar-text-color)!important;
    }
    .sidebarMenu li {
      font-weight: 200!important;
      background-color: var(--sidebar-background)!important;
      color: var(--sidebar-text-color)!important;
    }
    .sidebarMenu li.active {
      font-weight: 400!important;
      background-color: var(--sidebar-background)!important;
      color: var(--sidebar-text-color)!important;
    }
    /* Sidebar achtergrond verwijderen */
    ha-sidebar {
      background: var(--sidebar-background)!important;
      opacity: 1!important; /* Voorkomt transparantie */
    }
    ha-sidebar::before {
      background: none!important;
    }v
  bottomCard:
    type: weather-forecast
    cardOptions:
      name: Soesterberg
      show_forecast: true
      entity: weather.forecast_thuis
    cardStyle: |
      :host {
        width: 100%;
        position: relative;
        bottom: 0;
        left: 0;
      }
      ha-card {
        font-weight: 200;
        padding: none;
        width: 110%;
        border: none;
        overflow: hidden !important;
        box-shadow: none !important;
        ha-card-border-radius: 0px;
        margin-top: -16px;
        margin-right: -10px;
        margin-left: -10px;
        background: var(--sidebar-background)!important;
        color: var(--sidebar-text-color)!important;
      }
views:
  - title: Home
    cards:
      - type: custom:bubble-card
        card_type: pop-up
        hash: '#dreameRobot'
        button_type: name
        entity: sensor.dreamebot_x20_pro_plus_status
        name: Robot
        icon: mdi:robot-vacuum
    sections:
      - type: grid
        cards:
          - type: heading
            heading: null
          - type: vertical-stack
            cards:
              - type: custom:bubble-card
                card_type: pop-up
                hash: '#tuin'
                button_type: name
                name: Tuin
                icon: mdi:flower
              - type: custom:bubble-card
                card_type: separator
                name: Voortuin
              - type: custom:bubble-card
                card_type: separator
                name: Achtertuin
              - type: custom:bubble-card
                card_type: separator
                name: Serre
          - type: vertical-stack
            cards:
              - type: custom:bubble-card
                card_type: pop-up
                hash: '#BG'
                button_type: name
                name: Begane grond
                icon: mdi:home-floor-g
                sub_button: []
                auto_close: '15000'
              - type: custom:bubble-card
                card_type: separator
                name: Woonkamer
              - type: custom:bubble-card
                card_type: button
                button_type: state
                entity: sensor.dreamebot_x20_pro_plus_state
                name: Robot
                icon: mdi:robot-vacuum
                show_state: true
                sub_button:
                  - tap_action:
                      action: call-service
                      target:
                        entity_id: vacuum.dreamebot_x20_pro_plus
                      service: VACUUM.START
                    show_state: false
                    show_last_changed: false
                    show_attribute: false
                    icon: mdi:play
                    name: start
                    show_name: false
                  - entity: sensor.dreamebot_x20_pro_plus_state
                    name: pause
                    icon: mdi:pause
                    tap_action:
                      action: call-service
                      target:
                        entity_id: vacuum.dreamebot_x20_pro_plus
                      service: vacuum.pause
                  - name: home
                    icon: mdi:home
                    tap_action:
                      action: call-service
                      target:
                        entity_id: vacuum.dreamebot_x20_pro_plus
                      service: vacuum.return_to_base
                  - entity: switch.dreamebot_x20_pro_plus_child_lock
                    tap_action:
                      action: toggle
                      target:
                        entity_id: vacuum.dreamebot_x20_pro_plus
                      service: VACUUM.RETURN_TO_BASE
                    name: lock
          - type: custom:bubble-card
            card_type: horizontal-buttons-stack
            1_link: '#BG'
            1_name: BG
            highlight_current_view: false
            1_icon: mdi:home-floor-g
            2_link: '#tuin'
            2_name: Tuin
            2_icon: mdi:flower
    subview: true
kiosk_mode:
  non_admin_settings:
    kiosk: true

Here are some picture how it looks at the moment:


Whatever ChatGPT tries, the card will disappear when it tries to fix it. Who knows the answer to this issue?

2 posts - 2 participants

Read full topic


MQTT broker addon (Error message...disconnected, not authorized); Logs attached. How to fix?

MQTT broker addon (Error message...disconnected, not authorized); Logs attached. How do I fix?

$
0
0

Hello everyone,

Could someone help me figure out how to get these errors to stop in the mosquitto broker logs. I noticed that one of my falcon pi player lights wasn’t working properly and when I went to its internal url. There was an error message saying it was disconnected from mqtt. Below are the error messages I found in the mosquitto broker addon logs.

Looking at my broker, it looks like I haven’t created any users, which based on my reading is proper for home assistant. (so I have nothing in the “logins” section of mosquitto broker.)

When I’m looking in mqtt integration. It looks like I have used “mqtt” as user and it looks like I never changed the original password. I don’t know if this ok or not.

The thing that has me most confused about all of this is this setup worked for years and stopped probably within 6 months of now.

Also, I have a zwave device (zwave outlet that I use to help with knowing when laundry is ready to be moved to dryer) that is still properly communicating with mqtt properly through some of my manual yaml setup.–> I think this is much different than my issues being talked about here though because it looks like the things showing up in the logs below are actual physical devices (fpp device and wled device) that aren’t being allowed to talk to the broker.

How do I go about making the broker happy and allow the connections below to occur.

EDIT:
I’m reading the external ip shown below is something about “watchdog” so I guess I don’t worry about that one?

025-02-14 10:08:04: Client FPP_4172 disconnected, not authorised.
2025-02-14 10:08:07: New connection from 192.168.1.250:44760 on port 1883.

2025-02-14 10:09:53: New connection from 192.168.1.54:56902 on port 1883.
2025-02-14 10:09:53: Client WLED-6b7e24 disconnected, not authorised.

2025-02-14 10:06:01: New connection from 172.30.32.1:58718 on port 1883.
error: received null username or password for unpwd check

2025-02-14 10:06:06: New connection from 192.168.1.112:55724 on port 1883.
error: received null username or password for unpwd check
______________
2025-02-14 10:06:16: Client 6cac2c46 disconnected, not authorised.
2025-02-14 10:06:17: New connection from 172.30.32.2:46124 on port 1883.
2025-02-14 10:06:17: Client <unknown> closed its connection.

1 post - 1 participant

Read full topic

Speech-to-phrase training fails with aiohttp.client_exceptions.WSMessageTypeError

$
0
0

I’m trying to install the new add-on speech-to-text. When is start the training it fails with:

  File "/usr/src/.venv/lib/python3.11/site-packages/aiohttp/client_ws.py", line 386, in receive_str
    raise WSMessageTypeError(
aiohttp.client_exceptions.WSMessageTypeError: Received message 8:1000 is not WSMsgType.TEXT

1 post - 1 participant

Read full topic

Update 2025.2.3 - core do no start - startup fatal error

$
0
0

Hi there,
I expected a quite annoying issue by updating to 2025.2.3, i’m not anymore able to connect to the web interface (ERR_CONNECTION_REFUSED), where the CLI and observer works.
After lot of tries, it seems that the core does not anymore start.
I tried to downgrade, to rebuild, to repair the supervisor, to restart is safe mode, I usualy get the following error : No Home Assistant Core response, assuming a fatal startup error.

I also tried to setup a fresh new VMs and restore one of my backups (I tested the lastest one, but also an older one), the web interface never refesh after the restore.

I succeed to catch some logs in the supervisor in -f mode :

It seems that with the restore, the core component does not start anymore, but why ? I used a backup at a time where HA restart several times without issue.

I’m affraid I would have to reconfigure HA from 0, I’m feeling lost…

1 post - 1 participant

Read full topic

Adding VLAN to NIC - no success

$
0
0

I’m trying to add a VLAN to the NIC. Command within the termianl:

ha network vlan eth30 3 --ipv4-method auto --ipv6-method auto

I get the error-message:

Unexpected server response. Status code: 404

What’s my mistake?

Additional question:
If it works - will it survive a HA-backup/restore?

3 posts - 2 participants

Read full topic

Automation to change assist

$
0
0

Is there a way via automation to change speech-to-text or text-to-speech or conversational agent of an assist? This way I could use local voice recognition and llm while my computer is on and use cloud systems while it is off

2 posts - 2 participants

Read full topic

2 Zigbee Networks 1 Home Assistance instance?

$
0
0

The story is I have my server running in a building next to my house but the current Zigbee dongle i have ( SONOFF Zigbee 3.0 USB Dongle Plus Gateway) does not reach into my house. I have tried to run smart plugs that would be routers and it does not keep connection. Recently I went ahead and bought a new gateway to run in my house ( SMLIGHT SLZB-06 - Zigbee 3.0) while i keep the Sonoff 3.0 Dongle in the other building. Is there a way through home assistant that I will be able to have these two Zigbee networks on my single instance of Home Assistance? I am new to home assistance so I am still learning. Please help if you can I would greatly appreciate advice.
Thank you all!

4 posts - 3 participants

Read full topic


Hive - API - Error 403

$
0
0

Is anyone else having issues making changes to their Hive kit through HA? I am able to read Hive device data through the integration, but every time I try to make any kind of change (set temperature, set a device to off etc), I see in the logs that an error 403 is thrown back.

I’ve removed the integration and rebooted HA. I’ve removed all trusted devices from the Hive app then tried to re-install the integration. All devices come back okay but again, if I try to make any change, an error 403 is thrown back.

Specific error in the logs (this is an extract of, as the error log is much longer than this):

2025-02-14 15:57:54.168 | ERROR | apyhiveapi.api.hive_async_api:request:87 - Something has gone wrong calling https://beekeeper.hivehome.com/1.0/nodes/trvcontrol/1[REMOVED-FOR-PRIVACY]6 - HTTP status is - 403

2 posts - 1 participant

Read full topic

Docker Compose Traefik + HA causes websocket 404

$
0
0

I’ve been working though the forum + docs to set up Home Assistant in Docker and make it publicly available. My home lab currently uses tailscale + traefik to set up a FQDN and TLS for certs. This solution works fine for other services but for HA when I navigate to my domain root, e.g. machine.tailnet.net it will load the auth page and after a successful auth will redirect to https://machine.tailnet.net/lovelace?auth_callback=1&code=XXXXXXXXXXX&storeToken=true and display the persistent error Unable to connect to Home Assistant. Retrying in XX seconds…

Under the hood in dev tools I can see the hassTokens write to session storage. And the network tab shows a 404 error under the websocket path wss://machine.tailnet.net/api/websocket.

I created an additional issue since this differs slightly from Websockets Error 500 in traefik logs

Attached are my docker-compose files, 1x traefik + tailscale and 1x for home-assistant.

docker-compose-ts-traefik (click for more details) docker-compose-home-assistant (click for more details)

1 post - 1 participant

Read full topic

Frigate zone/loiter/recording help

$
0
0

Hi,
I’m hoping I might be able to get a bit of help? New to Frigate, and haven’t yet even contemplate HA, though the intention is to one day have both nicely integrated.

I’ve spent a long time reading documentation but still struggling with more than the most basic config.yml.

The present situation:
I have Frigate 0.15 running in a Docker container. I have one camera (front) configured. It is recording any person or car as an alert (pretty much the default config). I’m only interested in these object types and don’t want to record random motion. This much seems to work well.

I’m trying to take it to the next level but get problems.

My desired outcome:

I have defined 2 zones. “Driveway” and “Road”.
In the Driveway Zone: I want to record all moving people/cars, ignore shadows/trees, and do not want to record stationary objects.

In the Road Zone: I want to record all people, but only record cars if they remain for 7+ seconds. I want to stop recording cars once they are stationary/go beyond the 7 second loiter time. The idea is to avoid recording cars passing by normally, but have some record of cars loitering.

For both zones I want to keep qualifying recordings for 35 days.

What’s Actually happening:

All cars passing by (Road zone) are being recorded as alerts in my “Review items” as well as appearing in Explore as “tracked objects”. However, the loitering for 7 seconds requirement appears to be ignored. When exploring object lifecycle there is no zone associated with the alert. People are being recorded (correct) but similarly not associated with the Road zone.

I haven’t yet had a car enter the Driveway zone to test. However, a person is correctly recorded and appearing as a “Review item” in the Driveway zone.

I’m in well over my head with this but hope if someone can correct what I’ve got wrong it’ll start to make more sense.

Grateful to anyone who can help.

mqtt:
  enabled: false  # Disable MQTT if not using it

detectors:
  coral:
    type: edgetpu
    device: usb

ffmpeg:
  hwaccel_args:
    - -hwaccel
    - vaapi
    - -hwaccel_device
    - /dev/dri/renderD128
    - -hwaccel_output_format
    - yuv420p

cameras:
  front:
    ffmpeg:
      inputs:
        - path: rtsp://frigate:password@192.168.1.5:554/Streaming/Channels/102
          roles:
            - detect
        - path: rtsp://frigate:password@192.168.1.5:554/Streaming/Channels/101
          roles:
            - record
    detect:
      width: 640
      height: 480
      fps: 5
    objects:
      track:
        - person
        - car
    record:
      enabled: true
      retain:
        days: 35  # Keep recordings for 35 days
    snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      retain:
        default: 35  # Keep snapshots for 35 days
    motion:
      mask:
        - 0.268,0.047,0.268,0.082,0.334,0.082,0.334,0.039
        - 0.429,1,0.137,0.618,0.004,0.727,0.001,0.993
        - -0.001,0.354,0.08,0.251,0.136,0.237,0.144,0.038,0.132,0,-0.001,0.001
        - 1,0.182,0.665,0.074,0.394,0.066,0.157,0.086,0.147,0.005,0.996,0.001
        - 0.819,0.993,1,0.357,0.999,0.994
        - 0.242,0.188,0.233,0.215,0.35,0.238,0.426,0.242,0.429,0.205,0.328,0.184
      threshold: 35
      contour_area: 20
      improve_contrast: true
    zones:
      Driveway:
        coordinates: 
          0.313,0.988,0.916,1,0.956,0.428,0.885,0.374,0.686,0.32,0.695,0.294,0.457,0.221,0.44,0.193,0.416,0.154,0.235,0.137,0.112,0.149,0.002,0.28,0.003,0.761
        filters:
          person:
            min_area: 5000  # Adjust as needed to filter out false positives
          car:
            min_area: 8000  # Adjust as needed
      Road:
        coordinates: 
          0.974,0.355,1,0.107,0.657,0.009,0.521,0,0.15,0,0.147,0.111,0.429,0.155,0.452,0.214,0.688,0.282,0.766,0.318
        filters:
          person:
            min_area: 5000  # Adjust as needed
          car:
            min_area: 8000  # Adjust as needed
        loitering_time: 7  # Record cars only if they linger for 7 seconds or more
        inertia: 3

version: 0.15-1

1 post - 1 participant

Read full topic

Hue inegration rooms not available anymore

$
0
0

Hi,
I have been using the hue rooms to switch my lights since quite some time, but since a couple of days the rooms enities are unavailabe. Weirdly for one room this is not the case. Did I miss some kind of change.
The scenes for the rooms are still there.
Has anyone else the same issue?

Hope someone an idea.

Mischa

1 post - 1 participant

Read full topic

Trigger template with a condition

$
0
0

I am trying to do a template sensor that has a trigger with a condition that does an action and I’m running into formatting trouble.

I have a templates.yaml this is included from configuration.yaml. Here is what I have, but I cannot figure out where to put the condition so that it only runs on Mon-Fri:

- trigger:
  - trigger: time
    at: "08:45:00"
  condition:
    - condition: time

  action:
    - action: google_generative_ai_conversation.generate_content
      response_variable: response
      data:
        prompt: >-
          Tell me a joke

I cannot figure out how to get the condition. I’ve been following the docs and every combination of putting a condition in gives me some kind of error.

Any help would be appreciated.

1 post - 1 participant

Read full topic

Viewing all 105897 articles
Browse latest View live