I have X sensors:
— X1 sensors - provided by integrations;
— X2 sensors - manually created template sensors.
Some sensors from integrations may be stored in LTS - but they are NOT since I excluded them from Recorder.
Some template sensors are excluded from Recorder. Some of not-excluded have “state_class: measurement” - and stored in LTS.
Now we got Statistics in more-info pop up - instead of a real history - and this is:
— less informative;
— confusing - since some sensors are not in LTS, then probably the real history is supposed to be shown.
I would restore the previous more-info - but with one more “Statistics” tab - only if the sensor has LTS.
Does anyone have problems with adding cards to lovelace? I can add cards by entity but adding them by card the list is just blank. Same thing on Home Assistant application on Android.
EDIT: Solved problem by moving atomic-calendar-revive to test dashboard. After that “by card” list is back to normal. Although same problem exist with my test dashboard but problem is clearly with this custom card.
I really don’t like what they did with the entity history. When I open an entity I want its exact short term history, with every state change. Not some averaged approximation. I’m going to override them.
Already tried that with couple of reboots also. Strange because by entity everything is normal and this problem exists even on a totally new device. Maybe just waiting for some updates…
the new “Tile” card does recreate the look and feel of the mushroom cards.
Unfortunately, there are some details, which are not working “as a replacement” or addition to existing mushroom cards:
As you can see in the Screenshot, I’ve tried to compare mushroom cards with the new tile card.
row: Tile Card, door sensor - closed.
row: Tile Card, using an “update” entity.
Here we can see, that the icon does not show any color…
Compared with the “Update card” from Mushroom directly below.
row: Light entity in Tile Card - to compare the icon color from the Update Entitiy…
Since Icon Color is working here, I would also expect the same for the Update entity… ?!
also, the mushroom cards use a text style which is a bit more “bolt” than the tile card… that doesn’t look well when you are using the cards together in a layout…
Design is a very sensitive thing.
I never used mushroom cards (but I really really admire the work) only because of «too rounded cards». I hate round corners (not more than 4px), round background for icons, very very hate round persons’ avatars.
It is personal…
Isn’t the mushroom card guy working for NC now ? I seem to remember some announcement like this ? Would certainly explain the mushroom-like-but-not-quite design
I already got that “it is not mushroom” - but since Paul is now working for NabuCasa it is clear, where the design came from
And it would be nice - if we do have at least a “mushroom-alike” card, that the look and feel would match more closer to the original?
at least, what can be done:
In Mushroom Git an issue could be raised that the musroom cards to not apply to the themes font-design (regarding the bold entity status)…
Compared Mushroom / Tile Card with different themes:
Hi guys, I would also like to express my disappointment regarding the more info statistics graphs. No consistency and detailed information are getting lost. Please revert, there are so many other things which could be improved. I have one or two sensors which benefit from this, but this is the minority. A lot of sensor just look unsharp now:
I noticed that with this release if you use the map card in a grid card that your home/device is not centered in the middle but centured at the bottom of the page.
Please reconsider the More Info change from history to statistics data by default.
I think it is great to have better access to the statistics data, but when I click for more info, I want to see the fine grained detail, especially for sensors that might change rapidly like power, voltage, (some) temperature sensors.
I want to know When something changed and often want to see how fast it changed.
If a value briefly dropped or spiked, I want to be able to easily see that. There have been times where casually glancing at More Info has alerted me to something that I didn’t know was happening. If I have to dig for it, I’d rarely find those.
The releases have been really great and over the last year or more. So thanks for all the care that has gone into them.
please tell me:
What can you pick from the “old” history information, that you can’t pick from this statistics information?
In my opinion, the new statistics do provide a more detailed way for analysing any potential issues…
And I DO agree, that is doesn’t probably make much sense on all sensors…
But then, it could be considered, if it is required that these sensors have the state_class “measurement” or any other state_class that is writing long term statistics.
In fact, In my opinion, it does make sense to use this type of statistic on sensors that actually generating statistics with min/mean/max information.
For sensors, where I don’t want to use this, I can create templates - or, I haven’t really checked any history … at all…
The correct decission here can be pretty difficult I guess…
We are used to have the History with a clear “state changed from x to y” chart…
But on the other hand - I had to create a Dashboard with statistics card for each entity where I wanted to get such information… having that in the more information is a BIG improvement in my eyes…
What could the compromise be?
A parameter which you can use to decide what type of statistic can should be displayed?
Including both? and make it selectable?
Include a forth option into the graph for “state” - which can then be enabled or disabled?
