[APP] Aqara & Xiaomi Smart Home - Simplify your life with a smarter home

@MGD

Issues described above are persistant and very systematic over time. Hope they can be adressed. More than wiling to send logs when they occur. Will also consider to throw the problematic devices over to the other Aqara app (!) Aqara Community App | Homey to test FP300 and W600 reliability there.

This is relevant to my interests. Here’s hoping a talented individual like Ted can add official support! Thanks!

Yep, tried that and it still didn’t work. Same error.

On the Firmware updates (of the FP300’s) Athom is currently looking into the issue(s):

To support can you:

  1. switch on the verbose logging within the Zigbee section of the Homey developer tools
  2. Retry to update the firmware of a single FP300 sensor. Avoid pressing the retry button multiple times in a short timeframe.
  3. When failing, submit a Homey diagnostics report and share the 8 character code here

Verbose logging enabled, and an update in progress… I’ll report back when it’s eventually finished :+1:

How do you get that update?
I have massive problems with all my FP300 and W600 and would love to try out a firmware update. But unfortunately Homey does not offer one…

In the Homey mobile app:

Thanks for the quick reply!
That was were I was looking but it says that everything is up to date. - So I´ll have to take that as a fact.

Switched on verbose logging for Zigbee in dev tools.

I retried a previously failed update on my Spare Room FP300, but that immediately failed and disappeared from the list. So I took down the Bathroom FP300, took it downstairs and sat it on the shelf about 20 or so cm above my Homey Pro and started a new update.

That update finished downloading and then failed. I did a retry twice, both times as soon as it connected to the FP300 it failed saying that the device rejected the update due to a bad version.

The Diagnostic Report ID for Homey is:

A63B2926

The Diagnostic Report ID for the app is:

e3502b09-fe63-4191-8e0c-508d285b0612

If you need any other details let me know

The forum website decided to add my screenshots back to front… and trying to rectify that on my phone is driving me nuts… so they’re in reverse order ha ha

Until the OTA updates are fixed and actually completing updates I would not worry about it… watch this space :wink:

On the FP300 that finished, did it actually update the firmware version number to 0.0.0_6542 (after pressing the sensors button to send a lifeline report)?
Or does it still show the old version number?

It appears to be reporting the version number you state, at least in one of the two firmware version fields in the device settings page:

But that is the only FP300 out of 10 that has achieved this. So far all other attempts have failed spectacularly.

Hi Ted @TedTolboom

An update for you on the firmware situation… by sitting an FP300 almost on top of my Homey Pro and repeatedly bashing it over its metaphorical head with firmware updates until my Homey was begging for mercy from the high CPU load (at least half a dozen attempts later… including trying restarting the FP300, the app, and restarting both) it has finally seen sense and accepted the firmware update, at least it claims to have. I’m hoping this process can be somewhat streamlined and simplified, especially with the number of Aqara devices I have around my home :grin:

I’m running out of ideas, any other thoughts?

Can the app owner can help troubleshoot?:folded_hands:

Hmmm.. puzzling indeed. I haven’t had any issues with my T1 ceiling light, in pairing or operation.

The only other things I can think to suggest is to have a deeper look in to your Zigbee network, and any possible sources of interference (like WiFi using the same frequency band squashing the lower power Zigbee, so the light can’t complete the pairing process).

These apps (which I use myself) may help with diagnosing any Zigbee issues:

You can also have a look at the developer tools Zigbee page, although it doesn’t offer much more information than these apps already do.

I hope you manage to find a solution, and it’s not a hardware fault.

Latest firmware for W600 should be 0.0.0_2848 and 0.0.0_6542 for FP300. You can check your version under device settings–> scroll down to Advanced settings.

I updated them rather recently from the Aqara Home app (Android), and Homey also reports that no updates are available. Not sure which problems you have with them? I have the problem that some of them stop reporting e.g., lux, temp and valve position after 24h. Motion and presence keeps reporting relatively fine on the FP300s. I have now tried to downgrade to 1.19.2 (from 1.20.0) of the Homey Aqara app to check if that makes a difference. If not I will likely try to throw one of each of them into the alternative community Aqara app.

Thanks @Drako74 I’ve other ZigBee devices in the same room which work perfectly fine and the insight apps aren’t really shedding any light on the route cause. If it’s not a driver/app issue then … Any ideas how I can validate it’s a hardware issue without another ZigBee hub?

Sorry, I’m kinda stumped for much more in the way of ideas to try.

I didn’t see a reply to your diagnostic report from @TedTolboom the app developer, unless you received one via message?

Other than that, perhaps try doing a Homey diagnostic report (Homey app / More / Settings / General, at the bottom of the page) and logging it with Athom support, see if they can see anything wrong with your Zigbee network.

It might also be worth it to enable verbose Zigbee logging before trying a pair of the T1 and then creating the diagnostic report, to provide maximum logging. Just don’t forget to turn the verbose logging back off after creating the report (or you’ll fill your Homey with logs in short time).

You turn it on/off here:

Scroll to the bottom of the page where you’ll find the enable and disable buttons:

(Don’t click the Reset one unless you want to re-pair all your Zigbee and Thread devices from scratch! That would be a bad day indeed.)

Downgrade of app v did not help. I am currently testing one of the problematic FP300 in the community app. If it does not stop reporting on indicators in about 24h, I will also add one of the W600 there to check.