Periodic reset of z2m and faikin devices

Hello

HASS running on Pi4, using reflashed external dongle (sonoff). About 50 zigbee devices under z2m. Some sonoff, some localtuya, few automations.

I also have some 5 faikin converted units (had to build the boards myself, it was nice).

There is some strange behavior from some weeks now that I just cant find out why. As one of those strange things, its also hard to explain, imagine solve. Anyway, i decided to post here, maybe you just had the same problem. :slight_smile:

No logs at all, but it’s like some time to time devices get a reset or so. All faikin A/cs just beep, as if they received a command to repea the state they are in. They beep with just a very little delay between them, in sequence. All off, then beep all, still off.

On the Z2m side, same thing happen, but of course no beeps. I noted an interesting thing: on the garage there are two different switches for separate lights. I have created an automation that says: when someone turns on switch A, Hass turn on switch B for me. Also, when someone turns off switch A, Hass turns off switch b. This is action related, not state related.

The odd is that if I go there by hand and turn on Switch B (when A is off), b goes on okay. After some random time, Hass turns of switch B. This only happens when A is off (and with no action on a).

It all seems as if home assistant recycled itself, but I find nothing in Z2M or HASS logs.

Anyone? :slight_smile:

The common factor between z2m and fakin is mqtt. I’d be looking at your mqtt logs.

Been chasing based on that advice, that totally makes sense, for couple of days now. No luck. Today noticed exact times. 0800 and 1300 everything beeped. Nothing different on the log at those times:

25-04-25 12:54:27: New connection from 172.30.32.2:50384 on port 1883.

2025-04-25 12:54:27: Client <unknown> closed its connection.

2025-04-25 12:56:27: New connection from 172.30.32.2:49026 on port 1883.

2025-04-25 12:56:27: Client <unknown> closed its connection.

2025-04-25 12:56:35: Saving in-memory database to /data//mosquitto.db.

2025-04-25 12:58:27: New connection from 172.30.32.2:53122 on port 1883.

2025-04-25 12:58:27: Client <unknown> closed its connection.

2025-04-25 13:00:27: New connection from 172.30.32.2:39702 on port 1883.

2025-04-25 13:00:27: Client <unknown> closed its connection.

2025-04-25 13:02:27: New connection from 172.30.32.2:48868 on port 1883.

2025-04-25 13:02:27: Client <unknown> closed its connection.

Is your Wifi network resetting perhaps?

Though that would not explain the zigbee…

Check your logbook (as opposed to system logs) for what happens at those times.

Open your Home Assistant instance and show your logbook panel. ← click

There you go. Lots of became unavailable on the logbook at the beep time… those became unavailable are zigbee devices (beeps in wifi faikins). Will check all logs for more at 06:00:13 pm or around that…

btw
z2m logs are a pain, those tuya heated floor controllers really flood it.

Nothing besides huge zigbee network flood from heat controller… i think i will try to replace this controller with a wifi one…

|[2025-04-26 22:00:19] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:19-03:00,linkquality:104,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|---|---|
|[2025-04-26 22:00:19] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:19-03:00,linkquality:104,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:19] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:19-03:00,linkquality:108,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:19] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:19-03:00,linkquality:128,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:20] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:112,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:20] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:100,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:20] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:108,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:20] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:104,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:20] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:112,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:20] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:108,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:20] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:108,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:20] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:116,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:20] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:112,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:20] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:104,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:20] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:104,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:20] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:104,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:20] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:108,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:20] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:108,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:21] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:20-03:00,linkquality:120,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:21] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:21-03:00,linkquality:104,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:21] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:21-03:00,linkquality:108,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:21] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:21-03:00,linkquality:104,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:21] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:21-03:00,linkquality:104,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|
|[2025-04-26 22:00:21] info: |z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Piso aquecido cozinha', payload '{child_lock:UNLOCK,current_heating_setpoint:23,deadzone_temperature:null,heat:OFF,last_seen:2025-04-26T22:00:21-03:00,linkquality:104,local_temperature:23,local_temperature_calibration:null,max_temperature_limit:null,min_temperature_limit:null,preset:program,preset_mode:program,program:null,running_state:idle,sensor:null,system_mode:off}'|

Explains nothing, but…

14 messages a second! Which model is this?

Try to configure Reporting for that device, especially the Min reporting change & interval

Hi

Its a Moes… got on aliexpress at https://www.aliexpress.com/item/1005005202931454.html?spm=a2g0o.order_list.order_list_main.15.4abe1802x4lk9y

Never used the reporting tab, will try to do that now. I see you have multiple lines, is that needed, like for all reported attributes?

Thanks.

Regarding the beeps and strange behaviour, all I can narrow is that the saving db line is very close to the beeps.

As I`ve been reading, its normal. Only strange on that is the double slash… but can find where to configure it, so maybe its normal…?!

2025-04-27 21:58:29: Saving in-memory database to /data//mosquitto.db.

Post the actual model number as shown in the Z2M device page. Using that, you might find issues on the Z2M GitHub where someone figured out which reporting parameters you need to set

hello

It goes like this

Availability
Online
Device type
Router
Zigbee Model
TS0601
Zigbee Manufacturer
_TZE204_aoclfnxz
Description
Smart heating thermostat
Support status

Supported

IEEE Address
0xa4c1383772faa276
Network address
0x47BA / 18362
Manufacturer
[Moes](https://www.zigbee2mqtt.io/supported-devices/#v=Moes)
Model
[BHT-002/BHT-006](https://www.zigbee2mqtt.io/devices/BHT-002_BHT-006.html#moes-bht-002%252Fbht-006)

I had a look in Github and I’m afraid I don’t have great news for you.
First thing I found was this comment buried within a massive thread where they discuss the (known) spammy Tuya motion sensor.
Turns out, that sensor uses the same chip and has the same TS0601 zigbee model. Even then, that sensor ā€œonlyā€ sends a message once a second - far less than what you’re seeing.

Did some more digging, and found this issue. Apparently, these thermostats are so spammy that someone went out and created custom firmware update for them. There’s a link to a Russian writeup in the issue, but the actual github page which fixes this is here.

While it’s not entirely straightforward, it’s better than having your network spammed and having to take a hammer to that thermostat.

Thank you so much for putting that much time and effort in that.

Years ago, after spending much time i didnt have to spare on reflashing and opening devices to find serial ports, i decided to let go. But you simply cant live with those tuya and ewelink stuff connected to alexa. After a while a friend talked me to go into HASS cause of its really active community and efficient design. And he was right.

I am happy that this update does not involve removing stuff from the wall, ha. Did everything as instructed in githup, and the result is … update went okay, both thermostats went offline and after couple hours doing thousand things, did not get them back online.

Okay, will work on that another time. Now at least I dont have the flooders on the network, lets see if faikins stop beeping.

I could not find mosquitto.db, tho.

2100, faikins beeped, light is out, no flood and now data//mosquitto.db line. Oh man.

Try removing & re-pairing the thermostat in Z2M

We ended up with two different issues here, so here is an update 3 weeks later.

1- Zigbee flood by Moes thermostat: ota update was ok, but never got it back to the network. The thermostat itself still works great, local panel, touch, schedules, all ok. But it simply does not connect. Power cycle the thermostat, software update on hass, reversed the custom config for device in z2m, put it back on, power cycle raspberry, removed and reconnected dongle, try to join using only concentrator, or only repeater a b c… nothing. Bright side is no more zigbee flood. Ordered yesterday a wifi thermostat from aliexpress at 27 bucks, and will use my time more wisely.

2- bad part is that the faikins keep making noise. Every full hour all converted units go beeep. Its said, cause I have other faikin pcbs ready and the bedrooms ac waiting for the conversion, but… nono, no hourly beep in bedroom. Could not find anything related on logs or anywhere. Expected that maybe with no flood i would get it solved, but no luck.

Any idea is welcome.

thanks.

There are a lot of faikin users in this topic you could ask: Need Daikin Wifi? Use the Open-Source Faikin ESP32 Hardware instead of the official wifi Modules

1 Like