2024.3: Drag 'n Drop it like it's hot! 🎉

boheme61 · March 15, 2024, 11:17pm

Try to use “state_color: true”
I think you can even “move it out” inline with/under type: , as you use it for all entities


  - type: buttons
    state_color: true

Edit:however it should be default

On the other hand, i’ve never seen/used the type: buttons , now that my eyes are opened

Hilding76 · March 16, 2024, 1:11am

I upgraded, it worked the first time to not since then, no matching logs.

boheme61 · March 16, 2024, 1:58am

Not sure what you mean by " it worked the first time "

Nor this

And with above description, beside the " no matching logs " , you have not persuaded anyone to even try to understand what you mean, and which “log-files” you looked in etc

Tockers · March 16, 2024, 2:16am

Thanks for the reply - unfortunately no dice, still no colours both inline or across the set.

boheme61 · March 16, 2024, 2:31am

Yeah, i looked it up in Docs, entities, special row elements, “buttons”
~~Tried the example there, and even tried other “native” ways, no colors indeed, in the horizontal-line of entities/buttons~~

Edit: Correction

sparkydave · March 16, 2024, 11:48am

This is how I fixed mine manually.

Blacky · March 16, 2024, 12:29pm

@sparkydave

Thanks Dave for the information. I have spoken to Allen and I believe he has fixed it. it will be out in 2024.3.2 if not I will look into this.

Thanks for your help

Blacky

sparkydave · March 16, 2024, 12:34pm

No worries. Mate, you have given far more to the HA community than me so if I can help in any way, I’m happy.

evlo · March 16, 2024, 1:07pm

Can we get option to rename individual devices in energy dashboard?
If I create entities for individual devices using template in yaml settings link etc. does not work

boheme61 · March 16, 2024, 2:16pm

Give it a unique ID & a name in yaml (where you created the sensor)

evlo · March 16, 2024, 3:12pm

but it will not open the settings of the real sensor, right? Also creating new sensor just for the energy dashboard is not practical.

boheme61 · March 16, 2024, 3:22pm

Ofcause not

Energy, is kWh (Watt used over time) , i guess your Orig-sensor is Power(W) and Not Energy(kWh)
You get (kWh), by creating a template-sensor which have this “measurement” , if you buy a Device which does not provide(kWh) you have to create a template-senor ( As the Energy Dashboard, is (for obvious reasons) Not build for “calculating” every Power-Meter into kWh

karwosts · March 16, 2024, 4:05pm

I have a PR open to provide this feature, hasn’t been accepted yet though.

evlo · March 16, 2024, 4:17pm

Don’t make assumptions. It is just the name, lot threads about this already. Every line in individual devices ends with “energy” in energy dashboard for lots of people.

boheme61 · March 16, 2024, 4:35pm

I don’t, i answered to what i thought you wanted/mend

I’m use to name/rename my device/entities to a short form, and to avoid i.e repeated words, so the “energy” in the end has never bother me , And you didn’t mention that “that” was your concern

ski522 · March 16, 2024, 8:31pm

Still having trouble with SNMP and devices on my Mikrotik with latest version, had to go back to 2024.2.5 again

nickrout · March 16, 2024, 8:48pm

Logs? GitHub issue?

ski522 · March 16, 2024, 9:04pm

I’m using Debian, updated OS. Seeing a lot of these messages in the log files:

2024-03-16 16:58:48.258 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2024-03-16 16:59:00.259 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2024-03-16 16:59:12.260 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2024-03-16 16:59:24.260 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2024-03-16 16:59:36.265 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2024-03-16 16:59:48.265 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2024-03-16 17:00:00.266 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2024-03-16 17:00:12.267 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2024-03-16 17:00:24.268 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2024-03-16 17:00:33.359 WARNING (MainThread) [homeassistant.bootstrap] Setup timed out for bootstrap - moving forward
2024-03-16 17:00:36.269 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2024-03-16 17:00:48.270 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2024-03-16 17:00:48.362 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: snmp.device_tracker, media_source, google_translate, zha.sensor, homekit_controller.sensor, waze_travel_time.sensor, zha.cover, onkyo.media_player, mqtt.ca
mera, zwave_js.sensor, light, zwave_js.number, homekit_controller.button, cover, proximity.sensor, google_translate.tts, homeassistant.scene, blueprint, nut.sensor, google_assistant, mqtt.binary_sensor, am
crest, bluetooth_adapters, mqtt.number, script, homekit_controller.climate, zha.binary_sensor, zwave_js.event, mqtt.device_tracker, siren, zha.device_tracker, device_automation, nut, network, generic, upda
te, zha.button, mqtt.light, mqtt.text, zwave_js.lock, text, mqtt.cover, shopping_list, mqtt, mqtt.valve, zwave_js.select, zha.light, zha.switch, nws.weather, zha, google_assistant.button, zha.alarm_control
_panel, amcrest.camera, input_boolean, zeroconf, application_credentials, repairs, image, binary_sensor, onboarding, hassio.sensor, camera, zha.lock, homeassistant, notify, radio_browser, mqtt.fan, mjpeg,
valve, onvif.camera, kodi.media_player, zha.select, mqtt.lawn_mower, sensor, automation, owntracks, holiday, timer, accuweather.sensor, zha.fan, accuweather.weather, onvif.sensor, websocket_api, mqtt.humid
ifier, api, zha.siren, homekit_controller, diagnostics, sun.sensor, shopping_list.todo, usb, webhook, mqtt.vacuum, mqtt.siren, select, switchbot, foscam, analytics, bluetooth, zha.update, zwave_js.update,
onvif, trace, mqtt.scene, mqtt.water_heater, input_text, todo, device_tracker, switchbot.sensor, system_health, weather, tag, persistent_notification, openweathermap.sensor, backup, accuweather, zone, cale
ndar, climate, onvif.button, nws.sensor, mqtt.climate, hassio.binary_sensor, mqtt.update, lovelace, command_line.switch, tts, counter, mqtt.image, mjpeg.camera, mqtt.event, config, input_button, cast, lawn
_mower, zwave_js.light, kodi, zha.number, season, amcrest.switch, onvif.switch, fan, foscam.camera, schedule, file_upload, input_number, input_select, smtp.notify, hassio, search, switch_as_x, homekit_cont
roller.select, alarm_control_panel, waze_travel_time, openweathermap.weather, mqtt.sensor, zwave_js.switch, season.sensor, person, generic.camera, http, logbook, lock, logger, proximity, mqtt.select, hardw
are, mqtt.alarm_control_panel, mqtt.lock, owntracks.device_tracker, group, mqtt.switch, event, holiday.calendar, onvif.binary_sensor, sun, media_player, system_log, frontend, recorder, humidifier, water_he
ater, nws, mqtt.button, command_line, switch_as_x.light, switch, mpd.media_player, scene, button, auth, zwave_js, hassio.update, zwave_js.button, zha.climate, openweathermap, input_datetime, ffmpeg, image_
upload, history, number, cast.media_player, vacuum, zwave_js.binary_sensor

ski522 · March 16, 2024, 9:40pm

Actually, think I’ll just move away from SNMP and use the Mikrotik Integration as that does seem to work for tracking users.

bdraco · March 17, 2024, 3:05am

2024.4.x will have much better logging when this happens if you enable the following in configuration.yaml:

logger:
  default: info
  logs:
    homeassistant.bootstrap: debug
    homeassistant.setup: debug
    homeassistant.loader: debug
    homeassistant.config_entries: debug