Changing from CC2531 to ZiGate

[glory50]

Hi,

Is it necessary for replacing CC2531 with a ZiGate+ v2 USB to repair all divices or is it possible to use the old database/conf file?

Is there any problem with this new release of ZiGate?

Thanks in advance!

[pipiche]

Are you with CC2531 with the zigbee for DomoticZ plugin or are you with an other plugin ?

[glory50]

This is a zigbee plugin from China with modified FW.

[pipiche]

I was not aware that there is zigbee plugin from china working with Domoticz.

[glory50]

Yes, and it works very well! But it seems, that with ZLinky_TIC it doesn't. But I'm not very sure yet.

[pipiche]

Can you do a screenshoot of the Hardware menu where we see the plugin ?

[glory50]

There is nothing to shot. From the Linux dmesg I can paste:

Code: Select all

[    2.433508] kernel: usb 1-3: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[    2.433514] kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.433518] kernel: usb 1-3: Product: TI CC2531 USB CDC
[    2.433521] kernel: usb 1-3: Manufacturer: Texas Instruments
[    2.433524] kernel: usb 1-3: SerialNumber: __0X00124B0014B9378F

Bought from Aliexpress:



(Don't know why Imgur's image doesn't display here) The data about the plug:
CC2531 CC2540 Zigbee Sniffer Carte Sans Fil Bluetooth BLE 4.0 Dongle Module de Capture USB Programmeur
3.77€ w. free shipping
You can view it here: https://imgur.com/a/bW8RkDp

And on Domoticz HW, there are:

MQTT Client Gateway with LAN interface
Zigbee2MQTT

That's all.

[pipiche]

SO that was my question which plugin you are using ? and you are using Zigbee2MQTT in such I do not see any smooth transition from that to the ZigbeeforDomoticz plugin that you'll need for Zigate.

So unfortunately, you will have to repair all devices and it will create new Widgets on Domoticz. But you won't have a broker in between and that will ease the setup

If you had been already on Zigbee4Domoticz (as it supports now CCxxxx coordinator), this would have been an other story

[glory50]

Thank you very much, pipiche! Je vais t'offrir une bier ou un café, selon ta préférence.

[glory50]

Hi pipiche!

I changed to Zigate and almost everything works by now very well. Only thing is a Pihilips Hue White ZB bulb, that I cannot set in the pairing mode. But it's not a problem - only one single bulb, the others from Lidl or Lexman work perfectly.

But there is something I don't understand. I have very many motion sensors from Sonoff, SNZB-03, that worked well with CC2532 and Z2M. As everybody knows, they have a problem, tha is explained from the producer:

"Due to power consumption and power-saving considerations, there have some restrictions on the trigger
That is: when SNZB-03 detects the movement, it will send a signal to ZBBridge
If the device does not detect any movement for one minute, once the device triggered, it will send a signal to ZBBridge
If any movement is detected within one minute, the device will not send a trigger to ZBBridge. And effective detection and trigger signals to ZBBridge will be delayed for one minute. It means the motion sensor works with one-minute intervals."

https://github.com/Koenkk/zigbee2mqtt/issues/4874

So, to avoid the 1 minute period of non movement in the toilet, I created a script, that dims a light in 30 secs, then flashes the light several times, to remeber the toilet user to move his body a little. With CC2532 and Z2M it worked very well, because Z2M passes throgh all the messages it receives from a ZB device.

Now, with ZiGate, the script turns on the light, but the movement does not reactivate the counter in the sensor. So the toilet user stays in the dark bacause the sensor doesn't activate before there will be 60s after the last movement.

Is there any way to get over the issue or does the zigate plugin need to be updated?

[pipiche]

Let me summarize.

The Motion trigger a change when it notices a motion. Then it will send a signal 1 minute later. If there is a motion happening during that time the signal will be send 1 minute later after the last detection.
In other word, you have 2 signals, one for Motion detection, and one for end of motion detection (which can happen 1 minute after the motion, or several minutes after the 1st as it will come 1 minute after the last).

That should be the default behaviour.

Did you set anything in the Domoticz Widget ? like the "Off Delay:" ? which must be to 0 to follow the device

[glory50]

No I didn't change anything in the Domoticz widget. "Off Delay" is 0, of course. Actually, I deleted all ZB devices from Domoticz, turned Z2M off, and repaired them with ZiGate+, then recreated new witgets. And changed the devices' names in my script. The script started to switch on the light, but the sensor does not react when the light is flashing afte 30s. With Z2M, the sensor sent the new ocuppancy true signal to Z2M and the llight stayed on until using the toilet has stopped.

Now, with Zigate, the light turns off and the user stays in the dark.

[pipiche]

can you enable the debug parameter debugCluster, and then if you can provide me the logs when playing with the Motion sensor.

If you are on plugin stable5 branch, please look at the Domoticz Log
if you are on plugin beta6 branch, please look at Logs/PluginZigbee-xx.log

[glory50]

Thank you pipiche!

At first, I'm on plugin stable5 brache - but there is no domoticz.log file on /var/log. And I couldn't find the reason.

Code: Select all

root@dom:~$ cat domoticz/scripts/logrotate/domoticz
/home/riho/domoticz/log/domoticz.log {
        missingok
        weekly
        rotate 7
        compress
        notifempty
        postrotate
                if [ -x /usr/sbin/invoke-rc.d ]; then \
                        invoke-rc.d domoticz reload > /dev/null; \
                else \
                        /etc/init.d/domoticz reload > /dev/null; \
                fi
        endscript
}
riho@dom:~$

Secodly, I switched temporarily back to Z2M with CC2532 and looked the difference, how the PIR sensor acts under that environement. And it is different. After movement, the PIR switches on exactly for 60 seconds with occupancy:true, if no more movement happens, it turnes off with occupancy:false. If any movement happens even 1 sec before this 60 sec timer, it resets itself and starts a new timer, so the second 60 secs will be guaranteed, and so on. Until the movements will stop for 60 secs and the occupancy:false will be triggered.

No messages are sent if there is some movement that resets the PIR's internal timer. So, I could create a script, that blinks the light in the WC to warn a user to make a movement not to stay in the dark.

Code: Select all

Zigbee2MQTT:info  2022-03-11 17:41:00: MQTT publish: topic ***, payload '{"battery":100,"battery_low":false,"linkquality":102,"occupancy":true,"tamper":false,"voltage":3200}'
Zigbee2MQTT:info  2022-03-11 17:42:00: MQTT publish: topic ***, payload '{"battery":100,"battery_low":false,"linkquality":102,"occupancy":false,"tamper":false,"voltage":3200}'

With ZiGate, the PIR switches off in exactly 30 secs (!), and does not react on whatever movement happens within or after that 30 secs. So, it waits the other 30 secs and then sends occupancy:false and switches for 60 sec to stay for one minute interval fo delay, as said by the producer:

"Due to power consumption and power-saving considerations, there have some restrictions on the trigger
That is: when SNZB-03 detects the movement, it will send a signal to ZBBridge
If the device does not detect any movement for one minute, once the device triggered, it will send a signal to ZBBridge
If any movement is detected within one minute, the device will not send a trigger to ZBBridge. And effective detection and trigger signals to ZBBridge will be delayed for one minute. It means the motion sensor works with one-minute intervals."

So, a user has to stay in the dark for 1min30 secs. Something is wrong with Zigbee plugin. Maybe I should try beta6 branch? How should I update and should all the devices repaired?

With regards,
glory50

[waltervl]

Domoticz log file on file system you have to switch on in \etc\init.d\domoticz.sh , see also https://www.domoticz.com/wiki/Troublesh ... bugging.29

I was never able to setup a correct log rotation.

[waltervl]

Second, there is a setting in the plugin User interface on port 9440 that configures the motion device auto switch off time (default 30 sec).

[glory50]

The only thing I found, was:

PIROccupiedToUnoccupiedDelay

So I tried with

Code: Select all

{60}

in the settings, but the auto switch off is still 30 sec. Can you specify, what I'm doing wrong?

Ok, even with the right syntax: { 'parameter1': value, 'parameter2': value .... }

Code: Select all

{ 'PIROccupiedToUnoccupiedDelay': 60 }

Nothing changes...

[glory50]

Thank you for the Domoticz log file settings, I got it working now.

[waltervl]

I have the following "Delay in sec to reset motion detection" setting in menu settings:

Screenshot_20220312-094301-475.png (105.56 KiB) Viewed 1144 times

[glory50]

Thanks a lot! I found it and this really worked for 60 sec. But now there's left only one problem. ZiGate doesn't allow me to reset the PIR's internal counter. So if there is a movement within those 60 sec, the sensor switches still off after the 60 sec periond for another 60 sec delay and there will be a darkness. Z2M allowed, as it is previwed, to make a movement and move forward this 60 sec delay time, until the person has left the toilet.

Why it doesn't work with ZiGate plugin? Should I really let the CC2532 stay along with ZiGate only for those Mi PIR sensors?