Thank you so much! It works (with Skyconnect).
is it also possible to run the container in bridge mode?
With macvlan and working ipv6 yes, but not in Bridge mode.
Donāt know for the Flow controller. Iām using this with skyconnect and only for thread.
Zigbee is running with another dongle under z2m (with 129 devices, migration not planed).
In my case z2m Is working without repairing.
Only a Little issue:: aqara Door/Window sensor are 90% working. If i open (or close) a Door or a Window, 9 time out of 10 all are ok but 1 time out of 10 i havent the change status. I dont know why. With the old coordinator this Is never happened. I dont know if It Is a coordinator issue, fw not 100% stabile, multipan issueā¦ i dont know. Have you an idea?
simplified the documentation and also pushed the image to the docker hub
https://hub.docker.com/r/b2un0/silabs-multipan-docker
Good job.
I solved my issue!!! The problem was that zigbee and thread MUST be on the same channel!!!
Thread by default Is Channel 15. I had zigbee on 11. Changing zigbee Channel would have been a disaster (repairing all device) so i changed thread Channel. The only way to do this Is by using curl to ask the OpenThread REST API directly to change the channel.
Open a terminal and digit:
curl http://YOURIP:8081/node/dataset/active | \
jq '.ActiveTimestamp.Seconds = .ActiveTimestamp.Seconds + 1 |
{
ActiveDataset: select(.),
Delay: 30000,
PendingTimestamp: .ActiveTimestamp
} |
.ActiveDataset.Channel = 11' | \
curl -X PUT http://YOURIP:8081/node/dataset/pending -d@-
NOW ALL WORKS AT THE BEST
This morning a very strange issue: my zigbee network was empity, with 0 devices.
fortunately in the data folder of zigbe2mqtt i found a file called database.db.backup, auto-created some hours ago. I deleted the empity database.db and replaced It with backup and now It Is ok.
What Is happened? I dont kwon if It Is a multipan issueā¦ in the last 2 years with zigbee i never seen anything like it. Letās see if it happens again
Maybe add to this, so it stays actual:
@leopold your container works like a charme.
Only 2 things:
1)you should to indicate that zigbee and thread must be on the same channel. Zigbee can be changed by webui, thread by curl (i posted some days ago the string).
2)i changed in the yaml the loglevel from debug to notice to reduce the verbosity
After setting this up, zigbee has communication problems with devices.
- Already added devices are shown as
Offline
- It is possible to discover/add new devices
- Reading states of devices works
- If a new state is read (e.g. I press a switch), then it tries configuring the new device but fails due to timeout errors
- It is not possible to send states to the new devices because of timeout errors (e.g.
{"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 12795 - 1 - 53 - 6 - 11 after 10000ms)'
)
Any ideas?
I wrote that zigbee and thread must have the same channel. Check this first
already done this before by following your guide, thanks! Both are on channel 11.
multiprotocol also prints
Default: mDNSPlatformSendUDP got error 101 (Network is unreachable) sending packet to ff02::fb on interface 172.28.0.1/br-0dff7b2b3618/5
if this helps. Is this network correct? I set BACKBONE_IF
to eth0
, which this is not
The value BACKBONE_IF
must be configured to the correct network interface that is actually used in your network.
for example: in my case, it is enp0s31f6
instead of eth0
is your container really running in network mode HOST
?
Yes the container runs in host modeā¦
It runs in a container on my raspberry pi with the LAN port connected to the eth0-interface. Isnāt that the interface I should specify?
If you digit ifconfig you can see if the name Is eth0. In my case Is end0
hm for me itās eth0ā¦
I had the same problem. In my case a lookup with āip link showā helped to find the correct interface (for me it was enp1s0). After a simple ubuntu restart no error appeared. Unfortunately it did not solve the issue with Zigbee. Only Thread worksā¦
Which problem with zigbee?