Domoticz

THis is up to the Zigbe protocol stack to decide where to go, we (the plugin) doesn't have any influence to that !
What you can eventually try is to repair the xiaomi sensor closed to a repeater, but there is no guaranty, and from my experience I see the sensor prefering direct connection to the Controler (Zigate) instead of going through a router.
Last , this needs times ( days ) of stable routers (repeaters and other main powered devices) to get the sensors eventually moving.

tjabas wrote: ↑Friday 13 December 2019 20:23 i have installed 2 pcs of trådfri repeaters, i also have some aqara sensors, but it looks like the sensors doesnt connect to the trådfri repeaters, why is it like that?

Hi,
Do you have the the latest plugin for Zigate? It can help you to see the mesh connections. At least you should be sure that Tradfri repeaters are connected to Zigate. What do you have in devices list?
I struggled a lot with similar issues. Aquara (I have temp sensors mostly) sensor didn't want to connect to repeaters. I don't know what happened but after some time (I have upgraded Domoticz and Zigate plugin as well meanwhile) it started to work and it's stable since that.

tjabas wrote: ↑Friday 13 December 2019 20:23 i have installed 2 pcs of trådfri repeaters, i also have some aqara sensors, but it looks like the sensors doesnt connect to the trådfri repeaters, why is it like that?

Same here, my Aqara sensors don't want to connect to the trådfri repeater either.
It seems Aqara sensors only want to connect to the coordinator.

Hi,
Today suddenly some of the Xiaomi Aquara sensors what was connected to Tradfri repeater lost the connection. What is weird that one is working what connected to Tradrfri repeater. What I don't understand that Topology map doesn't show that connection. Only one another Temp sensor is visible what was connected directly to Zigate as well.
So only two temp sersors sending data currently. One (1.) was connected drirectly to Zigate, another one (2.) used Tradfri repeater but only 1. is visible on Topology map. Same issue after plugin restart.
What can I do now?

Johnny5 wrote: ↑Tuesday 24 December 2019 21:20 Hi,
Today suddenly some of the Xiaomi Aquara sensors what was connected to Tradfri repeater lost the connection. What is weird that one is working what connected to Tradrfri repeater. What I don't understand that Topology map doesn't show that connection. Only one another Temp sensor is visible what was connected directly to Zigate as well.
So only two temp sersors sending data currently. One (1.) was connected drirectly to Zigate, another one (2.) used Tradfri repeater but only 1. is visible on Topology map. Same issue after plugin restart.
What can I do now?

After reset Xiaomi sensors all started to work but not through Tradfri repeaters. Connected the Zigate directly this time. All of them visible on the Topology map as well. Tradfri repeaters are still not alive. Not even after reset them. I don't know what to do. The most strange thing that both of them lost today. That can't be a coincidence. I didn't change anything in the system. I'm clueless what happend.

Johnny5 wrote: ↑Tuesday 24 December 2019 22:02

Johnny5 wrote: ↑Tuesday 24 December 2019 21:20 Hi,
Today suddenly some of the Xiaomi Aquara sensors what was connected to Tradfri repeater lost the connection. What is weird that one is working what connected to Tradrfri repeater. What I don't understand that Topology map doesn't show that connection. Only one another Temp sensor is visible what was connected directly to Zigate as well.
So only two temp sersors sending data currently. One (1.) was connected drirectly to Zigate, another one (2.) used Tradfri repeater but only 1. is visible on Topology map. Same issue after plugin restart.
What can I do now?

After reset Xiaomi sensors all started to work but not through Tradfri repeaters. Connected the Zigate directly this time. All of them visible on the Topology map as well. Tradfri repeaters are still not alive. Not even after reset them. I don't know what to do. The most strange thing that both of them lost today. That can't be a coincidence. I didn't change anything in the system. I'm clueless what happend.

There is nothing we can do to force a device to use a particular route.
Could you let me know what is the Wifi 2.4 Channel you are using and what is the Zigbee/Zigate channel use (you can see that in the Log at plugin start)

When you said the repeater are still not alive, what does that mean ? How do you get to that conclusion ?

pipiche wrote: ↑Thursday 26 December 2019 12:41

Johnny5 wrote: ↑Tuesday 24 December 2019 22:02

Johnny5 wrote: ↑Tuesday 24 December 2019 21:20 Hi,
Today suddenly some of the Xiaomi Aquara sensors what was connected to Tradfri repeater lost the connection. What is weird that one is working what connected to Tradrfri repeater. What I don't understand that Topology map doesn't show that connection. Only one another Temp sensor is visible what was connected directly to Zigate as well.
So only two temp sersors sending data currently. One (1.) was connected drirectly to Zigate, another one (2.) used Tradfri repeater but only 1. is visible on Topology map. Same issue after plugin restart.
What can I do now?

After reset Xiaomi sensors all started to work but not through Tradfri repeaters. Connected the Zigate directly this time. All of them visible on the Topology map as well. Tradfri repeaters are still not alive. Not even after reset them. I don't know what to do. The most strange thing that both of them lost today. That can't be a coincidence. I didn't change anything in the system. I'm clueless what happend.

There is nothing we can do to force a device to use a particular route.
Could you let me know what is the Wifi 2.4 Channel you are using and what is the Zigbee/Zigate channel use (you can see that in the Log at plugin start)

When you said the repeater are still not alive, what does that mean ? How do you get to that conclusion ?

Hi Pipiche,
I know that devices take their own way to the Zigate. I meant about repeaters were not alive that Device manager on Plugin page reported as not alive. Unfortunately Domoticz doesn't show "real last connection time" for Tradfri repeaters. I don't know why. I never seen any real conenction data even when they worked fine. So that isn't so infromative.
Some of the devices used the repeater to connect as they were too far from Zigate. They didn't send any data anymore. Strangely both two repeaters lost their connection (and all connected devices) around same time. I couldn't see any usable info in Domoticz log about that. I tried to reconect Tradfri repeaters using reset switch without success. Log showed this (filtered for word "Tradfri"):

2019-10-29 23:36:50.815 (Zigate) timedOutDevice unit Tradfri repeater nwkid: fd56
2019-10-29 23:36:50.818 Error: (Zigate) Command: 0x0120:Configure reporting request failed on Tradfri repeater
2019-10-29 23:36:50.818 Error: (Zigate) - Device: Tradfri repeater NwkID: fd56 IEEE: 000d6ffffe7aceda
2019-11-29 21:24:39.398 Status: (Zigate) [1] NEW OBJECT: 94c7 Model Name: TRADFRI signal repeater
2019-11-30 21:24:37.980 Error: (Zigate) Device Health - Nwkid: 94c7,Ieee: 000d6ffffe2f13f9 , Model: TRADFRI signal repeater seems to be out of the network
2019-12-01 02:14:15.499 Error: (Zigate) Device Health - Nwkid: fd56,Ieee: 000d6ffffe7aceda , Model: TRADFRI signal repeater seems to be out of the network
2019-12-04 03:03:11.217 Error: (Zigate) Device Health - Nwkid: fd56,Ieee: 000d6ffffe7aceda , Model: TRADFRI signal repeater seems to be out of the network
2019-12-21 11:54:26.955 (Zigate) timedOutDevice unit Tradfri repeater 2 nwkid: 94c7
2019-12-21 11:54:26.957 Error: (Zigate) Command: 0x0100:Read Attribute request failed on Tradfri repeater 2
2019-12-21 11:54:26.957 Error: (Zigate) - Device: Tradfri repeater 2 NwkID: 94c7 IEEE: 000d6ffffe2f13f9
2019-12-21 11:54:26.957 Error: (Zigate) Command: 0x0100:Read Attribute request failed on Tradfri repeater 2
2019-12-21 11:54:26.958 Error: (Zigate) - Device: Tradfri repeater 2 NwkID: 94c7 IEEE: 000d6ffffe2f13f9
2019-12-21 11:54:27.059 Error: (Zigate) Command: 0x0100:Read Attribute request failed on Tradfri repeater 2
2019-12-21 11:54:27.059 Error: (Zigate) - Device: Tradfri repeater 2 NwkID: 94c7 IEEE: 000d6ffffe2f13f9
2019-12-21 11:54:27.059 Error: (Zigate) Command: 0x0100:Read Attribute request failed on Tradfri repeater 2
2019-12-21 11:54:27.059 Error: (Zigate) - Device: Tradfri repeater 2 NwkID: 94c7 IEEE: 000d6ffffe2f13f9
2019-12-24 02:55:52.598 (Zigate) timedOutDevice unit Tradfri repeater 2 nwkid: 94c7
2019-12-24 02:55:52.600 Error: (Zigate) Command: 0x0120:Configure reporting request failed on Tradfri repeater 2
2019-12-24 02:55:52.600 Error: (Zigate) - Device: Tradfri repeater 2 NwkID: 94c7 IEEE: 000d6ffffe2f13f9
2019-12-24 03:06:52.683 (Zigate) timedOutDevice unit Tradfri repeater 1 nwkid: fd56
2019-12-24 03:06:52.685 Error: (Zigate) Command: 0x0120:Configure reporting request failed on Tradfri repeater 1
2019-12-24 03:06:52.685 Error: (Zigate) - Device: Tradfri repeater 1 NwkID: fd56 IEEE: 000d6ffffe7aceda
2019-12-24 23:56:10.647 Error: (Zigate) Command: 0x0120:Configure reporting request failed on Tradfri repeater 2
2019-12-24 23:56:10.647 Error: (Zigate) - Device: Tradfri repeater 2 NwkID: 94c7 IEEE: 000d6ffffe2f13f9
2019-12-25 00:07:10.811 Error: (Zigate) Command: 0x0120:Configure reporting request failed on Tradfri repeater 1
2019-12-25 00:07:10.811 Error: (Zigate) - Device: Tradfri repeater 1 NwkID: fd56 IEEE: 000d6ffffe7aceda
2019-12-25 20:56:21.778 Error: (Zigate) Command: 0x0120:Configure reporting request failed on Tradfri repeater 2
2019-12-25 20:56:21.778 Error: (Zigate) - Device: Tradfri repeater 2 NwkID: 94c7 IEEE: 000d6ffffe2f13f9
2019-12-25 21:07:21.978 Error: (Zigate) Command: 0x0120:Configure reporting request failed on Tradfri repeater 1
2019-12-25 21:07:21.978 Error: (Zigate) - Device: Tradfri repeater 1 NwkID: fd56 IEEE: 000d6ffffe7aceda
2019-12-26 10:59:18.077 Status: (Zigate) Device Tradfri repeater 1 with IEEE: 000d6ffffe7aceda fully removed from the system.
2019-12-26 11:07:59.266 Status: (Zigate) [1] NEW OBJECT: fde9 Model Name: TRADFRI signal repeater

At the end I deleted the repeater from Domoticz rebooted the NAS and then it was ok to conenct using the reset button.
Losing the connection happeend after some time midnight 24 Dec. However same error messgaes appears before 24 Dec. But that time both repeaters worked fine. SO I really don't know what happened with them and what these errors are about.

Regarcing the question of Wifi channels. I searched on the Net some articles about Zigbee and 2.4 Wifi. It sad that there are many owerlappings. What I did yesterday I switched my router from Auto channel selection to channel 1.
Can you tell me where can I find the Log for that? I can see that teh channel is 0 on Plugin page.

One more thing to mention. Since this issue I can't run scan to see the topology. I doesn't show anything. What can be the issue with that?

Thank you!

Most likely the zigate is on channel 11( domoticz logs )

If that is the case move the WiFi 2.4 to 11 to avoid overlap


https://github.com/pipiche38/Domoticz-Z ... -Zigbee.md


Envoyé de mon iPhone en utilisant Tapatalk

pipiche wrote: ↑Saturday 28 December 2019 10:47 Most likely the zigate is on channel 11( domoticz logs )

If that is the case move the WiFi 2.4 to 11 to avoid overlap


https://github.com/pipiche38/Domoticz-Z ... -Zigbee.md


Envoyé de mon iPhone en utilisant Tapatalk

What I see in domoticz.log:

2019-10-02 23:32:35.296 Status: (Zigate) PluginConf: /usr/local/domoticz/var/plugins/Domoticz-Zigate/Conf/PluginConf.txt
2019-10-02 23:32:35.296 Status: MQTT: connected to: localhost:1883
2019-10-02 23:32:35.297 Status: (Zigate) -vibrationAqarasensitivity: medium
2019-10-02 23:32:35.297 Status: (Zigate) -enablegroupmanagement: 0
2019-10-02 23:32:35.297 Status: (Zigate) -resetMotiondelay: 30
2019-10-02 23:32:35.297 Status: (Zigate) -logFORMAT: 0
2019-10-02 23:32:35.297 Status: (Zigate) -logLQI: 0
2019-10-02 23:32:35.297 Status: (Zigate) -channel: ['11', '15', '19', '20', '25', '26']

This is visible for earlier dates only. No such data in past days when I restardted the plugin.
Also can't find PluginConf.txt in this folder. It has these files only in ...domoticz/var/plugins/Domoticz-Zigate/Conf:
-rw-r--r-- 1 root root 10743 Oct 2 23:59 DeviceConf.txt
-rw-r--r-- 1 root root 640 Oct 3 00:13 PluginConf-02.json

I'm not 100% sure if I understand the channel overlapping chart. Does that mean if 2.4 Wifi set in channel 1 (or 7) then Zigbee channel 15, 16, 21, 22 don't overlap with that?

Do you have any ide what could be wrong with topology scan? It doesn't give any result.
Thanks!

Johnny5 wrote: ↑Saturday 28 December 2019 14:43

pipiche wrote: ↑Saturday 28 December 2019 10:47 Most likely the zigate is on channel 11( domoticz logs )

If that is the case move the WiFi 2.4 to 11 to avoid overlap


https://github.com/pipiche38/Domoticz-Z ... -Zigbee.md


Envoyé de mon iPhone en utilisant Tapatalk

What I see in domoticz.log:

2019-10-02 23:32:35.296 Status: (Zigate) PluginConf: /usr/local/domoticz/var/plugins/Domoticz-Zigate/Conf/PluginConf.txt
2019-10-02 23:32:35.296 Status: MQTT: connected to: localhost:1883
2019-10-02 23:32:35.297 Status: (Zigate) -vibrationAqarasensitivity: medium
2019-10-02 23:32:35.297 Status: (Zigate) -enablegroupmanagement: 0
2019-10-02 23:32:35.297 Status: (Zigate) -resetMotiondelay: 30
2019-10-02 23:32:35.297 Status: (Zigate) -logFORMAT: 0
2019-10-02 23:32:35.297 Status: (Zigate) -logLQI: 0
2019-10-02 23:32:35.297 Status: (Zigate) -channel: ['11', '15', '19', '20', '25', '26']

This is visible for earlier dates only. No such data in past days when I restardted the plugin.
Also can't find PluginConf.txt in this folder. It has these files only in ...domoticz/var/plugins/Domoticz-Zigate/Conf:
-rw-r--r-- 1 root root 10743 Oct 2 23:59 DeviceConf.txt
-rw-r--r-- 1 root root 640 Oct 3 00:13 PluginConf-02.json

I'm not 100% sure if I understand the channel overlapping chart. Does that mean if 2.4 Wifi set in channel 1 (or 7) then Zigbee channel 15, 16, 21, 22 don't overlap with that?

Do you have any ide what could be wrong with topology scan? It doesn't give any result.
Thanks!

Here are the configuration information, but you should get an other line( Network state UP, PANID: 7538 extPANID: 0x6734484504015e10 Channel: 11 ) at plugin start where the Zigate informs on which channel it is .

If you want to avoid overlap, put Wifi on 11 and Zigbee on 11.
However if you want to change the Zigbee, you will have to repair all Zigbee devices. As I suspect (default) Zigbee is on 11

Ok, but which one is the plugin conf file? I can't see any PluginConf.txt.
By the way repeaters lost the connections again almost at the same time. Meanwhile directly connected sensors to Zigate works fine.
After reset (no need to delete fromdevice list) seems ok.

pipiche wrote: ↑Saturday 28 December 2019 14:52

Johnny5 wrote: ↑Saturday 28 December 2019 14:43

pipiche wrote: ↑Saturday 28 December 2019 10:47 Most likely the zigate is on channel 11( domoticz logs )

If that is the case move the WiFi 2.4 to 11 to avoid overlap


https://github.com/pipiche38/Domoticz-Z ... -Zigbee.md


Envoyé de mon iPhone en utilisant Tapatalk

What I see in domoticz.log:

2019-10-02 23:32:35.296 Status: (Zigate) PluginConf: /usr/local/domoticz/var/plugins/Domoticz-Zigate/Conf/PluginConf.txt
2019-10-02 23:32:35.296 Status: MQTT: connected to: localhost:1883
2019-10-02 23:32:35.297 Status: (Zigate) -vibrationAqarasensitivity: medium
2019-10-02 23:32:35.297 Status: (Zigate) -enablegroupmanagement: 0
2019-10-02 23:32:35.297 Status: (Zigate) -resetMotiondelay: 30
2019-10-02 23:32:35.297 Status: (Zigate) -logFORMAT: 0
2019-10-02 23:32:35.297 Status: (Zigate) -logLQI: 0
2019-10-02 23:32:35.297 Status: (Zigate) -channel: ['11', '15', '19', '20', '25', '26']

This is visible for earlier dates only. No such data in past days when I restardted the plugin.
Also can't find PluginConf.txt in this folder. It has these files only in ...domoticz/var/plugins/Domoticz-Zigate/Conf:
-rw-r--r-- 1 root root 10743 Oct 2 23:59 DeviceConf.txt
-rw-r--r-- 1 root root 640 Oct 3 00:13 PluginConf-02.json

I'm not 100% sure if I understand the channel overlapping chart. Does that mean if 2.4 Wifi set in channel 1 (or 7) then Zigbee channel 15, 16, 21, 22 don't overlap with that?

Do you have any ide what could be wrong with topology scan? It doesn't give any result.
Thanks!

Here are the configuration information, but you should get an other line( Network state UP, PANID: 7538 extPANID: 0x6734484504015e10 Channel: 11 ) at plugin start where the Zigate informs on which channel it is .

If you want to avoid overlap, put Wifi on 11 and Zigbee on 11.
However if you want to change the Zigbee, you will have to repair all Zigbee devices. As I suspect (default) Zigbee is on 11

im stealing the tread , so you mean that the wifi and zigbee should both be on channel 11? if so, then thy both must overlap big time? or am i wrong?
why i ask is that i also have tried different channels on both wifi and zigbee.

No they won't overlap, please read the link I provided. The chanels are not the same.