Ikea Tradfri bulb not changing status in domoticz with Zigate

Xiaomi, Ikea TRÅDFRI, Philips Hue and more.

Moderator: leecollings

pfloryann
Posts: 168
Joined: Wednesday 09 January 2019 10:14
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.1
Contact:

Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by pfloryann »

I noticed that Ikea tradfri bulb status is not changing in domoticz if the bulb it was swiched from IKEA Tradfri remote. He keeps the last domoticz status. Now the bulb is off but in domoticz the status is ON. I think the bulb or another device needs to communicate with zigate for domoticz to showing the real device status!!!
Domoticz on Raspberry Pi 4with Zigbee2mqtt
2 x xiaomi temperature sensor
7 x xiaomi plug
2 x xiaomi door sensor
1 x ikea plug
1 x ikea zigbee apdator
4 x xiaomi motion sensor
1 x xiaomi vibration sensor
2 x xiaomi wireless switch
Broadlink rm pro
pipiche
Posts: 1977
Joined: Monday 02 April 2018 20:33
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: France
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by pipiche »

Could you clarify Domoticz and Plugin version/branch
Zigbee for Domoticz plugin / RPI3B+ / Electrolama ZZH-P / 45 devices

If the plugin provides you value, you can support me with a donation Paypal.

Wiki is available here.

Zigbee for Domoticz FAQ
pfloryann
Posts: 168
Joined: Wednesday 09 January 2019 10:14
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.1
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by pfloryann »

I using Domoticz v10525 and plugin branch pre-4.1
Domoticz on Raspberry Pi 4with Zigbee2mqtt
2 x xiaomi temperature sensor
7 x xiaomi plug
2 x xiaomi door sensor
1 x ikea plug
1 x ikea zigbee apdator
4 x xiaomi motion sensor
1 x xiaomi vibration sensor
2 x xiaomi wireless switch
Broadlink rm pro
pipiche
Posts: 1977
Joined: Monday 02 April 2018 20:33
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: France
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by pipiche »

Make sure you are on the latest update of the branche.

I suggest that you edit the file Conf/PluginConf.txt and you add the following parameters if they are not yet in

Add them in the middle of the file, so you don't have any syntax issue (as the last line must not have the coma at the end of the line

Code: Select all

'resetConfigureReporting':'1',
'allowReBindingClusters':'1',
Then, restart the plugin and leave it running

Edit again the file Conf/PluginConf.txt and change . Because otherwise at each restart of the plugin a reset will be done.

Code: Select all

'resetConfigureReporting':'0',
The other parameter 'allowReBindingClusters' can stay to '1' as it's default value.

If you want to have more information on the Zigate Plugin parameters, please go here: https://github.com/pipiche38/Domoticz-Z ... onf.txt.md
Zigbee for Domoticz plugin / RPI3B+ / Electrolama ZZH-P / 45 devices

If the plugin provides you value, you can support me with a donation Paypal.

Wiki is available here.

Zigbee for Domoticz FAQ
pfloryann
Posts: 168
Joined: Wednesday 09 January 2019 10:14
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.1
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by pfloryann »

The latest update of the branch it was Saturday...i'll update again today and i'll be back with an feedback.
Domoticz on Raspberry Pi 4with Zigbee2mqtt
2 x xiaomi temperature sensor
7 x xiaomi plug
2 x xiaomi door sensor
1 x ikea plug
1 x ikea zigbee apdator
4 x xiaomi motion sensor
1 x xiaomi vibration sensor
2 x xiaomi wireless switch
Broadlink rm pro
pipiche
Posts: 1977
Joined: Monday 02 April 2018 20:33
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: France
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by pipiche »

with the 'allowReBindingClusters':'1', everytime you power (physicaly) off then off the Bulb, it should reset the binding, and should trigger the ConigreReporting should be back
Version of Saturday should be ok. very few fixes have been made seen that
Zigbee for Domoticz plugin / RPI3B+ / Electrolama ZZH-P / 45 devices

If the plugin provides you value, you can support me with a donation Paypal.

Wiki is available here.

Zigbee for Domoticz FAQ
pfloryann
Posts: 168
Joined: Wednesday 09 January 2019 10:14
Target OS: Raspberry Pi / ODroid
Domoticz version: 4.1
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by pfloryann »

I tested with lastest update(2 updates today) and it is working properly with Ikea remote control for now.

Another case : If the bulb is on and i swiched off the bulb from wall switch...in domoticz the bulb status keeps on. It is possible you adjust the plugin if zigate can't comunicate with the device for a while to automaticaly change the status to off?

Thank you Pipiche for your help!
Domoticz on Raspberry Pi 4with Zigbee2mqtt
2 x xiaomi temperature sensor
7 x xiaomi plug
2 x xiaomi door sensor
1 x ikea plug
1 x ikea zigbee apdator
4 x xiaomi motion sensor
1 x xiaomi vibration sensor
2 x xiaomi wireless switch
Broadlink rm pro
pipiche
Posts: 1977
Joined: Monday 02 April 2018 20:33
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: France
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by pipiche »

Making off on Domoticz seems not reasonable as this is nit the real state.

I’m currently evaluating the possibility to have a kind of device health, and in such case the status would be ‘not on the network anymore ‘ which not necessarily mean off!


Envoyé de mon iPhone en utilisant Tapatalk
Zigbee for Domoticz plugin / RPI3B+ / Electrolama ZZH-P / 45 devices

If the plugin provides you value, you can support me with a donation Paypal.

Wiki is available here.

Zigbee for Domoticz FAQ
ronaldbro
Posts: 327
Joined: Thursday 15 November 2018 21:38
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Location: Netherlands
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by ronaldbro »

I'm having the same problem with a Hue bulb. I can control it with Domoticz through Zigate and that works fine. Controlling the bulb with the remote dimmer also works fine. But when I control it with the dimmer the state in Domotics is not updated.

I'm using the latest beta of Domoticz and Zigate plugin 4.1.1

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.
fredo
Posts: 16
Joined: Thursday 28 March 2019 21:09
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by fredo »

ronaldbro wrote: Saturday 30 March 2019 21:47
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 could help: ( https://github.com/pipiche38/Domoticz-Z ... onf.txt.md )

You might try to set resetConfigureReporting to 1 to see if this works. As far as I understood it takes some time to rebuild the Configure Reporting, so better that you leave it for several hours.

In case this doesn't work, you might set enableReadAttributes to 1
ronaldbro
Posts: 327
Joined: Thursday 15 November 2018 21:38
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Location: Netherlands
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by ronaldbro »

Thanks, trying resetConfigureReporting now.
fredo
Posts: 16
Joined: Thursday 28 March 2019 21:09
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by fredo »

@ronaldbro you might do a git pull before, as there is a patch provided for the Configure Reporting
ronaldbro
Posts: 327
Joined: Thursday 15 November 2018 21:38
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Location: Netherlands
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by ronaldbro »

Thanks, the resetConfigureReporting this afternoon did not help.

I tried enableReadAttributes and I did see the lamp status change, but I don't know the poll time.

I restarted the configure reporting after a git pull, hope this helps and that it works without enableReadAttributes. Will see tomorrow.
pipiche
Posts: 1977
Joined: Monday 02 April 2018 20:33
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: France
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by pipiche »

seems from the source code that the polling is done every 900 sec
Zigbee for Domoticz plugin / RPI3B+ / Electrolama ZZH-P / 45 devices

If the plugin provides you value, you can support me with a donation Paypal.

Wiki is available here.

Zigbee for Domoticz FAQ
ronaldbro
Posts: 327
Joined: Thursday 15 November 2018 21:38
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Location: Netherlands
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by ronaldbro »

ok, thanks.

I guess 900 sec is good to poll for an update to check if something is changed.

If I can make a suggestion for an improvement... The Zigate plugin already detected that the remote and bulb are in a group and it knows the difference between the remote and bulb. If after a remote change an extra poll can be scheduled for the bulbs in the same group as the remote then it would work perfectly. That way the bulbs would be polled right after they changed.

I will also look if there are unprocessed messages from the bulb. But can't do that before the weekend.
fredo
Posts: 16
Joined: Thursday 28 March 2019 21:09
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by fredo »

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
Posts: 327
Joined: Thursday 15 November 2018 21:38
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Location: Netherlands
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by ronaldbro »

Hi fredo,

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.

The Configure Reporting did not work. How can I help to tune it in the plugin?
fredo
Posts: 16
Joined: Thursday 28 March 2019 21:09
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by fredo »

ronaldbro wrote: Tuesday 02 April 2019 10:43
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 ?
ronaldbro wrote: Tuesday 02 April 2019 10:43 The Configure Reporting did not work. How can I help to tune it in the plugin?
When you do a switch off/on of the bulb, what do you get in the Log. Is there any Device Announce and Rebinding messages ?
ronaldbro
Posts: 327
Joined: Thursday 15 November 2018 21:38
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Location: Netherlands
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by ronaldbro »

I will send this log as soon as possible. Unfortunatly this bulb and remote is in my son bedroom and he goes to bed early so I have limited testing time during the week.
ronaldbro
Posts: 327
Joined: Thursday 15 November 2018 21:38
Target OS: Raspberry Pi / ODroid
Domoticz version: 2020.2
Location: Netherlands
Contact:

Re: Ikea Tradfri bulb not changing status in domoticz with Zigate

Post by ronaldbro »

I did some testing, but didn't find anything.

Log when switching the light on:
Spoiler: show
2019-04-07 20:03:14.619 (Zigate) Processing 'WriteDirective' message
2019-04-07 20:03:14.619 (Zigate) Sending 41 bytes of data
2019-04-07 20:03:14.619 (Zigate) 01 02 10 30 02 10 15 b1 02 10 17 88 02 11 02 14 ac 72 19 02 ...0...�...�....�r..
2019-04-07 20:03:14.619 (Zigate) 12 02 10 02 11 02 13 02 10 15 8d 02 10 02 11 ed 46 fa 02 11 ..........�....�F�..
2019-04-07 20:03:14.620 (Zigate) 03 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .
2019-04-07 20:03:14.695 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:03:14.720 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:03:14.720 (Zigate) Received 18 bytes of data
2019-04-07 20:03:14.720 (Zigate) 01 80 02 10 02 10 02 15 fb 02 10 4e 02 10 30 02 10 03 .. .. .�......�..N..0...
2019-04-07 20:03:14.720 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:03:14.720 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:03:14.720 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:03:14.721 (Zigate) ZigateRead - decoded data : 0180000005fb004e00300003 lenght : 24
2019-04-07 20:03:14.721 (Zigate) ZigateRead - MsgType: 8000, MsgLength: 0005, MsgCRC: fb, Data: 004e0030; RSSI: 00
2019-04-07 20:03:14.721 (Zigate) ZigateRead - MsgType 8000 - reception status : 0180000005fb004e00300003
2019-04-07 20:03:14.721 (Zigate) Decode8000_v2 - MsgData lenght is : 8 out of 8
2019-04-07 20:03:14.721 (Zigate) Decode8000_v2 - status: Success SEQ: 4e Packet Type: 0030
2019-04-07 20:03:18.285 (Zigate) ZigateRead - MsgType 8030 - Reception Bind response : 0180300003944e006903
2019-04-07 20:03:18.285 (Zigate) Decode8030 - MsgData lenght is : 4 out of 2
2019-04-07 20:03:18.286 (Zigate) Decode8030 - Bind response, Sequence number : 4e Status : Success
2019-04-07 20:03:18.286 (Zigate) Processing 'WriteDirective' message
2019-04-07 20:03:18.286 (Zigate) Sending 83 bytes of data
2019-04-07 20:03:18.286 (Zigate) 01 02 11 20 02 10 2d 9e 02 12 d8 44 02 11 02 12 02 10 02 11 ......-�..�D........
2019-04-07 20:03:18.286 (Zigate) 02 10 02 10 02 10 02 10 02 13 02 10 29 02 10 21 02 1e 10 02 ............)..!....
2019-04-07 20:03:18.286 (Zigate) 1e 10 02 1f ff 02 11 02 10 21 02 10 02 10 02 11 2c ff fe 02 ....�....!......,��.
2019-04-07 20:03:18.286 (Zigate) 10 02 10 02 11 02 10 29 02 10 20 02 1e 10 02 1e 10 02 1f ff .......)...........�
2019-04-07 20:03:18.286 (Zigate) 02 11 03 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ...
2019-04-07 20:03:18.362 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:03:18.387 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:03:18.387 (Zigate) Received 18 bytes of data
2019-04-07 20:03:18.387 (Zigate) 01 80 02 10 02 10 02 15 59 02 10 fd 02 11 20 02 10 03 .. .. .�......Y..�......
2019-04-07 20:03:18.387 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:03:18.387 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:03:18.387 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:03:18.388 (Zigate) ZigateRead - decoded data : 01800000055900fd01200003 lenght : 24
2019-04-07 20:03:18.388 (Zigate) ZigateRead - MsgType: 8000, MsgLength: 0005, MsgCRC: 59, Data: 00fd0120; RSSI: 00
2019-04-07 20:03:18.388 (Zigate) ZigateRead - MsgType 8000 - reception status : 01800000055900fd01200003
2019-04-07 20:03:18.388 (Zigate) Decode8000_v2 - MsgData lenght is : 8 out of 8
2019-04-07 20:03:18.388 (Zigate) Decode8000_v2 - status: Success SEQ: fd Packet Type: 0120
2019-04-07 20:03:18.758 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:03:18.758 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:03:18.759 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:03:18.759 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:03:18.759 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:03:18.759 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:03:18.759 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:03:18.759 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:03:18.759 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:03:18.760 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:03:18.789 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:03:18.789 (Zigate) Received 1 bytes of data
2019-04-07 20:03:18.789 (Zigate) 01 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .
2019-04-07 20:03:18.789 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:03:18.790 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:03:18.790 (Zigate) Received 6 bytes of data
2019-04-07 20:03:18.790 (Zigate) 81 02 11 02 10 02 .. .. .. .. .. .. .. .. .. .. .. .. .. .. �.....
2019-04-07 20:03:18.790 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:03:18.790 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:03:18.790 (Zigate) Received 3 bytes of data
2019-04-07 20:03:18.790 (Zigate) 17 96 fd .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .��
2019-04-07 20:03:18.790 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:03:18.790 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:03:18.790 (Zigate) Received 2 bytes of data
2019-04-07 20:03:18.790 (Zigate) 02 12 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
2019-04-07 20:03:18.791 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:03:18.791 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:03:18.791 (Zigate) Received 1 bytes of data
2019-04-07 20:03:18.791 (Zigate) 02 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .
2019-04-07 20:03:18.791 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:03:18.791 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:03:18.791 (Zigate) Received 2 bytes of data
2019-04-07 20:03:18.791 (Zigate) 10 02 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
2019-04-07 20:03:18.791 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:03:18.791 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:03:18.792 (Zigate) Received 1 bytes of data
2019-04-07 20:03:18.792 (Zigate) 11 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .
2019-04-07 20:03:18.792 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:03:18.792 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:03:18.792 (Zigate) Received 1 bytes of data
2019-04-07 20:03:18.792 (Zigate) 02 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .
2019-04-07 20:03:18.792 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:03:18.792 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:03:18.792 (Zigate) Received 2 bytes of data
2019-04-07 20:03:18.792 (Zigate) 16 80 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .�
2019-04-07 20:03:18.792 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:03:18.792 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:03:18.793 (Zigate) Received 2 bytes of data
2019-04-07 20:03:18.793 (Zigate) 69 03 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. i.
2019-04-07 20:03:18.793 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:03:18.793 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:03:18.793 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:03:18.793 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:03:18.793 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:03:18.793 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:03:18.794 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:03:18.794 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:03:18.794 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:03:18.794 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:03:18.794 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:03:18.794 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:03:18.794 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:03:18.794 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:03:18.795 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:03:18.795 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:03:18.795 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:03:18.795 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:03:18.795 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:03:18.795 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:03:18.795 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:03:18.796 (Zigate) ZigateRead - decoded data : 018101000796fd02000106806903 lenght : 28
2019-04-07 20:03:18.796 (Zigate) ZigateRead - MsgType: 8101, MsgLength: 0007, MsgCRC: 96, Data: fd0200010680; RSSI: 69
2019-04-07 20:03:18.796 (Zigate) ZigateRead - MsgType 8101 - Default Response: 018101000796fd02000106806903
2019-04-07 20:03:18.797 (Zigate) Decode8101 - Default response - SQN: fd, EP: 02, ClusterID: 0001 , DataCommand: 06, - Status: [80] The supplied request type was invalid.
2019-04-07 20:03:19.522 (Zigate) Pushing 'onHeartbeatCallback' on to queue
2019-04-07 20:03:19.548 (Zigate) Processing 'onHeartbeatCallback' message
2019-04-07 20:03:19.548 (Zigate) Calling message handler 'onHeartbeat'.
2019-04-07 20:03:19.548 (Zigate) onHeartbeat - busy = False
and when switching off:
Spoiler: show
2019-04-07 20:02:20.354 Status: (Zigate) Device Annoucement ShortAddr: d844, IEEE: 0017880104ac7219
2019-04-07 20:02:20.356 Status: (Zigate) NetworkID : d844 is replacing e4e0 and is attached to IEEE : 0017880104ac7219
2019-04-07 20:02:20.240 Error: (Zigate) Decode8102 - Receiving a message from unknown device : d844 with Data : a5d84402fc000004004200053002210100
2019-04-07 20:02:21.850 (Zigate) 03 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .
2019-04-07 20:02:21.850 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:21.850 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:21.851 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:21.851 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:21.851 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:21.851 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:21.851 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:21.851 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:21.852 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:21.852 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:21.852 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:21.853 (Zigate) Pushing 'WriteDirective' on to queue
2019-04-07 20:02:21.853 (Zigate) ZigateRead - decoded data : 01803000039349006903 lenght : 20
2019-04-07 20:02:21.853 (Zigate) ZigateRead - MsgType: 8030, MsgLength: 0003, MsgCRC: 93, Data: 4900; RSSI: 69
2019-04-07 20:02:21.854 (Zigate) ZigateRead - MsgType 8030 - Reception Bind response : 01803000039349006903
2019-04-07 20:02:21.854 (Zigate) Decode8030 - MsgData lenght is : 4 out of 2
2019-04-07 20:02:21.854 (Zigate) Decode8030 - Bind response, Sequence number : 49 Status : Success
2019-04-07 20:02:21.854 (Zigate) Processing 'WriteDirective' message
2019-04-07 20:02:21.854 (Zigate) Sending 41 bytes of data
2019-04-07 20:02:21.854 (Zigate) 01 02 10 31 02 10 15 b0 02 10 17 88 02 11 02 14 ac 72 19 02 ...1...�...�....�r..
2019-04-07 20:02:21.854 (Zigate) 12 02 10 02 11 02 13 02 10 15 8d 02 10 02 11 ed 46 fa 02 11 ..........�....�F�..
2019-04-07 20:02:21.855 (Zigate) 03 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .
2019-04-07 20:02:21.930 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:21.955 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:21.955 (Zigate) Received 18 bytes of data
2019-04-07 20:02:21.955 (Zigate) 01 80 02 10 02 10 02 15 fe 02 10 4a 02 10 31 02 10 03 .. .. .�......�..J..1...
2019-04-07 20:02:21.955 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:21.956 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:21.956 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:21.956 (Zigate) ZigateRead - decoded data : 0180000005fe004a00310003 lenght : 24
2019-04-07 20:02:21.956 (Zigate) ZigateRead - MsgType: 8000, MsgLength: 0005, MsgCRC: fe, Data: 004a0031; RSSI: 00
2019-04-07 20:02:21.956 (Zigate) ZigateRead - MsgType 8000 - reception status : 0180000005fe004a00310003
2019-04-07 20:02:21.957 (Zigate) Decode8000_v2 - MsgData lenght is : 8 out of 8
2019-04-07 20:02:21.957 (Zigate) Decode8000_v2 - status: Success SEQ: 4a Packet Type: 0031
2019-04-07 20:02:22.338 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:22.338 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:22.338 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:22.338 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:22.338 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:22.339 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:22.358 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:22.358 (Zigate) Received 1 bytes of data
2019-04-07 20:02:22.358 (Zigate) 01 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .
2019-04-07 20:02:22.358 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:22.358 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:22.358 (Zigate) Received 5 bytes of data
2019-04-07 20:02:22.358 (Zigate) 80 31 02 10 02 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �1...
2019-04-07 20:02:22.358 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:22.358 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:22.358 (Zigate) Received 2 bytes of data
2019-04-07 20:02:22.359 (Zigate) 13 91 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .�
2019-04-07 20:02:22.359 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:22.359 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:22.359 (Zigate) Received 2 bytes of data
2019-04-07 20:02:22.359 (Zigate) 4a 02 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. J.
2019-04-07 20:02:22.359 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:22.359 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:22.359 (Zigate) Received 2 bytes of data
2019-04-07 20:02:22.359 (Zigate) 10 69 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .i
2019-04-07 20:02:22.359 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:22.359 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:22.360 (Zigate) Received 1 bytes of data
2019-04-07 20:02:22.360 (Zigate) 03 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .
2019-04-07 20:02:22.360 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:22.360 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:22.360 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:22.360 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:22.360 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:22.360 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:22.361 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:22.361 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:22.361 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:22.361 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:22.361 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:22.361 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:22.361 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:22.363 (Zigate) Pushing 'WriteDirective' on to queue
2019-04-07 20:02:22.363 (Zigate) ZigateRead - decoded data : 0180310003914a006903 lenght : 20
2019-04-07 20:02:22.363 (Zigate) ZigateRead - MsgType: 8031, MsgLength: 0003, MsgCRC: 91, Data: 4a00; RSSI: 69
2019-04-07 20:02:22.363 (Zigate) ZigateRead - MsgType 8031 - Reception Unbind response : 0180310003914a006903
2019-04-07 20:02:22.363 (Zigate) Decode8031 - MsgData lenght is : 4 out of 2
2019-04-07 20:02:22.364 (Zigate) ZigateRead - MsgType 8031 - Unbind response, Sequence number : 4a Status : Success
2019-04-07 20:02:22.364 (Zigate) Processing 'WriteDirective' message
2019-04-07 20:02:22.364 (Zigate) Sending 41 bytes of data
2019-04-07 20:02:22.364 (Zigate) 01 02 10 30 02 10 15 b1 02 10 17 88 02 11 02 14 ac 72 19 02 ...0...�...�....�r..
2019-04-07 20:02:22.364 (Zigate) 12 02 10 02 11 02 13 02 10 15 8d 02 10 02 11 ed 46 fa 02 11 ..........�....�F�..
2019-04-07 20:02:22.364 (Zigate) 03 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .
2019-04-07 20:02:22.440 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:22.465 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:22.465 (Zigate) Received 18 bytes of data
2019-04-07 20:02:22.465 (Zigate) 01 80 02 10 02 10 02 15 fe 02 10 4b 02 10 30 02 10 03 .. .. .�......�..K..0...
2019-04-07 20:02:22.465 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:22.465 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:22.465 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:22.466 (Zigate) ZigateRead - decoded data : 0180000005fe004b00300003 lenght : 24
2019-04-07 20:02:22.466 (Zigate) ZigateRead - MsgType: 8000, MsgLength: 0005, MsgCRC: fe, Data: 004b0030; RSSI: 00
2019-04-07 20:02:22.466 (Zigate) ZigateRead - MsgType 8000 - reception status : 0180000005fe004b00300003
2019-04-07 20:02:22.466 (Zigate) Decode8000_v2 - MsgData lenght is : 8 out of 8
2019-04-07 20:02:22.466 (Zigate) Decode8000_v2 - status: Success SEQ: 4b Packet Type: 0030
2019-04-07 20:02:23.427 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:23.427 (Zigate) Received 5 bytes of data
2019-04-07 20:02:23.427 (Zigate) 31 02 10 02 13 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 1....
2019-04-07 20:02:23.427 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:23.427 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:23.427 (Zigate) Received 3 bytes of data
2019-04-07 20:02:23.427 (Zigate) 97 4c 02 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. �L.
2019-04-07 20:02:23.427 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:23.427 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:23.427 (Zigate) Received 2 bytes of data
2019-04-07 20:02:23.428 (Zigate) 10 69 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .i
2019-04-07 20:02:23.428 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:23.428 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:23.428 (Zigate) Received 1 bytes of data
2019-04-07 20:02:23.428 (Zigate) 03 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .
2019-04-07 20:02:23.428 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:23.428 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:23.428 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:23.428 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:23.429 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:23.429 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:23.429 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:23.429 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:23.429 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:23.429 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:23.429 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:23.431 (Zigate) Pushing 'WriteDirective' on to queue
2019-04-07 20:02:23.431 (Zigate) ZigateRead - decoded data : 0180310003974c006903 lenght : 20
2019-04-07 20:02:23.431 (Zigate) ZigateRead - MsgType: 8031, MsgLength: 0003, MsgCRC: 97, Data: 4c00; RSSI: 69
2019-04-07 20:02:23.431 (Zigate) ZigateRead - MsgType 8031 - Reception Unbind response : 0180310003974c006903
2019-04-07 20:02:23.431 (Zigate) Decode8031 - MsgData lenght is : 4 out of 2
2019-04-07 20:02:23.431 (Zigate) ZigateRead - MsgType 8031 - Unbind response, Sequence number : 4c Status : Success
2019-04-07 20:02:23.432 (Zigate) Processing 'WriteDirective' message
2019-04-07 20:02:23.432 (Zigate) Sending 41 bytes of data
2019-04-07 20:02:23.432 (Zigate) 01 02 10 30 02 10 15 b0 02 10 17 88 02 11 02 14 ac 72 19 02 ...0...�...�....�r..
2019-04-07 20:02:23.432 (Zigate) 12 02 10 02 10 02 13 02 10 15 8d 02 10 02 11 ed 46 fa 02 11 ..........�....�F�..
2019-04-07 20:02:23.432 (Zigate) 03 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .
2019-04-07 20:02:23.507 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:23.533 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:23.533 (Zigate) Received 18 bytes of data
2019-04-07 20:02:23.533 (Zigate) 01 80 02 10 02 10 02 15 f8 02 10 4d 02 10 30 02 10 03 .. .. .�......�..M..0...
2019-04-07 20:02:23.533 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:23.533 (Zigate) Processing 'onMessageCallback' message
2019-04-07 20:02:23.533 (Zigate) Calling message handler 'onMessage'.
2019-04-07 20:02:23.534 (Zigate) ZigateRead - decoded data : 0180000005f8004d00300003 lenght : 24
2019-04-07 20:02:23.534 (Zigate) ZigateRead - MsgType: 8000, MsgLength: 0005, MsgCRC: f8, Data: 004d0030; RSSI: 00
2019-04-07 20:02:23.534 (Zigate) ZigateRead - MsgType 8000 - reception status : 0180000005f8004d00300003
2019-04-07 20:02:23.534 (Zigate) Decode8000_v2 - MsgData lenght is : 8 out of 8
2019-04-07 20:02:23.534 (Zigate) Decode8000_v2 - status: Success SEQ: 4d Packet Type: 0030
2019-04-07 20:02:23.887 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:23.887 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:23.887 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:23.887 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:23.887 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:23.888 (Zigate) Pushing 'ReadEvent' on to queue
2019-04-07 20:02:23.935 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:23.935 (Zigate) Received 2 bytes of data
2019-04-07 20:02:23.935 (Zigate) 01 80 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .�
2019-04-07 20:02:23.935 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:23.936 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:23.936 (Zigate) Received 4 bytes of data
2019-04-07 20:02:23.936 (Zigate) 30 02 10 02 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 0...
2019-04-07 20:02:23.936 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:23.936 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:23.936 (Zigate) Received 2 bytes of data
2019-04-07 20:02:23.936 (Zigate) 13 97 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .�
2019-04-07 20:02:23.936 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:23.936 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:23.936 (Zigate) Received 2 bytes of data
2019-04-07 20:02:23.937 (Zigate) 4d 02 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. M.
2019-04-07 20:02:23.937 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:23.937 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:23.937 (Zigate) Received 2 bytes of data
2019-04-07 20:02:23.937 (Zigate) 10 69 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .i
2019-04-07 20:02:23.937 (Zigate) Pushing 'onMessageCallback' on to queue
2019-04-07 20:02:23.937 (Zigate) Processing 'ReadEvent' message
2019-04-07 20:02:23.937 (Zigate) Received 1 bytes of data
It's not easy getting a clean log when 30 devices are connected. There might be some irrelevant messages in the logs...
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest