Matter Update Entity Not Finding Testnet DCL Update

[jvmahon]

The problem

I think the Update entity may not be finding firmware updates on testnet DCL.

Here's what is happening.

1. I have a number of Aqara P2 sensors, Firmware "1.0.0.0", Hardware "1.0.0.0" (diagnostic log attached below)
2. I have the Python Matter Server configured to enable test-net DCL usage
3. Testnet DCL shows an available firmware "1.0.1.0" and that Software Version Valid is true:

I assume this "1.0.1.0" firmware OTA version on testnet should show up as an available update, but it does not.

Note that on the "regular" DCL, there is a later firmware version "1.0.1.1" which is listed as being not valid. Is it possible that the update algorithm finds this latest version, but when it determines it is not valid, does not check for an earlier valid version? Or maybe something is wrong with the version comparisons between the current firmware version and the testnet update?

What version of Home Assistant Core has the issue?

2024.08.01

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Matter

Link to integration documentation on our website

https://www.home-assistant.io/integrations/matter/

Diagnostics information

Aqara P2 Diagnostic Data.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @home-assistant/matter, mind taking a look at this issue as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `matter` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign matter` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

matter documentation matter source _{^{(message by IssueLinks)}}

[marcelveldt]

We do not support testnet DCL updates (as that is very dangerous) - if you are a device manufacturer and you really want to test non stable device updates, you can manually put the json files in the updates folder:

addon_configs/core_matter_server/updates/

[marcelveldt]

Also, do not update the Aqara P2 sensor using that update, there is a 50% chance you wil brick your device.

[jvmahon]

We do not support testnet DCL updates (as that is very dangerous) - if you are a device manufacturer and you really want to test non stable device updates, you can manually put the json files in the updates folder:

addon_configs/core_matter_server/updates/

Thanks. Good to know. My real interest in the testnet DCL was less for the P2 update (I was just confirming testnet operation using the P2), and more for beta testing work that I'm assisting Inovelli with (they distribute their beta firmware through testnet). I'll try and figure out how to manually put the json files in the updates folder as you've suggested.

[marcelveldt]

5181-4097-10010011-Onvis-S4.json

Here is an example json file for an Onvis S4 powerplug. Just drop that file in the updates dir and restart the matter server. The json file is the same format as what you can download from DCL. Just note that installing updates that are NOT from main-net DCL are completely at your own risk.