search

Arnold-n / P1P2MQTT

Monitor and control Daikin/Rotex (hybrid/Altherma) heat pumps via the 2-wire P1/P2 thermostat interface with an ATmega328P, ESP8266, and electronics. The P1P2Serial library and P1P2Monitor program perform low-level bus operation, the P1P2-bridge-esp8266 program interprets data from/to MQTT supporting Home Assistant MQTT discovery. P1P2Serial may also be used for other Japanese Home Bus System based standards: DIII-NET (F1/F2) bus, Mitsubishi M-Net bus, Toshiba TCC-Link, Hitachi H-link, Panasonic/Sanyo SIII-Net, Haier, York, and others.
Other
272 stars 57 forks source link

Sporadic unavailability of all entities in HA #110

Open nash1975 opened 3 days ago

nash1975 commented 3 days ago

I have the problem that sporadically sometimes the sensor is not available at all in HA. All entities go then to "not available" status. After a few seconds, minutes or somethimes even hours the entities come back.

For me it seems that this is nothing related directly to the P1P2 HW. In MQTT explorer I see the relevant data with no issues

As an example 2 screenshots from yesterday evening with MQTT Explorer and HA sensor reading from LWT.

2024-06-29 20_30_31-ToDo letzte Abrechnung - OneNote 2024-06-29 20_30_54-MQTT Explorer

Arnold-n commented 3 days ago

It sounds like HA receives a will message offline on P1P2/L/P1P2MQTT/bridge0, making all entities unavailable, which a.o. is generated by the MQTT server when there is a longer MQTT disconnect (perhaps due to poor WiFi?) and when HA does not receive an online message when MQTT reconnects (although that message should be transmitted with QoS=1).

Can you check the value of P1P2/L/P1P2MQTT/bridge0 when this happens, and log via telnet if there are any errors reported (assuming WiFi connection stays in place when MQTT disconnects)?

As for WiFi signal strength, P1P2/P/P1P2MQTT/bridge0/A/9/WiFi_RSSI shows its strength.

nash1975 commented 2 days ago

The P1P2/L/P1P2MQTT/bridge0 data yesterday was very instable: (See table below) RSSI I think is not sooo bad. Telnet showed the complete day today no errors.

Welcome 192.168.178.67 to P1P2MQTT bridge v0.9.53 compiled Jun 5 2024 22:11:01 for Daikin E-Series (Use ^] + q to disconnect.) No telnet lock - use 'Pxx _lockword' to add magic lock word [ESP] 2024-06-30 09:09:46 < Telnet 192.168.178.67 connected

[MON] 2024-06-30 09:10:24 Initiating parameter write for packet-type 0x35 parameter nr 0x40 to value 0x1 [MON] 2024-06-30 09:10:24 Initiating parameter write for packet-type 0x35 parameter nr 0x3E to value 0x1 [MON] 2024-06-30 09:10:27 Executing E command for packet 0x35 setting param 0x40 to 0x1 [MON] 2024-06-30 09:10:27 Executing E command for packet 0x35 setting param 0x3E to 0x1 [MON] 2024-06-30 09:10:32 Initiating parameter write for packet-type 0x35 parameter nr 0x40 to value 0x0 [MON] 2024-06-30 09:10:32 Initiating parameter write for packet-type 0x35 parameter nr 0x3E to value 0x0 [MON] 2024-06-30 09:10:35 Executing E command for packet 0x35 setting param 0x40 to 0x0 [MON] 2024-06-30 09:10:35 Executing E command for packet 0x35 setting param 0x3E to 0x0 [MON] 2024-06-30 09:30:00 Initiating parameter write for packet-type 0x36 parameter nr 0x3 to value 0x226 [MON] 2024-06-30 09:30:00 write 0x36 nr 0 [MON] 2024-06-30 09:30:00 Executing E command for packet 0x36 setting param 0x3 to 0x226 [MON] 2024-06-30 12:41:08 Initiating parameter write for packet-type 0x35 parameter nr 0x40 to value 0x1 [MON] 2024-06-30 12:41:08 Initiating parameter write for packet-type 0x35 parameter nr 0x3E to value 0x1 [MON] 2024-06-30 12:41:09 Executing E command for packet 0x35 setting param 0x40 to 0x1 [MON] 2024-06-30 12:41:09 Executing E command for packet 0x35 setting param 0x3E to 0x1 [MON] 2024-06-30 12:41:21 Initiating parameter write for packet-type 0x36 parameter nr 0x3 to value 0x1F4 [MON] 2024-06-30 12:41:21 write 0x36 nr 0 [MON] 2024-06-30 12:41:21 Executing E command for packet 0x36 setting param 0x3 to 0x1F4 [MON] 2024-06-30 19:23:21 Initiating parameter write for packet-type 0x36 parameter nr 0x3 to value 0x226 [MON] 2024-06-30 19:23:23 write 0x36 nr 0 [MON] 2024-06-30 19:23:23 Executing E command for packet 0x36 setting param 0x3 to 0x226 [MON] 2024-06-30 20:19:45 Initiating parameter write for packet-type 0x35 parameter nr 0x40 to value 0x0 [MON] 2024-06-30 20:19:45 Initiating parameter write for packet-type 0x35 parameter nr 0x3E to value 0x0 [MON] 2024-06-30 20:19:45 Executing E command for packet 0x35 setting param 0x40 to 0x0 [MON] 2024-06-30 20:19:45 Executing E command for packet 0x35 setting param 0x3E to 0x0

2024-06-30 20_40_14-MQTT Explorer

P1P2/L/P1P2MQTT/bridge0 Datum Zeit Status Zeitdifferenz 30.06.2024 06:44:00 online - 30.06.2024 00:17:11 offline -6.45 hours 30.06.2024 00:16:44 online -27.29 seconds 30.06.2024 00:16:41 offline -3.36 seconds 30.06.2024 00:16:26 online -14.06 seconds 30.06.2024 00:13:47 offline -2.65 minutes 30.06.2024 00:13:17 online -30.05 seconds 30.06.2024 00:10:41 offline -2.6 minutes 30.06.2024 00:10:13 online -28.25 seconds 30.06.2024 00:07:29 offline -2.73 minutes 30.06.2024 00:07:00 online -28.78 seconds 30.06.2024 00:07:00 offline -0.43 seconds 30.06.2024 00:06:49 online -11.46 seconds 30.06.2024 00:06:48 offline -0.55 seconds 30.06.2024 00:06:34 online -13.92 seconds 30.06.2024 00:03:59 offline -2.58 minutes 30.06.2024 00:03:05 offline -54.06 seconds 30.06.2024 00:02:34 online -31.04 seconds 30.06.2024 00:02:21 offline -12.93 seconds 30.06.2024 00:02:11 offline -9.98 seconds 29.06.2024 23:56:07 online -6.08 minutes 29.06.2024 23:55:57 offline -9.88 seconds 29.06.2024 23:55:53 offline -3.51 seconds 29.06.2024 23:55:23 offline -30 seconds 29.06.2024 23:54:59 offline -23.96 seconds 29.06.2024 23:54:35 offline -23.88 seconds 29.06.2024 23:54:11 offline -24.11 seconds 29.06.2024 23:53:47 offline -24.01 seconds 29.06.2024 23:53:23 offline -24.03 seconds 29.06.2024 23:52:53 offline -30.01 seconds 29.06.2024 23:52:23 offline -29.99 seconds 29.06.2024 23:49:47 online -2.61 minutes 29.06.2024 23:49:37 offline -9.82 seconds 29.06.2024 23:49:35 offline -1.46 seconds 29.06.2024 23:49:11 offline -24.02 seconds 29.06.2024 23:40:40 online -8.53 minutes 29.06.2024 23:40:30 offline -9.75 seconds 29.06.2024 23:40:29 offline -0.52 seconds 29.06.2024 23:40:05 offline -24.04 seconds 29.06.2024 23:39:35 offline -29.95 seconds 29.06.2024 23:37:46 online -109.26 seconds 29.06.2024 23:37:27 offline -18.58 seconds 29.06.2024 23:37:27 offline -0.66 seconds 29.06.2024 23:37:05 offline -21.56 seconds 29.06.2024 23:36:35 offline -29.85 seconds 29.06.2024 23:36:03 online -32.47 seconds 29.06.2024 23:35:53 offline -9.67 seconds 29.06.2024 23:35:25 online -28.57 seconds 29.06.2024 23:32:41 offline -2.72 minutes 29.06.2024 23:32:15 online -26.02 seconds 29.06.2024 23:29:41 offline -2.56 minutes 29.06.2024 23:29:12 online -29.31 seconds 29.06.2024 23:27:07 offline -2.08 minutes 29.06.2024 23:26:23 offline -43.88 seconds 29.06.2024 23:25:29 offline -53.96 seconds 29.06.2024 23:24:41 offline -47.94 seconds 29.06.2024 23:24:14 offline -27.36 seconds 29.06.2024 23:24:12 offline -2.12 seconds 29.06.2024 23:23:35 offline -36.56 seconds 29.06.2024 23:23:05 online -30.16 seconds 29.06.2024 23:22:53 offline -11.87 seconds 29.06.2024 23:22:29 online -23.91 seconds 29.06.2024 23:17:31 offline -4.97 minutes 29.06.2024 23:16:27 offline -63.68 seconds 29.06.2024 23:15:33 offline -54.03 seconds 29.06.2024 23:15:04 offline -29.91 seconds 29.06.2024 23:13:57 offline -66.11 seconds 29.06.2024 23:13:28 offline -29.9 seconds 29.06.2024 23:12:05 offline -82.37 seconds 29.06.2024 23:11:45 offline -19.7 seconds 29.06.2024 23:10:51 offline -54.01 seconds 29.06.2024 23:10:28 online -23.16 seconds 29.06.2024 23:07:21 offline -3.11 minutes 29.06.2024 23:05:57 offline -84.01 seconds 29.06.2024 23:05:10 offline -47.95 seconds 29.06.2024 23:04:39 online -30.24 seconds 29.06.2024 22:57:45 offline -6.9 minutes 29.06.2024 22:56:46 offline -59.94 seconds 29.06.2024 22:55:21 offline -84.06 seconds 29.06.2024 22:54:47 online -34.85 seconds 29.06.2024 22:53:01 offline -105.19 seconds 29.06.2024 22:51:58 offline -63.86 seconds 29.06.2024 22:50:11 offline -106.83 seconds 29.06.2024 22:49:51 offline -19.26 seconds 29.06.2024 22:49:27 offline -24 seconds 29.06.2024 22:48:45 offline -42.64 seconds 29.06.2024 22:48:21 offline -23.39 seconds 29.06.2024 22:47:27 offline -53.99 seconds 29.06.2024 22:45:16 offline -2.2 minutes 29.06.2024 22:43:03 online -2.2 minutes 29.06.2024 22:42:46 offline -17.3 seconds 29.06.2024 22:42:46 offline -0.44 seconds 29.06.2024 22:39:55 online -2.84 minutes 29.06.2024 22:37:28 offline -2.46 minutes 29.06.2024 22:36:34 offline -53.97 seconds 29.06.2024 22:36:10 offline -24.06 seconds 29.06.2024 22:29:46 offline -6.4 minutes 29.06.2024 22:29:22 online -23.31 seconds 29.06.2024 22:29:22 offline -0.52 seconds 29.06.2024 22:29:09 online -12.7 seconds

Arnold-n commented 2 days ago

Hi @nash1975 ,

Thanks, well I guess you only see the RSSI values when connected, not when disconnected, so some RSSI values may be worse. In my experience around -80 is not good enough, and may trigger disconnects. I cannot explain why the "online" message is not always received properly, but I have experienced that the ESP MQTT client library struggles under higher load and not-so-good WiFi conditions, so I would recommend to see if improving your WiFi signal solves this issue.

If that does not work, I could repeat the "online" message regularly but it feels like a work-around instead of a solution. And if the WiFi disconnects are really so long as reported that would be an issue to solve.