#Heavy connectionproblems between the SLZB-06M and Home assistant

1 messages · Page 1 of 1 (latest)

cobalt ridge
#

Hi all,

Ive changed from DNS / DHCP server a couple of days ago, and it seems that i have some serious connectivity problems now between the SLZB-06M and the Z2M host. The SLZB-06 has been attached with a prefab ethernet cable.
Connection seems heavily instable. Sometimes devices cannot be managed by Z2M, sometimes they can. I just noticed this error message, which says nothing to me. The error message appears when a device switches state, but cannot access the SLZB-06M stick. Also if the devices are connected to eachother, there is quite a lag before the state visually changes in Z2M.

I changed from the TP-Link router DHCP/DNS server to Technitium. This is also a black hole (like PiHole).
Ive also set the DNS from both to the IP of the Technitium server. Since then ive got issues.

Yet, providing static IP addresses with openDNS configured on both devices doesnt seem to do much.

IP address of the stick is 192.168.6.2
IP address of the Z2M device is 192.168.178.8 . Both VLANS are open for eachother. At this moment ive configured a ping entity in home assistant which sends a ping towards the SLZB-06M to determine further network issues.

Does anyone know where i have to look for this issue?

Many thanks!

lusty granite
#

From my understanding while there has been work on making the various zigbee chipsets play nice with both Z2M and ZHA the EFR32MG21 that you have is noted to play nicer with ZHA than Z2M while the CC2652P plays more nice with Z2M than ZHA.

Also insure you have set it up correctly. https://smlight.tech/manual/slzb-06/guide/installation/

cobalt ridge
#

Ah okay, so id better switch back to ZHA then?

lusty granite
#

If you had it on ZHA without any issues then yea for sure

cobalt ridge
#

Nah, before it worked perfectly fine with Z2M

#

Weird thing i just noticed:

This would say that there is a connection between the SLZB-06M and Z2H if im right

#

Yet devices at this moment are not switching states

#

Here is some data about the VM where home-assistant is running on:

lusty granite
#

by "play nice" it just means things don't act as they should, does not suggest there is no connection at all.

cobalt ridge
#

It does look like the notify automations does work. When i open a curtain switch manually, a message pops up on my phone. So the actions doesnt seem to go through

cobalt ridge
#

Testing it now, but got it working after changing (or deleting if you will) the "domain suffix" from my router from both subnets (178 and 6).

#

Gonna test it for a bit. Current tests are positive tho. It keeps responding up to now, and it responds as before in terms of speed also

cobalt ridge
#

Ok, so a few hours later > it turns out that its non responsive again

#

It looks like a restart of the mosquito broker is a temporary fix. All start working again after restarting the broker

#

Just thinking out loud: Could this be an issue?

I have 5 of these modules configured. Can imagine it causes allot of spam like this

#

This is how the log looks like:

cobalt ridge
#

I think those mass storm of logging is causing the module to stop. Any way to fix this other then changing my IOT devices or restarting Z2M every 10 minutes?

cobalt ridge
#

Upgraded from EZSP to ember. Going to monitor that. Got no logging anymore now, which is fine for me but i do have error messages. I truly cant care less since its working at this moment.

somber wasp
#

Did you disable your router's DHCP server? It's also possible you have ip conflicts at the moment.