Forum Smart Home Automation Forum

Getting inconsistent/wrong sensor readings from N20 over RS485 Modbus RTU — hoping for some guidance. Setup: N20 connected via RS485 to a Server16 running Home Assistant, using the Modbus RTU integration (baud 38400, matching the N20 Modbus protocol spec). Issue: Reading the temperature register (offset 64, float, Chip 1) gives inconsistent results. N20's own display shows 33.7°C, but Home Assistant reads back 24.38°C — sometimes correct, sometimes way off (even negative values occasionally). Current/power/energy readings on the integer registers seem fine, it's mainly the float-type registers (temperature, power factor) that come back wrong or inconsistent. I've already tried: - Different byte-swap orders (byte swap gives correct values sometimes, but not consistently) - Re-tightening A/B terminals Questions: 1. Is there a known/confirmed byte order for the float registers (temp, PF) on N20? The protocol doc mentions "CDBA format" — is there a simpler way to interpret this? 2. Any guidance on termination/grounding recommendations for the RS485 bus on N20 and Server16 specifically? 3. Is there a minimum recommended polling interval to avoid read collisions? Any help appreciated — thanks! 2.PNG (Size: 42.79 KB / Downloads: 4) code.txt (Size: 422 bytes / Downloads: 0)

Hi. What is the situation regarding the analog inputs on the KC868-A6? Are all four 0–5V, or are two 0–5V and two 4–20mA? The reason I ask is that the system block diagram labels two as 0–5V and two as 4–20mA inputs, whereas the wiring diagram shows all four as 0–5V inputs. KC868-A6 system block diagram.png (Size: 429.8 KB / Downloads: 6) KC868-A6 schematic.png (Size: 48.99 KB / Downloads: 7)

Hi. What is the situation regarding the analog inputs on the KC868-A6? Are all four 0–5V, or are two 0–5V and two 4–20mA? The reason I ask is that the system block diagram labels two as 0–5V and two as 4–20mA inputs, whereas the wiring diagram shows all four as 0–5V inputs. KC868-A6 system block diagram.png (Size: 429.8 KB / Downloads: 5) KC868-A6 schematic.png (Size: 48.99 KB / Downloads: 5)

Hi all, I am building a new home setup, with a Proxmox server hosting Home Assistant, Mosquitto, VictoriaMetrics and Grafana. I am about to install an N30 into my switchboard, and would like to collect data from it into VictoriaMetrics, as well as use the energy data for Home Assistant dashboards and automations. Ideally the energy data would be recorded into VictoriaMetrics at one second intervals, while Home Assistant should deal with a lower frequency of data, e.g. every 30 seconds. What is the best (not necessarily simplest) way to do this? I can't find much documentation on the relative merits and functionality of the ESPHome vs KCS v3 firmware, how quickly the energy data updates, or which protocol would be best suited. Note the N30 will be connected by Ethernet, and I also have an Elfin EE11 RS485-Ethernet adapter if that's helpful. I'm also happy to install extra software (e.g. Telegraf) into Proxmox if that provides a better solution.

Hi all, I am building a new home setup, with a Proxmox server hosting Home Assistant, Mosquitto, VictoriaMetrics and Grafana. I am about to install an N30 into my switchboard, and would like to collect data from it into VictoriaMetrics, as well as use the energy data for Home Assistant dashboards and automations. Ideally the energy data would be recorded into VictoriaMetrics at one second intervals, while Home Assistant should deal with a lower frequency of data, e.g. every 30 seconds. What is the best (not necessarily simplest) way to do this? I can't find much documentation on the relative merits and functionality of the ESPHome vs KCS v3 firmware, how quickly the energy data updates, or which protocol would be best suited. Note the N30 will be connected by Ethernet, and I also have an Elfin EE11 RS485-Ethernet adapter if that's helpful. I'm also happy to install extra software (e.g. Telegraf) into Proxmox if that provides a better solution.

How do you connect a thermistor to an analog input?

Hello support team, I have A32 pro, I connected to it ethernet cable. The tuya part i set by wifi. It’s working. When the wifi fail, so no more controlling by tuya. I see on the display of A32 pro “tuya offline”. My question is: Can I keep controlling A32 pro With tuya by ethernet, even if wifi broke?

How do you connect a thermistor to an analog input?

Hello support team, I have A32 pro, I connected to it ethernet cable. The tuya part i set by wifi. It’s working. When the wifi fail, so no more controlling by tuya. I see on the display of A32 pro “tuya offline”. My question is: Can I keep controlling A32 pro With tuya by ethernet, even if wifi broke?

Hello everyone, I have two F16 boards connected with HA that started to have connection issues. The output from the MQTT logs: Code: 2026-09-20 11:00:44: New connection from x.x.x.12:53372 on port 1883. 2026-09-20 11:00:47: New client connected from x.x.x.12:53372 as &tMAC&t (p4, c1, k120, u'kincony12'). 2026-09-20 11:00:47: Client &tMAC&t [x.x.x.12:53372] disconnected: connection closed by client. 2026-09-20 11:00:50: New connection from x.x.x.11:63968 on port 1883. 2026-09-20 11:00:53: New client connected from x.x.x.11:63968 as kincony11_&tMAC&t (p4, c1, k120, u'kincony11'). 2026-09-20 11:00:53: Client kincony11_&tMAC&t [x.x.x.11:63968] disconnected: connection closed by client. kincony11 is configured to use MQTT for Home Assistant while kincony12 is configured to use standard MQTT as I was trying different solutions but the result is the same: disconnect loop. kincony11 is on fw v3.18.0 kincony12 is on fw v3.27.2 Home Assistant details: Installation method Home Assistant OS Core 2026.9.3 Supervisor 2026.09.2 Operating System 18.3 Frontend 20260826.7 MQTT v7.1.1 As fw v3.27.2 has logging view, this is some output: Code: W (1300036) sd: Failed to mount filesystem. Error: ESP_ERR_INVALID_RESPONSE E (1301096) mqtt_client: esp_mqtt_connect: mqtt_message_receive() returned 0 E (1301096) mqtt_client: MQTT connect failed I (1301096) mqtt: MQTT_EVENT_DISCONNECTED I (1305036) gpio: GPIO[9]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 E (1305236) sdmmc_sd:

Hello everyone, I have two F16 boards connected with HA that started to have connection issues. The output from the MQTT logs: Code: 2026-09-20 11:00:44: New connection from x.x.x.12:53372 on port 1883. 2026-09-20 11:00:47: New client connected from x.x.x.12:53372 as (p4, c1, k120, u'kincony12'). 2026-09-20 11:00:47: Client [x.x.x.12:53372] disconnected: connection closed by client. 2026-09-20 11:00:50: New connection from x.x.x.11:63968 on port 1883. 2026-09-20 11:00:53: New client connected from x.x.x.11:63968 as kincony11_ (p4, c1, k120, u'kincony11'). 2026-09-20 11:00:53: Client kincony11_ [x.x.x.11:63968] disconnected: connection closed by client. kincony11 is configured to use MQTT for Home Assistant while kincony12 is configured to use standard MQTT as I was trying different solutions but the result is the same: disconnect loop. kincony11 is on fw v3.18.0 kincony12 is on fw v3.27.2 Home Assistant details: Installation method Home Assistant OS Core 2026.9.3 Supervisor 2026.09.2 Operating System 18.3 Frontend 20260826.7 MQTT v7.1.1 As fw v3.27.2 has logging view, this is some output: Code: W (1300036) sd: Failed to mount filesystem. Error: ESP_ERR_INVALID_RESPONSE E (1301096) mqtt_client: esp_mqtt_connect: mqtt_message_receive() returned 0 E (1301096) mqtt_client: MQTT connect failed I (1301096) mqtt: MQTT_EVENT_DISCONNECTED I (1305036) gpio: GPIO[9]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 0| Pulldown: 0| Intr:0 E (1305236) sdmmc_sd: sdmmc_init_sd_if_cond: send_i

here is KinCony AIO Hybrid smart controller work with oxygen modbus sensor using RS485 oxygen-sensor-1.jpg (Size: 401.14 KB / Downloads: 7) oxygen-sensor-2.jpg (Size: 188.69 KB / Downloads: 8) here is oxygen sensor modbus protocol: oxygen-modbus-sensor.png (Size: 162.95 KB / Downloads: 8) here is config sensor in KCS "sensor" webpage, chose "modbus" type of sensor. kcs-oxygen-modbus-sensor.png (Size: 86.49 KB / Downloads: 7) slave: 22 function code: 03 register: 104 data type: uint16 byte order: abcd big endian multiplier: 0.1 KCS monitor will show the sensor value: oxygen-sensor-value.png (Size: 43.16 KB / Downloads: 7)