Phoscon Switch Editor: Aqara Opple “Choose action” dialog empty (existing rules work, cannot edit or add new actions)

Phoscon App Bug reports
1

:placard: Phoscon Switch Editor: Aqara Opple “Choose action” dialog empty (existing rules work, cannot edit or add new actions)

:green_circle: TL;DR

I recently wanted to add a new light to one of my Aqara Opple switches and found out that the button assignment in the Phoscon web app does not work anymore for these switches. I then started to debug that with the help of ChatGPT. I managed to add rules for the new light via the API but it still does not work via the app. I created this summary also with help of ChatGPT and hope that someone can pick this up. Happy to help and test, of course!

My Aqara Opple 6-button switches (lumi.remote.b686opcn01) still function via their old deCONZ rules,
but the Phoscon Switch Editor no longer shows any available actions when editing or adding mappings.
The “Choose action” dialog is completely empty.
This problem started long after the initial pairing (which worked fine) and persists even after upgrading to deCONZ 2.32.0 / firmware 26780700.

:toolbox: Environment

  • Phoscon App / deCONZ: 2.32.0 (Docker)
  • Firmware (RaspBee): 26780700
  • Hardware: RaspBee on Raspberry Pi 3
  • Browser: Safari and Chrome (same behavior)

:puzzle_piece: Summary

The Switch Editor in Phoscon no longer offers any actions for my Aqara Opple 6-button switches.
When selecting a button, the “Choose action” dialog opens but remains completely empty — no Toggle / On / Off / Dim options appear.

The switches themselves still work, because their previous rules remain active inside deCONZ,
but those rules are invisible and uneditable in the Phoscon web UI.

:ladder: Steps to Reproduce

  1. Have an existing Aqara Opple switch configured and working (mine were added about two years ago and worked fine initially).
  2. Open Phoscon → Switch Editor → select switch.
  3. Click any button → “Choose action” dialog opens empty.
  4. The switch still triggers its old lights/groups, but no new actions can be assigned.

:light_bulb: Expected Behavior

Phoscon should:

  • Display the available actions (Toggle, On, Off, Dim Up/Down, etc.)
  • Allow editing or adding new button mappings

:cross_mark: Actual Behavior

  • The “Choose action” dialog is blank.
  • Old rules continue to run (verified via /api/rules).
  • The Phoscon UI cannot modify or remove them.
  • Upgrading to deCONZ 2.32.0 / firmware 26780700 did not fix the issue.

:detective: Additional Notes

  • The problem did not appear after upgrading — it likely started with an older Phoscon version sometime after initial pairing.
  • Other remotes (e.g. IKEA TRÅDFRI) still show and edit actions normally.
  • The REST API shows that Opple switches no longer expose config.group or config.groups fields —
    this might be why the Switch Editor cannot render their available actions.
  • Reproducible on multiple browsers and systems.

:brain: Hypothesis

Phoscon’s Switch Editor likely depends on group metadata to populate the action list.
When the Opple’s ZHASwitch entries no longer contain these fields (but deCONZ rules still exist),
the UI silently fails and displays an empty dialog — even though the backend logic continues to work.

:receipt: Diagnostics

  • I can provide anonymized JSON excerpts from:
    • /api/sensors/<OppleID>
    • /api/rules
  • Confirmed that button events (x001, x002, etc.) still fire correctly in Home Assistant.
  • deCONZ logs confirm valid Zigbee traffic.

:speech_balloon: Question

Is this a known regression or limitation in the Phoscon App regarding Aqara Opple switches?
I’m happy to help by testing or providing logs and data from my setup if needed.

:white_check_mark: Let me know if screenshots or JSON snippets from the REST API would help reproduce this issue.

Thanks for your continuous support and work, I’ve been using deconz and Phoscon for many years and still happy especially with the variety of brands and devices it supports!