Where are my switches?

General
1

Hi all,
I use a Conbee II in combination with ioBroker and DeConz adapter. All my switches and sensors have been adopted with Phoscon. No problems at all. Just now I got two new problems:

  1. An IKEA SYMFONISK volume remote needed a new battery. Didn’t work instantly, so I deleted the object in ioBroker and restarted the DeConz instance. Usally it is imported to ioBroker objects. Not this time.
  2. I bought two new IKEA switches (Symfonisk Volume Remote Gen. 2 and a RODRET dimmer). Both are compatible in the DeConz list. After easy adoption in Phoscon (they react in Phoscon when I push a button) they will not show up in ioBroker DeConz objects after restarting DeConz instance.

My versions I use:
Gateway: 2.26.3
Firmware Conbee II: 26660700

Any idea? In case you reply please write it easy understandable…I’m no programmer :wink:
Thanks.

2

Hello are they in the API ?
You can check using phoscon/help/API Information.

Generaly third app make a “get all device” request at start to fill/update their database, have you tried to restart ioBroker ?

1 Like
3

Hi Smanar,
yes, they are in the API and “reachable=true”.
And yes, I stopped ioBroker, executed ‘iob fix’ and started again two times now.
Problem unfortunately not solved.
deCONZ Adapter is latest stable version 1.6.4.

4

Strange, can you share for exemple the JSON for one device from the API (still using phoscon/help/API Information)

Sometime third app can “refuse” an entry if it look not fine for them, but for me the problem is more from ioBroker, there isn’t log on their side ?

5

This is my new Gen 2 IKEA Symfonisk Sound Remote. I newly adopted it in Phoscon and it is absolutely responsive when I check the API events when pressing buttons. Therefore I agree that the problem does not seem to be located in the remote, Conbee II stick or Phoscon. It looks like the deCONZ Adapter is the problem. It appears to happen for an old volume control I just changed battery…same like above described.

One solution could be to delete the deCONZ adapter but then I lose all attached sensors and switches, rigtht? Not good :weary:

Screenshot 2025-03-19 191744
Screenshot 2025-03-19 191744434×517 10.2 KB

6

I don’t see something bad in the json, for me all is perfect.

On this page GitHub - Jey-Cee/ioBroker.deconz: Connects to deConz software developed by dresden-elektronik. This software aims to be a universal ZigBee Gateway solution, using hardware from dresden-elektronik the ConBee USB stick and RaspBee a modul for the Raspberry Pi. we can see

To avoid some errors after an update (deConz/adapter), stop the adapter and delete these entries in the object structure. When you start, the object structure is recreated.

On my third app, at every load all is erased and recreated, no database saved, but if I remove the plugin, I loose all the stuff made on the application, all history and ect …

Can try to ask on their github, you haven’t a setting to “block new device” in ioBroker ?

1 Like
7

I am not aware of having a setting to block new devices. Up to now it has always worked. After pairing the devices in Phoscon I could see them in the deCONZ instance as object with all available data points.
I struggle a little bit with deleting and repopulating all deCONZ objects by first deleting them. Most likely they will have new ids and I would need to change all my skripts. That would really be the last step to try :wink:

8

On my side, they have new ID if I delete them in third app.
On deconz all is invisible, you just need to NOT delete it, just re-include, the json is updated, not replaced/recreated.

9

Sorry, don’t know how to “re-include” and where? In Phoscon or in deCONZ Adapter in ioBroker? The deCONZ Adapter just has a few settings like IP, port, and API.

10

Using phoscon, just use “add new light” and make the reset procedure and the device (without deleting the device first).
Nothing will change in the API, same id, same name, ect … So third app don’t see the change.