2026.1: Home is where the dashboard is đŸ„‚

I see signs about it in various places. For example the roadmap mentions devices twice (device-based automation suggestions and device dashboard and device pages). Edit: actually it’s three times, that roadmap even introduced a whole separate row titled “devices”. I think that’s saying how the people setting up the direction of HA address thinking about this.

To be clear, I’m not saying entities will be removed, nothing like that, just that the suggested way of doing things will be through devices, more and more.

I think you “mix up” 2 Kinds of Devices(in those text you refer to), Devices used In HA-context / Devices used for HA

To be honest, This has Nothing to do with this Release (Device’s in Top has not changed, and it’s not New)

And Yes THIS topic has been “discussed” several times and several Topics/Forums 
AND you are very aware of this !
So Using this Release to bring it up here also, starting a Discussion Here , is just NOISE, Start a new Topic, don’t report a FR, cause im sure such already exist NOISE

They also have „The FĂŒhrer“-Voices as well as „Kanacken Weib“ 
 not gonna use it.

System came back after update but was really really really slow and the console shows this error:

I had to restart some module manually and all seems to work fine
 just slow.

Searching the web I found the same kind of error messages & slowness with previous updates but couldn’t find the root cause.

which storage are you using ? SD, SSD or ?

Another thing i find “not good”(but that’s me) I Do like and prefer short names in codes( but min 3 , and in particular in HA
Just make sure you don’t happen to name another Device, or some IOT device, per default broadcasts 
 hey im ha

1 Like

Your disk is not responding or timing out. What storage are you on? If it isn’t soldered or included in the compute module, (mentally) start preparing to replace it.

2 Likes

Could be similar, not sure about his “conclusions”

I don’t understand what you mean by this distinction. I was referring to devices as things you integrate into HA, like a switch, a light, or your car.

A Main reason when we talk about/say a/my Device it’s because it is !. i.e i want my light on, i want my heater on etc. etc. etc. no one says i want my entity on, and that’s the primary reason why Device is commonly used, and is still in top in i.e Automations
You mention Device-Dashboard, why ? , there are 2 kind of “Device Dashboards”, 1. For Devices you have in HA, 2. For Devices you view HA on.
Anyone of above you would like to call entity-Dashboards ?
What i mean is , if have no clue how you came to your Conclusions , by reading some Text, talking about Devices, it’s a “normal phrase”

Yes i was glad when i found out to “Rename an entity, to reflect My Device”
And Yes, in Automation, in “unstructured” moments i have happened to click the Device to, spite i clearly know it’s the Device’s entity i want(spite it only have 1 entity/trigger) , thou i normally just make a rough “overview” of my automations in UI, and go to Yalm-Mode, to figure out the rest(so no harm done)

There is a Natural, mentally and technically Hierarchy. Device(ID)-Entities(IDs)-attributes(IDs) Etc, most users relative fast learn this , you did, i did , And we also got frustrated 1st times we “discovered” those DeviceID’s, which might only have 1 trigger-function i.e On/Off ( Main-State of the Device ) If not only function/states.

New users and “unfortionally” also alot others, will only have their Devices to i.e Turn-on/of, they don’t think Or care about, the technique behind the UI/Device.
A Thermometer is another case/Device, as it can have many Triggers :grin:( No problem, just click and choose which )
The Tab/Click generation (no offense) just want things to work, with a click, no to much technical terms or peculiar program-language(feed me a spoon or i stave)

How would you ever be able to change/satisfy these various peoples way of thinking/living ?
It’s a learning-latter, either you stay on 1st-level, or you climb slowly further, Nature-Behavior.

Are you annoyed about “Device” is on top ? , Are you annoyed by people using it(instead of entity) intentionally or unaware (most likely last option :slight_smile: ?

Would it be better with a “pamphlet” explaining the differences, before they can go any further ?

Take the Thermometer ( try your self in the UI chose Device vs Entity), pretend you just recently learned HA, you just added your Temp Device, got a nice Card on your DeviceDashboard( Home) :grin: You figured out to name the device, you have no clue where all the other “stuff” is “hidden”, Your Device shows Temp, Humid, Battery.

You click Automation
Should UI editor After User Choosing My-Temp-Device then choosing the entity (i.e Humid) revert/change to that entity-name 
 sure sounds cool
Also check the “simplicity”(and actually weird difference) choosing Device, vs entities (when you as new user not know much about automations etc) You know the name of your Device

It’s actually amazing how the UI User-Friendliness has “developed”
And most likely someone could make it “code-clean” by replacing the id’s with it’s name upon save

Luckily, i can use it the way it is, and before i click Save, i can change the entity.id, and delete device.id

1 Like

Agree, I couldn’t understand how I could change the time periods after the update. There it was lurking in the bottom, almost invisible, finding it only after looking through the change history for 2026.1. It should have been in top, or in the energy dashboard title bar.

The U59 Pro’s were sadly junk ,for me anyway . I had 2 and they both died in less then 2 years each. Under HAOS it also used to constantly spit out CLI messages about the onboard BT adapter for years until finally HA included a kernel with support for it
 I moved on to the a different brand. My SER7 also has issues with the network timing out overnight which support were unable to fix. I would not recommend the brand anymore ,and definitely not for a a 24/7 critical use like HAOS.

Im not aware of what Hardware Alian(i answered to) have, but with your “tuning in” i sounds like he have to check his Hardware also,
People can always Post a FeatureRequest in Github for support of i.e network-cards etc, but im sure there are very low chances = 0 that they will implement Support for old Hardware, new cpu’s, etc yes
EDIT: However the post i linked to had a solution, Reinstall , So He might be lucky aswell

As is explained in the thread about why NOT to use Device ID’s, one big issue comes when you want to replace or relocate a piece of hardware. Using entity_id’s you can rename the new piece of hardware to use the same ID as the old one and all automations etc continue to work as if nothing changed but with device ID’s (that are auto-generated by HA in the backend) the new piece of hardware is allocated a new ID and as such all the automations etc need to be modified to suit.

Anyway, this is getting off-topic.

3 Likes

I know, And i quick learned to not use Device_id, and so will all people when/if they “get warm” And i still can’t say why they use the this in the first place, yes a device have various “name-prefixed” from factory, but i always rename my devices all through my network, maybe the registry can’t handle
MY-BedRoom-Corner-1st_Floor_Ceiling Light - -Brand-Name, Battery

Yes i hoped that “someone” would move this Side-Topic out, with my Essay :slight_smile:

It’s in bullet 2 on that topic, but feel free to update it (it’s a wiki anybody can edit). I added the bit on stats.

Nah, it’s all good. I was just reiterating what is already in that linked thread.

1 Like

Yes, also reloading Automation fails. Only a full restart of HA works for a certain perion.
My automation do not start correctly, the trace shows “still running” normailly it’'s finished in a second. The trigger in this case is built on “Frank Energie” hacs component

1 Like

I honestly don’t think you experience exactly the same “issue” as the person to you responded , As He says it works from his phone and another computer
But if i was You or Trevor, i would Restore from backup, to see if it works, and then follow this Topic, and read the coming release notes.
I sincerely doubt it has anything to do with Your Trigger, but you cold also check that Components Github-page for “reported” Issues

Hi Merc,

it is NOT an outdated Homematic version blocking you from working. I have had the same issue here, and I was (am) on the latest Versions everywhere around.

The problem seems to be, that the switch between the former version named “Homematic (IP) local” and the new (only renamed?) version “Homematic(IP) Local for OpenCCU” does not work flawlessly on all machines (I work on Yellow with my HA instance).

With Chattys help and now since nearly 4 hours, a lot of Terminal, FileZilla, File-Editor flic-flacs, it seem to come back to a working state, with a lot of dead bodies of old “homematicip_local” wiped out of every corner of the system.

Really bad shit


One more reason on the list for us to get rid of that old and meanwhile unreliable system “Homematic”


Anybody interested in tons of hardware from eq3?

tons?
I’m not a big user of homematic, but was kinda forced for it by my garage door supplier. As far as my experience goes, is the 868Mhz band very useful for devices and would consider extending my base.
How is your stuff connected to HA? (and what is your exact issue with reliability in operational sense?)