Open Habbie opened 6 months ago
- A simple install guide for Toon would be useful
both /install and /devices cover parts of this, but it can be better, yes.
- A note on how to contribute
very good idea. I'll make a nice PR adding some semi-simple entity type and use it as an example of how to add widgets, because that's the major non-refactoring work that's next.
- That mapping code from dashboard to uicomponents can be improved (and we should)
- The uicomponent has multiple or no haentities might also be something to fix
For both of these I feel expectation management is most important :)
A note on how to contribute
contribute and discuss!
Having now actually tried to use voorkant (main + #89 + #91 + #92) on a Toon1 against my real HA, clearly some more work is needed. Startup takes several minutes at 70%-80% CPU, just to consume all HA state (and debug log extensively about it). Then, with just 8 entities shown, we use 15-30% CPU. Part of that likely is the scrolling of long titles.
So, I think we want:
Also, I'm unsure (because startup took so long) but I think I once got caught trying to do things after the Toon software blanked the screen. Should investigate this and if necessary unblank on startup. (And once we have that, we can do auto-blank and wakeup-on-touch)
the Toon software blanked the screen.
it just happened again while voorkant was running. See also #83
The scrolling can be set with labelLongMode
. Or at least, that's how it should work :-)
When you say - maybe don't actually get all entities. Do we need some code that gets entities on demand? so while parsing the dashboard we go and get the entities?
Do we need some code that gets entities on demand? so while parsing the dashboard we go and get the entities?
That's the idea, yes. Need to check if the WS API can do it. First I'll see how much faster I can get all of this without making that change.
Startup takes several minutes
it turns out this goes down to 3 seconds if UIDummy doesn't try to log entire state JSONs.
- I think I'd like to support a few more plain sensor types (things that just show a temperature, a power in W, the state of the sun - should be simple)
What if we introduce a UISensor
that understood a little bit about units and use that instead of UIDummy
?
What if we introduce a
UISensor
that understood a little bit about units and use that instead ofUIDummy
?
nice one. Just printing the unit from the state might be enough of a start in fact, but UIDummy would have to special case that. UISensor makes sense I think.
What if we introduce a
UISensor
that understood a little bit about units and use that instead ofUIDummy
?
this is #104 now
Nice/needed (please add):