Status icons suggestions

[fhteagle]

I am confused by the Charging status icon div using the class "is-warning" / yellow color? I would think this would be a normal condition, and green in color instead?

The waiting to charge icon is a green background checkered flag:

This, to me, means "completed". Change it to a blue background hourglass icon, or maybe a clock icon?

Status icon label "Sleeping" does not have much meaning to me. What is this status communicating? It seems to me to be redundant with the red paused icon?

[KipK]

I don't get it. First icon represent the Openevse state ( active / disabled ) The waiting Icons replace the Sleep Icon when state is active and no vehicule is plugued

Sleep is same state as displayed on LCD , when it's disabled and nothing connected.

[fhteagle]

If the OpenEVSE is active, the EV is connected, but EV is not actually charging (due to EV internal charging time configuration), the third icon is a checkered flag with green background. I will get my system into this state and take a screen shot later today.

[KipK]

Ah I see, . I've changed for thumbs-up , let's see if it's more appropriated if you have other suggestions

[fhteagle]

I updated the original post with screenshots for clarity about what I was talking about.

I think you changed the blue moon with tooltip "Sleeping" to be the blue thumbs up, correct? This is not what I was trying to indicate. Probably my mistake for not being clear enough.

What if the green background flag was changed to a blue background hourglass, and make the tooltip say, "EV not yet charging"?

[KipK]

oups nope I've made a mistake, now it(s the good ones

[fhteagle]

Okay, the last icon being thumbs up and tooltip "Ready to Charge" for when the EV is not yet drawing power makes sense to me now. Thanks for fixing it!

Back to the charging icon being a yellow is-warning... I still think this should be green background for a normal condition.

[KipK]

The idea here is to give emphasis to state "Charging" by introducing a unique color.

Choosed Yellow as it fits for a lighning icon ( perhaps using a lightning Icon is more suited in this case.

Perhaps using Blue then ?

[KipK]

I've changed for Bolt icon, green background, and yellow icon color. Does this makes more sense ? ( Bolt icon is also more readable on little screen )

[fhteagle]

Yellow bolt on green background makes visual and logical sense to me. Good compromise between "this is normal" and "careful, power is flowing".

I wonder if a color blind person could see the yellow on green, though. I have a partial color shift, but not full color blindness. The white on green, or white on blue, or white on red each should have enough contrast to be legible. Yellow on green might be too close in contrast.

[fhteagle]

Since you are using the "Pause" icon for OpenEVSE disabled in the status box, what about using that for Mode: OFF , instead of the circle and slash?

Same suggestion about harmonizing Mode: ON icon and enabled status icon?

[KipK]

I was about to change the pause icon too, testing live some different ones. Seems the circle & slash is more appropriated to a disabled state. Or perhaps we can change this icon depending we have an auto_release true or not . Pause Icon could be appripriated for an auto release true, the other one when false

I won't use the bolt icon too for this as it will be confusing with the Charging state. I'm still not fan of the Circle Check we have now either :) Or pehaps we use bolt for Charge button and Active status,, we remove the Charging status Icon, and just use the bolt in yellow while charging in the current state icon

New thing I've just added, tell me what do you think about this: https://watch.screencastify.com/v/rfUevvOop9RcR79mJ7ud

It displays the current service that has the claim on the max_current setting here ( but could work like this for any property ) You can them from here delete any claim made by a service with lower priority than manual

[KipK]

ok I'm testing this, not bad, and less Icon on screen for same message: dizsabled: active, waiting for EV active, EV connected: active: charging: charging: error:

Then we have a bit more space on mobile to display a message

[fhteagle]

Two icons is still very clear and yes a bit more simple!

As to the Screencast with the MQTT thing ... I had written up an idea to display the various amp setpoints from Eco, MQTT, etc, each on their own line. Even if the automated amp levels cannot be changed by user in GUI, having multiple slider bars the same size that moved in response to what that automated control was commanding right now would be easy to compare visually. I.e., user asks self why am I only charging at 10 amps now, looks at sliders, sees lowest is shaper, oh that's why....

I think this might be better than trying to reuse one slider + manual/MQTT toggle.

[KipK]

that's what is happening here. The slider will adjust the value to related claim that has the priority , and display the claim id as a tag under the slider. :)

There's no need to display the whole /claims topic for all the other claims that are not taken in consideration yet. The live one should be sufficient. I haven't done it yet, but the delete button will appear only to service with lower or equal priority as override, and also not for divert

I have iconified few things

[fhteagle]

Hmm. I have a different opinion on this. I think it would be useful to be able to see the action of each "amp controller", and be able to easily toggle each on and off from the main page. Seeing a unified table of all the configured "controllers" is a great overview. And being able to see what would be happening with a particular controller, even if not active, would help the user to learn the system, confirm the system is configured as expected, and to notice unwanted quirks in what a controller is asking for.

But I will admit that my opinion is not so well informed, as I have yet to configure any amp controllers on my home setup just yet.

[KipK]

Imagine how bloated it would be as each property can have a different controller, so tracking the list off all the claims that are ignored for now.

Anyway, evse has no idea on who will have the priority but the main one. Those fuzzy logic would have to run on client side. Also those claims are always moving in real time, priority change etc, .

The only thing we can display without ending with a blinking data christmas tree is the main order for each property.