I created a lock management interface. When using the web interface this works fine. If you type a code in the code field and click submit it runs its course.
The issue in the app is that if you type in a code it does not know the code is in the field unless you click outside of the code field. So even though you entered a code in the code field and click submit it does not know the code exists unless you click outside of the input_text field.
Can you open an issue for this on github please?
You closed this issue on GitHub saying its custom. This is with input_text. That is not custom. The mobile app team asked me if it also happens in the mobile chrome browser and I stated yes so they transferred it to the front end team.
jkrangel
September 13, 2020, 2:22am
5
I am having this issue as well! I am using the built-in input_text too
Thank you @jkrangel for bringing this up as its kind of irritating the issue was closed.
AndreKR
February 14, 2023, 1:44am
7
Can you post a link to the issue?
It was closed because no one acted on it.
opened 04:01AM - 29 Sep 20 UTC
closed 04:20AM - 04 Jan 21 UTC
Bug
stale
<!-- READ THIS FIRST:
- If you need additional help with this template please r… efer to https://www.home-assistant.io/help/reporting_issues/
- Make sure you are running the latest version of Home Assistant before reporting an issue: https://github.com/home-assistant/home-assistant/releases
- Do not report issues for custom Lovelace cards.
- Provide as many details as possible. Paste logs, configuration samples and code into the backticks.
DO NOT DELETE ANY TEXT from this template! Otherwise, your issue may be closed without comment.
-->
## Checklist
- [X ] I have updated to the latest available Home Assistant version.
- [X ] I have cleared the cache of my browser.
- [ ] I have tried a different browser to see if it is related to my browser.
## The problem
The issue in the app is that if you type in input_text it does not know the data is in the field unless you click outside of the input_text field. So even though you entered a data in the field and click submit it does not know the data exists unless you click outside of the input_text field.
This issues exists within the mobile app and also within the mobile chrome browser.
## Expected behavior
Should work the same as it does on chrome for desktop which knows the data is in the input_text field as soon as it is typed in as a value.
## Steps to reproduce
Provide steps for us, that helps reproducing your issue.
For example:
1. Create an entities card
2. Add a an input_text entity and a button entity
3. Configure the button to grab the text from input_text and do something with it when the button is clicked
4. Click outside of the input_text field after you enter data and the button now sees the data vs how it works on desltop in chrome browser.
## Environment
HASS: Version 0.115.2
Browser: Chrome for mobile 85.0.4183.127
OS: Android Version 11
## State of relevant entities
<!--
If your issue is about how an entity is shown in the UI, please add the state
and attributes for all situations with a screenshot of the UI.
You can find this information at `/developer-tools/state`
-->
```- type: entities
entities:
- entity: input_text.lockcode_code
name: "CodeTest"
- entity: input_text.lockcode_status
type: button
name: "Submit Code Test"
show_state: true
```
## Problem-relevant configuration
<!--
An example configuration that caused the problem for you. Fill this out even
if it seems unimportant to you. Please be sure to remove personal information
like passwords, private URLs and other credentials.
-->
```yaml
```
## Javascript errors shown in your browser console/inspector
<!--
If you come across any javascript or other error logs, e.g., in your browser
console/inspector please provide them.
-->
```txt
```
## Additional information
mousspi
November 22, 2023, 8:27pm
9
Issue is still there. Is there a chance to reopen it on GitHub ?
no but just open a new issue making sure to complete the issue template
Coincidentally I raised the same issue 3 weeks ago, and there has been no activity on mine either, so it will get closed automatically. Not sure how to make this more important because the issue is significant. In my case I’m using the iOS companion app, but I raised the issue against frontend, because that’s where the problem is.
4timepi
March 16, 2024, 7:17am
12
Hi, I’m struggling with the same issue. Has anyone managed to solve the problem? Maybe some workaround?
