Relay No Longer Working After Updates #2120
Labels
Comments
JS1Dev
added
the
Bug
|
|
Thanks @edwardtfn,
Quick related question:
I ask because, once this works, I believe heat will remain on relay 1 (heater_relay: "1") and I'll specify relay 2 for cool (cooler_relay: "2") |
Wiring looks correct. |
|
I've just published branch |
|
I wanna your support to fill the following table:
In order to be able to compile with an older ESPHome compiler, you can use this add-on repository: https://github.com/khenderick/esphome-legacy-addons |
|
Hi @edwardtfn, with |
|
Try cleaning the build files. I've used your yaml (just changing substitutions:
###### CHANGE ME START ######
device_name: "nsplivingroom"
wifi_ssid: !secret wifi_ssid
wifi_password: !secret wifi_password
nextion_update_url: "http://homeassistant.local:8123/local/nspanel_us_land.tft"
nextion_blank_url: "http://homeassistant.local:8123/local/nspanel_blank.tft.tft"
##### addon-configuration #####
## addon_climate ##
heater_relay: "1" #Use relay 1
# temp_units: "°C" #Temperatures in Fahrenheit
# temp_min: "4.44" #Min supported temperature is 40°F
# temp_max: "26.66" #Max supported temperature is 80°F
# temp_step: ".5" #Temperature granularity is 1°F
# min_off_time: "1"
# min_run_time: "1"
# min_idle_time: "0"
temp_units: "°F" #Temperatures in Fahrenheit "°C"
temp_min: "40" #Min supported temperature is 40°F
temp_max: "80" #Max supported temperature is 80°F
temp_step: "1" #Temperature granularity is 1°F
min_off_time: "1"
min_run_time: "1"
min_idle_time: "0"
target_low: "40"
target_high: "75"
#addon_climate_heater_relay: "1"
# possible values: 1/2
##### CHANGE ME END #####
packages:
remote_package:
url: https://github.com/Blackymas/NSPanel_HA_Blueprint
ref: v4.2.5b
files:
- nspanel_esphome.yaml # Core package
#- advanced/esphome/nspanel_esphome_advanced.yaml # activate advanced (legacy) elements - can be useful for troubleshooting
#- nspanel_esphome_addon_climate_cool.yaml # activate for local climate (cooling) control
- nspanel_esphome_addon_climate_heat.yaml # activate for local climate (heater) control
refresh: 300s #300s #1s
esp32:
framework:
type: esp-idf
# - This will expose a "Factory Reset" button to Home Assistant, which will basically restore your NSPanel to use on y what is set in the yaml, cleaning its whole settings saved in flash.
# - See: https://github.com/Blackymas/NSPanel_HA_Blueprint/issues/1678#issuecomment-1903375436
#button:
# - platform: factory_reset
# name: Restart with Factory Default Settings
# internal: false
##### My customization - Start #####
# Encrypt the communication between ESPHome and Home Assistant
#api:
# encryption:
# key: !secret api_encryption_key_nsplivingroom
# More detailed log (for troubleshooting only)
#logger:
# level: VERBOSE
climate:
- id: !extend thermostat_embedded
default_preset: eco
on_boot_restore_from: memory #default_preset
heat_deadband: 1 # turn on differential (.5 °C; 1 °F)
heat_overrun: 1 # turn off differential / idle (.5 °C; 1 °F)
preset:
- name: sleep
default_target_temperature_low: 55 °F #55 °F; 12.7 °C
mode: "heat"
- name: eco
default_target_temperature_low: 60 °F #60 °F; 15.5 °C
mode: "heat" #heat_cool
- name: comfort
default_target_temperature_low: 64 °F #64 °F; 17.7 °C
mode: "heat"
- name: away
default_target_temperature_low: 55 °F #55 °F; 12.7 °C
mode: "heat" |
|
Sorry about that, it's practically muscle memory to clean the build files first but I clearly forgot to this time as it built just fine when I did. Unfortunately the NSPanel screen is stuck at the following (it's been that way for over 10 minutes so I don't think it'll recover), for ref, here's the log: logs_nsplivingroom_run_5_23.txt |
|
But even with the panel on that page, you should be able to try the relays from the device's page. Is that working? |
|
Ahh.. right, sorry, I just saw the screen and thought I couldn't move forward. Unfortunately, when I increased the temperature to trigger it to turn on, the relay didn't click (so the furnace didn't turn on). So it sounds like something changed beyond your code, i.e. ESPHome, to have caused this issue? If so, what's the next step to resolve? |
|
Could you please try it again with ESPHome v2023.12 and let me know if it is really working? |
|
I've updated the table: #2120 (comment) |
Same thing if you change the relay from the device's page (Settings > Devices and Services > ESPHome)? |
|
Here are some testing results Curve # 1 - ESPHome Switch (Settings > Devices and Services > ESPHome) NSPanel_HA_Blueprint: v4.3.7 kitchen panel
livingroom panel
2ndfloor panel
-- ref: v4.2.5b -- kitchen panel
livingroom panel
2ndfloor panel
I was able to use the ESPHome legacy add-on to install 2023.12.9 as you asked But then I went to compile with my .yaml using v4.2.5 but got an error on all 3 NSPanels I then noticed your table: #2120 (comment)) specifies "NSPanel_HA_Blueprint" - I understand Blueprint (though not sure how to revert that), but I'm not sure what NSPanel and HA mean? Is HA core & OS? If so, how do I revert those? ESPHome isn't referenced in "NSPanel_HA_Blueprint" but obviously that's needed as you gave me the addon to do that. |
Are you sure you are pointing to |
|
Hi @edwardtfn, yes, unfortunately I can confirm the error occurs on all 3 devices using |
|
So, are you sure you are using ESPHOME v2024.12 to compile? Try enabling "Show in sidebar" on the Add-on so you see the two instances in your side bar. |
|
Hey @edwardtfn, did you mean I seem to have v2023.12 (v2023.12.9) setup though when I get this error |
|
Sorry, you are right... I mean v2023.12.9. It shouldnt give that error when compiling with this version. I can compile here with no issues. Could you please share the full log from when compiling? The top of the log should display the ESPHome compiler version in use. |
|
After the logs showed the new version, I put the pieces together and now understand that I can choose the ESPHome 2023.12 from the left menu and install from there, sorry, I hadn't determined that until just now. Unfortunately still having problems installing now getting the error: "ERROR Unsupported OTA version 2" here's the log logs_nsplivingroom_run_5_25.txt
|
|
Well, this is getting more complex with time... 😂 You will have to install with latest versions, but adding this: ota:
version: 1Then you remove those lines again and try to install the older versions... |
|
Ok, so I put those lines above substitutions (that was the only place I could resolve any compile errors), then specified ref: main and the install seemed to be successful, here's the log: logs_nsplivingroom_run_5_261.txt. Below is the config, here's the full log: logs_nsplivingroom_run_5_261.txt I then stayed in the current ESPHome and cleaned the build files, then I whent to ESPHome 2023.12, removed the ota version 1 and went back to Because the install was so fast, I decided to stay in ESPHome 2023.12 and I cleaned the build files and installed again - this time a lot more happened (compiling). Here's the log (logs_nsplivingroom_run_5_263.txt), but still the same behavior as described in (#2120 (comment)). For ref, here's the panel |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TFT Version
4.3.7
ESPHome Version
4.3.7
Blueprint Version
4.3.7
Panel Model
None
What is the bug?
When the heat is turned on, it no longer seems to be trigging the relay to switch on the furnace like it did back on Feb 14 (see reference here)
Steps to Reproduce
Steps to Reproduce in this case appears to be the updates I did from the time it was working (Feb 14th) to yesterday when I made the updates
WHAT CHANGED (updates):
NOTES:
UPDATES:
ref: main)HOW IT WORKS:
NOTES:
heater_relay: "1"in the above mentioned nsplivingroom.yamlCONFIGURATION:
Your Panel's YAML
The text was updated successfully, but these errors were encountered: