HASPone bug!

[rossbate]

Found a bug.
Have temperature with icon on a button, then I have activate a page on that button. When changing to new page, page 9 the temperature icon is overlaid on the new page.

Also how can I get thermostat from Honeywell Evohome on that page? Can see a blueprint for thermostat??

[aderusha]

Are you using the Activate Page blueprint with that? If os, I've just pushed a minor change to the behavior on that blueprint, can you try re-importing and see if it makes any difference?

[bertmagin]

Yes,, just import it again

[eboston]

When I tried importing the core functionality blueprint, it reported the file already existed.

[rossbate]

Delete the old blueprint

[eboston]

okay. What about existing automation based on the old blueprint? Anything have to be done to them so they use the new blueprint?

[aderusha]

So long as the new blueprint retains the old blueprint's filename, you should be all set.

[aderusha]

I've just posted another update to "Activate Page" after doing some more testing. Previously, the "activate page" was being triggered on button press (not release), so when you pressed the button down the page immediately changed. The way that the overlay icons work is that they are triggered on release, so when you let up on the button, it paints the icon back into place (because pressing the button removes it). So, press button, page changes, that makes you release the button, icon is painted on the new screen.

In general, changing pages on Nextion on button press is problematic, and can lead to buttons being "stuck" as they might never catch a release event, as you never actually let off the button because the page changed before you removed your finger. So, step one was to fix that blueprint such that it triggers on release instead of press, which I should have done in the first place due to the issue above.

However... still doesn't fix the problem 100% of the time. It becomes a race as to which of the two blueprints are going to trigger and then execute first, with both responding to the same button-release event. After some testing, what I've "fixed" is to simply add a 100msec delay to the page change blueprint. You release the button, home assistant catches that, repaints the icon right away, and then 0.1 seconds later sends the command to change the page. In my testing this seems to work reliably while not interfering w/ icon overlays.

[IIAIronWolf]

Does this mean we will be getting an update and need to re-run the core functionality automation?

[IIAIronWolf]

I ask because I am not using a custom 'activate page' blueprint, only the core functionality as of right now.

[aderusha]

OK, so the OP was using the Activate Page blueprint. Sounds like you are seeing some unexpected icon hanging out somewhere. If you’re not using the Activate Page blueprint, can you explain a bit about what you’re seeing on your HASP?

[IIAIronWolf]

I am actually seeing the exact same issue as the OP on occasion, with the sticking icons, sometimes being the temperature icon. I am not using a activate page blueprint. I simply added the four blueprints you made in order to recreate the status page you had before HASPone, including date, time, temp, and weather condition. Therefore, either those blueprints have this same issue, or the Core Functionality blueprint may also need to be updated.
In addition, and as you mentioned in this first comment, the page buttons sometimes stick in the 'activated' color, but those were only setup by core functionality on my device. I have not customized page buttons. I have submitted issue #28

[IIAIronWolf]

Having the same issue here. This belongs in the Issues section though.

[aderusha]

Is the current version working for you?

[IIAIronWolf]

Does this mean we will be getting an update and need to re-run the core functionality automation?

[aderusha]

You’ll want to re-import the Activate Page blueprint to address the issue in the OP.