I think Its something related to blueprints. Every blueprint I tried has this issue. I noticed this because I only tried blueprints with HASPone. Tag error is appearing in file editor addon when I open a blueprint file.
!st thing to try, delete the blueprint and add it agaim.
Have you tried any non-HASP blueprints?
edit: reading your post again, I think you are seeing two different things going on here. Whatever editor youāre using to open the blueprint is complaining about the !input tag which is non-standard yaml used by home assistant. So thatās probably not a real error, just an artifact of your editorās YAML linting not knowing about home assistant.
If you havenāt deployed any blueprints, your configuration problem lies elsewhere.
I think its something to do with the editor. But when I deleted all the blueprints and automations related to HASP config validation worked just fine. I havenāt made any changes to config file other than playing with hasp automations and blueprints.
Iām gonna give it another try
Thanks for the info !!!
having some issues flashing to v1. downloading the bin file it seems to be 100kb compared to the 467kb of the v.40 version. after flashing this file the d1 mini doesnt boot and flashing on the board. If i re-flash the v.40 or v.41 file it boots up and works fine.
Has anyone had this?
Exactly which file are you downloading?
HASwitchPlate/HASwitchPlate.ino.d1_mini.bin at master Ā· aderusha/HASwitchPlate (github.com)
or even from the plates web ui where it says update v1 is availableā¦ still fails
That file is 12 months old
hmm good point. still does it from the web ui on the plate also
nope - 112kb - flashes ok but no bootā¦ 
It is 632kb.
1 Like
seems to have worked this time. i tried this way first last night while they were still in the wall and they both failed. this morning had to remove them from the wall and flash on the desk. not sure why it works nowā¦
also, I have a test plate on v1 and find it almost longer to set it up from scratch - everytime you create an automation and save it, it takes time to reload the automations before you can test it. previously i could make a whole heap of changes or copy and paste from an old to a new plate, rename everything then just reboot HA and everything would work ok.
the test plate is on v1.00 and lcd version 3, and lcd speed is 921600 and it has a half second delay in changing screens or running actions. a previously plate on V.41 seems to be more snappy than the v1.
Thinking of taking my dead Wink Relays, gutting them, and installing HASP or HASP-lvgl hardware if the LCDs will fit properly.
What hardware do they have and?
This is the one downside to switching from packages to blueprints. Packages did make it easy to take one device, configure everything, and then clone out a bunch of copies with some search and replace.
Technically, this is still true if youāre up to some hacking. In your automations.yaml youāll find all of your GUI-created automations, including automations deployed from blueprints. You can take a set of blueprints configured for a given HASPone device, copy and paste, then replace the device ID on each automation, and also change the āidā of each automation to a unique number. The automation ID doesnāt really matter so long as there is only one of each ID in your config.
So, still possible but itās a little weird to handle.
Out of curiosity - what sort of hardware are you running Home Assistant on? This conversation might be of some help.
If you make it work - post pics!
I do want to point out that thereās a HASPone project which has 3D printable enclosures that donāt need any gutting at all to make things fit properly 
1 Like
Iāve got it running on a Dell Thin client with 4gb ram and 256gb SSD running on Debian Linux. iāve also transferred the DB over to MariaDB but havenāt had any luck with the touch speed on the V1.0 panels.
I still have 1 V.41 panel in a room and it is still fast to respond to touch events. Is there any difference in how the system reads automationās compared to packages?
There are substantial differences all around with how the blueprinted HASPone approaches automations, triggering, and conditions. I wonder if we could track down where the delays are in your setup as you have both running side-by-side. Is there any chance you can pull an MQTT log w/ timestamps (preferably millisecond resolution) of both systems sending a button press for a page change, home assistant responding, then HASP responding back w/ the new page? That might be instructive to discover if the delay is on the HASP side or the Home Assistant side.
edit: hereās one way to get the millisecond (nanosecond in this case) timing using format strings and mosquitto_sub
MQTT_BROKER=hassio.local
MQTT_USER=hassio
MQTT_PASS=hassio
mosquitto_sub -h $MQTT_BROKER -u $MQTT_USER -P $MQTT_PASS -F "[\e[36m@x \e[96m@X.@N\e[39m] [\e[94mr%r:l%l\e[39m]\t\e[0m%t\t\e[1m%p\e[0m" -t "#"
1 Like