search

SirGoodenough / HA_Blueprints

🧯 My Collection of Automation and Script Blueprints for Home Assistant 🧯
Other
132 stars 22 forks source link

[BUG] Conflict with Awtrix & topic 'cube' with last_side variable. #23

Closed SirGoodenough closed 10 months ago

SirGoodenough commented 11 months ago

Which Blueprint is This Concern About / Related To? All 3 cube blueprints

Describe the bug Reported on Discord: https://discord.com/channels/693125294957133844/693156036214915082/1161720199670673448 madmax — Yesterday at 12:41 PM In fact, I've figured out why the "last side" variable created by your blueprint suddenly stopped working. It turns out that when I added an Awtrix Light and activated it in Home Assistant, the "last side" variable gave me the message "This entity is no longer provided by the MQTT integration." However, when I deactivate this MQTT device (Awtrix Light), it starts working again.

So, the root of my issue seems to be that having both MQTT streams active at the same time is causing a problem for this variable provided by your code. I apologize for any language confusion. Do you have any ideas on where to look in Home Assistant to resolve this?

To Reproduce install a cube BP with Awtrix installed.

Expected behavior They should work happy, even if the cube is named cube. Once the name of the cube was changed, the conflict went away.

Additional context Add any other context about the problem here.

SirGoodenough commented 10 months ago

Could not duplicate or verify. Problem went away when user change cube topic/name and something else. Don't think I can prevent via software or documentation fix.