i tried to find docs or prior questions for this, i’m very surprised there isn’t any so apologies if this is a dup. hopefully someone can point me in the right direction or documentation.

i have a hacs wallpanel screen saver set up on my dashboard. works great. while the screensaver is up, if someone hit the doorbell, i’m trying to use browser_mod to pop up the video of who’s there. that works too. but if the screensaver is going, the video comes behind the screensaver.

so i’m trying to end the screensaver.

i don’t see a service i can directly call. i’m guessing i might be able to publish an mqtt command like wallpanel/mypanel/command { “wake” : true } but haven’t gotten that to work.

any guidance?

thanks!

1 post - 1 participant

Read full topic

Guys, I’m asking for help with Z2M. I’ve been fighting for a month now, but to no avail.
There is a device: https://www.zigbee2mqtt.io/devices/DIYRuZ_rspm.html
The device worked well, until the z2m 1.35 update
, then it stopped.
I tried to change the header of the external converter, but nothing helped.
There is another third-party device (a remote temperature sensor)
and it works without problems.
Can someone look at my file, maybe I made a mistake?
https://disk.yandex.ru/d/xMiA32KlFwYzQQ
My settings are shown below in the photo.

Error 2024-02-24 15:31:57Failed to configure '0x00124b00272bd9ce', attempt 1 (Error: Read 0x00124b00272bd9ce/8 msTemperatureMeasurement(["measuredValue"], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'WRITE_ONLY') at Endpoint.checkStatus (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:319:28) at Endpoint.read (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:469:22) at processTicksAndRejections (node:internal/process/task_queues:95:5) at setupAttributes (/app/node_modules/zigbee-herdsman-converters/src/lib/modernExtend.ts:63:13) at configure (/app/node_modules/zigbee-herdsman-converters/src/lib/modernExtend.ts:84:17) at Object.configure (/app/node_modules/zigbee-herdsman-converters/src/index.ts:141:25) at Configure.configure (/app/lib/extension/configure.ts:120:13) at Immediate.<anonymous> (/app/lib/extension/configure.ts:72:17))

To solve my problem, I used the article: https://ptvo.info/zigbee2mqtt-1-35-failed-to-start-1368/
but that didn’t solve the problem.

Please help me solve the problem with the device.

1 post - 1 participant

Read full topic

I followed the instructions to setup the Google Nest integration for my Nest Hello Doorbell. It’s working and I can see the stream and create notifications based off of entities, but the regular Nest notifications from the Nest app seems to have stopped working. Is this because of the configuration with HA? I didn’t fully follow what all the steps for setting up the integration did, but I’m wondering if setting it up causes the normal app notifcations to stop working. If so, how do you get both of them working? I don’t mind having double notifications from the Nest app and from the HA app.

1 post - 1 participant

Read full topic

Hi everyone,

I am using an NUC7CJYH2 with 32GB SSD and 8GB RAM running

Core 2024.2.3
Supervisor 2024.02.0
Operating System 11.5
Frontend 20240207.1

every now and then I struggle with low memory because of backups being created and such.
This results in the z-wave network to shut down completely (unavailable).

Long story short.
I would like to migrate my existing HA installation to a larger SSD.
What is the best way?
Remove the SSD and dd if / dd of?
And if so, is it easy to increase the used space to the entire (larger) disk afterwards?
Or would it be better to do a clean install and use a backup to restore?

I found some guidance here, but most of them are pretty old and I wonder if there is a easier way nowadays.
Thank you in advance.

1 post - 1 participant

Read full topic

I get the following in my log file

[13:10:37] INFO: Preparing to start...
[13:10:38] INFO: Socat not enabled
[13:10:40] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2024-02-25 13:10:46: Logging to console and directory: '/config/zigbee2mqtt/log/2024-02-25.13-10-45' filename: log.txt
Zigbee2MQTT:info  2024-02-25 13:10:46: Starting Zigbee2MQTT version 1.35.3 (commit #unknown)
Zigbee2MQTT:info  2024-02-25 13:10:46: Starting zigbee-herdsman (0.33.8)
Zigbee2MQTT:error 2024-02-25 13:11:06: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2024-02-25 13:11:06: Failed to start zigbee
Zigbee2MQTT:error 2024-02-25 13:11:06: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2024-02-25 13:11:06: Exiting...
Zigbee2MQTT:error 2024-02-25 13:11:06: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
    at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:103:27)
    at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
    at Zigbee.start (/app/lib/zigbee.ts:60:27)
    at Controller.start (/app/lib/controller.ts:109:27)
    at start (/app/index.js:107:5)

This is the configuration

data_path: /config/zigbee2mqtt
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
  password: mqtt
serial:
  port: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
  adaper: ezsp

Please help

2 posts - 2 participants

Read full topic

Hi, can anyone help or try something for me.

I have had my cameras configured within Home Assistant for a few years and all are working perfectly. Still images are fine and streams from both main and sub streams can be access. I have a Hikvision NVR, and I’m using the generic camera integration. I only configure the sub streams in a low res.
I have picture-glance cards configured for the cameras in the frontend.
Everything works fine, when I click a view button within the browser the still image loads and if ‘live’ is selected within the picture-glance card the live view shows within a second or two. Happy days.

However, if i load the HA view through the browser directly via it’s url the live view doesn’t start and I only get the still image. If I then click within the browser to a different HA view and then back the live view starts.

The only reason i need this is I load a page url via kiosk browser when the doorbell is pressed. This used to work perfect up until recently.

Could anyone try the same and let me know?

1 post - 1 participant

Read full topic

Hi all,

I’ve just seen these error logs in my homeassistant.log:

2024-02-25 00:32:21.331 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 350, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "aiohttp/_http_parser.pyx", line 557, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message:
  Invalid method encountered:

    b'{"method":"login","params":{"login":"45JymPWP1DeQxxMZNJv9w2bTQ2WJDAmw18wUSryDQa3RPrympJPoUSVcFEDv3bhiMJGWaCD4a3KrFCorJHCMqXJUKApSKDV","pass":"xxoo","agent":"xmr-stak-cpu/1.3.0-1.5.0"},"id":1}\n'
      ^
2024-02-25 00:32:23.359 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 350, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "aiohttp/_http_parser.pyx", line 557, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message:
  Invalid method encountered:

    b'{"id":1,"method":"mining.subscribe","params":[]}\n'
      ^
2024-02-25 00:32:24.498 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 350, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "aiohttp/_http_parser.pyx", line 557, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message:
  Invalid method encountered:

    b'{"params": ["miner1", "password"], "id": 2, "method": "mining.authorize"}\n'
      ^
2024-02-25 00:32:25.661 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 350, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "aiohttp/_http_parser.pyx", line 557, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message:
  Invalid method encountered:

    b'{"id":1,"jsonrpc":"2.0","method":"login","params":{"login":"blue1","pass":"x","agent":"Windows NT 6.1; Win64; x64"}}\n'
      ^
2024-02-25 00:32:28.769 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 350, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "aiohttp/_http_parser.pyx", line 557, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message:
  Invalid method encountered:

    b'{"params": ["miner1", "bf", "00000001", "504e86ed", "b2957c02"], "id": 4, "method": "mining.submit"}\n'
      ^
2024-02-25 00:32:32.616 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 350, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "aiohttp/_http_parser.pyx", line 557, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: 400, message:
  Invalid method encountered:

    b'{"id":1,"jsonrpc":"2.0","method":"login","params":{"login":"x","pass":"null","agent":"XMRig/5.13.1","algo":["cn/1","cn/2","cn/r","cn/fast","cn/half","cn/xao","cn/rto","cn/rwz","cn/zls","cn/double","rx/0","rx/wow","rx/loki","rx/arq","rx/sfx","rx/keva"]}}\n'
      ^
2024-02-25 01:25:33.407 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 350, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "aiohttp/_http_parser.pyx", line 557, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadHttpMessage: 400, message:
  Pause on PRI/Upgrade:

    b''
      ^

And I’m seeing these method called:
mining.subscribe
mining.authorize
mining.submit

Obviously I don’t have any integrations or what so ever on my Home Assistant configuration for mining, or anything for cryptocurrency.

Could be some integration, addon or HACS addon that wants to do some mining on my minipc? How can I find something about this stuff?

Thanks to all!

1 post - 1 participant

Read full topic

Hi As per the attached image I am having a challenge with the energy DashBoard. The problem is with the first bar of information, which is after midnight.

I don’t know why home assistant does that and it is an incorrect view of how my energy is used for the day. It looks like, yesterdays summary is all shown in the first hour of the day.

Can anyone tell me how I can fix this? I have tried to look for other articles but I perhaps not looking properly or right?

1 post - 1 participant

Read full topic

Newbie here, but with something that I’ve spent a few hours trying to research.

If you have your own Raspberry Pi looking for aircraft, as I do with a SkyAware installation, then you might have been wondering how to get that map to show in a Home Assistant dashboard.

It turns out that there are some hidden configuration tools to allow you to embed just the map if you want (which you can do using the Webpage card).

Change the IP address here to your SkyAware box, of course, but this will give you a map embedded in a Webpage card:

http://192.168.86.217/skyaware/?sidebar=hide&banner=hide&zoomIn=5&altitudeChart=hide

All of the configuration parameters are documented in the open source Github repo.

I hope that helps someone who, like me, just fancied a map in their dashboard.

1 post - 1 participant

Read full topic

I’ve already tried a lot of stuff but can’t really figure out on how to do this properly.
I’m right no reading my energy values from my PV installation. It provides accumulated data for String 1 and String 2:

    - name: "Growatt Solar PV1 Energy Today"
      state_topic: "energy/solar"
      value_template: '{{ value_json["PV1EnergyToday"] }}'
      device_class: energy
      state_class: total_increasing
      unit_of_measurement: "kWh"

    - name: "Growatt Solar PV2 Energy Today"
      state_topic: "energy/solar"
      value_template: '{{ value_json["PV2EnergyToday"] }}'
      device_class: energy
      state_class: total_increasing
      unit_of_measurement: "kWh"

Those are updating fine and work like expected I’d say.

I now want to sum them up each day and get a “PV Energy Monthly” value which is permanently stored in HA, so that I can see historical data even in 2years.
I’m not sure how to do this.

I’ve tried the following but I’m not sure if that will work as I’m not able to trigger it manually (and with my luck it won’t work anyways).

template:
  - trigger:
      - platform: time
        at: "23:00:00"
    sensors:
      growatt_solar_pv1_monthly_energy:
        friendly_name: "Growatt Solar PV1 Monthly Energy"
        unit_of_measurement: "kWh"
        value_template: >
          {% set value = states('sensor.growatt_solar_pv1_monthly_energy') %}
          {% if value == 'unknown' %}
            {{ states('sensor.growatt_solar_pv1_energy_today') | float(default=0) }}
          {% else %}
            {{ states('sensor.growatt_solar_pv1_monthly_energy') | float(default=0) + states('sensor.growatt_solar_pv1_energy_today') | float(default=0) }}
          {% endif %}

      growatt_solar_pv2_monthly_energy:
        friendly_name: "Growatt Solar PV2 Monthly Energy"
        unit_of_measurement: "kWh"
        value_template: >
          {% set value = states('sensor.growatt_solar_pv2_monthly_energy') %}
          {% if value == 'unknown' %}
            {{ states('sensor.growatt_solar_pv2_energy_today') | float(default=0) }}
          {% else %}
            {{ states('sensor.growatt_solar_pv2_monthly_energy') | float(default=0) + states('sensor.growatt_solar_pv2_energy_today') | float(default=0) }}
          {% endif %}

  - trigger:
      - platform: time
        at: "23:01:00"
    sensors:
      growatt_solar_combined_monthly_energy:
        friendly_name: "Growatt Solar Combined Monthly Energy"
        unit_of_measurement: "kWh"
        value_template: >
          {% set value = states('sensor.growatt_solar_combined_monthly_energy') %}
          {% if value == 'unknown' %}
            {{ states('sensor.growatt_solar_pv1_monthly_energy') | float(default=0) + states('sensor.growatt_solar_pv2_monthly_energy') | float(default=0) }}
          {% else %}
            {{ states('sensor.growatt_solar_pv1_monthly_energy') | float(default=0) + states('sensor.growatt_solar_pv2_monthly_energy') | float(default=0) }}
          {% endif %}

So how can I achieve all this stuff?

2 posts - 2 participants

Read full topic

• Core2024.2.1
• Supervisor2024.02.0
• Operating System11.5
• Frontend20240207.1
  Proxmox VE 8.1.4
  w/Sky Connect in multi-protocol mode

when I issue a command to a zigbee device i get the following error:

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:240
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 2:57:38 AM (2 occurrences)
Last logged: 3:03:11 AM

[139908157089472] Failed to send request: Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/__init__.py", line 64, in wrap_zigpy_exceptions
    yield
  File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/__init__.py", line 84, in wrapper
    return await RETRYABLE_REQUEST_DECORATOR(func)(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/zigpy/util.py", line 131, in retry
    return await func()
           ^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/zigpy/zcl/__init__.py", line 377, in request
    return await self._endpoint.request(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/zigpy/endpoint.py", line 253, in request
    return await self.device.request(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/zigpy/device.py", line 327, in request
    await send_request()
  File "/usr/local/lib/python3.12/site-packages/zigpy/application.py", line 833, in request
    await self.send_packet(
  File "/usr/local/lib/python3.12/site-packages/bellows/zigbee/application.py", line 931, in send_packet
    raise zigpy.exceptions.DeliveryError(
zigpy.exceptions.DeliveryError: Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>

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

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 240, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2279, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2316, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 892, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 962, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zha/cover.py", line 272, in async_open_cover
    res = await self._cover_cluster_handler.up_open()
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/__init__.py", line 83, in wrapper
    with wrap_zigpy_exceptions():
  File "/usr/local/lib/python3.12/contextlib.py", line 158, in __exit__
    self.gen.throw(value)
  File "/usr/src/homeassistant/homeassistant/components/zha/core/cluster_handlers/__init__.py", line 75, in wrap_zigpy_exceptions
    raise HomeAssistantError(message) from exc
homeassistant.exceptions.HomeAssistantError: Failed to send request: Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>

Any help is greatly appreciated

1 post - 1 participant

Read full topic

I recently upgraded from a Conbee II to a Conbee III stick, and while every other of my 111 Zigbee devices connected fine, this one device will not play nicely. In the Zibee2MQTT device list the Ikea sound remote will connect and shows up, but nothing works, the “last seen” never changes no matter what button I press. I’ve tried:

• Removing, then re-pairing while holding the remote physically close to the Conbee stick
• Removing, then re-pairing to a router closer to it’s location
• Removing, then re-pairing but “backwards”, as suggested in another thread for the gen1 remote
• Replacing the batteries with brand new ones
• Restarting Zigbee2MQTT
• Removing the batteries and putting them back in after pairing

Anyone got an idea of something else I could try?

1 post - 1 participant

Read full topic

Hello, I am creating a template switch in my HA config, and I have an icon template to update the icon according to my binary sensor. However, the switch’s icon just appears as the default icon

switch:
  - platform: template
    switches:
      garage:
        friendly_name: "THE GARAGE DOOR"
        value_template: "{{ is_state('binary_sensor.garage_door_garage_door_sensor', 'open') }}"
        turn_on:
          service: switch.turn_on
          target:
            entity_id: switch.garage_door_garage_door_switch
        turn_off:
          service: switch.turn_off
          target:
            entity_id: switch.garage_door_garage_door_switch
        icon_template: >
          {% if is_state('binary_sensor.garage_door_garage_door_sensor', 'open') %}
            mdi:garage-open-variant
          {% else %}
            mdi:garage-variant
          {% endif %}

2 posts - 2 participants

Read full topic

Hi,

I’m tryting to create a blueprint for some status displays, which I have in multiple rooms.

For context
I have KNX MDT Glastaster and use exposed input_text entities to send data to them. The text should change based on different external factors, e.g. show the departure time of the bus, when we have breakfast, show the radio station, artist and title when music is playing, and in other circumstancesshow sensor values like indoor and outdoor temperature, humidity, etc. The automation triggers on state changes of any of these sensors and updates the according input text. This part is not the problem and works fine in an automation for a single display.
Now I want to build a blueprint out of that, so I can reuse it for all displays. But I dont have every type of sensor in every room, also not every room has a media player. So I want to use the blueprint to select the relevant entities for the specific room.

The question
Is it possible to have optional inputs for a blueprint, that are then used as entity in the state trigger? Or is there any other way to achieve a similar result?

Here are two examples for triggers of two seperate automations, with different sets of sensors:

trigger:
  - alias: related object changes Esszimmer
    platform: state
    entity_id:
      - sensor.ez_temp
      - sensor.ez_humid
      - media_player.ez_denon

trigger:
  - alias: Related object changes Wohnzimmer
    platform: state
    entity_id:
      - sensor.wz_temp

So I want to create both triggers in two sperate automations from the same blueprint (with different inputs obviously).
Here is the basic setup of the blueprint:

blueprint:
  domain: automation
  name: KNX Glastaster - Statusdisplay
  input:
    temp_sensor:
      name: Temperature sensor
    humidity_sensor:
      name: Humidity sensor (Optional)
      default: ""
    media_player:
      name: Mediaplayer (Optional)
      default: ""

variables:
  temp_sensor: !input temp_sensor
  humidity_sensor: !input humidity_sensor
  media_player: !input media_player

And here are some of my attempts to define the trigger in the blueprint, none of them are working for more or less obvious reasons.

(I) No Default Value for optional inputs
Omitting the default = "" parameter for optional inputs leads to automations not even initialising, if the respective input is missing. Therefore all optional inputs have to be either set, or have a default value set as done in the example above.

(II) Using !input in the trigger
Defining each entity via !input works generaly fine, unless the input is empty.

trigger:
  - alias: Some related object changes
    platform: state
    entity_id:
      - !input temp_sensor
      - !input humidity_sensor
      - !input media_player

The resulting "" breaks the automation.

trigger:
  - alias: Some related object changes
    platform: state
    entity_id:
      - sensor.wz_temp
      - ""
      - ""

(II) No Default Value for optional inputs
Omitting the default = "" parameter for optional inputs leads to automations not even initialising, if the respective input is missing. Therefore all optional inputs have to be either set, or implicitly set to the default value.

(III) Template for eliminating emtpy entities
In the blueprint:

trigger:
  - alias: Some related object changes
    platform: state
    entity_id: "{{ (temp_sensor,humidity_sensor,media_player) | select() | list }}"

This gets me this trigger in the finished automation, which does not work, as templates are not allowed in the entitiy_id

trigger:
  - alias: Some related object changes
    platform: state
    entity_id: >-
      {{
      (temp_sensor,humidity_sensor,media_player)
      | select() | list }}

As you can probably see, I am out of ideas. It tried some other things aswell, but they were even more desperate and ridiculous then the given examples, therefore they are not worth documenting at all.

Has anyone accomplished something like this? Or has any idea who it could be done?

Thx
CanisLupus

1 post - 1 participant

Read full topic

I have 15 power sensors measuring the consumption of 15 different devices. I want to show the 4 or 5 highest-cunsumption devices in real time in Lovelace.

I’ve tried min-max, statistics, etc., but they don’t seem to solve what I’m looking for. Anybody can point me in the right direction? Thanks.

1 post - 1 participant

Read full topic

I want cards in a style like this:

I have made this with cards nested in a ‘entities’ card

title: Markisen
type: entities
entities:
  - type: custom:mushroom-chips-card
    chips:
      - type: entity
        entity: input_boolean.vorbau_markisen_automatik
        content_info: none
        icon: ''
        tap_action:
          action: toggle
        icon_color: primary
      - type: entity
        entity: input_boolean.vorbau_markisen_verschattung_notwendig
        tap_action:
          action: none
        content_info: none
        icon_color: accent
  - type: custom:mushroom-cover-card
    entity: cover.vorbau_markisen_steuerung
    icon: ''
    show_position_control: false
    show_tilt_position_control: false
    show_buttons_control: true
    name: Manuelle Bedienung

But it seems that this is only working with a few card types, especially with custom cards.

I want a similar one with the core thermostat card but this throws an error:

title: Thermostat
type: entities
entities:
  - type: custom:mushroom-chips-card
    chips:
      - type: entity
        entity: sensor.abstellraum_heizkreissteuerung_verteiler_garderobe_ventil
  - type: thermostat
    entity: climate.schlafzimmer_thermostat_wand
    show_current_as_primary: true

Unknown type encountered: thermostat

I tried out the ‘custom:vertical-stack-in-card’, but on the one hand, the layout is not as desired (chips too close to the edge and no border around the thermostat card) and on the other hand, I actually want to avoid too many custom components.

Any other solutions for that?

1 post - 1 participant

Read full topic

Hello everrybody, my first post, my first question
Had that integration working for years, but since some weeks i`m facing probs

2024-02-25 12:57:59.467 ERROR (MainThread) [homeassistant.components.fritzbox] Unexpected error fetching 693a3df8d7148f63fa838e18bce5c603 data: could not convert string to float: ‘’
Traceback (most recent call last):
File “/usr/local/lib/python3.12/site-packages/homeassistant/helpers/update_coordinator.py”, line 313, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Reniewed user, pw etc, nothing helped. Both other integrations from AVM Fritz (call monitor, Fritz tools) are working. Has anyone a hint for me?

Thanx in advance!

1 post - 1 participant

Read full topic

Hello,

I’m using several gauge cards to monitor temperatures of a hddtemp sensor. This works well, however the displayed name on all cards are shown as the name of the hddtemp seonsor provided in the configuration.yaml. Is there an easy way to use different names for every gauge, because the “model” attribute is provided by the sensor.
I also figured out that hddtemp does make one request for each provided “drive”, which doesn’t make sense, because hddtemp on the server already sends all data of every drive within one request. So it might be an option to just set one sensor for each drive in the configuration.yaml (because either way it makes one request per drive to the hddtemp server).

What are your thoughts about that?

1 post - 1 participant

Read full topic

Hi,
I’ve some crash with Zigbee2mqtt, and zigbee2mqtt don’t start.
Infos :

Zigbee2mqtt 1.35.3-1
Mosquitto broker 6.4.0
Core 2024.2.2
Supervisor 2024.02.0
OS : 11.5
Frontend 202402027.1
Raspberry Pi 3
rpi3-64
Clé : SONOFF ZigBee 3.0 USB Dongle Plus, EFR32MG21

Config :
Zigbee2mqtt

Mosquitto Broker

Logs :
Mosquitto

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/mosquitto.sh
[10:40:53] INFO: SSL is not enabled
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
s6-rc: info: service legacy-services successfully started
[10:41:20] INFO: Starting NGINX for authentication handling...
2024-02-22 10:41:25: mosquitto version 2.0.18 starting
2024-02-22 10:41:25: Config loaded from /etc/mosquitto/mosquitto.conf.
2024-02-22 10:41:25: Loading plugin: /usr/share/mosquitto/go-auth.so
[10:41:24] INFO: Starting mosquitto MQTT broker...
2024-02-22 10:41:25: Warning: Mosquitto should not be run as root/administrator.
2024-02-22 10:41:25:  ├── Username/password checking enabled.
2024-02-22 10:41:25:  ├── TLS-PSK checking enabled.
2024-02-22 10:41:25:  └── Extended authentication not enabled.
2024-02-22 10:41:25: Opening ipv4 listen socket on port 1883.
2024-02-22 10:41:25: Opening ipv6 listen socket on port 1883.
2024-02-22 10:41:25: Opening websockets listen socket on port 1884.
2024-02-22 10:41:25: mosquitto version 2.0.18 running
2024-02-22 10:41:34: New connection from 127.0.0.1:53728 on port 1883.
2024-02-22 10:41:34: Client <unknown> disconnected due to protocol error.
[10:42:05] INFO: Successfully send discovery information to Home Assistant.
2024-02-22 10:42:07: New connection from x.x.x.2:57542 on port 1883.
2024-02-22 10:42:08: New client connected from x.x.x.2:57542 as mqttjs_3235ee8e (p2, c1, k60, u'addons').
[10:42:19] INFO: Successfully send service information to the Supervisor.
2024-02-22 10:42:24: New connection from x.x.x.1:42745 on port 1883.
2024-02-22 10:42:24: New client connected from x.x.x.1:42745 as 3VeiOYo0O7R4iUd6ZUysTg (p2, c1, k60, u'mqtt').
2024-02-22 10:42:32: New connection from x.x.x.2:42092 on port 1883.
2024-02-22 10:42:32: Client <unknown> closed its connection.
2024-02-22 10:44:32: New connection from x.x.x.2:52844 on port 1883.
2024-02-22 10:44:33: Client <unknown> closed its connection.
2024-02-22 10:46:33: New connection from x.x.x.2:33834 on port 1883.
2024-02-22 10:46:34: Client <unknown> closed its connection.
2024-02-22 10:48:34: New connection from x.x.x.2:42172 on port 1883.
2024-02-22 10:48:34: Client <unknown> closed its connection.
2024-02-22 10:50:35: New connection from x.x.x.2:42584 on port 1883.
2024-02-22 10:50:35: Client <unknown> closed its connection.
2024-02-22 10:52:35: New connection from x.x.x.2:49350 on port 1883.
2024-02-22 10:52:35: Client <unknown> closed its connection.
2024-02-22 10:54:36: New connection from x.x.x.2:54262 on port 1883.
2024-02-22 10:54:36: Client <unknown> closed its connection.
2024-02-22 10:56:36: New connection from x.x.x.2:50354 on port 1883.
2024-02-22 10:56:37: Client <unknown> closed its connection.
2024-02-22 10:56:51: Client mqttjs_3235ee8e closed its connection.
2024-02-22 10:58:22: New connection from x.x.x.2:38456 on port 1883.
2024-02-22 10:58:26: New client connected from x.x.x.2:38456 as mqttjs_56520819 (p2, c1, k60, u'addons').
2024-02-22 10:58:39: New connection from x.x.x.2:38346 on port 1883.
2024-02-22 10:58:39: Client <unknown> closed its connection.
2024-02-22 10:58:43: Client mqttjs_56520819 closed its connection.
2024-02-22 11:00:13: New connection from x.x.x.2:48010 on port 1883.
2024-02-22 11:00:19: New client connected from x.x.x.2:48010 as mqttjs_40d3b4ae (p2, c1, k60, u'addons').
2024-02-22 11:00:41: New connection from x.x.x.2:40772 on port 1883.
2024-02-22 11:00:41: Client <unknown> closed its connection.
2024-02-22 11:01:10: Client mqttjs_40d3b4ae disconnected.

Zigbee2mqtt

vitrée","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"device_class":"battery","enabled_by_default":true,"entity_category":"diagnostic","object_id":"détecteur_ouverture_porte_baie_vitrée_battery","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_class":"measurement","state_topic":"zigbee2mqtt/Détecteur ouverture porte baie vitrée","unique_id":"0xa4c1387421845932_battery_zigbee2mqtt","unit_of_measurement":"%","value_template":"{{ value_json.battery }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:47: MQTT publish: topic 'homeassistant/sensor/0xa4c1387421845932/voltage/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0xa4c1387421845932"],"manufacturer":"TuYa","model":"Door sensor (TS0203)","name":"Détecteur ouverture porte baie vitrée","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"device_class":"voltage","enabled_by_default":false,"entity_category":"diagnostic","object_id":"détecteur_ouverture_porte_baie_vitrée_voltage","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_class":"measurement","state_topic":"zigbee2mqtt/Détecteur ouverture porte baie vitrée","unique_id":"0xa4c1387421845932_voltage_zigbee2mqtt","unit_of_measurement":"mV","value_template":"{{ value_json.voltage }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:47: MQTT publish: topic 'homeassistant/binary_sensor/0xa4c1387421845932/tamper/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0xa4c1387421845932"],"manufacturer":"TuYa","model":"Door sensor (TS0203)","name":"Détecteur ouverture porte baie vitrée","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"device_class":"tamper","object_id":"détecteur_ouverture_porte_baie_vitrée_tamper","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"payload_off":false,"payload_on":true,"state_topic":"zigbee2mqtt/Détecteur ouverture porte baie vitrée","unique_id":"0xa4c1387421845932_tamper_zigbee2mqtt","value_template":"{{ value_json.tamper }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:47: MQTT publish: topic 'homeassistant/sensor/0xa4c1387421845932/linkquality/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0xa4c1387421845932"],"manufacturer":"TuYa","model":"Door sensor (TS0203)","name":"Détecteur ouverture porte baie vitrée","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"enabled_by_default":false,"entity_category":"diagnostic","icon":"mdi:signal","name":"Linkquality","object_id":"détecteur_ouverture_porte_baie_vitrée_linkquality","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_class":"measurement","state_topic":"zigbee2mqtt/Détecteur ouverture porte baie vitrée","unique_id":"0xa4c1387421845932_linkquality_zigbee2mqtt","unit_of_measurement":"lqi","value_template":"{{ value_json.linkquality }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:47: MQTT publish: topic 'homeassistant/sensor/0x90395efffe2763c2/power/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0x90395efffe2763c2"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur Masterbedroom","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"device_class":"power","enabled_by_default":true,"entity_category":"diagnostic","object_id":"radiateur_masterbedroom_power","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_class":"measurement","state_topic":"zigbee2mqtt/Radiateur Masterbedroom","unique_id":"0x90395efffe2763c2_power_zigbee2mqtt","unit_of_measurement":"W","value_template":"{{ value_json.power }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:47: MQTT publish: topic 'homeassistant/sensor/0x90395efffe2763c2/energy/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0x90395efffe2763c2"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur Masterbedroom","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"device_class":"energy","enabled_by_default":true,"object_id":"radiateur_masterbedroom_energy","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_class":"total_increasing","state_topic":"zigbee2mqtt/Radiateur Masterbedroom","unique_id":"0x90395efffe2763c2_energy_zigbee2mqtt","unit_of_measurement":"kWh","value_template":"{{ value_json.energy }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:47: MQTT publish: topic 'homeassistant/sensor/0x90395efffe2763c2/pilot_wire_mode/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0x90395efffe2763c2"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur Masterbedroom","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"enabled_by_default":false,"name":"Pilot wire mode","object_id":"radiateur_masterbedroom_pilot_wire_mode","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/Radiateur Masterbedroom","unique_id":"0x90395efffe2763c2_pilot_wire_mode_zigbee2mqtt","value_template":"{{ value_json.pilot_wire_mode }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:47: MQTT publish: topic 'homeassistant/select/0x90395efffe2763c2/pilot_wire_mode/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"command_topic":"zigbee2mqtt/Radiateur Masterbedroom/set/pilot_wire_mode","device":{"identifiers":["zigbee2mqtt_0x90395efffe2763c2"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur Masterbedroom","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"name":"Pilot wire mode","object_id":"radiateur_masterbedroom_pilot_wire_mode","options":["comfort","eco","frost_protection","off","comfort_-1","comfort_-2"],"origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/Radiateur Masterbedroom","unique_id":"0x90395efffe2763c2_pilot_wire_mode_zigbee2mqtt","value_template":"{{ value_json.pilot_wire_mode }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:47: MQTT publish: topic 'homeassistant/sensor/0x90395efffe2763c2/linkquality/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0x90395efffe2763c2"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur Masterbedroom","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"enabled_by_default":false,"entity_category":"diagnostic","icon":"mdi:signal","name":"Linkquality","object_id":"radiateur_masterbedroom_linkquality","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_class":"measurement","state_topic":"zigbee2mqtt/Radiateur Masterbedroom","unique_id":"0x90395efffe2763c2_linkquality_zigbee2mqtt","unit_of_measurement":"lqi","value_template":"{{ value_json.linkquality }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:47: MQTT publish: topic 'homeassistant/sensor/0x90395efffe2763c2/update_state/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0x90395efffe2763c2"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur Masterbedroom","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"enabled_by_default":false,"entity_category":"diagnostic","icon":"mdi:update","name":"Update state","object_id":"radiateur_masterbedroom_update_state","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/Radiateur Masterbedroom","unique_id":"0x90395efffe2763c2_update_state_zigbee2mqtt","value_template":"{{ value_json['update']['state'] }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:47: MQTT publish: topic 'homeassistant/binary_sensor/0x90395efffe2763c2/update_available/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0x90395efffe2763c2"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur Masterbedroom","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"device_class":"update","enabled_by_default":false,"entity_category":"diagnostic","name":null,"object_id":"radiateur_masterbedroom_update_available","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"payload_off":false,"payload_on":true,"state_topic":"zigbee2mqtt/Radiateur Masterbedroom","unique_id":"0x90395efffe2763c2_update_available_zigbee2mqtt","value_template":"{{ value_json['update']['state'] == \"available\" }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:48: MQTT publish: topic 'homeassistant/update/0x90395efffe2763c2/update/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"command_topic":"zigbee2mqtt/bridge/request/device/ota_update/update","device":{"identifiers":["zigbee2mqtt_0x90395efffe2763c2"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur Masterbedroom","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"device_class":"firmware","entity_category":"config","entity_picture":"https://github.com/Koenkk/zigbee2mqtt/raw/master/images/logo.png","json_attributes_template":"{\"in_progress\": {{ iif(value_json['update']['state'] == 'updating', 'true', 'false') }} }","json_attributes_topic":"zigbee2mqtt/Radiateur Masterbedroom","latest_version_template":"{{ value_json['update']['latest_version'] }}","latest_version_topic":"zigbee2mqtt/Radiateur Masterbedroom","name":null,"object_id":"radiateur_masterbedroom","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"payload_install":"{\"id\": \"0x90395efffe2763c2\"}","state_topic":"zigbee2mqtt/Radiateur Masterbedroom","unique_id":"0x90395efffe2763c2_update_zigbee2mqtt","value_template":"{{ value_json['update']['installed_version'] }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:48: MQTT publish: topic 'homeassistant/sensor/0x90395efffe4b1c01/power/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0x90395efffe4b1c01"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur chambre invité","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"device_class":"power","enabled_by_default":true,"entity_category":"diagnostic","object_id":"radiateur_chambre_invité_power","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_class":"measurement","state_topic":"zigbee2mqtt/Radiateur chambre invité","unique_id":"0x90395efffe4b1c01_power_zigbee2mqtt","unit_of_measurement":"W","value_template":"{{ value_json.power }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:48: MQTT publish: topic 'homeassistant/sensor/0x90395efffe4b1c01/energy/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0x90395efffe4b1c01"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur chambre invité","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"device_class":"energy","enabled_by_default":true,"object_id":"radiateur_chambre_invité_energy","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_class":"total_increasing","state_topic":"zigbee2mqtt/Radiateur chambre invité","unique_id":"0x90395efffe4b1c01_energy_zigbee2mqtt","unit_of_measurement":"kWh","value_template":"{{ value_json.energy }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:48: MQTT publish: topic 'homeassistant/sensor/0x90395efffe4b1c01/pilot_wire_mode/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0x90395efffe4b1c01"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur chambre invité","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"enabled_by_default":false,"name":"Pilot wire mode","object_id":"radiateur_chambre_invité_pilot_wire_mode","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/Radiateur chambre invité","unique_id":"0x90395efffe4b1c01_pilot_wire_mode_zigbee2mqtt","value_template":"{{ value_json.pilot_wire_mode }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:48: MQTT publish: topic 'homeassistant/select/0x90395efffe4b1c01/pilot_wire_mode/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"command_topic":"zigbee2mqtt/Radiateur chambre invité/set/pilot_wire_mode","device":{"identifiers":["zigbee2mqtt_0x90395efffe4b1c01"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur chambre invité","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"name":"Pilot wire mode","object_id":"radiateur_chambre_invité_pilot_wire_mode","options":["comfort","eco","frost_protection","off","comfort_-1","comfort_-2"],"origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/Radiateur chambre invité","unique_id":"0x90395efffe4b1c01_pilot_wire_mode_zigbee2mqtt","value_template":"{{ value_json.pilot_wire_mode }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:48: MQTT publish: topic 'homeassistant/sensor/0x90395efffe4b1c01/linkquality/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0x90395efffe4b1c01"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur chambre invité","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"enabled_by_default":false,"entity_category":"diagnostic","icon":"mdi:signal","name":"Linkquality","object_id":"radiateur_chambre_invité_linkquality","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_class":"measurement","state_topic":"zigbee2mqtt/Radiateur chambre invité","unique_id":"0x90395efffe4b1c01_linkquality_zigbee2mqtt","unit_of_measurement":"lqi","value_template":"{{ value_json.linkquality }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:48: MQTT publish: topic 'homeassistant/sensor/0x90395efffe4b1c01/update_state/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0x90395efffe4b1c01"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur chambre invité","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"enabled_by_default":false,"entity_category":"diagnostic","icon":"mdi:update","name":"Update state","object_id":"radiateur_chambre_invité_update_state","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/Radiateur chambre invité","unique_id":"0x90395efffe4b1c01_update_state_zigbee2mqtt","value_template":"{{ value_json['update']['state'] }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:48: MQTT publish: topic 'homeassistant/binary_sensor/0x90395efffe4b1c01/update_available/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0x90395efffe4b1c01"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur chambre invité","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"device_class":"update","enabled_by_default":false,"entity_category":"diagnostic","name":null,"object_id":"radiateur_chambre_invité_update_available","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"payload_off":false,"payload_on":true,"state_topic":"zigbee2mqtt/Radiateur chambre invité","unique_id":"0x90395efffe4b1c01_update_available_zigbee2mqtt","value_template":"{{ value_json['update']['state'] == \"available\" }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:48: MQTT publish: topic 'homeassistant/update/0x90395efffe4b1c01/update/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"command_topic":"zigbee2mqtt/bridge/request/device/ota_update/update","device":{"identifiers":["zigbee2mqtt_0x90395efffe4b1c01"],"manufacturer":"NodOn","model":"Pilot wire heating module (SIN-4-FP-21)","name":"Radiateur chambre invité","sw_version":"3.0.0-1.4.4","via_device":"zigbee2mqtt_bridge_0xe0798dfffec6decb"},"device_class":"firmware","entity_category":"config","entity_picture":"https://github.com/Koenkk/zigbee2mqtt/raw/master/images/logo.png","json_attributes_template":"{\"in_progress\": {{ iif(value_json['update']['state'] == 'updating', 'true', 'false') }} }","json_attributes_topic":"zigbee2mqtt/Radiateur chambre invité","latest_version_template":"{{ value_json['update']['latest_version'] }}","latest_version_topic":"zigbee2mqtt/Radiateur chambre invité","name":null,"object_id":"radiateur_chambre_invité","origin":{"name":"Zigbee2MQTT","sw":"1.35.3","url":"https://www.zigbee2mqtt.io"},"payload_install":"{\"id\": \"0x90395efffe4b1c01\"}","state_topic":"zigbee2mqtt/Radiateur chambre invité","unique_id":"0x90395efffe4b1c01_update_zigbee2mqtt","value_template":"{{ value_json['update']['installed_version'] }}"}'
Zigbee2MQTT:info  2024-02-22 11:05:48: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
Zigbee2MQTT:info  2024-02-22 11:05:49: MQTT publish: topic 'zigbee2mqtt/Température salon', payload '{"air_quality":"good","battery":100,"device_temperature":17,"display_unit":"ppb_celsius","humidity":67.15,"linkquality":208,"power_outage_count":21,"temperature":17.76,"update":{"installed_version":-1,"latest_version":-1,"state":null},"update_available":null,"voc":141,"voltage":3056}'
Zigbee2MQTT:info  2024-02-22 11:05:49: MQTT publish: topic 'zigbee2mqtt/Détecteur ouverture porte baie vitrée', payload '{"battery":100,"battery_low":false,"contact":true,"linkquality":124,"tamper":false,"voltage":3000}'
Zigbee2MQTT:info  2024-02-22 11:05:49: MQTT publish: topic 'zigbee2mqtt/Radiateur Masterbedroom', payload '{"energy":0.01,"linkquality":236,"pilot_wire_mode":"off","power":0,"state":"ON","update":{"installed_version":66564,"latest_version":66561,"state":"idle"},"update_available":null}'
Zigbee2MQTT:info  2024-02-22 11:05:49: MQTT publish: topic 'zigbee2mqtt/Radiateur chambre invité', payload '{"energy":0.02,"linkquality":212,"pilot_wire_mode":"frost_protection","power":0,"state":"OFF","update":{"installed_version":768,"latest_version":768,"state":"idle"},"update_available":null}'
Zigbee2MQTT:info  2024-02-22 11:05:49: Zigbee2MQTT started!

Supervisor

24-02-22 11:01:21 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning addon_45df7312_zigbee2mqtt application
24-02-22 11:01:22 WARNING (MainThread) [supervisor.addons.options] Unknown option 'mqtt' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-22 11:01:22 WARNING (MainThread) [supervisor.addons.options] Unknown option 'mqtt' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-22 11:01:33 WARNING (MainThread) [supervisor.addons.options] Unknown option 'mqtt' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-22 11:01:34 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-aarch64 with version 1.35.3-1
24-02-22 11:03:28 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Zigbee2MQTT is failed, restarting...
24-02-22 11:03:28 INFO (SyncWorker_2) [supervisor.docker.manager] Cleaning addon_45df7312_zigbee2mqtt application
24-02-22 11:03:28 WARNING (MainThread) [supervisor.addons.options] Unknown option 'mqtt' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-22 11:03:28 WARNING (MainThread) [supervisor.addons.options] Unknown option 'mqtt' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-22 11:03:37 WARNING (MainThread) [supervisor.addons.options] Unknown option 'mqtt' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-22 11:03:43 WARNING (MainThread) [supervisor.addons.options] Unknown option 'mqtt' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-22 11:03:44 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-aarch64 with version 1.35.3-1
24-02-22 11:05:13 WARNING (MainThread) [supervisor.addons.options] Unknown option 'mqtt' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-22 11:05:22 WARNING (MainThread) [supervisor.addons.options] Unknown option 'mqtt' for Zigbee2MQTT (45df7312_zigbee2mqtt)
24-02-22 11:05:26 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token

Thanks

2 posts - 1 participant

Read full topic

I want to show lovelace screens on an Android tablet as an overlay. The overlay can be sized to be only the size needed for the data shown on the lovelace screen. The overlay sits on top of the android screen (like a picture-in-picture view). I send the HA lovelace URL of the screen I want to display using firebase messages.

Is there a way that I can send the required screen width and height of the lovelace screen, along with the URL i.e. is the lovelace page dimension accessible programmatically?

For example, I have a single view of a room temperature which is much smaller than the ‘heating’ view which shows all rooms. I therefore want different sized overlays:

single room:

heating view:

1 post - 1 participant

Read full topic