Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug Climate Addon will not control relay #2374

Open
domerich opened this issue Nov 10, 2024 · 14 comments
Open

Bug Climate Addon will not control relay #2374

domerich opened this issue Nov 10, 2024 · 14 comments
Labels
Add-on: Climate Bug Identifies an issue where the system is not functioning as expected.
Milestone

Comments

@domerich
Copy link

domerich commented Nov 10, 2024

TFT Version

No response

Firmware Version

No response

Blueprint Version

No response

Panel Model

None

What is the bug?

I have configured the NSpanel according to the instructions, I want to control the underfloor heating.
When I turn off or on the thermostat in HA I expect the relay to click but nothing happens.

How can I debug this? In HA I can see relay1, relay2 and the thermostat. I would not expect to see relay1 as I should not be able to use it with this config.

image

Steps to Reproduce

I installed the updated config wirelessly

Your Panel's YAML

substitutions:
  # Settings - Editable values
  device_name: "nspanel-schlafzimmer"
  friendly_name: "NSPanel Schlafzimmer"
  wifi_ssid: !secret wifi_ssid
  wifi_password: !secret wifi_password
  nextion_update_url: "http://homeassistant.local:8123/local/nspanel_eu.tft"  # Optional
  # Add-on configuration (if needed)
  # heater_relay: "1"  # Possible values: "1" or "2"

 ##### addon-configuration #####
  ## addon_climate ##
  heater_relay: "1" #Use relay 1
  temp_min: "15" 
  temp_max: "22" 
  temp_step: "0.1"
  cold_tolerance: "0.1"
  hot_tolerance: "0.1"
    
  ##### CHANGE ME END #####
climate:
  - id: !extend thermostat_embedded
    visual:
      temperature_step: ${temp_step}
    preset:
      - name: Home
        default_target_temperature_low: 18.3
        mode: "heat"

# Customization area
##### My customization - Start #####
##### My customization - End #####

# Core and optional configurations
# Basic and optional configurations
packages:
  remote_package:
    url: https://github.com/Blackymas/NSPanel_HA_Blueprint
    ref: main
    refresh: 300s
    files:
      - nspanel_esphome.yaml # Basic package
      # Optional advanced and add-on configurations
      # - esphome/nspanel_esphome_advanced.yaml
      # - esphome/nspanel_esphome_addon_ble_tracker.yaml
      # - esphome/nspanel_esphome_addon_bluetooth_proxy.yaml
      # - esphome/nspanel_esphome_addon_climate_cool.yaml
      - esphome/nspanel_esphome_addon_climate_heat.yaml
      # - esphome/nspanel_esphome_addon_climate_dual.yaml

esp32:
  framework: 
    type: esp-idf

ESPHome Logs

No response

Home Assistant Logs

No response

@domerich domerich added the Bug Identifies an issue where the system is not functioning as expected. label Nov 10, 2024
@quenthal
Copy link

quenthal commented Nov 10, 2024

In your first screenshot current temp is 22.4, which is more than what thermostat is set to (22)?

@edwardtfn
Copy link
Collaborator

When I turn off or on the thermostat in HA I expect the relay to click but nothing happens.

Could you please share the logs from ESPHome while you are toggling the relay on/off?

@domerich
Copy link
Author

domerich commented Nov 10, 2024

home-assistant_esphome_2024-11-10T21-25-48.607Z.log

When I turn off or on the thermostat in HA I expect the relay to click but nothing happens.

Could you please share the logs from ESPHome while you are toggling the relay on/off?

Yes I set it to debug mode, switched on to heat, the relay clicked. But when I turn off the heat or reduce the target temperature nothing happens.

2024-11-10 22:17:22.444 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type ClimateStateResponse: key: 816166854
current_temperature: 13.866951
target_temperature: 22
preset: CLIMATE_PRESET_HOME
2024-11-10 22:17:22.446 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type SensorStateResponse: key: 899752953
state: 13.866951
2024-11-10 22:17:32.447 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type ClimateStateResponse: key: 816166854
current_temperature: 13.8550968
target_temperature: 22
preset: CLIMATE_PRESET_HOME
2024-11-10 22:17:32.449 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type SensorStateResponse: key: 899752953
state: 13.8550968
2024-11-10 22:17:42.446 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type ClimateStateResponse: key: 816166854
current_temperature: 13.8471909
target_temperature: 22
preset: CLIMATE_PRESET_HOME
2024-11-10 22:17:42.448 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type SensorStateResponse: key: 899752953
state: 13.8471909
2024-11-10 22:17:42.983 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Sending ClimateCommandRequest: key: 816166854
has_mode: true
mode: CLIMATE_MODE_HEAT
2024-11-10 22:17:42.983 DEBUG (MainThread) [aioesphomeapi._frame_helper.base] nspanel-schlafzimmer @ 192.168.178.100: Sending frame: [0009300dc6b7a53010011803]
2024-11-10 22:17:43.066 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type SwitchStateResponse: key: 1878979320
state: true
2024-11-10 22:17:43.173 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type ClimateStateResponse: key: 816166854
mode: CLIMATE_MODE_HEAT
current_temperature: 13.8471909
target_temperature: 22
action: CLIMATE_ACTION_HEATING
preset: CLIMATE_PRESET_HOME
2024-11-10 22:17:44.379 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type SensorStateResponse: key: 2543775268
state: -53
2024-11-10 22:17:50.187 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Sending ClimateCommandRequest: key: 816166854
has_mode: true
2024-11-10 22:17:50.187 DEBUG (MainThread) [aioesphomeapi._frame_helper.base] nspanel-schlafzimmer @ 192.168.178.100: Sending frame: [0007300dc6b7a5301001]
2024-11-10 22:17:50.230 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type ClimateStateResponse: key: 816166854
current_temperature: 13.8471909
target_temperature: 22
action: CLIMATE_ACTION_HEATING
preset: CLIMATE_PRESET_HOME
2024-11-10 22:17:50.458 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type TextSensorStateResponse: key: 1245159599
state: "nspanel_schlafzimmer"
2024-11-10 22:17:52.447 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type ClimateStateResponse: key: 816166854
current_temperature: 13.8208466
target_temperature: 22
action: CLIMATE_ACTION_HEATING
preset: CLIMATE_PRESET_HOME
2024-11-10 22:17:52.449 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type SensorStateResponse: key: 899752953
state: 13.8208466
2024-11-10 22:17:56.538 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Trying to connect to nspanel-zimmer1 @ 192.168.178.89
2024-11-10 22:17:56.538 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Connected lock acquired for nspanel-zimmer1 @ 192.168.178.89
2024-11-10 22:17:56.539 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-zimmer1 @ 192.168.178.89: Connecting to IPv4Sockaddr(address='192.168.178.89', port=6053)
2024-11-10 22:17:56.542 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Trying to connect to nspanel-wohnzimmer @ 192.168.178.99
2024-11-10 22:17:56.542 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Connected lock acquired for nspanel-wohnzimmer @ 192.168.178.99
2024-11-10 22:17:56.542 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-wohnzimmer @ 192.168.178.99: Connecting to IPv4Sockaddr(address='192.168.178.99', port=6053)
2024-11-10 22:17:56.545 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Trying to connect to nspanel-bad1 @ 192.168.178.97
2024-11-10 22:17:56.545 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Connected lock acquired for nspanel-bad1 @ 192.168.178.97
2024-11-10 22:17:56.546 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-bad1 @ 192.168.178.97: Connecting to IPv4Sockaddr(address='192.168.178.97', port=6053)
2024-11-10 22:17:56.548 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Trying to connect to nspanel-bad2 @ 192.168.178.98
2024-11-10 22:17:56.548 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Connected lock acquired for nspanel-bad2 @ 192.168.178.98
2024-11-10 22:17:56.549 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-bad2 @ 192.168.178.98: Connecting to IPv4Sockaddr(address='192.168.178.98', port=6053)
2024-11-10 22:17:56.551 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Trying to connect to nspanel-zimmer2 @ 192.168.178.95
2024-11-10 22:17:56.551 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Connected lock acquired for nspanel-zimmer2 @ 192.168.178.95
2024-11-10 22:17:56.552 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-zimmer2 @ 192.168.178.95: Connecting to IPv4Sockaddr(address='192.168.178.95', port=6053)
2024-11-10 22:17:59.640 DEBUG (MainThread) [aioesphomeapi.connection] Cleaning up connection to nspanel-wohnzimmer @ 192.168.178.99
2024-11-10 22:17:59.640 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for nspanel-wohnzimmer @ 192.168.178.99: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.178.99', port=6053))]: [Errno 113] Connect call failed ('192.168.178.99', 6053) (SocketAPIError)
2024-11-10 22:17:59.640 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Retrying nspanel-wohnzimmer @ 192.168.178.99 in 60.00 seconds
2024-11-10 22:17:59.641 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Scheduling new connect attempt in 60.00 seconds
2024-11-10 22:17:59.642 DEBUG (MainThread) [aioesphomeapi.connection] Cleaning up connection to nspanel-zimmer2 @ 192.168.178.95
2024-11-10 22:17:59.643 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for nspanel-zimmer2 @ 192.168.178.95: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.178.95', port=6053))]: [Errno 113] Connect call failed ('192.168.178.95', 6053) (SocketAPIError)
2024-11-10 22:17:59.643 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Retrying nspanel-zimmer2 @ 192.168.178.95 in 60.00 seconds
2024-11-10 22:17:59.643 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Scheduling new connect attempt in 60.00 seconds
2024-11-10 22:17:59.644 DEBUG (MainThread) [aioesphomeapi.connection] Cleaning up connection to nspanel-bad2 @ 192.168.178.98
2024-11-10 22:17:59.644 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for nspanel-bad2 @ 192.168.178.98: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.178.98', port=6053))]: [Errno 113] Connect call failed ('192.168.178.98', 6053) (SocketAPIError)
2024-11-10 22:17:59.644 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Retrying nspanel-bad2 @ 192.168.178.98 in 60.00 seconds
2024-11-10 22:17:59.645 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Scheduling new connect attempt in 60.00 seconds
2024-11-10 22:17:59.646 DEBUG (MainThread) [aioesphomeapi.connection] Cleaning up connection to nspanel-zimmer1 @ 192.168.178.89
2024-11-10 22:17:59.646 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for nspanel-zimmer1 @ 192.168.178.89: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.178.89', port=6053))]: [Errno 113] Connect call failed ('192.168.178.89', 6053) (SocketAPIError)
2024-11-10 22:17:59.646 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Retrying nspanel-zimmer1 @ 192.168.178.89 in 60.00 seconds
2024-11-10 22:17:59.646 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Scheduling new connect attempt in 60.00 seconds
2024-11-10 22:17:59.648 DEBUG (MainThread) [aioesphomeapi.connection] Cleaning up connection to nspanel-bad1 @ 192.168.178.97
2024-11-10 22:17:59.648 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for nspanel-bad1 @ 192.168.178.97: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.178.97', port=6053))]: [Errno 113] Connect call failed ('192.168.178.97', 6053) (SocketAPIError)
2024-11-10 22:17:59.648 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Retrying nspanel-bad1 @ 192.168.178.97 in 60.00 seconds
2024-11-10 22:17:59.648 DEBUG (MainThread) [aioesphomeapi.reconnect_logic] Scheduling new connect attempt in 60.00 seconds
2024-11-10 22:18:02.445 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type ClimateStateResponse: key: 816166854
current_temperature: 13.8252354
target_temperature: 22
action: CLIMATE_ACTION_HEATING
preset: CLIMATE_PRESET_HOME
2024-11-10 22:18:02.446 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type SensorStateResponse: key: 899752953
state: 13.8252354
2024-11-10 22:18:08.783 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Sending ExecuteServiceRequest: key: 2983745176
args {
  string_: "home.outdoor_temp"
}
args {
  string_: "2.3°"
}
2024-11-10 22:18:08.784 DEBUG (MainThread) [aioesphomeapi._frame_helper.base] nspanel-schlafzimmer @ 192.168.178.100: Sending frame: [00232a0d9856d8b112132211686f6d652e6f7574646f6f725f74656d7012072205322e33c2b0]
2024-11-10 22:18:08.787 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Sending ExecuteServiceRequest: key: 1809223668
args {
  string_: "home.weather.pic=8"
}
2024-11-10 22:18:08.787 DEBUG (MainThread) [aioesphomeapi._frame_helper.base] nspanel-schlafzimmer @ 192.168.178.100: Sending frame: [001b2a0df48fd66b12142212686f6d652e776561746865722e7069633d38]
2024-11-10 22:18:10.004 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type TextSensorStateResponse: key: 675312281
2024-11-10 22:18:10.005 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type HomeassistantServiceResponse: service: "esphome.nspanel_ha_blueprint"
data {
  key: "device_name"
  value: "nspanel_schlafzimmer"
}
data {
  key: "entity"
}
data {
  key: "esphome_version"
  value: "4.3.12"
}
data {
  key: "page"
  value: "screensaver"
}
data {
  key: "type"
  value: "page_changed"
}
is_event: true
2024-11-10 22:18:10.110 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type TextSensorStateResponse: key: 2394264602
state: "screensaver"
2024-11-10 22:18:10.111 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type SensorStateResponse: key: 1361203055
2024-11-10 22:18:12.445 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type ClimateStateResponse: key: 816166854
current_temperature: 13.8515835
target_temperature: 22
action: CLIMATE_ACTION_HEATING
preset: CLIMATE_PRESET_HOME
2024-11-10 22:18:12.448 DEBUG (MainThread) [aioesphomeapi.connection] nspanel-schlafzimmer @ 192.168.178.100: Got message of type SensorStateResponse: key: 899752953
state: 13.8515835

@domerich
Copy link
Author

In your first screenshot current temp is 22.4, which is more than what thermostat is set to (22)?

that is correct, I fixed the offset but still nothing

@edwardtfn
Copy link
Collaborator

I mean the log from ESPHome. You can get that from your ESPHome dashboard, click on the "Log" button related to your panel.

@domerich
Copy link
Author

I mean the log from ESPHome. You can get that from your ESPHome dashboard, click on the "Log" button related to your panel.

Ok I hope I got it this time.
config_entry-esphome-01JC1E47MX3N07F20A779C6AT5.json

@edwardtfn
Copy link
Collaborator

Nope. 😆

You have to go to your ESPHome Dashboard, where you will find the "Logs" button:
image

That will open a Log screen where you see live what is happening with your device. That is the log I'm looking for. 😉

@domerich
Copy link
Author

domerich commented Nov 11, 2024

Okay 3 is a charm :D Thanks for the 4 arrows that really helped ;)

logs_nspanel-schlafzimmer_logs.txt

@edwardtfn
Copy link
Collaborator

Those are exactly the logs I was looking for, however, I don't see any event of you toggling the relays during the time that log was captured. Have you done that?

@domerich
Copy link
Author

Those are exactly the logs I was looking for, however, I don't see any event of you toggling the relays during the time that log was captured. Have you done that?

What I have done is this: restart the panel, switch to mode heat, raise target temperature from 15 to 22 deg. Then the relay 1 clicked. Then I lowered the target temperature and turned heat mode off. Nothing happens then,

@domerich
Copy link
Author

domerich commented Nov 11, 2024

I will try to flash it again, some errors occur.

[19:49:22][E][nextion:576]: ERROR: Received numeric return but next in queue "send_command_printf" is not a valid sensor type 0

[19:49:22][E][nextion:576]: ERROR: Received numeric return but next in queue "set_component_value" is not a valid sensor type 0

[19:49:52][E][nextion:576]: ERROR: Received numeric return but next in queue "backlight_brightness" is not a valid sensor type 0
logs_nspanel-schlafzimmer_run.txt

it still does not work, something seems wrong.

Do I need to set up something in the blueprints first?

I have setup a basic blue print, nothing special. I can touch the temperature and the temperature controller opens but nothing happens when I operate it.

@domerich
Copy link
Author

domerich commented Nov 12, 2024

I mean, the heat command seems to work, according to the log:

[09:56:24][D][climate:011]: 'Thermostat' - Setting
[09:56:24][D][climate:015]: Mode: HEAT
[09:56:24][D][switch:012]: 'Relay 1' Turning ON.
[09:56:24][D][switch:055]: 'Relay 1': Sending state ON
[09:56:24][D][climate:396]: 'Thermostat' - Sending state:
[09:56:24][D][climate:399]: Mode: HEAT
[09:56:24][D][climate:401]: Action: HEATING
[09:56:24][D][climate:410]: Preset: HOME
[09:56:24][D][climate:419]: Current Temperature: 19.10°C
[09:56:24][D][climate:425]: Target Temperature: 20.90°C
[09:56:31][D][sensor:094]: 'ntc_source': Sending state 1.66317 V with 2 decimals of accuracy
[09:56:31][D][resistance:039]: 'resistance_sensor' - Resistance 11380.2Ω
[09:56:31][D][sensor:094]: 'resistance_sensor': Sending state 11380.18555 Ω with 1 decimals of accuracy
[09:56:31][D][ntc:026]: 'Temperature' - Temperature: 22.1°C
[09:56:31][D][sensor:094]: 'Temperature': Sending state 19.11852 °C with 1 decimals of accuracy
[09:56:31][D][climate:396]: 'Thermostat' - Sending state:
[09:56:31][D][climate:399]: Mode: HEAT
[09:56:31][D][climate:401]: Action: HEATING
[09:56:31][D][climate:410]: Preset: HOME
[09:56:31][D][climate:419]: Current Temperature: 19.12°C
[09:56:31][D][climate:425]: Target Temperature: 20.90°C

and when I turn it off, this also seems to do something, but relay 1 remains "on"

[09:57:41][D][sensor:094]: 'ntc_source': Sending state 1.66683 V with 2 decimals of accuracy
[09:57:41][D][resistance:039]: 'resistance_sensor' - Resistance 11430.9Ω
[09:57:41][D][sensor:094]: 'resistance_sensor': Sending state 11430.87988 Ω with 1 decimals of accuracy
[09:57:41][D][ntc:026]: 'Temperature' - Temperature: 22.0°C
[09:57:41][D][sensor:094]: 'Temperature': Sending state 19.02045 °C with 1 decimals of accuracy
[09:57:41][D][climate:396]: 'Thermostat' - Sending state:
[09:57:41][D][climate:399]: Mode: OFF
[09:57:41][D][climate:401]: Action: HEATING
[09:57:41][D][climate:410]: Preset: HOME
[09:57:41][D][climate:419]: Current Temperature: 19.02°C
[09:57:41][D][climate:425]: Target Temperature: 20.90°C
[09:57:43][D][esp32.preferences:114]: Saving 1 preferences to flash...
[09:57:43][D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed

I can manually turn off relay 1 which works:

[09:58:29][D][switch:016]: 'Relay 1' Turning OFF.
[09:58:29][D][switch:055]: 'Relay 1': Sending state OFF

But now when I switch the mode to "heat" then relay 1 will remain off:

[10:00:11][D][climate:396]: 'Thermostat' - Sending state:
[10:00:11][D][climate:399]: Mode: HEAT
[10:00:11][D][climate:401]: Action: HEATING
[10:00:11][D][climate:410]: Preset: HOME
[10:00:11][D][climate:419]: Current Temperature: 19.01°C
[10:00:11][D][climate:425]: Target Temperature: 22.00°C

What am I doing wrong?

@edwardtfn
Copy link
Collaborator

I will try to duplicate this here.

@edwardtfn edwardtfn added this to the v4.4.0 milestone Nov 12, 2024
@domerich
Copy link
Author

domerich commented Nov 12, 2024

I will try to duplicate this here.

OK if it helps I can expose the device and send the IPv6 address in a PM.

the config is this:
config.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Add-on: Climate Bug Identifies an issue where the system is not functioning as expected.
Projects
None yet
Development

No branches or pull requests

3 participants