when I log into esphome I see a mess. tons of configs I can not maintain. why the heck are these here and why cant I stay on the current version of esp home !?
office-test.yaml - It contais ESPHome specific configuration for the screen like e.g. API-key, WiFi-secrets, WiFI-ap config, ...
ofifce-test.local.yaml - is used if you want override standard tessera configuration like screens DPI or if you want to add ESPHome configuration for extra sensors on your screens GPIO pins
office-test.plugins.yaml - contains configuration for extra plugins you use
I don't know about technical restrictions why the plugins need an extra YAML file. I have to admit, that I do not like the idea of having three files for one screen. The many questions about it show that the intention is not clear.
I wonder if it is possible to put it all into one YAML with three 'chapters'.
Thank you very much that is very helpful, My question was really about the why the results are as they are because I don't understated where the dependencies exist. for example: I have a panel I can get fired up on espcontrol but not on tessera. This is all relatively new as well and I see this growing by leaps and bounds..
tessera
Discussion 2
Add a commentTrying to shed some light on this:
I don't know about technical restrictions why the plugins need an extra YAML file. I have to admit, that I do not like the idea of having three files for one screen. The many questions about it show that the intention is not clear. I wonder if it is possible to put it all into one YAML with three 'chapters'.
Thank you very much that is very helpful, My question was really about the why the results are as they are because I don't understated where the dependencies exist. for example: I have a panel I can get fired up on espcontrol but not on tessera. This is all relatively new as well and I see this growing by leaps and bounds..