NSPanelManager icon indicating copy to clipboard operation
NSPanelManager copied to clipboard

Relay default mode on, off after power failure

Open ebcjaa opened this issue 3 months ago • 6 comments

Describe the bug If relay default mode is set to on, after a poweroutage when power is restored the relay is off

To Reproduce Steps to reproduce the behavior:

  1. in NSPanelmanager set relay1 mode to "on"
  2. verify relay is on, e.g. lamp is on
  3. power off nspanel 4 restart homeassistant 5 power on nspanel -. relay is off

Expected behavior realay should be on after powercycle

Screenshots If applicable, add screenshots to help explain your problem.

Environment info (please complete the following information):

  • Home Assistant
  • Browser chrome,
  • NSPanelManager versionVersion: 2.1.1-beta-h1
  • NSPanel Firmware version 0.3.666

Additional context

ebcjaa avatar Sep 19 '25 07:09 ebcjaa

This is strange as it works as expected on my end. Do you happen to have the relay added to a relay group?

tpanajott avatar Sep 28 '25 14:09 tpanajott

Sorry, Incomplete "To reproduce" it is now updated, and I verified that it does reproduce the issue...

ebcjaa avatar Sep 29 '25 19:09 ebcjaa

That all very strange as I have that setup for one of my panels and it's working just fine. When does it fail? Do you have to restart HA for it to fail or does it fail when simply restarting the panel?

tpanajott avatar Oct 05 '25 15:10 tpanajott

Yes, this is strange, I am sure that I had to restart HA the last time I tested. but now it happens with only a reboot of the NSPanel. I am on 2.1.3-beta did a force firmware update. I did try with diffrent settings on button and relays, but after a NSP reboot relays are off :( I did check the log only one warnig " Failed to convert temperature to float" Any ideas?

ebcjaa avatar Nov 20 '25 21:11 ebcjaa

No, not really of the top of my head. I'll try and walk through the logic or the default states once more this weekend if I have the time.

Thanks for doing aom testing and reporting back!

tpanajott avatar Nov 21 '25 11:11 tpanajott

I think I found the issue in the firmware, the fix should be available in the next beta release.

tpanajott avatar Nov 22 '25 16:11 tpanajott