Sonoff NSPanel by ITead - Smart Scene Wall Switch based on ESP32 and custom Nextion Touch Screen Panel Display (non-Pro variant)

frankz · October 14, 2023, 12:10pm

Is there a possibility to round sensor values using appdaemon?

{{ states('sensor.active_power')|float)|round(0) }}

Does not work in the screensaver entity page.

jobraun · October 18, 2023, 3:07pm

please post your screensaver config, you can overwrite the value with a template like on all other entities

JJ6767 · October 19, 2023, 6:01am

Hello !

I’m trying to format timeAdditionalTemplate to:

Capitalise the first letter of the weather condition (so it shows as ‘Cloudy’ and not ‘cloudy’)
possibly change the font size to make it larger
I’m also trying to change the font color using tTimeAdd but not getting the syntax correct.

Any guidance would be awesome

    timeAdditionalTemplate: '{{states("weather.home")}}'
    tTimeAdd: [102,255,25]

jobraun · October 21, 2023, 10:29am

    screensaver:
      timeAdditionalTemplate: '{{states("weather.home") | capitalize }}'
      theme:
        tTimeAdd: [102,255,25]

There is no way to change the font size.

JJ6767 · October 22, 2023, 9:51am

@jobraun is the bloody best !

Works perfectly - thank you so much !!

JJ6767 · November 16, 2023, 2:28am

Y’all going to need this today after the Appdaemon update …

ClaireRovic · November 30, 2023, 6:31am

Hi All,
Before all the recent changes I would use a include statement that looked like
!include /config/appdaemon/apps/nsp-masterss.yaml.
This for obvious reasons no longer works.

Unfortunately I have tried a few combo’s (randomly) i.e.
!include /addon_configs/a0d7b954_appdaemon/apps/nsp-masterss.yaml
Can somebody point me in the correct direction to using includes correctly in the new world.

Thanks Heaps

veli · December 4, 2023, 8:13pm

edit: i seem to be blind and/or dumb, since Blakadder had already updated their document…

Found it some time later had to uart the Nextion, but here it is for those still rocking the stock:

  - platform: template
    name: Wallpaper
    id: ${device_name}_wallpaper
    icon: mdi:cat # mdi:wallpaper
    entity_category: config
    optimistic: true
    restore_mode: RESTORE_DEFAULT_OFF
    turn_on_action: # „ºU™á.."HMI_wallpaper":1m2U™Ö'. 0x87 135 {"HMI_wallpaper":1}
      lambda: |-
        id(ns_panel).send_json_command(0x87, "{\"HMI_wallpaper\":1}");
    turn_off_action:
      lambda: |-
        id(ns_panel).send_json_command(0x87, "{\"HMI_wallpaper\":0}");

stomko · December 5, 2023, 1:40pm

Can microphone be used by esphome firmware? I have searched a lot but have not found a single mention of GPIO where microphone is connected, other than it has microphone (in marketing materials)

Hedda · December 5, 2023, 2:05pm

Sounds like you are confusing the original “Sonoff NSPanel” which this thread is about with the “Sonoff NSPanel Pro”(?), as the former that is based on an Esspressif ESP32 does not have a built-in microphone but the latter that is based on Android OS does, (note that they are not based on the same platform components at all, as you might understand).

Or do you mean you soldering your own microphone to the original “Sonoff NSPanel” (which this thread is about)?

Anyway, the ESPHome does support Microphone Components if the hardware is already connected, see → Microphone Components — ESPHome

For a ESP32 development kit hardware with built-in microphone (and speaker) check out Espressif ESP32-S3-BOX-3 and the M5Stack Atom Echo.
ESP Home and ESP32 S3 Box? or for better hardware the Onju Voice (Google Nest Mini speaker replacement PCB with ESP32-S3):

github.com

esphome/firmware/blob/d584c44151100d5ef36d2994347807b76027eef0/voice-assistant/esp32-s3-box-3.yaml

---
esphome:
  name: esp32-s3-box-3
  friendly_name: ESP32 S3 Box 3
  name_add_mac_suffix: true
  platformio_options:
    board_build.flash_mode: dio
  project:
    name: esphome.voice-assistant
    version: "1.0"
  min_version: 2023.11.5
  on_boot:
      priority: 600
      then: 
        - display.page.show: initializing_page
        - component.update: s3_box_lcd
        - delay: 30s
        - if:
            condition:
              lambda: return id(init_in_progress);

This file has been truncated. show original

github.com

esphome/firmware/blob/d584c44151100d5ef36d2994347807b76027eef0/voice-assistant/m5stack-atom-echo.yaml

---
esphome:
  name: m5stack-atom-echo
  friendly_name: M5Stack Atom Echo
  name_add_mac_suffix: true
  project:
    name: m5stack.atom-echo-voice-assistant
    version: "1.0"
  min_version: 2023.11.1

esp32:
  board: m5stack-atom
  framework:
    type: esp-idf

logger:
api:
ota:

dashboard_import:

This file has been truncated. show original

stomko · December 5, 2023, 2:46pm

thanks. According to the description, NSpanel (not PRO version) does have microphone:

https://itead.cc/product/sonoff-nspanel-smart-scene-wall-switch/

【Multiple Ways to Control】You can use the dual-channel switches, touchscreen, and eWeLink App to control SONOFF NSPanel; Besides, SONOFF NSPanel supports Alexa , Alice , Google Assistant , and even Siri Shortcuts , you can control your home appliances with simple voice control.

ah, I see now how they mean it. So it does not have microphone indeed. Sad.

Hedda · December 5, 2023, 4:30pm

The original original “Sonoff NSPanel” does not have a built-in microphone, and its description only mentions that it can be integrated (over a WiFi network) and controlled by third-party smart home ecosystems like Alexa (e.i. Amazon Echo smart speakers/displays) and Google Assistant (e.i. Google Home/Nest smart speakers/displays).

cfgroenewald · January 9, 2024, 2:42pm

Hi Blackadder. Sorry I am very inexperiences, but do you have a photo or info on what pins to connect to 5V for the spaniel pro please?

IanQ · January 22, 2024, 6:01pm

This is used in the Esphome code for a Sonoff NS Panel, using Esphome 2023-11-6.

number:
  # Screen brightness
  - platform: template
    name: Brightness
    id: brightness
    entity_category: config
    unit_of_measurement: '%'
    min_value: 0
    max_value: 100
    step: 1
    initial_value: 30
    set_action:
      then:
        - lambda: 'id(disp1).set_backlight_brightness(x/100);'
        - lambda: 'id(disp1).send_command_printf("Home.brightness.val=%i", int(x));'
        - lambda: 'id(disp1).send_command_printf("Settings.n0.val=%i", int(x));'
        - lambda: 'id(disp1).send_command_printf("Settings.bright.val=%i", int(x));'

It creates a “Brightness” slider control in Home Assistant that has an initial value of 30. When it’s moved, the control shows the value it is moved to and it sends that value to the NS Panel using the set_action: lines. This is all working correctly.

Using the touch screen on the NS Panel you can also set the screen brightness using a “Screen Brightness” slider control. I have managed to get the “Brightness” slider in Home Assistant to move the NS Panel “Screen Brightness” slider position and it’s value to match the Home Assistant “Brightness” position and value so they stay in sync.

What I have been unable to do after nearly 3 days of searching, reading and trying different methods is to make the “Brightness” control in Home Assistant change position and value to match the NS Panel “Screen Brightness” slider when that is moved. I don’t think the problem I’m having is just because it’s a Sonoff NS Panel I’m using it with. I think I’m just not using the correct method to do it, but I could be wrong.

Has anyone any suggestions on what I’m doing wrong and how to achieve this?

IanQ · January 23, 2024, 1:21am

Typically after posting my question a couple of hours later I found an alternative way to do it!

In Home Assistant I created a helper input_number.test_slider. Then created an automation that is triggered when the input_number.test_slider is moved which sets the NS Panel Screen Brightness slider to the same value

alias: Test Slider NS Panel Brightness Change
description: Test Slider Changes NS Panel Screen Brightness
trigger:
  - platform: state
    entity_id:
      - input_number.test_slider
    from: null
condition: []
action:
  - service: number.set_value
    target:
      entity_id: number.nspanel_brightness
    data:
      value: |
        {{ states('input_number.test_slider')|int(0) }}
mode: singletype or paste code here

I created a second automation that is triggered by the NS Panel lightslider being moved which sets the input_number.test_slider to the same value

alias: NS Panel Brightness Change
description: NS Panel Screen Brightness Changes Test Slider
trigger:
  - platform: state
    entity_id:
      - sensor.nspanel_lightslider
    from: null
condition: []
action:
  - service: input_number.set_value
    target:
      entity_id: input_number.test_slider
    data:
      value: |
        {{ states('sensor.nspanel_lightslider')|int(0) }}
mode: singletype or paste code here

I tried to use number.nspanel.brightness as the trigger entity_id and for the value in the second automation but it didn’t work. So I had to create a new sensor in the Esphome code

sensor:
  # Gets the value of the Screen Brightness into HA
  # Uses On Release code in the Nextion Screen Brightness slider for it to work.
  - platform: nextion
    id: lightslider
    name: lightslider
    variable_name: lightslidertype or paste code here

In the Nextion Editor add this code to the Touch Release Event for the Screen Brightness slider to pass the brightness value to Home Assistant via the lightslider sensor

printh 91
prints "lightslider",0
printh 00
prints n0.val,0
printh FF FF FF

Moving either slider now changes the screen brightness and the other sliders value and position so they stay in sync.

The only remaining issue is that the lightslider sensor shows as “Unknown” in Home Assistant until the Screen Brightness slider is moved. Trying to check for “Unknown” using isnan doesn’t work and I haven’t been able to find a way that does work.

sensor:
  # Gets the value of the Screen Brightness into HA
  # Uses On Release code in the Nextion Screen Brightness slider for it to work.
  - platform: nextion
    id: lightslider
    name: lightslider
    variable_name: lightslider
    filters:
      - lambda: !lambda |-
          if (isnan(x)) return 30;
          return x;

Hopefully other people will find this useful.

EdwardTFN · January 23, 2024, 7:05am

github.com/esphome/feature-requests

Change in Nextion integration to make more efficient use of the ESP-Home flash memory

opened 05:28AM - 07 Apr 22 UTC

Hellis81

integration: nextion

**Describe the problem you have/What new integration you would like** I would like a change in the Nextion integration. The reason is that many of us can't squeeze enough in the ESP to get what we want from our displays/NS panels. Currently adding "buttons" means you add this kind of code: ``` binary_sensor: - platform: nextion name: Light1 page_id: 2 component_id: 23 on_click: - homeassistant.service: service: light.toggle data: entity_id: light.light1 ``` I noticed however even without this yaml the Nextion display sends a message to ESP-Home saying: ``` Got touch page=2 component=23 type=PRESS Got touch page=2 component=23 type=RELEASE ``` What if we don't include page and component_id in the yaml and just have a "Nextion sensor" that is exposed to Home Assistant. Perhaps a sensor with state `page=2, component=23, type=press` then release. That way we can do all the automations in HA instead of loading the ESP full of yaml that is only button clicks. With the above we would have one sensor that captures any "clicks". What we have today is perhaps 20 sensors just to get the buttons to work. Another change I would love to see is a sensor with the current page number. The reason is again to get fewer sensors in ESP-Home. Imaging a sensor saying `page0`. In Home Assistant we add a template sensor with an array like this: ``` array = ["page0.component0": "light.light1", "page1.component0": "sun.sun", "page3.component0": "person.someone_geocoded_location"] {{ states(array[states('sensor.page') ~ "component0"]) }} ``` and then we add another with componenet1 for all pages. So the above sensor will change between several states depending on the page, and I think that can be used to push the correct states to each Nextion field. **Please describe your use case for this integration and alternatives you've tried:** I tried using the logger and send that to Home Assistant but I could not get it to work. I posted my test on the community page: https://community.home-assistant.io/t/sonoff-nspanel-smart-scene-wall-switch-by-itead-coming-soon-on-kickstarter/332962/623 **Additional context** Whoever does this change will probably be a hero to all NS panel owners who is currently dreading the 68.4% limit.

EdwardTFN · January 23, 2024, 12:50pm

Anyone here ever succeeded in using PSRAM from NSPanel?

bassor · January 25, 2024, 5:19pm

Been using GitHub - joBr99/nspanel-lovelace-ui: Custom Firmware for NsPanel with the design of HomeAssistant's lovelace UI in mind, works with Tasmota. for quite a long time succesfully. Now the panel is not responding to touch much at all.
Is there a way to boot the system? (other than removing house fuses…)

EdwardTFN · January 25, 2024, 6:55pm

Have you tried the reset button in the bottom of the panel?

bassor · January 25, 2024, 7:42pm

Thanks! Totally forgot that there’s a reset button. Pressing that didn’t help, just resulted in “Waiting for content” screen.
The Tasmota gui is working and there’s a reset option, also: same thing.

Somehow HA has lost the device totally.

EDIT: Updated HACS, AppDaemon, restarted HA… at least. Now NSPanel entities are seen by the HA again. Just the panel GUI is still missing.
Now it seems that the AppDaemon stops working.

EDIT2: AppDaemon secrets.yaml location needed an update, this solved it AppDaemon won't start - complains about secrets.yaml - #21 by p-x