Having problems with template errors?

[aderusha]

Over the last week several people have been reporting template errors and I'm struggling to piece together just what the heck is happening. On my own test systems this has never happened and the traces I've received have me scratching my head.

It's obviously an issue, and I want to get to the bottom of it! I'm going to be hanging out on Discord today, if you are experiencing this problem and have some time to work through it with me, maybe jump on to Discord and give me a shout. It'd really help me out!

[aderusha]

edit: ignore all this, actual fix is a couple replies below

One suggestion that might help clear things out in your installation:

1. Configuration > Automations > HASP Core functionality and click the Edit button (pencil icon)
2. Top right ⋮ menu > Delete Automation
3. Configuration > Devices > > DELETE
4. Repeat step 3 for any additional devices with the same name
5. Restart the HASPone device
6. Re-deploy the HASP Core functionality, select the HASPone device, SAVE, RUN ACTIONS

[deltaroe]

Throwing some more observations into the mix here. It appears that a freshly installed unit doesn't have any rgb_color values in the *selected_*ground_color entites. For example here's a screenshot of my selected_foreground_color state

It looks like the previous steps to the one failing seem to be attempting to set a default so no idea why that's not working. The theme blueprints seem to be setting the missing values which seems to be why the solution found here works. #89

Maybe set the default rgb_color values when instantiating the color object in case they aren't found in the entity? https://github.com/HASwitchPlate/HASPone/blob/main/Home_Assistant/blueprints/hasp_Core_Functionality.yaml#L450

[deltaroe]

May have been a bit premature on calling this solved. I think alot of the issue was I renamed the device in HA and a lot of the blueprint templates seem to rely on that name being consistent when building mqtt topics

[aderusha]

If anyone can take a minute to test this out it would help a lot!

I've addressed the issue above through a combination of firmware and blueprint changes, pushing the theme RGB light discovery process into the firmware so the blueprint doesn't need to rely on creating and then using the RGB light entities in the same process.

edit: test looks good, moved 1.02 to release!

HASPone v 1.02 upgrade procedure

1. HASPone web admin > Update Firmware > Update ESP8266 from URL, then click "Update ESP from URL" and allow the firmware update to complete
2. In Home Assistant, go to Configuration > Blueprints and hit the trash can icon next to "HASP Core functionality" to delete the existing copy.
3. Click this here button to deploy the 1.02 version of the Core Functionality blueprint:
   
4. Finally, go to Configuration > Server Controls > YAML configuration reloading > Automations to reload the core functionality blueprints+automations.

[deltaroe]

As long as I don't rename the device, it works great. Thanks!

[aderusha]

Renaming the device should create a new device and new entities associated with it. You'll then need to update all of your deployed blueprints to point at the new device.

[Is0mniac]

You're a wizard, it works!! Thank you, appreciate the fix.

[MihleTX]

This finally solved my issue where it was hanging on the WIFI and MQTT connected page!!!! Thank you so much! I am back up and running.

[aderusha]

Thanks for the feedback! I guess we're good, so moving this to release.

[raa1n]

This HASPone v1.02 works like a charm. Loads of thanks for this fix.

I just have one query actually. I have a fan at my place whose speed can be varied. I am trying to add it as a dimmer so that I can have Time, Dimmer Light and Fan in a single page (Page 4). But this dimmer page accepts only lights. Is there any turnaround for this to have it done. Currently I am struggling to do it by creating a dummy template light and linking it various speeds of the fan to bring it here.

In any case, kudos to your HASPone fix in a quick time.