Aldaran
commented
2 years ago I may have screwed up somewhere, I'm using HA and had to separately install appdaemon. Wondering if you might have some guidance as to why the cards I've set up in the yaml are not loading.
It works for me... normal. I see a slowdown, but this is the specifics of the AppDaemon backend and TFT driver due to heavy workload. But you can use.
After touching, your cards with entities (Lights / Alarm / Media) should appear on your screen. If not, then there is some kind of problem, I only had this on Tasmota, when I ran the wrong script responsible for loading the driver via 'autoexec.be' and when I uploaded the developer firmware. "pageType\~cardThermo\~" causes just an empty thermostat card, then you need to call your entity update...: entityUpd,*internalNameEntiy*,*heading*,*currentTemp*,*destTemp*,*status*,*minTemp*,*maxTemp*,*stepTemp* And this call will be on time, in fact it's like notifity...
I'm trying to figure it out a little, without normal manuals it's very hard ...
For example: **- platform: gpio name: $friendly_name Relay 1 id: relay_1 pin: number: 22 restore_mode: RESTORE_DEFAULT_OFF on_turn_on:
- lambda: 'id($device_name).send_custom_command("pageType\~popupNotify");'
- lambda: |-
if(id(relay_2).state) {
id($device_name).send_custom_command("entityUpdateDetail\~id\~Light in Bedroom\~65535\~ON\~3840\~ON\~3840\~ \~65535\~5");
} else {
id($device_name).send_custom_command("entityUpdateDetail\~id\~Light in Bedroom\~65535\~ON\~3840\~OFF\~61440\~ \~65535\~5");
}
on_turn_off:
send to screensaver
- lambda: 'id($device_name).send_custom_command("pageType\~popupNotify");'
- lambda: |- if(id(relay_2).state) { id($device_name).send_custom_command("entityUpdateDetail\~id\~Light in Bedroom\~65535\~OFF\~61440\~ON\~3840\~ \~65535\~5"); } else { id($device_name).send_custom_command("entityUpdateDetail\~id\~Light in Bedroom\~65535\~OFF\~61440\~OFF\~61440\~ \~65535\~5"); }** Here you can certainly put instead of the 'if' condition the state of relay (id(relay_2).state and id(relay_1).state)...
In this case... The light can be called with one command, but in fact it will be a new page with one (the one that was indicated) entity: **... on_turn_on:
- lambda: 'id($device_name).send_custom_command("pageType\~popupLight\~Relay 1\~light.ns_panel_1_relay_1\~On");'**
PS. And I want to ensure that after five minutes my page is returned to page #1, and not in the state that was changed by my actions
omrishiv
sairon
Hello, I really appreciate taking the time to make this compatible with ESPHome. I think I have everything set up correctly? I can see MQTT messages, I have appdaemon running and the display is able to get the time and date; however, sending commands other than a page for my lights doesn't seem to work. Using the app.yaml, I don't think my changes are being persisted (no cards, screen timeout doesn't change, can't seem to get the weather on it).
I may have screwed up somewhere, I'm using HA and had to separately install appdaemon. Wondering if you might have some guidance as to why the cards I've set up in the yaml are not loading.
I can use the HA service to sent
pageType~cardThermo~themostat~climate.ecobee_2and get the card displayed, but it disappears very quickly and also doesn't have an entity. Same with the alarm and media cards