Closed svollebregt closed 2 months ago
Sorry, i forgot to update docs. Replace address: RMU_S3 with system: 3
Thanks. It now compiles but in the log it states:
[I][nibegw:155]: Publishing to rmu: 0x1b temp: nan -> 00.80
Earlier on when initializing:
[10:08:52][C][api:139]: API Server:
[10:08:52][C][api:140]: Address: nibe.local:6053
[10:08:52][C][api:142]: Using noise encryption: YES
[10:08:52][C][homeassistant.sensor:030]: Homeassistant Sensor 'current_temperature_s3'
[10:08:52][C][homeassistant.sensor:030]: Device Class: 'temperature'
[10:08:52][C][homeassistant.sensor:030]: State Class: 'measurement'
[10:08:52][C][homeassistant.sensor:030]: Unit of Measurement: '°C'
[10:08:52][C][homeassistant.sensor:030]: Accuracy Decimals: 1
[10:08:52][C][homeassistant.sensor:031]: Entity ID: 'sensor.tfa_ts34c_cresta_5f_0e_temperature'
The sensor is defined like this, I first tried the minimal example without the state and device class as in your example but got the same result:
sensor:
- platform: htu21d
temperature:
name: "TR Temperature"
humidity:
name: "TR Humidity"
update_interval: 60s
- platform: homeassistant
id: current_temperature_s3
unit_of_measurement: "°C"
device_class: "temperature"
state_class: "measurement"
entity_id: sensor.tfa_ts34c_cresta_5f_0e_temperature
The sensor itself works in HASS and has a valid number, so I am puzzled as to why the ESP nodes make it NaN.
Finally my HASS log:
Logger: aioesphomeapi.reconnect_logic
Source: runner.py:190
First occurred: 9:55:19 AM (3 occurrences)
Last logged: 10:20:28 AM
Can't connect to ESPHome API for nibe @ 192.168.1.31: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.31', port=6053))]: [Errno 111] Connect call failed ('192.168.1.31', 6053) (SocketAPIError)
Can't connect to ESPHome API for nibe @ 192.168.1.31: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.1.31', port=6053))]: [Errno 113] Connect call failed ('192.168.1.31', 6053) (SocketAPIError)
Right. Then switch the climate entity to heat cool
Climate system S3 does not show up in HASS. When I force enable it, it throws an error that it does not exist. Do all pumps support multiple climate systems, mine is a F1255 if that is relevant
Edit now trying to see if it works linked to S1 Edit 2: same result. ESPHome logs shows it is transmitting NaN but now to RMU 0x19
It shows up under the esphome device, not the nibe integrationen. This is not really a good solution i agree
Ok, how do I control the state to HEAT_COOL? I see I need to define an action, but if I try to do it on_boot: or on_time_sync:, it won't compile.
You control that easiest from home assistant.
Ah, found it. This indeed works! Thanks!!
I wanted to try out the virtual RMU option as this has been something I was looking for, but I get the following error when building:
Below is my configuration, which builds fine with the climate: part commented out:
It may be something trivial, but I cannot find the solution. I am running the latest ESPHome (2024.8.1) and performed a cleanup of the build configuration. As mentioned, without the last climate part, it compiles fine.