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
As the new version of Hassio 2021.1.3 and browser_mod are released, is not possible to use Tap_action with the call service for the browser_mod popup service. I know that other custom cards has the same problems but new released was done in order to use the fire-dom-event option instead of classic call service. Is it in program to do the same upgrade for this fantastic card that I use everywhere?
Thanks you
The text was updated successfully, but these errors were encountered:
For developers of lovelace plugins
This change makes use of the fire-dom-event tap action.
It's actually been in the code for almost a year, but has never been used (yet).
If your lovelace plugin does not support this, they will not work for direct triggering of browser_mod functions.
Calling a service as before still works, though, it's just the deviceID: this that's gone.
See: https://github.com/home-assistant/frontend/blob/8d13745c6b822a76f6724e32c2b10bf57ae645e7/src/panels/lovelace/common/handle-action.ts#L137
fire-dom-event show a popup only in browser where action are called.
flex-horseshoe-card don not handle this events, but only "more-info", "navigate" and "call-service" (line 1615).
As the new version of Hassio 2021.1.3 and browser_mod are released, is not possible to use Tap_action with the call service for the browser_mod popup service. I know that other custom cards has the same problems but new released was done in order to use the fire-dom-event option instead of classic call service. Is it in program to do the same upgrade for this fantastic card that I use everywhere?
Thanks you
The text was updated successfully, but these errors were encountered: