Page 1 of 1
Zigate Plugin release 4.2.0
Posted: Wednesday 24 April 2019 11:48
by pipiche
Just to inform you that we are just about releasing 4.2 of Zigate plugin.
We have now some additional devices supported by the plugin. Big thanks to the gentle contributors whom help us to buy devices and test them.
Details are available here :
https://github.com/sasu-drooz/Domoticz- ... 2019---420
PS/
- Don't forgett to use the Wiki
https://github.com/sasu-drooz/Domoticz-Zigate/wiki has a main source of informations
Re: Zigate Plugin release 4.2.0
Posted: Saturday 27 April 2019 16:47
by mpx2
Hi
I installed Zigate some time ago. Then I updated to version 4.2.0 and added Xiaomi Aqara temp, hum, and pressure sensor. Now I have lost connections few times and one time Domoticz stopped responding. I have ZiGate USB-TTL.
Code: Select all
2019-04-27 17:41:17 Ready
2019-04-27 17:41:12 No Communication
2019-04-27 16:31:16 Ready
2019-04-27 16:31:11 No Communication
2019-04-27 10:36:06 Ready
2019-04-27 10:35:56 Startup
Code: Select all
2019-04-27 16:31:11 Ping: Connection with Zigate Lost
2019-04-27 10:35:56 Zigate Channel: 15
2019-04-27 10:35:56 Zigate IEEE: xxxxxxxxxxxxxx
2019-04-27 07:01:41 Ping: Connection with Zigate Lost
2019-04-26 16:31:30 Successful creation of Widget for :lumi.weather DeviceID: 34bc
2019-04-26 16:31:21 Zigate Channel: 15
2019-04-26 16:31:21 Zigate IEEE: xxxxxxxxxxxxxx
2019-04-26 16:29:00 Zigate Channel: 15
2019-04-26 16:29:00 Zigate IEEE: xxxxxxxxxxxxxx
2019-04-17 15:21:22 Zigate Channel: 15
2019-04-17 15:21:22 Zigate IEEE: xxxxxxxxxxxxxx
2019-04-17 14:26:19 Zigate Channel: 11
Code: Select all
2019-04-27 16:26:11.527 Error: (ZiGate) Transport is not connected, write directive to 'ZiGate' ignored.
2019-04-27 16:31:11.560 Error: (ZiGate) Ping - no Heartbeat with Zigate
2019-04-27 17:36:12.208 Error: (ZiGate) Transport is not connected, write directive to 'ZiGate' ignored.
2019-04-27 17:41:12.242 Error: (ZiGate) Ping - no Heartbeat with Zigate
2019-04-27 17:46:12.318 Error: (ZiGate) Transport is not connected, write directive to 'ZiGate' ignored.
Re: Zigate Plugin release 4.2.0
Posted: Saturday 27 April 2019 18:00
by pipiche
Ca ressemble à des problèmes de connexion avec ta Zigate .
Ta Zigate est en direct ?
Envoyé de mon iPhone en utilisant Tapatalk
Re: Zigate Plugin release 4.2.0
Posted: Sunday 28 April 2019 0:22
by mpx2
I did power off averything. Let's see what happens.
---
I bought an Osram Smart+ plug switch
https://zigate.fr/le-materiel-compatibl ... mlightify/
If I restart Domoticz and then plug in Osram it starts switching on and off four times every 60 seconds. If I remove Zigate stick Osram stops behaving badly. If I restart Domoticz Osram stops switching on and off. Domoticz shows Osram in red color until you switch it on or off.
Now Osrams works OK but if you unplug it and plug it, it starts switching on and off four times every 60 seconds.
Here is what you can see in log
https://pastebin.com/8VSnLy28
Re: Zigate Plugin release 4.2.0
Posted: Sunday 28 April 2019 9:11
by pipiche
You can try to set the parameter allowReBindingClusters to 0 in PluginConf-xx.txt
See here for more information :
https://github.com/pipiche38/Domoticz-Z ... onf.txt.md
Re: Zigate Plugin release 4.2.0
Posted: Sunday 28 April 2019 13:03
by mpx2
That fixed the problem I descibed. But. When I unplugged Osram and plugged it back, it started switching on and off randomly. No 60 seconds delay and four repeats. I cannot reproduce this problem.
I don't dare to use Osram for anything important if it start switching on and off.
Re: Zigate Plugin release 4.2.0
Posted: Sunday 28 April 2019 13:56
by mpx2
BTW. Is there a way to update the "Last seen" time in other way than pressing on or off. How can I be sure that Osram is pluggeg in?
In picture above Osram is seen 45 min ago even it has been on all the time. Now I unplugged it and status is on and last seen is same.
More Info:
After two hours when I unplugged Osram Domoticz shows that all is ok. State is ON. When I click it off "Last seen" gets updated to current time even Domoticz and Zigate could not have seen Osram switch because it has been unplugged over 2 hours.
Re: Zigate Plugin release 4.2.0
Posted: Sunday 28 April 2019 16:47
by mpx2
The first part of the log is when Osram started to switching randomly on and off. After that Osram stopped working and it did not respond (second part of the log).
https://pastebin.com/7DFhShTR
More info:
I'm going to reinstall averything.
Re: Zigate Plugin release 4.2.0
Posted: Sunday 28 April 2019 18:32
by pipiche
mpx2 wrote:BTW. Is there a way to update the "Last seen" time in other way than pressing on or off. How can I be sure that Osram is pluggeg in?
You have to enable a parameter ReadAttributes , please check the pluginconf wiki
This will créa load on Zigate by polling information on a regular basis.
Envoyé de mon iPhone en utilisant Tapatalk
Re: Zigate Plugin release 4.2.0
Posted: Sunday 28 April 2019 19:03
by pipiche
mpx2 wrote: ↑Sunday 28 April 2019 13:56
BTW. Is there a way to update the "Last seen" time in other way than pressing on or off. How can I be sure that Osram is pluggeg in?
enableReadAttributes 0 If set to 1, the plugin will poll information from each of the main powered devices. It might be needed for some devices which doesn't all to set Configure Automatic reporting
Re: Zigate Plugin release 4.2.0
Posted: Sunday 28 April 2019 20:35
by mpx2
pipiche wrote: ↑Sunday 28 April 2019 19:03
mpx2 wrote: ↑Sunday 28 April 2019 13:56
BTW. Is there a way to update the "Last seen" time in other way than pressing on or off. How can I be sure that Osram is pluggeg in?
enableReadAttributes 0 If set to 1, the plugin will poll information from each of the main powered devices. It might be needed for some devices which doesn't all to set Configure Automatic reporting
Thanks but it did not help. I have to give up. 'enableReadAttributes':'1', and 'allowReBindingClusters':'0', did not solve problems.
Code: Select all
{
'channel':'26',
'vibrationAqarasensitivity':'medium',
'resetMotiondelay':'30',
'enablegroupmanagement':'0',
'logLQI':'0',
'enableReadAttributes':'1',
'allowReBindingClusters':'0',
'logFORMAT':'0'
}
I plugged Osram back in and it Zigate lost it.
Code: Select all
2019-04-28 21:25:10.269 (Zigate) onCommand - unit: 8, command: On, level: 0, color:
2019-04-28 21:25:10.269 (Zigate) onCommand called for Devices[8].Name: Zigate - Plug 01 SwitchType: 0 Command: On Level: 0 Color:
2019-04-28 21:25:10.269 (Zigate) mgtCommand - NWKID = 158f
2019-04-28 21:25:10.269 (Zigate) mgtCommand : found Device : 1056 in Ep 03 Plug
2019-04-28 21:25:10.269 (Zigate) mgtCommand - List of TypeName : ['Plug']
2019-04-28 21:25:10.269 (Zigate) mgtCommand - DeviceType : Plug
2019-04-28 21:25:10.269 (Zigate) mgtCommand : Found Ep 03 for Device 1056 Cluster 0006
2019-04-28 21:25:10.269 (Zigate) EPout = 03
2019-04-28 21:25:10.270 (Zigate) UpdateDevice_v2 for : 8 Battery Level = {} Signal Level = 90
2019-04-28 21:25:10.270 (Zigate) UpdateDevice_v2 for : 8 RSSI = 4
2019-04-28 21:25:10.270 (Zigate) UpdateDevice - (Zigate - Plug 01) 1:On
2019-04-28 21:25:10.270 (Zigate) Update Values 1:'On:' (Zigate - Plug 01)
2019-04-28 21:25:10.376 (Zigate) ZigateRead - decoded data : 018000000533002400920003 lenght : 24
2019-04-28 21:25:10.377 (Zigate) ZigateRead - MsgType: 8000, MsgLength: 0005, MsgCRC: 33, Data: 00240092; RSSI: 00
2019-04-28 21:25:10.377 (Zigate) ZigateRead - Calling Decoder: <function Decode8000_v2 at 0x6a7dcdb0> for Message type: 8000
2019-04-28 21:25:10.377 (Zigate) Decode8000_v2 - MsgData lenght is : 8 out of 8
2019-04-28 21:25:10.377 (Zigate) Decode8000_v2 - status: Success SEQ: 24 Packet Type: 0092
2019-04-28 21:25:10.377 (Zigate) ZigateRead - decoded data : 018702000e95e9010302158f0000000000006d0003 lenght : 42
2019-04-28 21:25:10.378 (Zigate) ZigateRead - MsgType: 8702, MsgLength: 000e, MsgCRC: 95, Data: e9010302158f0000000000006d; RSSI: 00
2019-04-28 21:25:10.378 (Zigate) ZigateRead - Calling Decoder: <function Decode8702 at 0x6a7e7bb8> for Message type: 8702
2019-04-28 21:25:10.378 (Zigate) timedOutDevice unit Zigate - Plug 01 nwkid: 158f
2019-04-28 21:25:10.390 (Zigate) Device : 158f MacCapa : 8e updating SQN to 6d
2019-04-28 21:25:10.231 Status: User: username initiated a switch command (1056/Zigate - Plug 01/On)
2019-04-28 21:25:10.378 Error: (Zigate) Communication error when transmiting a previous command to 158f ieee 7cb03eaa0a0128db
2019-04-28 21:25:10.390 Error: (Zigate) Decode8702 - SQN: 6d AddrMode: 02 DestAddr: 158f SrcEP: 01 DestEP: 03 Status: e9 - No acknowledgement received when expected
Re: Zigate Plugin release 4.2.0
Posted: Sunday 28 April 2019 21:44
by pipiche
Why channel 26 ?
Envoyé de mon iPhone en utilisant Tapatalk
Re: Zigate Plugin release 4.2.0
Posted: Monday 29 April 2019 14:08
by pipiche
mpx2 wrote: ↑Sunday 28 April 2019 20:35
pipiche wrote: ↑Sunday 28 April 2019 19:03
mpx2 wrote: ↑Sunday 28 April 2019 13:56
BTW. Is there a way to update the "Last seen" time in other way than pressing on or off. How can I be sure that Osram is pluggeg in?
enableReadAttributes 0 If set to 1, the plugin will poll information from each of the main powered devices. It might be needed for some devices which doesn't all to set Configure Automatic reporting
Thanks but it did not help. I have to give up. 'enableReadAttributes':'1', and 'allowReBindingClusters':'0', did not solve problems.
Code: Select all
{
'channel':'26',
'vibrationAqarasensitivity':'medium',
'resetMotiondelay':'30',
'enablegroupmanagement':'0',
'logLQI':'0',
'enableReadAttributes':'1',
'allowReBindingClusters':'0',
'logFORMAT':'0'
}
I plugged Osram back in and it Zigate lost it.
Code: Select all
2019-04-28 21:25:10.269 (Zigate) onCommand - unit: 8, command: On, level: 0, color:
2019-04-28 21:25:10.269 (Zigate) onCommand called for Devices[8].Name: Zigate - Plug 01 SwitchType: 0 Command: On Level: 0 Color:
2019-04-28 21:25:10.269 (Zigate) mgtCommand - NWKID = 158f
2019-04-28 21:25:10.269 (Zigate) mgtCommand : found Device : 1056 in Ep 03 Plug
2019-04-28 21:25:10.269 (Zigate) mgtCommand - List of TypeName : ['Plug']
2019-04-28 21:25:10.269 (Zigate) mgtCommand - DeviceType : Plug
2019-04-28 21:25:10.269 (Zigate) mgtCommand : Found Ep 03 for Device 1056 Cluster 0006
2019-04-28 21:25:10.269 (Zigate) EPout = 03
2019-04-28 21:25:10.270 (Zigate) UpdateDevice_v2 for : 8 Battery Level = {} Signal Level = 90
2019-04-28 21:25:10.270 (Zigate) UpdateDevice_v2 for : 8 RSSI = 4
2019-04-28 21:25:10.270 (Zigate) UpdateDevice - (Zigate - Plug 01) 1:On
2019-04-28 21:25:10.270 (Zigate) Update Values 1:'On:' (Zigate - Plug 01)
2019-04-28 21:25:10.376 (Zigate) ZigateRead - decoded data : 018000000533002400920003 lenght : 24
2019-04-28 21:25:10.377 (Zigate) ZigateRead - MsgType: 8000, MsgLength: 0005, MsgCRC: 33, Data: 00240092; RSSI: 00
2019-04-28 21:25:10.377 (Zigate) ZigateRead - Calling Decoder: <function Decode8000_v2 at 0x6a7dcdb0> for Message type: 8000
2019-04-28 21:25:10.377 (Zigate) Decode8000_v2 - MsgData lenght is : 8 out of 8
2019-04-28 21:25:10.377 (Zigate) Decode8000_v2 - status: Success SEQ: 24 Packet Type: 0092
2019-04-28 21:25:10.377 (Zigate) ZigateRead - decoded data : 018702000e95e9010302158f0000000000006d0003 lenght : 42
2019-04-28 21:25:10.378 (Zigate) ZigateRead - MsgType: 8702, MsgLength: 000e, MsgCRC: 95, Data: e9010302158f0000000000006d; RSSI: 00
2019-04-28 21:25:10.378 (Zigate) ZigateRead - Calling Decoder: <function Decode8702 at 0x6a7e7bb8> for Message type: 8702
2019-04-28 21:25:10.378 (Zigate) timedOutDevice unit Zigate - Plug 01 nwkid: 158f
2019-04-28 21:25:10.390 (Zigate) Device : 158f MacCapa : 8e updating SQN to 6d
2019-04-28 21:25:10.231 Status: User: username initiated a switch command (1056/Zigate - Plug 01/On)
2019-04-28 21:25:10.378 Error: (Zigate) Communication error when transmiting a previous command to 158f ieee 7cb03eaa0a0128db
2019-04-28 21:25:10.390 Error: (Zigate) Decode8702 - SQN: 6d AddrMode: 02 DestAddr: 158f SrcEP: 01 DestEP: 03 Status: e9 - No acknowledgement received when expected
I don't really understand what you are trying to achieve, by plug in and out, but from the log you are refereing here:
The Zigate seems not to be able to communicate with the plug. May be by pluging in and out you reset it ... or it is simply not reachable.
As per my precedent, message, why Channel 26 ? Some devices do not support
Re: Zigate Plugin release 4.2.0
Posted: Monday 29 April 2019 14:51
by mpx2
I wanted to try if Osram and Xiaomi Aqara sensors support channel 26. Seemed to be working ok.
I cannot take a risk that Osram loses power or there's a glitch in Zigate and therefore Osram starts switching on and off. This can damage controlled equipment.
I need to know the state of that Osram power switch. It's not enough that I know it worked eg 6 hours ago.
I have WiFi controlled schuko power switches. I always know by looking from app that those switches are reachable. I know are they on or off. Never have those switches started switching on and off in any circumstances.
Re: Zigate Plugin release 4.2.0
Posted: Monday 29 April 2019 16:43
by pipiche
mpx2 wrote: ↑Monday 29 April 2019 14:51
I wanted to try if Osram and Xiaomi Aqara sensors support channel 26. Seemed to be working ok.
I cannot take a risk that Osram loses power or there's a glitch in Zigate and therefore Osram starts switching on and off. This can damage controlled equipment.
I need to know the state of that Osram power switch. It's not enough that I know it worked eg 6 hours ago.
I have WiFi controlled schuko power switches. I always know by looking from app that those switches are reachable. I know are they on or off. Never have those switches started switching on and off in any circumstances.
From my end, I think that you are mixing different tests and as the Channel 26, I would consider doing it from a stable environment.
Nevertheless as mentioned if you want to have a regular test, you have to enable the parameter: 'enableReadAttributes':'1', which will do a regular polling to each of the main powered devices.
As regards to the OSRAM it seems that there are issues with them and they do not support the resetBinding , so you need to disable that with 'allowReBindingClusters':'0',
Now, if you still get messages like the one here after, there is a clear communication issue between Zigate and the end device. That could be from a Protocol standpoint and/or some other issues.
2019-04-28 21:25:10.378 Error: (Zigate) Communication error when transmiting a previous command to 158f ieee 7cb03eaa0a0128db
2019-04-28 21:25:10.390 Error: (Zigate) Decode8702 - SQN: 6d AddrMode: 02 DestAddr: 158f SrcEP: 01 DestEP: 03 Status: e9 - No acknowledgement received when expected