-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I can't get this to work #6
Comments
Hi @RedNo7, First of all, try to check if there are any errors in the logs. Later I‘ll try with my partner‘s device (an iPhone), I have only tested it with a MacBook Pro, an Android phone and an Android tablet. Let me know your results. Regards Edit: This will not work by the way, your previous configuration is OK, do not add target because it is not needed: action: call-service
service: input_boolean.turn_on
data:
target:
entity_id: input_boolean.kiosk_mode |
Don‘t forget to restart Home Assistant.
Tested on the iOS device of my partner and it also works. Just take into account the speed at which you are trying to tap, maybe you are too fast or too slow, these are the parameters to recognise the taps:
Try to slow down a bit if you are going too fast or try to speed it up if you are going too slow, I am sure that you will find the spot quickly. But first we need to be sure that the plugin is loaded correctly. |
Hi! Thanks for replying! I have no relevant errors in my logs. |
Hi @RedNo7, |
Hey @RedNo7, |
Hi there - sorry, no it's been pretty busy. I hope to try it later this week. I'll let you know! |
Hi, The debug* option has been helpful. I can see the following so it is picking ups the taps but the service-call is not working:
edit: typo* and added extra log lines |
btw, do I need to restart if I change the contents of secret-taps.yaml? (I have been restarting up until now). |
That's great, that means that the taps are working but it is failing to call the service. We need to figure it out why.
No, it doesn't need a restart, only if you change the
Let‘s try to find what is happening, go to service: input_boolean.turn_on
target:
entity_id: input_boolean.kiosk_mode And let me know if it works. |
huh. It's just started working - no idea why. |
Are the taps working now? |
Yes, but only on the desktop (not on my iPhone). Then I turned I am restarting and clearing the cache (desktop and iPhone) after any chnage so not really sure what iOS going on, tbh. |
I really don‘t know what could be happening. Try to delete the Companion App cache in the app settings. |
These options are not related to the funcionality itself, they are just extras to log stuff, it should not make any difference. |
I can systematically make it work / not work by making changing OK, so 100% working on the desktop but only with Also, this is one of the reasons that It was never working on the iPhone - as, when I got it working with So the iPhone now also works, but it is hit and miss for me. The exact same sequence of taps (from a speed point of view) will now always work on the desktop and only sometimes work on the iPhone. I assume that I am on the threshold of speed (sometimes under, sometimes over). |
OK, it's working most of the time. If I tap softly on the iPhone it seems wot work much better. 👍 Thanks for your patience! |
It doesn‘t make much sense, could you try to reproduce it on the
Try to make it slower, real taps with fingers tend to be faster than with a touchpad/mouse. Slow your taps a bit and you will find the sweet spot. Let‘s try to focus on why |
will do - but later today - thanks! |
Hi @RedNo7, |
I’m so sorry. I got it working with ‘toggle’ and forgot to test turn_on. I’ll try to get to it this weekend. Thanks for your continued interest! |
Hi @RedNo7, |
Yes, absolutely. Thanks for your patience. |
Firstly I think this is a fantastic idea! 👍
I cannot, however get it to work.
I've added the repository installed via HACS, add the
extra_module_url
, addedwww\secret-taps.yaml
, reset the front-end cache on my iPhone but I cannot get it to work.Here is my yaml
I've tried variations eg:
But it doesn't work. Is there anything obvious I have got wrong?
The text was updated successfully, but these errors were encountered: