Yes, it’s working, I’m using companion app.
alias: tts na nspanel
sequence:
- service: notify.mobile_app_nspanel
data:
message: TTS
data:
ttl: 0
priority: high
media_stream: alarm_stream_max
tts_text: Hello
mode: single
icon: mdi:cellphone-message
I have to restart the panel every day, because it stopped receiving notifications after a few days. I use the panel as a doorbell chime for my eufy video doorbell.
I made an automation with adb integration sending a reboot command every day. Its working fine with seakys Tools (THANK YOU btw for this beautiful app!)and the companion app.
Something is happening…
New version is comming soon: NSPanel Pro Tools 2.2
Stay alert 
How to upgrade from a previous version?
did you ever resolve this? I’m getting the same now… despite not getting the message on an identical device yesterday!!! same firmware, straight out the box etc.
Nowadays you dont need to install Xposed, check my github link above
I had homeassistant working nspanel pro done via adb, but somewhere I had the feeling I needed to update the firmware. so did reset (5 times power thing) and did the update. now I am not able to connect via adb anymore via network (connection refused)
so after restoring back to firmware 1.6, stil no luck with connection via network. the app (iphone) tells me adb is enabled, but cant seem to connect. anyone an idea how to connect? kind of frustrating…
regards
ok, solved it.
I took the screen apart so I could use the micro usb connector. I had to remove the touch screen flat cable, but you can put it back once done.
I connected a keyboard via micro usb connector (used OTG cable), went to settings (windows button + N). enable developer mode, and enable usb debugging.
still no idea why it doesn’t by default as the mobile app tells me adb is enabled. hope this helps other people.
ciao!
Hi there, new here and a newby, but I have some thoughts to share.
Initially I wanted to extend the useCases for my NSPanel Pro with v3.3.0.
I soon found out that the original eWeLinkControllePanel Launcher needs to run in Foreground in order to be “online” in the eWeLink-Cloud (controlle Subdevices and get Temprature readings in HA Sonoff Integration).
My solution:
Running HA Companion App in the Background while still useing the original Launcher and have a HA Dashboard via URL Website open.
This enabled me to sync some sensors and use NSPanel as Bluetooth Beacon Monitor while not loosing any OutOfTheBox Features. I also got a proximity Sensor Flow working for auto. screen on time.
Open NSPanel customization options:
Proximity Sensor:
Home Assistant Companion App:
At the end:
Switch to the eWeLinkControllePanel Launcher, to reactivate native NSPanel Pro functions.
Accomplished:
If you guys are interested in more detailed information I might write a Guide.
Time for me to look into NSPanel Pro Open API
Have a good one.
Do you have any idea how you resolved this issue? My NSpanel pro is stuck on the unanimated sonoff logo. And it seems there is nothing I can do to get it to boot again.
You are the Best!
You just go all the way again with adb connect -ipAddress, then do the adb insttall command with a " -r" (without the " ") attached. Then it will “update” the existing apk.
Hello guys,
Today I updated my NSPanel to 3.0.0, hoping for a webvew update.
But te versione is still 107.x…
My dashboard isn’t really smooth, what do you suggest? Is a Webview update a way to make it better?
A year ago I tried to update it installing xposed, but it soft briked my device. Is there a way to do it without xposed?
Thanks
Anyone tried the new NS Panel Pro 120?
120mm height instead of 86mm, higher resolution, probably faster HW, and apparently Matter support besides Zigbee.
I was looking at this earlier. It has a slightly updated GPU, that appears to be it. Probably needed for the higher resolution display. Same rockchip quad core arm CPU, 2gb or ram and 8GB emmc storage. Regarding matter, most devices used IPv6 but now thread devices are starting to slowly release. Thread was created by the same people that created Zigbee and is very close to the 2.4Ghz network so I imagine all the matter stuff is more software related. They are supposed to be running the same code but the original was so broken out of the box that you have to do multiple firmware updates but that apparently causes other issues if you want to follow one of the ADB guides. There might be some small hardware changes but based on Sonoff’s website the GPU is the only difference in the specs. That and a 4.7" display instead of 4" s.
I have issues with installation of “Xposed” New NSPanel Pro 120.
Device doesn’t boot up (stuck at “Sonoff” logo). The only way to return it back to normal is to reset the power 5 times during the boot for the recovery image to get installed.
Actually, if anyone was able to fix that, please let me know.
Xposed isn’t needed on the 120 as WebView is already at the correct version. Another user was having the same issue with the Sonoff logo posting on Reddit. He followed blakadder’s guide and just skipped the entire updating of WebView. Xposed is only needed to update WebView on the original napanel pro. I would imagine the napanel pro utility works also but hasn’t been confirmed to my knowledge.
I’m wishing I would have gotten one when it was 50% off from Sonoff but that deal is over. Easily worth 65$ US but now it’s back to its original price.
I bricked it while trying to update the WebView component, but it comes with 107 out of the box. So after restarting from the recovery image I left it as it is.
Without Xposed you can simply upgrade Webview to any version just check my github link there is the solution.
It’s important to emphasize that installing Xposed is NO LONGER necessary these days, but everyone seems to try it and take the risk!