FoH dimming problem

Hey everyone,

I’ve searched the Internet and this forum, but can’t find a solution for my problem.

I have some Friends of Hue switches from Senic. I guess with the same ZGP device as all the other FoH switches.
The pairing works flawless and switching lights on and off is also no part of the problem.
Just longpress will not be recocnized properly.
It worked in really really rare cases.

My setup:
Deconz: 2.26.2 (Docker)
Conbee III: 26500900
Raspberry Pi 5

I also mentioned that the Conbee III has in deconz the identifer Conbee II.

Here is a capture from trying to get a longpress.
It seems like it ist not recocnized bei the Conbee.

Ist this normal, because i can’t find any similar problems. Is this maybe different in a Docker emvironment?

Thanks in advance.

{
    "19:17:34:691": {
        "attr": {
            "id": "7",
            "lastannounced": null,
            "lastseen": "2024-03-25T18:17Z",
            "manufacturername": "PhilipsFoH",
            "mode": 0,
            "modelid": "FOHSWITCH",
            "name": "Küche Eingang",
            "swversion": "1.0",
            "type": "ZGPSwitch",
            "uniqueid": "00:00:00:00:01:71:e7:5c-f2"
        },
        "e": "changed",
        "id": "7",
        "r": "sensors",
        "t": "event",
        "uniqueid": "00:00:00:00:01:71:e7:5c-f2"
    },
    "19:17:34:698": {
        "e": "changed",
        "id": "7",
        "r": "sensors",
        "state": {
            "buttonevent": 1000,
            "lastupdated": "2024-03-25T18:17:35.556"
        },
        "t": "event",
        "uniqueid": "00:00:00:00:01:71:e7:5c-f2"
    },
    "19:17:34:879": {
        "e": "changed",
        "id": "7",
        "r": "sensors",
        "state": {
            "buttonevent": 1002,
            "lastupdated": "2024-03-25T18:17:35.758"
        },
        "t": "event",
        "uniqueid": "00:00:00:00:01:71:e7:5c-f2"
    },
    "19:17:37:406": {
        "e": "changed",
        "id": "7",
        "r": "sensors",
        "state": {
            "buttonevent": 2000,
            "lastupdated": "2024-03-25T18:17:38.286"
        },
        "t": "event",
        "uniqueid": "00:00:00:00:01:71:e7:5c-f2"
    },
    "19:17:40:221": {
        "e": "changed",
        "id": "7",
        "r": "sensors",
        "state": {
            "buttonevent": 2003,
            "lastupdated": "2024-03-25T18:17:41.050"
        },
        "t": "event",
        "uniqueid": "00:00:00:00:01:71:e7:5c-f2"
    },
    "19:17:40:944": {
        "e": "changed",
        "id": "7",
        "r": "sensors",
        "state": {
            "buttonevent": 2000,
            "lastupdated": "2024-03-25T18:17:41.827"
        },
        "t": "event",
        "uniqueid": "00:00:00:00:01:71:e7:5c-f2"
    },
    "19:17:43:710": {
        "e": "changed",
        "id": "7",
        "r": "sensors",
        "state": {
            "buttonevent": 2003,
            "lastupdated": "2024-03-25T18:17:44.486"
        },
        "t": "event",
        "uniqueid": "00:00:00:00:01:71:e7:5c-f2"
    },
    "19:17:44:726": {
        "e": "changed",
        "id": "7",
        "r": "sensors",
        "state": {
            "buttonevent": 1000,
            "lastupdated": "2024-03-25T18:17:45.536"
        },
        "t": "event",
        "uniqueid": "00:00:00:00:01:71:e7:5c-f2"
    },
    "19:17:47:762": {
        "e": "changed",
        "id": "7",
        "r": "sensors",
        "state": {
            "buttonevent": 1003,
            "lastupdated": "2024-03-25T18:17:48.637"
        },
        "t": "event",
        "uniqueid": "00:00:00:00:01:71:e7:5c-f2"
    },
    "19:17:48:517": {
        "e": "changed",
        "id": "7",
        "r": "sensors",
        "state": {
            "buttonevent": 2000,
            "lastupdated": "2024-03-25T18:17:49.331"
        },
        "t": "event",
        "uniqueid": "00:00:00:00:01:71:e7:5c-f2"
    },
    "19:17:50:560": {
        "e": "changed",
        "id": "7",
        "r": "sensors",
        "state": {
            "buttonevent": 2003,
            "lastupdated": "2024-03-25T18:17:51.354"
        },
        "t": "event",
        "uniqueid": "00:00:00:00:01:71:e7:5c-f2"
    },
    "19:17:51:900": {
        "e": "changed",
        "id": "7",
        "r": "sensors",
        "state": {
            "buttonevent": 2000,
            "lastupdated": "2024-03-25T18:17:52.737"
        },
        "t": "event",
        "uniqueid": "00:00:00:00:01:71:e7:5c-f2"
    },
    "19:17:52:22": {
        "e": "changed",
        "id": "7",
        "r": "sensors",
        "state": {
            "buttonevent": 2002,
            "lastupdated": "2024-03-25T18:17:52.905"
        },
        "t": "event",
        "uniqueid": "00:00:00:00:01:71:e7:5c-f2"
    }
}

Hello from here Supported Devices · dresden-elektronik/deconz-rest-plugin Wiki · GitHub

The event 2003 is the release after long press for the button 2. So you have it on your log.

I thought there has to be another value like 2001 for longpress start and 2003 stands for longpress end.
Dimming did not work with 2003.
So there is somewhere a problem with the xx01 values.
It does simply nothing and after release I got 2003.
On and Off with shortpress is correct.
New pairing or programming the actions did also Not work for me.

Ha ok, so you are using “bind” between your switch and a light ? You are not using automation ?
You are using phoscon ?

You have device without battery ? So not possible having a “hold” action, XX01 .

I use phoscon with the light mapped to the Switch.
Sometimes (really rare) a xx01 is submitted an then it works and yes these ZGP devices are without battery.
That is what ist confusing me.

Ha ok so, sorry, I don’t know ho work the “zigbee mapping”, on my side I use direclty API return.
Not the same working mode.

But physically, thoses device use the energy you make when pressing it, to power the device, and can use a “resilience” (not sure for the name, I have bad english) to do same when you release it.
So I don’t see how they can manage long press.

It’s probalby possible using software (with a timer), but the one I have don’t have it.

If someone know if it exist some ZGP switch supporting long press ?

Hmm ok I thought that nobody else had this problem, because it works sometimes.
I thought that it worked time ago before I migrated to Docker, but can’t go back to reproduce.
The original hue bridge can handle this stuff too.
I hope anyone can tel if he or she has the same problem or a working solution.
The Switches are also supported without any marks of restriction.

Hello again,
has anyone an idea for a working solution or is it possible to get a statement if this is the correct behavior or not?
I can’t believe that this is normal because these switches are in the compatbility list.
Thanks in advance.

Could please someone check in to clarify if this is a bug or am I alone with this problems?
Is it possible to get an answer from phoscon here?
Thanks for anyone who can help.

@de_employees

Tagged them but seems your alone.

1 Like

Thank you.
I guess if I am alone it is possibly the Docker version or the switches are not fully compatible.

There’s no difference between docker and other installs :slight_smile:

But have you already see a Green power switch that detect the long press ?
Here another model from Z2M EnOcean PTM 215ZE control via MQTT | Zigbee2MQTT no long press too.

For me all is fine.

Ah OK thanks, so the truth is that the switches are not 100% compatible? Really bad that this information is only at a competitors Page :frowning:
Would be cool if there were a statement from the phoscon employees.
If it is what it is I would look for another solution, but if there is another way around or update that would be great.

No for me, it’s just this kind of device don’t support long press because it’s not possible physicaly.
I can be wrong, but in this situation show me a post or other thing with this kind a device supporting the long press.

And Z2M are saying same, I don’t understand what you are calling “100% compatible” but there is no long press and it’s normal.

It works in really rare situations and the Hue Bridge can handle this. So the Advertisement for these switches ist also with longpress (for Hue Bridge I know).
Maybe it is just only my opinion, but if there is like 5 possible functions and 1 is not compatible that is not 100% compatible, it is 80% and that ist worth a note.
I am also just a not very technically user and always think of “why is this not working, it works on other systems”.
I guess I sound sometimes rude and I am sorry for that and my english. That is not what I want and I appreciate the help here.

1 Like

You are sure of that ? Because deconz is able to handle long press request too, but only if the device is able to do it.

So the Advertisement for these switches ist also with longpress

It mean nothing, the process can just use a timer.

why is this not working, it works on other systems”.

Have searched again, and I haven’t found a device able to generate them.
On another one we can read

It is therefore possible to distinguish between radio telegrams sent when the energy bar was pushed and radio telegrams sent when the energy bar was released.
By identifying these different telegrams types and measuring the time between pushing and releasing of the energy bar, it is possible to distinguish between “Long” and “Short” push button presses. This enables simple implementation of applications such as dimming control or blinds control including slat action.

It is feature set included in Zigbee 3.0 and it enables battery-less devices to communicate, by using the energy harvested by pressing buttons.
I think this is why there are no “hold” actions sent; because no energy can be harvested by simply holding a button.
This can only be done by pressing a button.
A device with a battery can use Zigbee Green Power to achieve lower battery consumption, but sacrifices bi-directional communication (beware of exceptions).

Hmm ok I guess it is time to take it as it is.
Thanks for your kindness, patience and help here.
I will change my setup than to the wall switch module.