I understand that this is annoying, but do you need to create a new post about this issue every couple of hours?
There is no functionality to remove unknown Zigbee nodes yourself, except for restarting your Homey (which is supposed to remove them).
If the unknown node remains in the list in Homey Developer Tools and it does not show itself as an actual device in the Device tab in the mobile app, then it is best to reach out to Athom’s support desk, as I indicated before.
By the way: your screenshot shows multiple unknown nodes, so there is more going on.
I am not opening a new post, but trying to help with the development, which is why I am sending the diagnostic report. I am showing that I removed both devices on the developer page and they did disappear from the Zigbee network, then I unplugged the Homey for 30 minutes. After this, I tried to add them and it says the exact same thing: the device is already added. Since the problem has been occurring ever since a faulty FW update ruined all the Aqara devices. And after this I also talked to Athom, obviously I sent everything to them too. But they can’t see any more either. I am not posting hourly, but after the method suggested by Athom didn’t solve the problem, I thought the pictures and diagnostics would show you more about where the issue might be.
So the issue did not start with the Aqara app update, but a prior Homey OS update?
If Athom is not able to help, then an alternative is to perfom a Zigbee reset (via the Homey Developer Tools). The downside is that you’ll have to repair (not re-pair) all your Zigbee devices again via the Repair option in the (Maintenance menu of the) device tile.
The devices that are all unknown, other than the circled one, are all Aqara Wi-Fi Wall Switch D1 models, and they do not identify their manufacturer. They never have.
I am not referring to the unknowns in the Manufacturer column, but the Unknown Nodes at no. 7, 13 and 14.
I didn’t even notice those, I was so focused on the water leak sensor. Those will be Aqara stuff too: two Aqara H1 EU no-neutral switches. But it’s interesting because all of these are working and they are visible as devices on the Homey interface.
@TedTolboom any news here? 
Hi Ted,
I’ve tried the same setup as prior to 1.18 update and the button presses act the same as before. Three presses can trigger events successfully and then 10 in a row can go unregistered, and so on for random amounts of presses each time. (Tried now also with 1.18.1)
So seems very similar to before unfortunately 
Cheers,
Christopher
Are you going to implement OTA updates for the Zigbee devices? I have some battery report issues, I hope an update solve this
This has been mentioned before by @Doekse that OTA updates won’t be added to Aqara, because Aqara does not want to provide update files.
Aqara indeed isn’t open to providing the firmware files for their Zigbee devices unfortunately.
Hi all,
I’m struggling with my W600 thermostate. Immediately after connecting the device is working fine but after a couple of hours it seems to lose connectivity and temperature measured is reported as 0. I ('m trying to) use the device in zigbee mode and it’s able to connect initially. Zigbee connectivity also looks fine in the developer tools.
I’m looking into this issue and running long term stability test on the W600 on an update to see if that is solving this issue.
The M3 hub had some money off recently so I got one. My H2 switches are now child devices on the hub & the Matter bridge makes them visible to Homey. Connected like that everything works flawlessly.
The only downside is there doesn’t seem to be a way to access the multi press functions of the switches. Apart from that, switch presses do what they are supposed to first time, every time. That compares to sometimes needing to do 4 or 5 presses to get any response (or giving up & manually switching whatever combination of lights I wanted) when connected directly to Homey Pro via ZigBee. The flows always worked when activated from the Homey App but communication of the button presses was failing at one end of the signal chain or the other (I’m guessing the Homey end as theswitch presses are fine with the hub.
My experience with the Aqara M3 hub so far has been pretty flawless. You certainly seem to get a more stable, consistent, and reliable connection with Aqara devices when connected to the M3 (not a huge surprise really, that they make sure their own kit works best with their own hub). I’m not sure if it is just Homey’s multi-radio/antenna design, or the drivers in the Aqara app on Homey. I am looking into trying some of the less reliable devices I have on the new community Aqara app, see if I have better luck 
This is a Matter limitation, and is similar for all devices and brands… Matter does offer inter-band support well, but at the cost of manufacturers seemingly keeping the best features to themselves ha ha. The dream is there, just not fully realised yet.
Glad to hear you got your problem resolved though. And you can always use the multi-presses in Aqara automations on the M3 (you can selectively Matter bridge some devices back to the M3, messy workaround I know, but I’ve had it working quite well and reliably).
Hi @TedTolboom,
E1 radiator thermostats (lumi.airrtc.agl001, FW 0.0.0_0030) still don’t apply setpoints sent from Homey with v1.18.1.
Setup: Homey Pro (Early 2023), Homey 13.5.1, Aqara app 1.18.1, 4x E1, Aqara Wall Outlet H2 EU as Zigbee routers.
Test today 12:32 (stable network): set target 23 °C on all four via Flow.
- Developer Tools: 2 tx / 0 errors / 2 rx per thermostat, device lastSeen = command time → frames are delivered and answered.
- Homey shows 23 °C, but all four displays keep the old setpoint.
- At the next heartbeat (~50 min) Homey reverts to the real (old) value.
- Changes made on the device itself are reported to Homey instantly. Child lock behaves the same way.
Before 1.18.1 roughly 1 in 3–4 commands was applied; with 1.18.1 0 of 8 so far.
Already tried: new batteries, re-parenting to H2 outlets, Homey reboot.
Diagnostic report: da91c5e9-a41b-4bbf-8d1a-c30ccacaaea2
Had this problem in the past. So I disabled the flow to control the themostats. Now I restarted to get them working.
Thank you!
Best regards,
Jan
Version 1.19.0 will have a complete reworked handling of the external temperature sensor input, for the E1 radiator thermostat and as well as the W100, W600 thermostats and will enable it for the W500 thermostat.
Duration tests are running atm and will release this update to the app store within this week.
Thanks a lot! This drives me crazy … and my wife.
Version 1.19.0 has just been released to the App Store’s test environment.
Pending Athom’s approval.
Given that it is a substantial change, I will only push it to the main App Store after a few days.
Detailed changelog:
Aqara v1.19.0
This version adds 9 new devices, improves the external sensor input of the Aqara thermostats and makes battery powered devices more reliable.
Requires Homey v13.1.0 or newer.
New devices
- Presence sensor FP1 (RTCZCGQ11LM): presence and a Presence event detected flow card (e.g. enter, leave, approach, away), with settings for sensitivity, monitoring mode and approach distance. Includes a Reset no presence maintenance action. Thanks to @Gabriel_Pedrosa_Mach for your contribution here!
- Motion sensor E1 (RTCGQ15LM): motion, illuminance and battery.
- High precision motion sensor (RTCGQ13LM): motion and battery, with sensitivity and a detection interval setting (2–180 s).
- Door and window sensor E1 (MCCGQ14LM)
- Water leak sensor E1 (SJCGQ13LM)
- Wireless remote switch E1, single rocker (WXKG16LM) and double rocker (WXKG17LM)
- Wireless mini switch E1 (WXKG20LM)
- Wall switch H1 Pro, triple rocker with neutral (QBKG32LM)
Thermostats and climate sensor: external sensor input
Applies to: Smart Radiator Thermostat E1, Floor Heating Thermostat W500, Smart Radiator Thermostat W600, Climate sensor W100
- The last external value is kept alive. The app re-sends the last temperature (and humidity) set by your flow every 30 minutes, for up to 3 hours. Without a new value within 3 hours, the device falls back to its internal sensor. It switches back to the external sensor automatically with the next value.
- E1: the E1 doesn’t fall back by itself (it keeps its last external value), so after 3 hours without a new value the app tells it that the external sensor is offline (falling back to the internal sensor).
- The “Temperature sensor” setting stays on “external” when the thermostat falls back by itself.
- Requests from the thermostats are answered with the last value, also after an app restart.
Tip: run the Set the external room temperature / humidity flow on every change of your sensor and periodically (e.g. every 15 minutes). The flow card hints now explain this.
Presence sensors
- FP300:
- Presence and PIR detection are reported reliably, and an alarm that should have reset no longer stays on.
- Added LED indicator setting.
- FP1E: detection range and sensitivity updates.
Cube T1 Pro
- Operation mode switching works: the new mode is sent when the cube opens its configuration window. After saving, throw the cube or press its LINK button once. The setting also follows the cube when you switch the mode on the cube itself (LINK button 5 times).
- A rotation now triggers one Rotate event with the total angle, instead of several partial ones.
Vibration sensors
- Vibration sensor (DJT11LM):
- Tilt angles are corrected.
- The Set tilt reference setting is replaced by a maintenance action.
- The relative tilt angle now updates with every tilt event.
- Vibration sensor T1:
- The sensitivity setting is fixed.
- Battery percentage added.
Light sensor T1
- Darkness now shows as 0 lux instead of 1 lux, and values are rounded to whole lux.
- Each light change is reported once instead of twice. Existing sensors are corrected automatically the next time they report.
- Battery percentage added.
Smoke detector and water leak sensors
- Smoke detector: battery percentage added.
- Water leak sensor T1: the water alarm is checked against the sensor’s regular status report, so a missed alarm or “dry” message no longer leaves the wrong state in Homey.
All devices
- Firmware version in the device settings: shows the version as in the Aqara app (e.g.
0.0.0_0035), read from the device. This now also covers older devices such as the door and window sensor, water leak sensor and temperature and humidity sensor. For devices added before this version it is filled in the next time the device reports. - Settings on battery powered devices are no longer lost when the device is asleep. The app writes them the next time the device wakes up, so there is no need to wake the device right before saving.
- Fewer devices dropping off the network:
- The app answers the reset request of wall switches, relay modules and several remotes.
- Button and scene presses:
- The waiting time after a press is shorter, so a quick second press is no longer missed.
- The app checks that buttons and remotes stay in the mode that reports button presses.
