General ZBMini issue. #4016

ghost · 2020-12-24T10:16:56Z

Describe the bug

I have issues with 4 of my 5 Sonoff Zigbee mini switches (ZBmini) in Deconz, also in combination with HA. The ZBmini are recognized in Deconz in phoscon and in the VNC viewer and also in HA. Also the connected regular switches connected to the ZBmini’s work fine (you can hear the relay). However, the switching in phoscon and HA does not works:

Switching in HA or Deconz to on or off only works one time.
Switching triggers multiple events in HA history and in Deconz. Example:
2873: 14:10:49:898 Websocket 172.29.0.1:41700 send message: {"e":"changed","id":"35","r":"lights","state":{"alert":null,"on":true,"reachable":true},"t":"event","uniqueid":"84:71:27:ff:fe:93:13:58-01"} (ret = 140)
2874: 14:10:49:899 Websocket 192.168.2.20:54220 send message: {"e":"changed","id":"35","r":"lights","state":{"alert":null,"on":true,"reachable":true},"t":"event","uniqueid":"84:71:27:ff:fe:93:13:58-01"} (ret = 140)
2875: 14:10:49:900 Websocket 192.168.2.20:54434 send message: {"e":"changed","id":"35","r":"lights","state":{"alert":null,"on":true,"reachable":true},"t":"event","uniqueid":"84:71:27:ff:fe:93:13:58-01"} (ret = 140)

One of my ZBmini is working, but still triggering multiple events. I do not know why this ZBmini is working. I do not see a difference in Deconz.

My problems looks the same as described here: #3632 and https://community.home-assistant.io/t/zigbee2mqtt-switch-automatically-toggles-from-off-to-on-after-1-second/244833

Steps to reproduce the behavior

The issue is seen for 4 out of the 5 Sonoff ZBmini's. Restarting de HA and deCONZ containers does not help. Same for restarting the host (Qnap NAS). There also is no difference between deCONZ 2.7.1 and 2.8

Expected behavior

In HA and deCONZ is should be possible to swith the ZBmini on and off (independent of the regular switch connected to the ZB mini).

Screenshots

For screenshots see #3632

For me the screenshots form issue 3632 are the same. Only the Date code is difference (20200927) and the Power Source (unkown).

Additional screenshot:

Please let me know if any other screenshot is needed.

Environment

Host system: Qnap 253be NAS
Running method: HA core Docker container / Marthoc Docker container
Firmware version: 26680700
deCONZ version: 2.7.1
Device: ConBee II
Do you use an USB extension cable: yes
Is there any other USB or serial devices connected to the host system? yes, DSMR to P1 cable. And Zwave stick using extension cable.

deCONZ Logs

I do no see errors in the debug INFO, ERROR,ERROR_L2,APS,APS_L2 (besides the multiple entries shown above).

Also see https://pastebin.com/jNQzdf2E

During the log I have tried switching the light (logeerkamerlamp) in phoscon en the regular wall light switch attached to the ZBmini.

Additional context

According HA I have 90 nodes and 150 entities.

ghost · 2020-12-24T11:03:50Z

Today I have made a new debug INFO, ERROR,ERROR_L2,APS,APS_L2

see https://pastebin.com/RS2RmbEv

During the log I have switched the lights logeerkamerlamp and kluskamerlamp in HA end using the regular wall light switch attached to the ZBmini. Strangely they now both work, but still showing multiple entries in HA (in the history of the lights) and in the log.

SwoopX · 2020-12-24T23:33:39Z

Thanks for the logs. You mean like those 2 here?

10:58:09:093 APS-DATA.indication srcAddr: 0x493b, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -43
10:58:09:094 	asdu: 086e0a00002801
10:58:09:095 APS-DATA.request id: 114 erase from queue
10:58:09:095 Node data 0x842e14fffe9e1404 profileId: 0x0104, clusterId: 0x0006
10:58:09:096 0x842E14FFFE9E1404: update ZCL value 0x01/0x0006/0x0000 after 0 s
10:58:09:097 enqueue event state/on for /lights/33
10:58:09:097 ZCL attribute report 0x842E14FFFE9E1404 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
10:58:09:098 	payload: 00002801
10:58:09:098 APS-DATA.request id: 117, addrmode: 0x02, addr: 0x493b, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
10:58:09:100 Websocket 172.29.0.1:58844 send message: {"e":"changed","id":"33","r":"lights","state":{"alert":null,"on":false,"reachable":true},"t":"event","uniqueid":"84:2e:14:ff:fe:9e:14:04-01"} (ret = 141)
10:58:09:100 enqueue event event/checkgroupanyon for /groups/65520
10:58:09:138 APS-DATA.indication srcAddr: 0x493b, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 255, rssi: -43
10:58:09:139 	asdu: 086f0a00001001
10:58:09:140 Node data 0x842e14fffe9e1404 profileId: 0x0104, clusterId: 0x0006
10:58:09:140 0x842E14FFFE9E1404: update ZCL value 0x01/0x0006/0x0000 after 0 s
10:58:09:141 enqueue event state/on for /lights/33
10:58:09:142 ZCL attribute report 0x842E14FFFE9E1404 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
10:58:09:142 	payload: 00001001
10:58:09:143 APS-DATA.request id: 119, addrmode: 0x02, addr: 0x493b, profile: 0x0104, cluster: 0x0006, ep: 0x01 -> 0x01 queue: 1 len: 5 tx.options 0x00
10:58:09:144 Websocket 172.29.0.1:58844 send message: {"e":"changed","id":"33","r":"lights","state":{"alert":null,"on":true,"reachable":true},"t":"event","uniqueid":"84:2e:14:ff:fe:9e:14:04-01"} (ret = 140)

The remarkable thing is that the device seems to send 2 attribute reports shortly after another. The first payload (00002801) contains an incorrect data type being signed 8-bit integer, the second (00001001) the correct data type boolean.

So on the one hand, the device does something odd, on the other hand, we should evaluate to let only bool values through...

thundergreen · 2020-12-26T22:37:24Z

I am facing same issue her. Thught i WOuld give it a try before buyinf sonnof zigbee bridge and flash this with tasmota :(

manup · 2020-12-27T10:00:56Z

I guess this is a case where it's better to have the real device for testing. I'll put it on the order list for January.
The two faced attribute report looks really strange, note that our unholy group0 0xfff0 is also at play here /groups/65520.

The group0 bindings will be removed in the next release, and /group/0 will use a normal broadcast to all routers, however every other group to which the device is added leads to the same effect.

KodeCR · 2020-12-27T20:46:18Z

note that our unholy group0 0xfff0 is also at play here /groups/65520.
The group0 bindings will be removed in the next release, and /group/0 will use a normal broadcast to all routers, however every other group to which the device is added leads to the same effect.

@manup, note that I implemented it like that because of the suggestion by you and @ebaauw in #1005. (and only because I wanted to add Hue scenes support #1471, which still isn't merged...).

I only recently found out that group 65520 is invalid according to the zigbee specs (#3744 (comment)), and that sometimes sensors were added to the group, perhaps causing quite a few of the group0 issues.

ghost · 2020-12-27T22:14:11Z

Thanks for your efforts so far! I am not in expert in de debug logs nor in the deCONZ api. @manup, I live in the netherlands, if you also live there I am happy to supply you the ZBmini to speed things up.

eklex · 2020-12-28T02:52:33Z

I am seeing the same problem.
However I noticed that if I open the On/Off Cluster in Deconz, and execute manually the "On", "Off" or "Toggle" commands, the device behaves properly. It is only when I use Phoscon or HA that the device doesn't work as expected.

raddi · 2020-12-28T08:45:01Z

@manup I live in Germany and have 3 Sonoff ZBMinis laying around. I would send you one over if this helps.

ghost · 2020-12-28T09:39:41Z

I am seeing the same problem.
However I noticed that if I open the On/Off Cluster in Deconz, and execute manually the "On", "Off" or "Toggle" commands, the device behaves properly. It is only when I use Phoscon or HA that the device doesn't work as expected.

That is exactly what I noticed as well.

manup · 2020-12-30T22:13:08Z

@manup I live in Germany and have 3 Sonoff ZBMinis laying around. I would send you one over if this helps.

Thanks, I've already put them on the order list, should arrive in next two weeks.

If the switch works in the deCONZ Cluster Info panel it really seems to be more an issue in the plugin handling of it.

commonslibs · 2021-01-01T10:12:11Z

Hi,

Same bug in my HA installation.
My environment:

RPi 4 4Gb
HAOS 5.9 (same problem with 5.8)
Conbee 2 Firmware: 26660700, Version: 2.07.01 / 12/8/2020

I have 4 ZBMINIs and I have exactly the same problem with all of them. If more information is needed, please tell me what you need.

And another question. The ZBMINI recognizes HA as "light" instead of "switch". I think you should really recognize it as a "switch" rather than a "light".

Greetings and thanks to the team for being attentive to the problem and hopefully it will be resolved soon.

ads1230 · 2021-01-05T15:11:31Z

Had some issues setting these up but finally got them to work.
I found after pairing, the device shows in HA but has issues with control (immediately toggles off).
I found the following worked to get the devices set up and working

Restart HA and deconz
Reset the device whilst paired to deconz (holding down the physical button on the sonoff for 10s)
Then re-pair with deconz.

conbee II
2.07.01
Firmware: 26660700
Latest HA on Rasp Pi 3b+

Issue now is the weird flickering of states
https://user-images.githubusercontent.com/53495346/103662757-3a67b400-4f68-11eb-9ce1-4ad68891dcb2.mov

commonslibs · 2021-01-05T16:13:52Z

Hi;

I don't know how, but today I have (physically) connected two of the ZBMINI devices and reconnected them, and now they work perfectly for me. I don't know what could have happened to make them work for me now. :-(

But hey, it was just that, commenting that with the same software versions the devices are working correctly.

I will monitor and comment again if they stop working.

A greeting.

andrejem · 2021-01-05T19:26:46Z

I am using 2.09.0 and I am able to control the ZBMINI. But it is recognized as light/bulb and I am not able to see the status. It switches to off in the UI and json answer. But the power is still on.

@JCSCatena Do you see the correct status of the ZBMINI?

commonslibs · 2021-01-05T21:55:23Z

I am using 2.09.0 and I am able to control the ZBMINI. But it is recognized as light/bulb and I am not able to see the status. It switches to off in the UI and json answer. But the power is still on.

@JCSCatena Do you see the correct status of the ZBMINI?

In phoscon appears like this.....

As Light

But in HA appears like this....

As switch

yes, I see the correct status.

A greetings.

thundergreen · 2021-01-06T07:31:46Z

I switched to ZHA with flashed sonoff ZigBee bridge and never got problems again. Also my light bulbs and ithe ZigBee stuff without issues. I still use deconz for some sensors but replaced hue finally complete with sonoff Jose Carlos Serrano Catena <notifications@github.com> schrieb am Di., 5. Jan. 2021, 22:55:

…

I am using 2.09.0 and I am able to control the ZBMINI. But it is recognized as light/bulb and I am not able to see the status. It switches to off in the UI and json answer. But the power is still on. @JCSCatena <https://github.com/JCSCatena> Do you see the correct status of the ZBMINI? In phoscon appears like this..... As Light [image: image] <https://user-images.githubusercontent.com/43066090/103703815-85a1b700-4fa8-11eb-9f50-dcea707b97e9.png> But in HA appears like this.... [image: image] <https://user-images.githubusercontent.com/43066090/103704035-e16c4000-4fa8-11eb-9b90-32b854577734.png> yes, I see the correct status. A greetings. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4016 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADFUA77GHGBRBKKMLTWFVZTSYODFXANCNFSM4VIBPVNQ> .

jonnycastaway · 2021-01-09T23:28:36Z

Ok, here's another one with same problem.
ZBmini is connected and can be switched on and off. But the state is switching immediately to off afer switching to on.
So the status of device is always off in Phoscon. And as consequence also in my home automation system.

retoziegler · 2021-01-13T17:01:31Z

Have the same issue with both my new ZBMINIs.
I discovered that an update in HA can be forced by force-reading the attributes of cluster On/Off in deCONZ.
So it seems that the attribute OnOff (0x0000) is not always auto-updated in deCONZ when changed in the device (sometimes it works in my case).

Update: took it off- and online again and checked the configs for "IEEE Address" and "Read power descriptor" in deCONZ - works in HA now (although it still often switches back and forth, but the status is correct after some flickering).

Whatsek · 2021-01-17T15:30:02Z

Had some issues setting these up but finally got them to work.
I found after pairing, the device shows in HA but has issues with control (immediately toggles off).
I found the following worked to get the devices set up and working

Restart HA and deconz

Reset the device whilst paired to deconz (holding down the physical button on the sonoff for 10s)

Then repair with deconz.

conbee II
2.07.01
Firmware: 26660700
Latest HA on Rasp Pi 3b+

Issue now is the weird flickering of states
https://user-images.githubusercontent.com/53495346/103662757-3a67b400-4f68-11eb-9ce1-4ad68891dcb2.mov

How do you do step 3? I cant find repair in deconz.

jmpaiva · 2021-01-17T19:29:55Z

Had some issues setting these up but finally got them to work.
I found after pairing, the device shows in HA but has issues with control (immediately toggles off).
I found the following worked to get the devices set up and working

Restart HA and deconz

Reset the device whilst paired to deconz (holding down the physical button on the sonoff for 10s)

Then repair with deconz.

conbee II
2.07.01
Firmware: 26660700
Latest HA on Rasp Pi 3b+
Issue now is the weird flickering of states
https://user-images.githubusercontent.com/53495346/103662757-3a67b400-4f68-11eb-9ce1-4ad68891dcb2.mov

How do you do step 3? I cant find repair in deconz.
i believe he meant "re-pair" and not "repair".

I'm having the same issue and will try this

Whatsek · 2021-01-17T21:23:01Z

How do you do step 3? I cant find repair in deconz.
i believe he meant "re-pair" and not "repair".

Ah, that makes sense. I tried this, but unfortunately it didn't work for me. I can switch them on, but the status is then off again, so I cant turn them really off. Turning off with a switch works fin. Then I can switch them on again with home assistant. (but never off without the physical button)

jmpaiva · 2021-01-17T21:25:25Z

How do you do step 3? I cant find repair in deconz.
i believe he meant "re-pair" and not "repair".

Ah, that makes sense. I tried this, but unfortunately it didn't work for me. I can switch them on, but the status is then off again, so I cant turn them really off. Turning off with a switch works fin. Then I can switch them on again with home assistant. (but never off without the physical button)

well, I tried but I screwed something up, now conbee is having some issue, asking for a reboot :/

On step 3, do you re-pair in deconz or on phoscon? If you do it on deconz (from inside HA) how do you do it?

ads1230 · 2021-01-17T22:00:15Z

How do you do step 3? I cant find repair in deconz.
i believe he meant "re-pair" and not "repair".

Ah, that makes sense. I tried this, but unfortunately it didn't work for me. I can switch them on, but the status is then off again, so I cant turn them really off. Turning off with a switch works fin. Then I can switch them on again with home assistant. (but never off without the physical button)

well, I tried but I screwed something up, now conbee is having some issue, asking for a reboot :/

On step 3, do you re-pair in deconz or on phoscon? If you do it on deconz (from inside HA) how do you do it?

I used phoscon.
The reset of the sonoff should break the pairing, and will add it as a new device. Then you can delete the old pairing.
Any on/off issues I was having was corrected by a HA reboot after this.
Not an exact science but I did get 3 devices to work with this method.

jmpaiva · 2021-01-17T22:09:16Z

I 'm without luck.

ZBmini works great within deCONZ but either in HA or Phoscon just won't work. it never changes states properly

I'm running latest HA on a pi4, deCONZ 2.07.01, fw 26660700

spiff42 · 2021-01-22T18:39:55Z

I have the same issue (light can be toggled using local switch, not working in Phoscon, or at least only occasionally can be turned on, I do not use HA).
EDIT: After reloading the clusters through the deCONZ GUI, the vendor is reported correctly:
Vendor SONOFF
Model 01MINIZB
Version 20200927
I can control the device through deCONZ GUI by using the exec buttons in the on/off cluster, but after that I have to manually read the attributes (through deCONZ), before the state is updated and shown in Phoscon. I can neither turn on or off through phoscon.

commonslibs · 2021-01-22T19:02:12Z

I have two ZBMINI configured correctly, but now I have bought 5 more and I have the problem that is described in the BUG, that is, if the device is off, Phoscon or HA manages to turn it on, but then it is impossible to turn it off.

From deConz if I can turn it off and on every time without problems.

Hopefully it will be solved soon.

Another thing that happens is that I have added the 5 devices to HA through Phoscon and now I have deleted them from Phoscon but in HA I cannot remove them, does anyone know how I can remove them from HA?

Thank you.

marithpl · 2021-01-23T10:59:08Z

How you pair ZBmini? Phoscone app doesn't found it as light or switch.
Ok. Problem solved - I have to move ZBmini close to Conbee.

I also have problem with ZBmini and Home Assistant. Phoscone and Deconz make toggles correctly.
Is there any update for fixing this issue?

commonslibs · 2021-01-24T11:17:11Z

Hi,

I believe that I confirm that the problem is due to the fact that the ZBMINI device, once we pair it with phoscon / deconz / HA, does not refresh correctly in phoscon / HA.

If we follow the steps indicated below, we can link them without problems. I had 2 ZBMINIs linked correctly, but I bought another 5 and there was no way they would work correctly in Phoscon / HA, but following the steps below all 5 have been linked without problems:

Reset the ZBMINI by pressing the only button that has at least 10 seconds.
Restart HA.
Delete the ZBMINI devices that we do not have properly configured in HA. In my case, two of them had been able to link them for a long time, but another five that I had bought could NOT link them and I had them registered in Phoscon, HA and deconz, but they only worked well in deconz.
Call the service "deconz.remove_orphaned_entries" to clean up any devices that exist in HA but no longer exist in Phoscon because we have removed them from Phoscon in the previous step but they had remained in HA. What is done from the menu -> Development tools -> Services -> select "deconz.remove_orphaned_entries" in combo service and push the "call service" button
Add a ZBMINI device to phoscon, searching for the device in the section.
Optionally, but surely you will need it since the names that Phoscon offers when we install the device are not usually the definitive ones, update the name of the device in Phoscon and also optionally include the ZBMINI in the group that you see convenient also in Phoscon.
Restart Phoscon. What is done from the menu -> Supervisor -> Phoscon -> RESTART
We recharge the devices installed in Phoscon. Menu -> Configuration -> Phoscon Integration -> Click on the three dots -> Reload

I hope these instructions help you.

A greeting.

marithpl · 2021-01-24T11:54:19Z

It doesn't work for me

Delete the ZBMINI devices that we do not have properly configured in HA. In my case, two of them had been able to link them for a long time, but another five that I had bought could NOT link them and I had them registered in Phoscon, HA and deconz, but they only worked well in deconz.

Where should delete ZBMINI?

Restart Phoscon. What is done from the menu -> Supervisor -> Phoscon -> RESTART

If I don't have supervisor should I restart Deconz container?

marithpl · 2021-03-01T17:36:16Z

What is the best way to update Docker version of Deconz?
When I update an image all my sensor gone, I see only a hex names like this:

spiff42 · 2021-03-01T21:33:37Z

I am running deconz in docker, updated to marthoc/deconz:latest, and I can confirm that it works with the remaining zbmini that did not work before. The two that I had already gotten to work are still working. I am still a bit confused regarding why it was possible to get the two others configured and working before this update (they worked across restarts of deconz, etc.), but I guess it does not matter much now that they all work. Good job!

ghost · 2021-03-01T21:47:06Z

It just updated the docker marthoc as well. And yes, all mine zbmini’s work fine now!!! Great work! Thanks for the help! I am a happy topicstarter now! Rick Verstuurd vanaf mijn iPhone

…

Op 1 mrt. 2021 om 22:33 heeft Mikkel Holm Olsen ***@***.***> het volgende geschreven: I am running deconz in docker, updated to marthoc/deconz:latest, and I can confirm that it works with the remaining zbmini that did not work before. The two that I had already gotten to work are still working. I am still a bit confused regarding why it was possible to get the two others configured and working before this update (they worked across restarts of deconz, etc.), but I guess it does not matter much now that they all work. Good job! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

SwoopX · 2021-03-01T22:41:49Z

I guess this is confirmation enough and we see more happy people now 😄 Closing this one as resolved. Enjoy!

gang-himself · 2021-03-06T15:47:30Z

not solved in my case... use HA on a raspberry pi 4 with

HA
core-2021.3.1

deCONZ
Current version: 6.7.2

The HA-Addon is still on an older Deconz-Version without the bugfix

cylonr · 2021-03-07T07:59:25Z

I´am having the same ptoblem!
5 Sonoff Zigbee Mini not working

Versão | core-2021.3.2
Versão do Sistema Operativo | 5.7.9-arm-64
Sistema operativo anfitrião | Armbian 20.07 Buster
Versão do Supervisor | supervisor-2021.03.4
deCONZ (6.7.2)

Mimiix · 2021-03-08T10:42:36Z

@cylonr As @gang-himself mentioned: The HA Addon doesn't have this fix yet.

Mimiix · 2021-03-08T10:42:57Z

@SwoopX You stole my pride here :(

Metaleon · 2021-03-12T19:32:26Z

Hi everyone, I also still have the problem with deConz version 2.09.03 in HA.
Who should I contact to request the update?
Thank you

Mimiix · 2021-03-12T19:34:28Z

@Metaleon the people who maintain the ha addon.

gang-himself · 2021-03-12T20:33:50Z

@Metaleon the people who maintain the ha addon.

I tried that on the HA-Addon Discord-Channel but I wasn‘t heard. And unfortunately it looks like I‘m to newbie to github to manage to do a PR... 😢

ads1230 · 2021-03-12T20:42:21Z

@Metaleon the people who maintain the ha addon.

I tried that on the HA-Addon Discord-Channel but I wasn‘t heard. And unfortunately it looks like I‘m to newbie to github to manage to do a PR... 😢

Swap to the Marthoc Docker image.
Enable "Advance Mode"
Install Portainer in the Add-ons store and then create a new container using the following:
`
image: marthoc/deconz

container_name: deconz

network_mode: host

restart: always

volumes:
  - /opt/deconz:/root/.local/share/dresden-elektronik/deCONZ

devices:
  - /dev/ttyUSB0

environment:
  - DECONZ_WEB_PORT=80
  - DECONZ_WS_PORT=443
  - DEBUG_INFO=1
  - DEBUG_APS=0
  - DEBUG_ZCL=0
  - DEBUG_ZDP=0
  - DEBUG_OTAU=0

`

gang-himself · 2021-03-25T07:54:11Z

Now the HA-Addon is on 2.10.03.
Thx for all the work!

lambu76 · 2021-03-25T11:59:53Z

confirmed also from my side.

Add v. 6.8.0

ghost · 2021-11-22T21:12:57Z

Good evening, I have a question concerning Sonoff ZBMini. It’s connected via Conbee II to phoscon/DeConz headless at its latest version and firmware. I can pair the device but after a few hours it isn’t reachable anymore — the connection gets lost, device is greyed out. If I click on „search for new lights“, the device comes back to life. This happens two or three times a day. In the near there are some Osram Smart Plugs which act as repeater. The stick itself is about 7 meters away. Linux is Debian Buster on an intel Nuc. Conbee II is connected via USB2. All other devices are reachable and acting as normal. Can someone help? Many thanks 🙏🏼

LeoeLeoeL · 2021-11-22T21:40:15Z

I reported this issue too.
No solution.
You have 2 choices:

Use ZBMini 1.0 with HUE bridge;
Swap your ZBMini 1.0 with newer 2.0; They don't suffer this problem with Conbee II.
If you think to update the firmware.... you cannot. I bought the Sonoff bridge for that but this feature is not provided.

ghost · 2021-11-23T05:38:04Z

I reported this issue too.

No solution.

You have 2 choices:

Use ZBMini 1.0 with HUE bridge;

Swap your ZBMini 1.0 with newer 2.0; They don't suffer this problem with Conbee II.

If you think to update the firmware.... you cannot. I bought the Sonoff bridge for that but this feature is not provided.

Thanks! How do I identify V2?

gang-himself · 2021-11-23T06:46:46Z

I had these problems too, but since the Conbee II Firmware-Update to 26700700 they seem to be gone.

In my case it helped also to bring back the devices alive to simply switch the local switch on the zbmini (of course only if there is one connected). But some hours later they were offline again.

ghost · 2021-11-23T07:14:02Z

Is there a possibility to trigger "search new lights" via API or shell command? That could be a temporary solution.

LeoeLeoeL · 2021-11-23T10:48:16Z

No way to identify V2 by the orange box or the chassis.
I discovered the difference in Phoscon.
1.0 is

2.0 is

ghost · 2021-11-23T10:56:00Z

No way to identify V2 by the orange box or the chassis.

I discovered the difference in Phoscon.

1.0 is

2.0 is

So then I already habe version 2 - with the above described issues.

LeoeLeoeL · 2021-11-23T10:59:30Z

I never had disconnections (device in pairing state) with 2.0.0

matteos1 · 2021-12-05T15:19:45Z

in deCONZ 2.12.6 with 2 sonoff mini 2.0 there is still the same problem

LeoeLeoeL · 2021-12-05T15:29:30Z

Happy to have the issue with 1.0 only.

Dragger81 · 2021-12-21T12:03:19Z

Hi,
have the problem with the status.
Pairing is ok, but when you switch the state in phoscon it is shown off but still on. Every third click it goes on and 1sec later automaticly off.

This only happens with ZBmini Version 2:
Hersteller: SONOFF
Modell: 01MINIZB
Version: 2.0.0

I have also an old one:
Hersteller: Heiman
Modell: 01MINIZB
Version: 20200927
working since 1 year fine with no roblems

System:
deconz 26720700 running on raspi3B/Buster and conbee stick II 2.07.01/19.9.2021 on USB2.
12 Xiaomi Aqara Sensors running with no problems
3 Opple switch working also great
4 Osram smartplugs also no problems

Some new ideas how to fix?
THX Chris

Dragger81 · 2021-12-21T12:11:23Z

Hi, have the problem with the status. Pairing is ok, but when you switch the state in phoscon it is shown off but still on. Every third click it goes on and 1sec later automaticly off.

This only happens with ZBmini Version 2: Hersteller: SONOFF Modell: 01MINIZB Version: 2.0.0

I have also an old one: Hersteller: Heiman Modell: 01MINIZB Version: 20200927 working since 1 year fine with no roblems

System: deconz 26720700 running on raspi3B/Buster and conbee stick II 2.07.01/19.9.2021 on USB2. 12 Xiaomi Aqara Sensors running with no problems 3 Opple switch working also great 4 Osram smartplugs also no problems

Some new ideas how to fix? THX Chris

.... OK my fault, the phoscon update was not correctly installed. After updating again to version 2.13.04 statusrequest are correct

ghost added the Bug report label Dec 24, 2020

SwoopX closed this as completed Mar 1, 2021

mamrai1 mentioned this issue Mar 8, 2021

PTVO Switch Relay 4/8 #3324

Closed

gang-himself mentioned this issue Mar 17, 2021

Update Deconz to 2.10.01 - Fix for Sonoff zbMini home-assistant/addons#1926

Closed

Mimiix mentioned this issue Mar 23, 2021

SONOFF 01MINIZB goes in pairing mode alone #4564

Closed

General ZBMini issue. #4016

General ZBMini issue. #4016

Comments

ghost commented Dec 24, 2020 • edited by ghost Loading

Describe the bug

Steps to reproduce the behavior

Expected behavior

Screenshots

Environment

deCONZ Logs

Additional context

ghost commented Dec 24, 2020 • edited by ghost Loading

SwoopX commented Dec 24, 2020 • edited Loading

thundergreen commented Dec 26, 2020

manup commented Dec 27, 2020

KodeCR commented Dec 27, 2020

ghost commented Dec 27, 2020

eklex commented Dec 28, 2020

raddi commented Dec 28, 2020

ghost commented Dec 28, 2020

manup commented Dec 30, 2020

commonslibs commented Jan 1, 2021 • edited Loading

ads1230 commented Jan 5, 2021 • edited Loading

commonslibs commented Jan 5, 2021

andrejem commented Jan 5, 2021

commonslibs commented Jan 5, 2021 • edited Loading

thundergreen commented Jan 6, 2021 via email

jonnycastaway commented Jan 9, 2021

retoziegler commented Jan 13, 2021 • edited Loading

Whatsek commented Jan 17, 2021

jmpaiva commented Jan 17, 2021

Whatsek commented Jan 17, 2021

jmpaiva commented Jan 17, 2021

ads1230 commented Jan 17, 2021 • edited Loading

jmpaiva commented Jan 17, 2021 • edited Loading

spiff42 commented Jan 22, 2021 • edited Loading

commonslibs commented Jan 22, 2021

marithpl commented Jan 23, 2021 • edited Loading

commonslibs commented Jan 24, 2021

marithpl commented Jan 24, 2021 • edited Loading

marithpl commented Mar 1, 2021

spiff42 commented Mar 1, 2021

ghost commented Mar 1, 2021 via email

SwoopX commented Mar 1, 2021

gang-himself commented Mar 6, 2021

cylonr commented Mar 7, 2021

Mimiix commented Mar 8, 2021

Mimiix commented Mar 8, 2021

Metaleon commented Mar 12, 2021

Mimiix commented Mar 12, 2021

gang-himself commented Mar 12, 2021

ads1230 commented Mar 12, 2021 • edited Loading

gang-himself commented Mar 25, 2021

lambu76 commented Mar 25, 2021

ghost commented Nov 22, 2021

LeoeLeoeL commented Nov 22, 2021

ghost commented Nov 23, 2021

gang-himself commented Nov 23, 2021

ghost commented Nov 23, 2021

LeoeLeoeL commented Nov 23, 2021

ghost commented Nov 23, 2021

LeoeLeoeL commented Nov 23, 2021

matteos1 commented Dec 5, 2021

LeoeLeoeL commented Dec 5, 2021

Dragger81 commented Dec 21, 2021

Dragger81 commented Dec 21, 2021

ghost commented Dec 24, 2020 •

edited by ghost

Loading

ghost commented Dec 24, 2020 •

edited by ghost

Loading

SwoopX commented Dec 24, 2020 •

edited

Loading

commonslibs commented Jan 1, 2021 •

edited

Loading

ads1230 commented Jan 5, 2021 •

edited

Loading

commonslibs commented Jan 5, 2021 •

edited

Loading

retoziegler commented Jan 13, 2021 •

edited

Loading

ads1230 commented Jan 17, 2021 •

edited

Loading

jmpaiva commented Jan 17, 2021 •

edited

Loading

spiff42 commented Jan 22, 2021 •

edited

Loading

marithpl commented Jan 23, 2021 •

edited

Loading

marithpl commented Jan 24, 2021 •

edited

Loading

ads1230 commented Mar 12, 2021 •

edited

Loading