You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now I'm running into an issue where if I'm doing development on my computer while the addon is running on HASS they sometimes conflict as they are both running similar but often not the same code. To get around this I currently need to turn the automations running on HASS off while doing development.
I've added a toggle helper that is turned on by the dev server when its running and in production stops all my automations from running. I'm just wondering if others are doing non-local dev if this might be a useful built-in feature.
The text was updated successfully, but these errors were encountered:
Setting this will cause entity update events to not fire, and for the socket to black hole outgoing messages. Internal workflows, such as maintaining accurate state & registry should still work properly, allowing it to pick up without missing a beat.
I haven't run across a standardized approach to automatically controlling that flag that'd work out of the box though. When the upgraded synapse integration is complete, this would probably be a lot more straightforward to accomplish
Right now I'm running into an issue where if I'm doing development on my computer while the addon is running on HASS they sometimes conflict as they are both running similar but often not the same code. To get around this I currently need to turn the automations running on HASS off while doing development.
I've added a toggle helper that is turned on by the dev server when its running and in production stops all my automations from running. I'm just wondering if others are doing non-local dev if this might be a useful built-in feature.
The text was updated successfully, but these errors were encountered: