Automations work but logbook and dashboards fail?

Configuration
1

I’ve got a weird one here…

I have several Home Assistant automations running perfectly well through my Ikea hub for a very long time. Examples: Laundry door opens with Aqara door sensor, the Ikea light panel turns on; motion is detected at my desk with EP1, the Ikea lamp turns on. All automations are working as expected all the time.

However recently, the logbook does not show any state changes for these devices (other devices appear fine). I have only noticed the issue with Ikea devices so far. Also, the state changes are not reflected on the dashboard. Changing the light state (on/off) using the dashboard fails and does not change the lights. If I reload the Ikea integration, the dashboards and logbook entries will work again, but just for a while. Again, the super-weird part: all automations work fine all the time.

The only thing that has changed recently is that 2024.05 was installed.

Issue summary:

  1. Recently installed 2024.05
  2. All automations work
  3. Logbook entries of state changes are absent
  4. Dashboard commands fail periodically
  5. Automations continue to work
  6. Reloading integration resolves issues temporarily

Has anyone else encountered this? What could be the problem and how I do I fix it?

Thank you for your help!

Current Config:
Core: 2024.5.2
Supervisor: 2024.05.1
Operating System: 12.3
Frontend: 20240501.1

2

Errors in your system log?

3

Nothing there seems obviously wrong. There are no direct entries naming the Ikea devices that are showing symptoms; the only Ikea errors revolve around devices that are not longer on the network.

What are some suggested keywords (besides “ikea”) to search for in the error log?

4

Share your full error log.

5

Let me know if this link works (prepare for lots of Roborock errors):

[link removed]

6

Blocked where I am at the moment. This works: https://hatebin.com/

7

That one is not working for me. How about this?

8

:astonished:

That is one sick installation. I don’t know where to start.

Fix all your templates.

Disable the vacuums.

Report this:

2024-05-08 10:10:21.181 WARNING (MainThread) [homeassistant.core] Something is blocking Home Assistant from wrapping up the start up phase. We’re going to continue anyway. Please report the following info at https://github.com/home-assistant/core/issues: govee_ble, map, matter.sensor, vacuum, hue.binary_sensor, binary_sensor, synology_dsm.sensor, matter.switch, proximity, stream, mqtt.number, reolink, roborock, my, deconz.number, met.weather, speedtestdotnet.sensor, tile.device_tracker, esphome, bluetooth, deconz, litterrobot.sensor, humidifier, tasmota.light, broadlink.remote, ping.binary_sensor, websocket_api, auth, roku.binary_sensor, counter, sun.sensor, input_button, logbook, device_automation, input_text, uptime, http, ecobee.climate, lock, deconz.siren, matter.cover, pi_hole.sensor, mqtt.sensor, image_upload, tile, weather, siren, homekit_controller.switch, ping.sensor, person, default_config, nanoleaf.button, matter, zone, ecobee, systemmonitor.binary_sensor, tplink.switch, mqtt_room.sensor, device_tracker, ipp, zeroconf, matter.lock, energy.sensor, event, cloud.stt, smartthinq_sensors, tasmota.switch, esphome.binary_sensor, deconz.select, denonavr.media_player, homeassistant, onboarding, update, conversation, system_log, esphome.sensor, systemmonitor, reolink.number, reolink.update, bluetooth_adapters, matter.event, uptime.sensor, litterrobot.vacuum, system_health, mqtt.button, group.cover, esphome.update, tasmota.sensor, switch, esphome.number, reolink.binary_sensor, hassio.update, brother, minecraft_server, group.light, tradfri.cover, hacs, ipp.sensor, pi_hole, esphome.select, hue.event, hue.sensor, synology_dsm.binary_sensor, dhcp, zha, deconz.sensor, tasmota.fan, deconz.climate, ecobee.notify, media_player, reolink_dev, radio_browser, matter.binary_sensor, api, deconz.cover, repairs, hue.scene, wake_word, matter.climate, govee_ble.sensor, met, switch_as_x.light, roku.remote, mqtt.switch, thread, logger, template.sensor, deconz.button, reolink.button, mobile_app.sensor, cast.media_player, litterrobot.switch, synology_dsm.button, tradfri.switch, stt, scene, tag, wled, diagnostics, input_select, brother.sensor, roku.sensor, homeassistant_alerts, broadlink.sensor, reolink.light, deconz.lock, group, mobile_app, litterrobot.update, automation, backup, sun, systemmonitor.sensor, history, reolink.sensor, cover, select, input_number, ibeacon.sensor, onvif.button, onvif.switch, roku, cast, tradfri, synology_dsm.switch, synology_srm.device_tracker, homekit_controller, min_max, deconz.scene, blueprint, trace, denonavr, pi_hole.update, mqtt.binary_sensor, lovelace, synology_dsm.camera, ecobee.humidifier, synology_dsm.update, sensor, media_source, deconz.fan, broadlink.switch, hue.switch, tplink, tasmota.binary_sensor, zwave_js, hardware, ibeacon.device_tracker, fan, ibeacon, hassio, esphome.switch, reolink.select, cloud, timer, config, broadlink, deconz.alarm_control_panel, threshold, tradfri.light, file_upload, analytics, cloud.tts, script, matter.light, deconz.binary_sensor, onvif, esphome.light, tpms_ble, litterrobot.binary_sensor, notify, pi_hole.binary_sensor, litterrobot, esphome.button, template, energy, tplink.sensor, webhook, climate, input_datetime, homeassistant.scene, ping, mobile_app.device_tracker, cloud.binary_sensor, threshold.binary_sensor, hue, intent, light, remote, onvif.sensor, number, tradfri.fan, mobile_app.binary_sensor, alarm_control_panel, ecobee.binary_sensor, application_credentials, dlna_dmr.media_player, search, roku.select, pi_hole.switch, deconz.switch, reolink.switch, tpms_ble.sensor, network, ecobee.sensor, tts, speedtestdotnet, dlna_dmr, recorder, time_date.sensor, dlna_dms, button, frontend, proximity.sensor, nanoleaf.light, schedule, tradfri.sensor, tplink.light, switch_as_x, synology_dsm, roku.media_player, homekit_controller.button, reolink.camera, homekit_controller.media_player, input_boolean, litterrobot.select, hacs.sensor, hassio.binary_sensor, influxdb, tasmota.cover, onvif.camera, tasmota, deconz.light, hue.light, fitbit.sensor, assist_pipeline, hassio.sensor, camera, persistent_notification, ffmpeg, ping.device_tracker, onvif.binary_sensor, usb, ecobee.weather, ssdp, ecobee.number, mobile_app.notify, mqtt, reolink.siren, min_max.sensor, nanoleaf The system is waiting for tasks: {<Task pending name=‘Task-3283’ coro=<HacsBase.startup_tasks() running at /config/custom_components/hacs/base.py:695> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()]> cb=[set.remove()]>}

9

sick as in awesome or sick as in injured?

10

The latter.

11

I thought it was awesome… :cry:

The templates are based on examples I found in various spots. What is a good example of a bad template and how should I fix it?

I have this running so that there is a button I can press to start the vacuum in the room the button was pressed. It works right now. How should this be fixed?

What should the report look like and include? The entire log? Just copy/paste what you have quoted should be good enough?

Thank you for your help!

12

Here is an example you need to fix. The error tells you what is wrong:

2024-05-08 10:09:59.228 ERROR (MainThread) [homeassistant.components.template.template_entity] TemplateError(‘ValueError: Template error: float got invalid input ‘None’ when rendering template ‘{{ ((state_attr(‘media_player.desk_speakers’,‘volume_level’)) | float * 100) | round(2) }}’ but no default was specified’) while processing template ‘Template<template=({{ ((state_attr(‘media_player.desk_speakers’,‘volume_level’)) | float * 100) | round(2) }}) renders=4>’ for attribute ‘_attr_native_value’ in entity ‘sensor.desk_speakers_volume’

Either supply a default value or use an availability template to prevent the error.

I have no idea but this should not be happening repeatedly:

2024-05-08 10:10:53.244 WARNING (MainThread) [homeassistant.components.roborock] Not setting up S7 Max Ultra because we could not get the network information of the device. Please confirm it is online and the Roborock servers can communicate with it
2024-05-08 10:10:53.245 WARNING (Thread-115 (_thread_main)) [roborock.cloud_api] [S7 Max Ultra] A network protocol error occurred when communicating with the broker.
2024-05-08 10:10:53.377 ERROR (Thread-17 (_thread_main)) [roborock.cloud_api] [S7 Max Ultra] Failed to connect (Unknown error.)

Just the error I quoted.

13

The issue has now been reported.

Is there a log analyzing tool that will help summarize the mountain of entries in the error log?

14

I think I have the same issue: on 2024.5.0 everything is working fine, but as soon as I install a higher version then my energy dashboard disappears (and I believe I get issues with the logbook). Will dive deeper and submit logs.