dresden-elektronik / phoscon-app-beta

Access to Phoscon app beta
79 stars 5 forks source link

Xiaomi Mijia Zigbee 3.0 Smart Home Light Sensor parring fails in phoscon #361

Closed goegsig closed 3 years ago

goegsig commented 3 years ago

When i try to add a new sensor it just times out. billede

it appears in deCONZ, but it is not working billede

Iam using the deCONZ add-on in Home Assistent and it is this version billede

It looks like these issue https://github.com/dresden-elektronik/deconz-rest-plugin/issues/2380 https://github.com/dresden-elektronik/phoscon-app-beta/issues/166

goegsig commented 3 years ago

billede

billede billede billede

tellerbop commented 3 years ago

I have the exact same issue with controller firmware 260B0500

YKO-de commented 3 years ago

Can you try phoscon.de/pwabeta?

stefanmechelen commented 3 years ago

I tried that, doesn't solve it. Any solution for this coming up?

MasterMik commented 3 years ago

Same problem here with the Mi light detection sensor.

YKO-de commented 3 years ago

It works for me under the beta. Possibly update the deCONZ version again. image

MasterMik commented 3 years ago

@YKO-de Danke, hat geklappt.

stefanmechelen commented 3 years ago

I'm having problems updating. Script runs. It's flashing.

Yet I still get in the app: 2.06.00 / 15-11-2020 - 266B0700

But I choose deCONZ_ConBeeII_0x266b0700.bin.GCF, which is from april 29, 2021 (can't do that with a beta by the way, that sees downloading error)

Log: https://controlc.com/31f1bc71

What am I doing wrong?

UPDATE: [solved] nevermind, firmware was correct, docker deconz container on the contrary was serious out of date, my mistake, sensors added ....

stale[bot] commented 3 years ago

As there hasn't been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

stale[bot] commented 3 years ago

As there hasn't been any response in 28 days, this issue will be closed. @ OP: If this issue is solved post what fixed it for you. If it isn't solved, request to get this opened again.