No se como configurar esta parte “Set NSPanelPro Spkr Audio Address → Enter the audio file addres”. Podrias darme un ejemplo de como seria la ruta?
I wish we could also be able to see the Media so we can set text to speech messages as well. Sadly one cannot have it all.
I hope you had a nice holidays.
I conducted a test and encountered the same issue you described. This may be related to the NSPanelPro’s system. Please allow me some time to investigate further. Thank you for your understanding.
Thank you for taking the time to test this. Any updates?
It is a common use case to create room detection where you have the beacon transmitter on your phone and the beacon monitor on stationary devices in every room. At the moment I am not able to accomplish this without the described bluetooth permission on NSPP.
Microphone and speaker capabilities will be enabled in version 4.4.0 (scheduled for February 9th), supporting their use within Home Assistant.
It was, thank you. There is a slight issue though. The system requires the audio file played from the speaker to be inside NSPP file system that is not accessible in any way (not through device nor through eWeLink). Only way to add a file to be played through the speaker, that I found, is by recording it with the microphone. This causes loss of quality and is also otherwise quite rudimentary.
The goal is to have the NSPP speaker play a notification or a welcome sound that I have created for example using AI. We just have to find a way to move the sound file to the device in the correct location and then I can input it with the HA mqtt interface into the Spkr play command.
Hi, it’s being processed. We’ve found a solution to enable this permission, but we’re not sure if it will take effect after enabling it. May I ask how you specifically use this feature? (I want to verify if the function works properly.) Can you see the RSSI of each device? Or do you need to configure it on other pages?
In addition to playing the built-in audio on the NSPanelPro, you can also enter the audio file address.
But this way I’ve to set a link to an sound file (accesable through http). Afterwards I can play it.
It’s not possible to simply play an internal sound with only one command, right? Like the http API endpoint /open-api/v1/rest/hardware/speaker, where I can send:
{
"type": "play_sound",
"sound": {
"name": "doorbell1",
"volume": 100,
"countdown": 1
}
}
Hi, After version 4.x.x, some API interfaces are temporarily unavailable, so this setting will not take effect. If you choose to play internal files, you can select the audio list after choosing NSPanelPro (Spkr Select NSPanelPro Audio), where the local alarm ringtones of NSPanelPro will be displayed.
My NSPPs are now updated to 4.3 and I’m interested in the announcement that screen sensors (on/off, brightness etc.) are exposed to Home Assistant via MQTT.
Although I do have Mosquito broker for HA, it’s not currently running, but through the SonoffLAN custom integration I can see controls for screen On and Off. If I opt to use MQTT, will that enable the additional ‘brightness’ etc sensors/controls, or will that create an entirely different device, independent of that provided by SonoffLAN and with all the sensors and controls promised for NSPP 4.3?
Just trying to get a handle on what provides, or will provide what.
If you connect MQTT through the entry provided in the eWeLink app, you can synchronize the NSPanel Pro itself and some of its capabilities (such as the screen switch, brightness you mentioned, and the new version also supports syncing the speaker and microphone to Home Assistant for playing audio files) to Home Assistant. This is a different synchronization method compared to SonoffLAN. The synchronization via the eWeLink app supports more features.
Thanks for that and I have now set this up using Mosquitto MQTT broker.
However, when using the ewelink app (iOS) to set up the NSPanels it is not at all obvious that one needs to access the Zigbee over MQTT settings, just to set up the MQTT connection even though nothing to do with Zigbee.
More importantly, it is impossible to use a hostname and only an actual IP address is accepted. If a real working hostname is entered, the app just complains about an ‘invalid DNS name’ (or words to that effect) which is totally untrue. I run my own local DNS and can access any device over the LAN by its hostname. The (search) domain and address for this DNS server are supplied by the DHCP server and it works. Always has done in fact. Why is your app unable to utilise the correct standard protocols to resolve a simple hostname. The iPhone on which it is running has all the correct details and can resolve every hostname used on this LAN. Why is the ewelink unable to do this?
This is a serious error as the IP address of the Mosquitto server may change and then your devices would fail. Using a hostname avoids this as that can be persistent and never change which is after all one of the great advantages of the DNS system.
Why are your devices unable to cope with real resolvable DNS hostnames?
Ken G i l l e t t
////////
As already mentioned I have set up the MQTT connection and can access more data from the NSPP, but it is stated that v4.3 exposes the screen brightness and in Home Assistant/Mosquitto this is indeed shown, but as ‘Unavailable’.
Why is that and how can I enable it and be able to control the level?
Hi, the NSPanel Pro supports mDNS discovery. However, when this feature was being implemented, we encountered some issues with domain name resolution, so it currently does not support domain name resolution. I agree with your suggestion — since IP addresses can change, I will submit a technical pre-study ticket to the team. We will look into a solution in a future version.
Turning off Auto Brightness does indeed enable the manual Brightness control. 
However, I have another question about screen brightness.
How does Auto mode control the brightness level?
By which I mean what are the max. and min. limits and what are the actual light levels that correspond to the brightness levels being set? What is the relationship between light level and screen Brightness?
I’d rather just leave it on Auto, but would like to know what the Brightness level is being set at so I can determine if I need to take manual control or not.
There is a light intensity sensor and it is set to what the screen brightness should be at a given level.
We’ll say I’ll wing it and it’ll be the same.
My domain: I don’t believe they would actually test what the appropriate screen brightness is at a given level. For that, a test room with the necessary equipment needs to be built.