Frontend: Unable to input text on automation condition template type

[move[bot]]

@zerog2k commented on Aug 26, 2018, 9:44 PM UTC:

Running
Home Assistant 0.76.0
docker, ubuntu 16.04

Attempting to use UI to to create new automations, with condition to look at mqtt (json) payload value using value template.

Whenever I select "template" for "condition", the "value template" text area box does not show any text when typed in. So I'm unable to enter any text into "value template" field. (See red circled area of screenshot.)

(I can create other types of automations OK, and with other types of conditions, text boxes are working ok.)

have tested with safari and chrome, both exhibit this behavior.

This issue was moved by fabaff from home-assistant/home-assistant#16213.

[move[bot]]

@zerog2k commented on Aug 26, 2018, 9:46 PM UTC:

this also happens with "numeric state" condition type in the "value template" entry box:

I'm unable to enter any text in "value template"

[zerog2k]

also if I edit the automations.yaml directly and add a value template, the value of the value template will show up in this text box, but will still not be editable.

[pstreef]

I have the same issue. The input does seem to handle events because when I try to change the value after created the following template {{true}} in yaml it does show the save button. Also when attempting to change the value and saving the following error gets displayed: Message malformed: not a valid value for dictionary value @ data['condition'][0]['condition']
This same problem goes for template triggers.
Tested on firefox

[nkaminski]

Seeing this exact same issue on Chrome 71.0.3578.62 running under Mac OS X 10.14 with home assistant 0.82.1.

[dominikschubert]

Same in Chrome 71.0.3578.98 and Firefox 64.0 on Windows 10. Home assistant 0.84.6 (Docker)

[iantrich]

Throwing a reference in here for myself: https://github.com/home-assistant/home-assistant-polymer/blob/dev/src/panels/config/js/condition/template.js#L18

[markdepalma]

Same in Chrome 71.0.3578.98 and HA 0.82.1 (Hass.io)

[Zebble]

Same in Chrome 71.0.3578.98, HA 0.86.4 (Hass.io) and Windows 10.

[zerog2k]

anybody know if polymer is officially deprecated in favor of lovelace? (I'm assuming they are separate and lovelace is replacement for polymer ui?)

[iantrich]

@zerog2k Polymer is the web components that were used to build the UI. Lovelace was built with Polymer as well, but is in the process of being migrated to LitElement (still provided by the Polymer Project)

[DoctorIOT]

Any update on this getting the same issue

[nkaminski]

This issue is quite bothersome to me as well, I may make an effort to debug this in the near future.

[iantrich]

@nkaminski perfect to get started, tackle a problem that impacts you. How I got started as well :)

[nkaminski]

Not the first time I will have contributed either; I presently have changes merged for the SNMP sensor and Venstar thermostat components.

However my area of strength is certainly on the backend side of things as opposed to the web UI so I'm expecting a bit a of a learning curve with this one.

On February 20, 2019 7:17:51 PM CST, Ian Richardson [e-mail] wrote:

@nkaminski perfect to get started, tackle a problem that impacts you.
How I got started as well :)

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/home-assistant/home-assistant-polymer/issues/1601#issuecomment-465822025

--
Sent from my Android device with K-9 Mail.

[gpearston]

I have the same issue of not being able to type in the text box for Value Templates under the Automations editor. HA 86.4.

[0evmc]

Has anyone found a fix for this yet? I'm using hass.io 0.88.1 and I am unable to use the GUI to enter text for a template. I have to edit the automations.yaml file, after which I can view the template info in the GUI, but not edit the template fields.
Other things like "state" I have no trouble creating/editing in the.

[twerff]

Experiencing the same issue. (new user, clean install today). This error occurs in both Safari and Chrome

[cwhits]

Still exists in 0.90.1.

[gpearston]

Consistency is the key.....

On Sat, Mar 23, 2019, 12:45 PM Chris Helming [e-mail]
wrote:

Still exists in 0.90.1.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant-polymer/issues/1601#issuecomment-475903281,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZ55hB5MbM56TX58SV4W9w8XbnOiHi6Yks5vZpJbgaJpZM4WN_yR
.

[Vedeneb]

Same issue on 0.91.0...

[nkaminski]

No promises, but I will try to look into this over the weekend. Significant pain point for myself too.On Apr 4, 2019 8:54 AM, Vedeneb [e-mail] wrote:Same issue on 0.91.0...

—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.

[dgtal1]

My goodness...soon it'll be a year when the issue got reported and still there's no fix for this yet. Even more - no sign of a fix coming :-/ I guess it's not even diagnosed - I mean no one knows where the problem lies. I'm on the newest HA 0.93 and this is still not working. Shame. Maybeit's not a crucial functionality but sometimes would be handy to change something without hte need of editing the automations.yaml file.

[PurelyNicole]

It looks like there updates to automations coming in 1.0. I'm hoping this will be fixed there.

[nkaminski]

After some investigation, I was able to narrow down the affected element to the ha-textarea custom element initially introduced by @balloob in PR #1576 to work around a Webkit bug.

As the WebKit bug has now been fixed upstream for quite some time and given my limited experience working with Polymer and preact, I have opted to revert the breaking change as opposed to trying to make ha-textarea and paper-textarea functionally equivalent. This revert does indeed resolve this issue on Safari 12.1.1 (14607.2.6.1.1) as well as Chrome 75.0.3770.100.

However, I am not sure if there is a better way to implement this that does not break compatibility with older versions of WebKit.

Here is my fork with the (nontrivial) revert of this change https://github.com/nkaminski/home-assistant-polymer/tree/revert_1576

[dgtal1]

Great work guys! Thanks a lot @balloob for fixing this. What a relief it works now in HA!