Depends on a particular author and their motivation, and of course their life circumstances.
1 Like
… and if the changes in core really must be that often that way, that that much is destroyed.
did you check with Ivan Pereira (Elchininet) ? He’s awesome at this stuff, and just fixed my custom. plugin more-info that stopped working too…
Linking there so you can chime in and ask
2 Likes
He just forked the repo… 
I really miss the additional history chart in the more info dialog… 
1 Like
And Elchininet provided a fix. Genius. Briliant. Thanks so much.
See
Which includes a js replacement.
7 Likes
Is it possible to set somehow minimal y-axis range (not ymin offset!)? I mean I have sensor that reaches any values between 0 and 500, but meaningful data is coming for relatively short time (few times per day for few minutes) when some devices are used. Outside this window sensor state oscillates around very small values (call it background noise) that are in range of 0~0.001 and are negligible to what I’d like to be drawn. Yet automatic scaling stretches chart trying to display this meaningless data, which is somehow misleading, as in reality nothing important to observe is happening. It would be great to be able to set fixed, minimum scale for y-axis (lets say to 1) to make such noisy data variation unnoticeable unless meaningful and then normally scale the chart up to maximum data received. Any advice?
I’ve run into another problem by using the PR file for the more-info card…
I opened up a (rarely used) history explorer card panel and I got a big red “! configuration error” notification in that view.
So I made sure that my history explorer card was up to date (the one from HACS was). so I switched my lovelace resources back to using that one.
Then my history explorer card panel view worked again but then the more-info stopped working again.
So it seems that we can only have one of the two functionalities working until this PR gets merged?
there’s nothing that tells me what the config error is using the new PR file.
just this:
Not that problems here.
would you mind giving me your card config just to be sure I didn’t screw that part up somehow? I don’t think I did since it’s pretty basic but you never know. 
Sorry, misread that. Thougth that you are only refering to adding a card via UI. No sorry. Don’t use this panels at all.
1 Like
I guess there isn’t anything really special about using the card in a panel or in a normal view. Would you mind posting the yaml for your card you configured via the UI?
e.g.
type: custom:history-explorer-card
stateColorSeed: 137
cardName: history-explorer-card-47111
showCurrentValues: true
refresh:
automatic: true
interval: 30
timeTickDensity: height
stateTextMode: auto
tooltip:
size: compact
showColorsLine: false
showColorsTimeline: false
showDuration: true
showLabel: false
stateTextMode: raw
defaultTimeRange: 7d
header: Testauswertungen
decimation: false
lineMode: stepped
uimode: dark
showUnavailable: false
recordedEntitiesOnly: false
axisAddMarginMax: true
axisAddMarginMin: false
rounding: 2
statistics:
enabled: true
mode: max
uiLayout:
toolbar: top
selector: bottom
uiColors:
gridlines: grey
labels: "#ffffff"
buttons: "#2e2e2e"
selector: "#2e2e2e"
closeButton: "#2e2e2e"
stateColors:
gestoppt: "#414141"
"on": "#6da620"
"off": "#414141"
open: "#ad3631"
closed: "#6da620"
tilted: "#ff9800"
locked: "#ad3631"
unlocked: "#ad3631"
battery.on: "#ad3631"
battery.off: "#6da620"
door.on: "#ad3631"
door.off: "#6da620"
shutter.open: "#649ace"
shutter.closed: "#6da620"
entityOptions:
sensor.sensor:
type: line
lineMode: stepped
card_mod:
style: |
button2 {
background-color: #2e2e2e;
border: none;
color: #ffffff
}
input {
border: none !important;
}
input::placeholder {
color: var(--secondary-text-color);
}
br {
display2: none;
}
graphs:
- type: line
entities:
- entity: sensor.aussenthermometer_actual_temperature
1 Like
Thank you.
I’ll give it a try when I get some time.
Nope.
I tried your exact card config with the only difference being that I replaced your entity with one of my own and I get the same result.
I even tried it as a regular card in a regular view instead of a panel view and get the same error:
if I switch back to the HACS version then the panel/card works but the more-info panel doesn’t.
I’m not sure what would be the difference between yours and mine tho.
Try using my file
- Unzip attrached zip
- Replace the history-explorer-card.js in www\community\history-explorer-card folder
- Either gz that in the gz file or just rename the history-explorer-card.js.gz to history-explorer-card.js.gz.old or move it anyhere else => old gz fil is not in the folder anymore
- Reload js in browser via hard reload or developer tools without cache or …
1 Like
I finally had a chance to try your card and I end up with the same result. I have no idea why your experience is different than mine. I’ve checked everything I know to check.
right now I can use the history explorer card as a card and use the built-in history in the more info card so I guess that’s well enough.
hopefully things eventually get sorted with the main card in the repo and it might fix my issues as well.
until then thank you for trying to help. I just have no idea what might be the problem.
Do you have a schema of all parameters? Are there any not in the read me file?
Is there a background color parameter or just use card mod?
Also are there parameters for top and bottom heights to compress the density?
I do not think there are options for this (at least I cannot recall them). So, try cardmod.
It seems that selecting a climate entity shows only its state (i.e., the climate mode). The HA built-in history shows both temperatures: current and target at once, and the mode.
Since these temperatures are stored in attributes, I see no way to show them via the History Explorer Card.
Don’t you know if this fork is going to catch up? Or does it start to look abandoned, too?
BTW, is it possible to enable/disable replacing more info without actually adding the card to some dashboard?
Maybe create sensors based on the attributes and use these in History Explorer?