-
|
Hi all, I have two panels, one running FW 1.7, the other 2.2. The 1.7 has a usable proximity sensor, reporting 0 from a distance of about 2.5 meters, so I have no problems with waking the display when a person approaches. The one running 2.2 doesn't go lower than ~1000, and doesn't pick up on motion until you're about 20cm away, which makes the wake up on approach very unintuitive for people that don't know the inner workins of the sensor settings. Verbose log from the FW2.2 device in first comment, but nothing obvious there, just getting triggered... My first question is, does anyone know if this is a firmware issue, or a hardware issue? Any other ideas or troubleshooting tips? See screenshot from each one, with no one anywhere close to them. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 11 replies
-
|
Log from FW 2.2 after enabling DEBUG+VERBOSE 06-30 19:48:29.781 1354 1354 I c : Log level is DEBUG |
Beta Was this translation helpful? Give feedback.
-
|
Sorry to say that but this sensors are not designed to sense meter distances. Originally the reliable sense distance is only couple of cm. Usually <20cm. So you are quite lucky to have one which has 2.5m long distance sensitivity. |
Beta Was this translation helpful? Give feedback.
-
Ok so if you have them connected to HA with NSPanel Pro Tools, you get a few button entities. To wake you just have to do a button.press action on button.yournspanel_wakeup and _sleep. You can also skip the whole MQTT thing and set up an integration called "Android Debug Bridge", that gives you access to sending ADB command directly to the OS on the panel, which can in some cases be more reliable. I actually use a mix of these, I use the button.nspanel_wakeup to wake the screen, but I use the ADB command "adb shell input keyevent KEYCODE_POWER" to put it to sleep. This is the action call for each: Let me know if you have any questions! |
Beta Was this translation helpful? Give feedback.
-
Why dont you use mqtt sleep command? |
Beta Was this translation helpful? Give feedback.
-
|
Great question, I think the original reason was that some combination of nspanel pro tools settings and fullykiosk settings was making it work inconsistently. I'm pretty sure the issue was on my end so I'll test going back to the mqtt command to simplify... |
Beta Was this translation helpful? Give feedback.
-
what do you mean "does not work from any distance"? what do you see on sensor tab? Does it stay 0 always? |
Beta Was this translation helpful? Give feedback.
-
|
wakeup is working, no I have only issue with triggering sleep if noone nearby as I wrote in the another thread |
Beta Was this translation helpful? Give feedback.
-
|
Thank you. The 'buttoon' to sleep is working fine and with the proximity
sensor I can wake up the device. However I have one issue, I can't find an
entity which can be used for trigger to turn off the display when there is
no proximity
I have only this
event.nspanel1_proximity
However, the events are quite interesting :)
[image: image.png]
…On Sun, Sep 29, 2024 at 10:16 PM seaky ***@***.***> wrote:
can you please share how to do it? I also have a new nspanel120 and
wake-up by wave/proximity not working at all (from any distance), so since
I have an mqtt server as well, it seems a great idea to wake up by some
automation.
Thank you L:
Ok so if you have them connected to HA with NSPanel Pro Tools, you get a
few button entities. To wake you just have to do a button.press action on
button.yournspanel_wakeup and _sleep. You can also skip the whole MQTT
thing and set up an integration called "Android Debug Bridge", that gives
you access to sending ADB command directly to the OS on the panel, which
can in some cases be more reliable.
I actually use a mix of these, I use the button.nspanel_wakeup to wake the
screen, but I use the ADB command "adb shell input keyevent KEYCODE_POWER"
to put it to sleep.
This is the action call for each:
target:
entity_id: media_player.adb_nspanel_eldhus (the ADB integration creates "media player" devices for the panels
data:
command: adb shell input keyevent KEYCODE_POWER
action: androidtv.adb_command
target:
entity_id: button.nspanel_stofa_wakeup
data: {}
action: button.press
Let me know if you have any questions!
Why dont you use mqtt sleep command?
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3RO2QY46E2VS4VTWAIIADZZBNYBAVCNFSM6AAAAABKEBC7Q6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZZGEZDEOI>
.
You are receiving this because you commented.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
This is the picture I mentioned above... so what should I use as a trigger?
|
Beta Was this translation helpful? Give feedback.
-
|
I have no idea what I'm looking at there or what those values are, you have to paste something else. Are you using the proximity sensor on the panel? What are those values? |
Beta Was this translation helpful? Give feedback.
-
|
This is the only entity for proximity sensor for this nspanel and the picture above represents the 'states' I see in MQTT event.nspanel1_proximity |
Beta Was this translation helpful? Give feedback.
-
|
The history shows it has been getting a lot of different values, what are those values? |
Beta Was this translation helpful? Give feedback.
-
|
I have no idea.
All I can see is ' detected an event' in different colors which if
beautiful but not very useful :)
L:
…On Thu, Oct 3, 2024 at 4:46 PM fcassata ***@***.***> wrote:
The history shows it has been getting a lot of different values, what are
those values?
—
Reply to this email directly, view it on GitHub
<#111 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3RO2VCUU5CPOIQAUEIZPLZZVKFLAVCNFSM6AAAAABKEBC7Q6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOBTGMYTMMY>
.
You are receiving this because you commented.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
Sorry to say that but this sensors are not designed to sense meter distances. Originally the reliable sense distance is only couple of cm. Usually <20cm. So you are quite lucky to have one which has 2.5m long distance sensitivity.