Johannes

The mqtt credentials are not passed though to the application - no clue why and I also cannot do anything to debug this as I don't have the issue. (never...

hey, the decision on which page is going to be used is made before any further rendering of the config, so it's purely based on the number of entities in...

It's just sending the update for the screensaver alternating with different entities. I've started to reimplement the backend without appdaemon. Didn't implement communication though Homeassistent events so far. But besides...

I think the least confusing way to implement this would be something like this: ``` screensaver: entities: - entity: head - entity: left_3_rows - entity: left_3_rows - entity: left_3_rows -...

@Armilar So far my main prio is to create a drop in replacement for the appdaemon app, so no breaking changes for now

You can already display an addional line in screensaver, you only need to figure out how to get the next appointment with an home assistant template. ``` timeAdditionalTemplate: " {{...

button press events are triggered with the entity type button where the last column is getting a button (Doesn't have much to do with on release though)

You can configure a defaultCard, this way the panel will always return to the configured card.

I'm not an esphome user, so I cannot tell you want you need to configure, but I would guess that you have to remove the onclick from the config. https://github.com/sairon/esphome-nspanel-lovelace-ui/blob/dev/examples/basic-config.yml#L32C15-L32C15

what do you mean with the pageid?