think here it makes little sense - better would be github discussion or discord. On discord I already have a group for the US version testing it
Could you please send me the link for this group? I’m testing exactly with a US version device.
Thanks to Blacky I downloaded the two versions of the tft/hmi 3.2 files and from these I obtained 3 versions in Italian eu_ita us_l_ita and us_p_ita. The portrait version differs from the other two in the lack of text for the physical buttons. Now they should be tested, logically I think that to test them the 3.2 versions of both the Blueprint and the Yaml file should be installed!
Yeah… this didn’t work. The NS Panel just gets stuck on the ‘initialising’ screen. It does however connect to HA and report it’s temp sensor etc so I’m not sure what the problem is.
EDIT: actually, now it isn’t even connecting to my network, so Iit looks like I’ll need to serial flash it back to the base config.
Sparky one question, did you flash esphome directly from the original firmware, or did you flash the Lovelace UI first?
Version v3.2 is online 
5 Likes
I flashed ESPhome onto a brand new NS Panel running the factory firmware.
Before I post an issue… anyone run into the error below when moving to v3.2?:
The automation “nspanel01” (automation.nspanel01) has an action that calls an unknown service: esphome.nspanel01_set_settings_entity
Screen on NSPanel is sitting a “loading…”. I did apply the new .TFT and I’m running the US panel.
this is a problem in your configuration of the blueprint.
Please check all fields in the blueprint if the correct entity is selected and this entity has a correct status.
→ wrong outdoor sensor
Perfect now. Is there a specific code required to give the chips an icon? I tried mdi:door (to get a door icon but it shows MD as the chip)
Thanks again for your help.
Is it me or do the panels react slower since the last update? It takes a couple of seconds to load each page. When going back home it also takes some time, I had the idea it was much faster on 3.1 or 3.0.?
please red Release Notes 3.2 point 2
Big thanks - can you share the files?
Interesting enough I loaded it w/out ANY sensors defined and it still stuck on the “loading” screen. I found out when I hit the "reboot’ via the reboot entity, it then connects correctly. The “loading” screen does returns if I reboot HA and then I have to manually reboot the panel and all is good. I have now created an automation that reboots the panel 10 seconds after HA starts and everything work fine.
It’s odd behavior and I have tested this in both my dev and prod HA environments with the same results.
Another note of interest, if you have multiple panels, any change to one panel (hitting save) causes ALL panels to reset/update.
Yes I saw. However it also takes much more time when I press a on-screen button to toggle script, light etc. You got have to wait for it. Its on all my panels. It’s this also expected? Should I post a video for you to check the behaviour
It’s not only saving the automation for that panel, it’s is when you change any automation.
This is not new, it was there from the beginning, but now with the boot screen it takes longer and is now visible.
Unfortunately HA doesn’t have info about which automation was reloaded so the panel have to reboot on any reload. 
I’ve already requested an improvement to Home Assistant in order to have this info on the automation reload event data.
Does anyone have the orginal firmware en hmi screen file for the US version?
I am having some reboot issues on one of them and it seems a screen/power problem