It looks like its not a breaking change. I checked my panel directly before making any changes and it was still fine.
I then deleted my automation and recreated from blueprint.
It defaults to “Unknown entity selected” when a drop down is empty but populated fields stay populated so fingers crossed, this shouldn’t stop anyones panels from functioning! Still needs to be looked at however as its a bit misleading.
I have a strange issue when I create a new NSpanel configuration. I have one running without issues for a while now, but this new one drives me a bit crazy.
This is the error, after creating a basic new config…
This is usually related to Home Assistant naming the services differently than naming the entities inside the device.
Please go to Settings > Developer Tools > Actions tab, then type “_component_text” on the action name and you should find the name it is using for this specific panel (you will also see the name for other panels, just ignore those).
When you have the proper name used on the actions, you can find the “Override name” (or something like that) at the very end of your Blueprint settings and try to add the name you found.
If that isn’t working, please report as a bug on GitHub and share details about your panel’s yaml.
Thanks. I played with it some more and deleted out the setup I had. Paid attention to the naming and all while reinstalling it and all went good. No more errors.
Can anyone help me out? I’m planing to buy a sonoffo panel and connect to a two button swith. Those are smart bulbs. I control them now with hue switch.
Now I want to control those lights with sonoff panel. Is it possible to use the sonoff panel buttons to active scene for those lights. Or is that not possible?
You can use the panel to control any light connected to Home Assistant. You will be able to adjust brightness, temperature, and color, apart of turning your light on/off.
You don’t have to wire your light to the panel’s relays, as the control could be done via Home Assistant.
If you have a light wired to the panel’s relays, you can control locally, but those relays are limited to power on/off.
In cases like yours, what I have seen people doing is to connect the light to the relays, but set all the control via Home Assistant. You have all the flexibility.
With this setup, you can configure your panel to use HA normally, but use the relays when Home Assistant (or the WiFi) is not available, so you have a fallback to ensure things will work anyways.
I got to install and play with an NS Panel last weekend and got it working without too much hassle. Hereby my thanks for making this fantastic blueprint.
It makes me excited to install more of them through my home.
I do have one question, I added the airco unit of our bedroom (also where I installed the panel) to the climate entity page, and it works for the most part.
Temperature, heating, cooling, regular fan and drying options are all present, the only thing I am missing the fan’s speed control.
Is that hidden somewhere, or has it been left out for a reason?
It’s not a huge deal, as we can control it through the HA app on the phone as well.
I did the upgrade as discribed , but after the flash :
> :49:38.564][W][nextion:109]: Not connected > [09:49:39.181][W][nextion:109]: Not connected > [09:49:39.919][W][nextion:109]: Not connected > [09:49:40.429][W][nextion:109]: Not connected > [09:49:41.180][W][nextion:109]: Not connected > [09:49:41.920][W][nextion:109]: Not connected > [09:49:42.431][W][nextion:109]: Not connected > [09:49:43.175][W][nextion:109]: Not connected > [09:49:43.908][W][nextion:109]: Not connected > [09:49:44.420][W][nextion:109]: Not connected > [09:49:45.171][W][nextion:109]: Not connected > [09:49:45.920][W][nextion:109]: Not connected
If i experience problems with inconsistant updates i often get lucky with an old trick: cold restart.
Unplugging the panel from power is a bit more work than software reset but mostly successful. Triggering a TFT update worked after the restart.
Hi Edward. I have migrated to NS Panel Easy and all went smoothly and works perfectly, except the _wake_up action is missing in your config. I looked in the actions in the developer tools, all the actions are there except _wake_up. Any suggestions?