Wake on gesture, mode of operation
tom8635 opened this issue · comments
Hello,
I currently have 4 x NSPanel Pro's, 2 on FW 1.11.0 and 2 on 1.5.0 all configured with wake on wave, wake from screen saver but no wake on gesture. MQTT server is configured.
The devices on FW 1.5.0 when I tap the screen the automations run, but the screen does not wake up
The devices on FW 1.11.0 when I tap the screen the automations mostly run but the screen wakes up, sometimes the automations do not run, I guess this is due to the screen wakening up prior to registering the touch event
Wave always wakes the screen.
Running your App version 2.1.0
My question is what the intended mode of operation is, my preference would be as per FW 1.5.0 and can this be replicated on the FW 1.11.0 devices, I am happy to Downgrade/upgrade FW if I can get the desired results.
Regards
Hi
First, clould you post or attach here your log snippet, what I would like to check the before sleep and after touch logs.
Just search for the ACTION_DREAMING_STARTED keyword.
Next, please post your config file but make sure not to include your password.
Config location:
adb root
adb shell cat /data/user/0/com.seaky.nspanelpro.tools/shared_prefs/com.seaky.nspanelpro.tools_preferences.xml
regards
ümmmm you mentioned you use the wake from screensaver and meanwhile you say that "the screen does not wake up"
If you use the wake from screensaver options you need to configure a screensaver app which leads to the screen will never turn off. That's the purpose of the screensaver. So the screen wont wake up I'd reather say it will exit the screensaver.
Do you really configured the screensaver properly?
nspanelpro.tools_preferences FW 1.5.0.txt
nspanelpro.tools_preferences FW 1.11.0.txt
I have attached the preference from a 1.5 & 1.11 FW device as requested.
Struggling to access the logs, do you have any advice, I have tried 'adb shell logcat > log.txt' and searching for 'ACTION_DREAMING_STARTED' but nothing is found
I am not using a Screensaver so maybe I should turn this off, I have tested with both and has no change on the end result
Indeed you dont need the wake from screensaver it is non-effective in your scenario.
1.)
I dont see any sensor configuration in your config file!
If you read the manual you will see that I emphasize everywhere that the sensors need to be configured properly!!
2.)
In the MQTT integration you tirgger every tini-tiny events. I mentioned in the manual you configure only those events what you really need. Because you will flood your HA with a tons of unsed events.
3.) Based on the manual
wake-on-wave: will wake up the device only if you move your hand in front of the device. So wont wake up upon screen touch.
wake-on-gesture: will wake up the device if you touch the screen by a simple tap or any othe gesture. (TAP is the simpliest gesture)
wake from screensaver: will exit the screensaver if you use wake-on-wave becuse a screen tap will dismiss the screensaver by default so you dont need any app for it.
All in all you have to know what you want and read the manual by the way in the end of the manual there is a some HA config examples for different scenarios.
In your case I assumed that
- you want to fire a trigger in HA if you touch the screen while the screen is dark
- Display: Turn off wake-on-gesture
- Integration: Enable Gesture - tap publish event
- you want to wake up the device if you do a handwave without triggering anything
- Sensor: configure proximity sensor trigger point
- Display: Turn on wake-on-wave
Why has this worked for you?
You haven't configured your proximity sensor so the range is almost infinte when you touched the screen sometimes the wake-on-wave was trigged. It heavily depends on the device preconfigured sensitivity.
Did it work?
Hello, Apologies for delay in response
Wake from screensaver is now turned off.
- I honestly did think I had configured this as per the manual, I have now configured on all units but there has been no change in operation or range of wake on wave. They are all set to about 1000 for about 30mm range. I also tried to set the threshold high so that the sensor only picked up when almost touching the device without success.
- MQTT configuration has been limited to only required triggers, I understand your point, I only had this as I was testing what I can do.
Your assumption is correct, The devices on FW 1.5.0 do exactly that, The devices on FW 1.11.0 wake up on tap (even if I approach the device from the bottom, trying to avoid the proximity sensor) all devices are configured then same.
U were right, I got a new device with fw 3.0.0 and I realized that the touch gesture is not working properly because in newer fw-s they changed the powermanagement behaviour and the device can wakes up to touch without my app. I’ll continue the investigation…