I am quite new to this so forgive my ignorance. I have installed some dimmer switches for my downlights, but when I add them to Phoscon they just show up as a light, not a switch. I guess they should be both? They work fine as a light, but I would like to use them as a switch and connect several other lights to also be controlled by them. Am I doing something wrong or does Phoscon need some update?
These are the 2 switch types I have installed:
You need to fire up the Deconz GUI and provide the clusters exposed by the device.
Unsure if a device can be both a light and a switch …
Also I can not find a DDF for 1402769 in the repository, so the first step to make one is have a look at those exposed clusters.
Thanks for the reply. It is a hardwired dimmer switch that controls the wired lights, but I would also like to use it to turn on some random bulbs around the house. Having it as both a light with on/off and a switch would give full flexibility I guess, but if that is not possible then I guess it should be a switch? How are other hardwired dimmers/switches in Phoscon/deconz?
Deconz is very confusing to me, but maybe I have to learn to use it. Is this what you want to see?
Select the basic cluster and do a Read in the cluster info tab bottom left.
As suspected, there is no DDF…
Hi, from the screenshot you provided, I can conclude that this device does not have an OnOff/LevelControl client. It only has these clusters as a server (which is why the cluster numbers are blue). Servers accept commands, while clients emit commands.
This means the device cannot send control commands to other Zigbee devices but can likely only control itself.
Thanks for that clarification. And the clusters available does not change by providing a DDF?
So then it is correct that it is set as a light in Phoscon. So to control these wired lights and other lights I have to use another switch. I was hoping to get rid of my wireless IKEA switches 
Is it possible to solve this in Phoscon using automation? “If the wired lights turn on, then also turn these other lights on”. It seems that only motion sensors can be used? I guess it should be possible for me to solve that in Home Assistant, but I would prefer to solve it in Phoscon so I am not reliant on HA.
No, a DDF will not solve this, as this is a missing capability of the device itself.
I primarily work on embedded firmware, but I asked about this in our internal chat. The developers mentioned that you can use rules to turn on other lamps when the state of a lamp changes. However, you will need to use the REST API for that, as there is currently no GUI available.
Deconz REST API Documentation – Rules
{
"actions": [
{
"address": "/groups/0/action",
"body": {
"on": true
},
"method": "PUT"
}
],
"conditions": [
{
"address": "/lights/1/state/on",
"operator": "eq",
"value": "true"
},
{
"address": "/lights/1/state/on",
"operator": "dx"
}
],
"name": "Light 1 On/Off"
}
You could also try Home Assistant (with ZHA), as the ConBee is supported out of the box, and they provide an automation wizard for this.
Best regards,
Eric
(which is why the cluster numbers are blue).
Didn’t know that color coding …
So these are the Input clusters found in the user manual.
Had there been any Output clusters, what color would they had been?
I also checked 2 Sunricher Rotary dimmers, and they had the exact same clusters, probably because Namron is a rebranded Sunricher.
Do rotary dimmers from any other vendors support light/switch functionality?
The automation path works fine (I use openHab), but not when the hub is down.
Thanks for the idea. I got it working by setting a rule with the API as you showed. However, it is very slow to react. After I press the switch the wired lights turn on right away of course, but the rule takes 20-30 seconds to turn on the other lights. If I use Phoscon to connect them both to a wireless switch they react right away.
Is there anyway to make the rule I set up react faster? It seems to be the “on” state of the light that takes a long time to update.
Input clusters are blue.
Ouput clusters are grey.
Generaly wired switches are routers, and have only input clusters, so can only receive order > light
Battery switches are end device, have ouput cluster, can only send order > sensor
Thanks for the info …
Curious, why is OTAU an output cluster?
Lol good question, perhaps with taking a look in “zigbee rules”
The OTAU has the classical client-server architecture. Both a client and a server shall support the OTAU
cluster, but in different modes: an OTAU client shall register the OTAU cluster as an output cluster, while a
server shall support an input OTAU cluster to be able to process incoming requests. The network may contain
multiple servers, although typically there is only one OTAU server in the network. A server can be either a
common in-network device with OTAU cluster support or a device temporally added to the network, which in
the reference implementation is a Runner device
And blablabla (very long story)
And if you look at the corrdinator cluster, you will found this cluster as Input.
