Weird behaviour Asus AX-82U

I've got a mesh network of a AX-82 and AX-53. It's been running about a year. AX53 is stock, AX82 runs gnuton/asuswrt-merlin. Basically flawless until the last few months. At seemingly random intervals the network will dump wireless clients running Espressif chips (ESP32 & ESP8266), plus a Samsung oven (MAC not Espressif) . The oven is isolated from the ESP clients (different SSID) and the ESP devices are shared across 2 x SSID. The clients will stay off the network for up to 15 minutes. It was most noticeable as MQTT (a raspberry pi) would drop out sometimes. I has logging on some ESP devices and they only showed a loss of MQTT. I run Uptime Kuma and that pings all my IOT every minute. This showed the ESP devices being dumped and re-connected. MQTT was never dumped.

I thought I'd isolated it to a home assistant/open Beken Tuya BK7231N/CBS3 in a temperature sensor, but the problem continued for months. I'd forgotten about a door sensor that is infrequently used. Same tuya chip. If either device associate with the AX82, it dumps most ESP devices off the network. If they associate with the AX53 there is normally not a problem - just had the Tuya associate with the AX53 and a nearby device associated with te AX82 was dumped. Go figure.

These are battery devices with fresh batteries, running in sleep mode.

I've changed so many router settings I've almost lost track

I've a few smart plugs which had various Tuya devices, but 1 failed and I'd already replaced the others with pin compatible ESP8266, so no issues found there.

For info

All the devices compile in Platformio, using  Arduino.  As a general rule, all the ESP are V2 Arduino/ pre 6.10.0 PIO. I've got other ESP which aren't booted off, but the majority are. Some are 802.11n, some g, some b.

The door sensor (with AX82) only crashes the network when the door is closed.

Router log - shed door is the door sensor

Jul 27 10:59:49 wlceventd: wlceventd_proc_event(685): wl0.1: Auth SHED DOOR, status: Successful (0), rssi:0

Jul 27 10:59:49 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc SHED DOOR, status: Successful (0), rssi:-78

Jul 27 11:01:00 kernel: WEATHER STATION  not mesh client, can't delete it

Jul 27 11:01:00 kernel: OVEN ] not mesh client, can't delete it

Jul 27 11:01:00 kernel: SHED DOOR not mesh client, can't delete it

Jul 27 11:01:10 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind WEATHER STATION , status: 0, reason: Previous authentication no longer valid (2), rssi:-77

Jul 27 11:01:10 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind CPI2 , status: 0, reason: Previous authentication no longer valid (2), rssi:-76

Jul 27 11:01:10 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind SHED DOOR, status: 0, reason: Previous authentication no longer valid (2), rssi:-78

Jul 27 11:01:10 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind IOTAWATT , status: 0, reason: Previous authentication no longer valid (2), rssi:-40

Jul 27 11:01:10 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind SUNNYBOY , status: 0, reason: Previous authentication no longer valid (2), rssi:-62

Jul 27 11:01:10 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind BEDROOM-CLOCK [, status: 0, reason: Previous authentication no longer valid (2), rssi:-72

Jul 27 11:01:10 wlceventd: wlceventd_proc_event(645): wl0.3: Deauth_ind OVEN ], status: 0, reason: Previous authentication no longer valid (2), rssi:0

Jul 27 11:01:10 wlceventd: wlceventd_proc_event(645): wl0.3: Deauth_ind OVEN ], status: 0, reason: Previous authentication no longer valid (2), rssi:0

Jul 27 11:01:10 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind WEATHER STATION , status: 0, reason: Previous authentication no longer valid (2), rssi:-77

Jul 27 11:01:10 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind CPI2 , status: 0, reason: Previous authentication no longer valid (2), rssi:-76

Jul 27 11:01:10 wlceventd: wlceventd_proc_event(645): eth5: Deauth_ind IOTAWATT , status: 0, reason: Previous authentication no longer valid (2), rssi:-40

Jul 27 11:01:10 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind SHED DOOR, status: 0, reason: Previous authentication no longer valid (2), rssi:-78

A later log for the temperature sensor doesnt show the ESP devices being dumped

Jul 27 11:17:34 wlceventd: wlceventd_proc_event(685): wl0.1: Auth TEMPERATURE SENSOR 1 , status: Successful (0), rssi:0

Jul 27 11:17:34 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc TEMPERATURE SENSOR 1 , status: Successful (0), rssi:-75

Jul 27 11:17:38 kernel: MQTT IP is used by someone else, can't use it

Jul 27 11:17:53 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind TEMPERATURE SENSOR 1 , status: 0, reason: Unspecified reason (1), rssi:-73

Jul 27 11:17:53 wlceventd: wlceventd_proc_event(685): wl0.1: Auth TEMPERATURE SENSOR 1 , status: Successful (0), rssi:-73

Jul 27 11:17:53 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc TEMPERATURE SENSOR 1 , status: Successful (0), rssi:-73

Jul 27 11:19:02 kernel: WEATHER STATION  not mesh client, can't delete it

Jul 27 11:19:02 kernel: OVEN ] not mesh client, can't delete it

Jul 27 11:20:04 wlceventd: wlceventd_proc_event(662): wl0.1: Disassoc STUDY_RADIO , status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

Jul 27 11:20:04 wlceventd: wlceventd_proc_event(662): wl0.1: Disassoc STUDY_RADIO , status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

Jul 27 11:20:07 kernel: MQTT IP is used by someone else, can't use it

Jul 27 11:20:32 kernel: AC  not mesh client, can't delete it

Jul 27 11:20:32 kernel: MQTT (PI5 wifi)  not mesh client, can't delete it

Asus Zeneye camera

This is one of very few posts that exist for these cameras. I guess they were never very popular. I paid 25€ 6 months ago for a working set of 2, with base. They work fine, battery life is good. They are waterproof. Or at least they are until they are dropped. I'm guessing mine was dropped as 2 internal mounting pillars are broken, meaning the screws with O-rings no longer sealed to the PCB.

Long story short, I drowned a camera. It was foolish on my part. I put the camera upside down in a gutter. It worked fine for a few days and I've plenty of footage with the camera submerged.

It's now in pieces to dry out.

The disassembly starts with a T6 in the base mounting hole. This reveals a removable outer shell (non-lens side, which is fixed) Careful unclip and remove this. Now remove all the 000 screws and off pops the case; to fully separate carefully jiggle the small pcb (bottom photo middle left) which will readily come loose.

Leave in the airing cupboard a few days and re-assemble. I should probably wash it in IPA or ethanol, but it was clean rain water.

X capacitor goes bang

A large bang and an awful smell. X capacitor in an extension block.

Quite a mess to clean up as it leaked into the base. At least it didn't go pop into a PSU with a fan.

WD SN520 NVME raspberry pi

 As reported widely, WD drives are avoided for RPI 5. The WD SN520 NVME raspberry pi does not work. A few photos in case anyone finds a driver for the Sandisk controller

Whatsapp transfer

 tldr; I messed up the transfer of messages to my new phone. However, it worked out fine.

The mistake I made; that the backup on google was up to date. It was a day old. What I'd forgotten that I'd done a lot of messaging that day. So I'd moved the SIM to the new phone, started whatsapp and accepted a restore from google. This was a few hours out of date.

Googling suggested lots of ways to now move the data including 'tough, too late'

Logically, all the messages were still on the old phone. Leaving the sim in the new phone, I removed whatsapp (didnt keep old data), then re-installed, but didn't open it. All this lost was a local database. There is still a backup on google. On the old phone I opened whatsapp and set it up with the old phone number. Then I followed the instructions here https://faq.whatsapp.com/209942271778103/?cms_platform=android which basically tell you to goto settings/chats/transfer chats ie follow the instructions for a normal transfer (which you should have done originally, muppet) You are guided from there, but in short, once the old phone is setup, open WA in new phone and accept the transfer from the old phone, scan a QR code shown on the new phone.

What didnt work. On the old phone, registered to my number (no sim) do a back up. It was over 24 hours since the last one, and it said it was working, but the backup date never changed. When restoring to the new phone, I was missing messages.

Crimping large lugs

 I ordered a cheapo lug crimper to do a 50mm2 lug. The seller turned out to be a scammer. Got my money back, but I still needed to crimp the lugs. I looked at the tool and decided that my vice would give enough force. I ordered the jaws for 3€ and made a small jig

The small bit of 0.5mm sheet steel shrinks the die a bit, as it's a 50mm lug and 1 awg cable (43mm2)

Generic Tuya thermometer module

direct match https://www.elektroda.com/rtvforum/topic4098816.html

Desoldered the battery to get at the programming pads.

Flashed with open beken.

No voltage regulator. Chip BK7231N is rated 2.3 to 3.6V max

{

  "vendor": "Tuya",

  "bDetailed": "0",

  "name": "Full Device Name Here",

  "model": "enter short model name here",

  "chip": "BK7231N",

  "board": "TODO",

  "flags": "1024",

  "keywords": [

    "TODO",

    "TODO",

    "TODO"

  ],

  "pins": {

    "6": "CHT83XX_SCK;1;0",

    "9": "CHT83XX_SDA;1;2",

    "16": "dInput_n;0",

    "17": "BAT_Relay;5",

    "20": "dInput;43",

    "23": "BAT_ADC;40",

    "26": "WifiLED_n;37"

  },

  "command": "// start some drivers\r\nstartDriver CHT83XX\r\nstartDriver battery\r\n\r\n// hold button 20 to get into safe mode\r\naddEventHandler OnHold 20 SafeMode\r\n\r\n// battery\r\nBattery_Setup 2350 3000\r\nBattery_Measure\r\n\r\n//cal temp sensor, temp then humi\r\nCHT_calibrate -5 19\r\n\r\n// 20s timeout to deep sleep for 600s if following events never complete\r\naddRepeatingEventID 20 -1 1337 DeepSleep 600\r\n// wait until wifi is connected\r\n//waitFor WiFiState 4\r\n// wait for MQTT to connect\r\nwaitFor MQTTState 1\r\n\r\ncancelRepeatingEvent 1337\r\n\r\n// wait 5 seconds\r\ndelay_s 2\r\n\r\npublishChannels\r\ndelay_s 5\r\n\r\n// Deep sleep (shut down everything) and reboot automatically\r\n//DeepSleep 30s\r\n//temp diff, ignore humi, sample time, fault q\r\nCHT_Alert 0.5 0 60 2\r\n//20 min sleep. should wake up if large change as above\r\nPinDeepSleep 1200",

  "image": "https://obrazki.elektroda.pl/YOUR_IMAGE.jpg",

  "wiki": "https://www.elektroda.com/rtvforum/topic_YOUR_TOPIC.html"

}