How many devices can connect to zigate? The maximum amount of devices. Verstuurd vanaf mijn LM-V405 met Tapatalk This has nothing to do with the plugin. The limitation is on the hardware itself. https://zigate.fr/2019/02/11/maj-firmware-zigate-version-3-0f/ 70 devices in total where 40 in direct ...

The hue remote is seen by the plugin and a separate device is created. So for Hue it could work. But anyway, this would not be the best solution but could be a workaround. This is ok, but the plugin doesn't have the relationship between the hue remote and the bulb ? The Configure Reporting did not ...

From my understanding the Tradfri remote events are not seen by the plugin, so your idea will not work.
So I think this is really the Configure Reporting which should work. And which work at home with Tradfri and Aqara Bulb. May be some specific on the Philips Hue which need to be tuned in the plugin

@ronaldbro you might do a git pull before, as there is a patch provided for the Configure Reporting

According to the zigate docs there should also be a tripple click and 4 click, but that doesn't work. I think the device doesn't support this.

What do you mean According to the Zigate docs ?

Thanks for such detailed Logs. Here after is what I have been able to identify. In short: 4 clicks and 3 clicks do not report anything. At least the Hardware Zigate doesn't send anything to the plugin. Long press - is reported to domoticz with Level 20 (should be 3 Click) 2 Click - is reported to ...

As said, if you could post the log when you are pressing once, twice, long press ...., this would be more helpfull.

I also tried enabling groups and then I get a new group device. But also the group device is not updated when I use the remote dimmer. As the group is updated based on the information from the Bulb, I think that is expected that you don't get it updated ... I think there is maybe a parameter which ...

Is the device on Domoticz correctly created ? Means you have a Switch selector with Click 1, 2, 3 and 4 ? ==> If that is the case, the creation is correctly done, and the patch you did work. ==> If that is not the case, this mean , something is wrong in the device creation and so the patch is not ...

From your last log, there is indeed a effect-cause which is when the value is updated to On, then you get immediatly a onCOmmand to switch it off. Domoticz scripts are under scripts folder (and you can also have Blocky scripts from domoticz Web interface) As regards to to timer .. this is directly ...

I believe you can add the line. Or may be better is to replace your existing one, by the recommended patch . https://raw.githubusercontent.com/sasu-drooz/Domoticz-Zigate/7958653fe7bcdf85cde223cfb649d2ad96a741df/Conf/DeviceConf.txt It might be good to do some backup before in case it breaks something

I'm afraid that onCommand are coming from Domoticz

Check; https://github.com/sasu-drooz/Domoticz-Zigate/pull/389

Yep, I tried about 20 times and stil in pairing mode. Log is the same every time: 2019-03-28 23:49:34.367 Status: (Zigate) Leave indication from IEEE: 00158d00021311e6 , Status: 00 2019-03-28 23:49:35.837 Status: (Zigate) Device Annoucement ShortAddr: 6c2c, IEEE: 00158d00021311e6 2019-03-28 23:49 ...

DId you tried several time ? Was the zigate still in pairing mode ?

From your log I have extracted the following: Don't know, what is Delaying switch . This doesn't sound as a plugin message 2019-03-16 09:52:57.964 Delaying switch [zigate1 - Plug 4 -84182600000c7707-03] action (On) for 2 seconds Here is the switch on , you have done it. 2019-03-16 09:52:57.963 ...