Active 2 Premium device sources still missing in a few places

[cubemike]

I didn't notice this at first because I was only using API 1, but when using API 2 and up the Active 2 premium device sources are missing. I have 2 examples to share:

active2pTests.zip

configV2_active2p:

I've added the Active 2P deviceSource to the app.json directly.

What I expect:
To be able to simulate or preview this project as normal.

What I see:
The following error when running zeus dev or zeus preview:

warning  Unsupported targets(default) have been removed.
error  Please set at least one package.

You can go into the app.json and swap out the deviceSource with one of the base Active 2 device sources (e.g. 8913159). This works fine, no issues.

configV3_active2p

What I expect:
To be able to preview this project on an Active 2 Premium watch

What I see:
I am able to generate a qr code without an issue. But during that process when I select to preview on the Active 2, I see this output:

$ zeus preview
info  building...
? Which device would you like to preview? Amazfit Active 2 (Round)
info  Start building package, device sources: 8913155, 8913159.

Only those two device sources above are generated. When I actually scan the QR code with my phone, I get an error. Clearly the premium device sources aren't included.

[zeppos-hx]

Please make sure that you have updated the zeus to latest version v1.6.6, and maybe you should delete the devices cache file on ~/.zepp/.zeus_devices and try zeus preview again

the latest zeus version will print out like this:
zeus -v node: v22.14.0 npm: v10.9.2 zeus: v1.6.6 zpm: v3.1.4

[cubemike]

I'm in the Eastern USA.

[zeppos-hx]

You can just access this json url in browser and check, is Active 2 Premium device sources like 10092800 in the content?

[cubemike]

I just checked again, and the premium device sources are definitely not in the json of that page.

[zeppos-hx]

The cloud team has refreshed the CDN content, and I checked it is the newest now, please check again, we will keep updating

[cubemike]

Yes, it's working now. The issue is solved for me. I'm going to close the discussion.