@videogame95 yes there are two different ways of coding the pages
You can use the module names as you are doing
I always found this frustrating. Looking at a module config, I had to scroll back to the pages config to find out where it was and then scroll back to the module config, where was that?
So I documented the page classes approach
In pages
Call them useful names , page1,page2, mom, dad, kids, house
Then at each module after the module:
Add
classes:"page1”,
Or whatever page (or space separated list of page names)
On the pages config fixed, I use “on_every_page”
This also solves the problem with multiple of same module on different pages(weather current on one forecast on another)
But I also am confused, as the latest pages config uses a different timing variable name?
