You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow me to elaborate on my environment and use case: I use a Sonoff iHost to integrate devices into Apple Home. iHost, in addition to native functionality which integrates a variety of Zigbee devices, it includes a docker hosting feature. iHost also includes a Matter Bridge for the devices it supports. For instance, I am using iHost to integrate Zigbee IKEA roller shade (without using an IKEA hub) and Zigbee Sonoff light controller and expose it to Apple Home via the integrated Matter Bridge. I am also running Homebridge in a iHost docker to integrate various WiFi devices to Apple Home. Shelly devices make up a large part of my home automation. I've integrated them via two Homebridge plugins but this does not seem to be a supported approach going forward (Shelly Gen3 devices are not supported by any Homebridge plugin.) Shelly recommends matterbridge and has a robust matterbridge-shelly plugin. In order to simplify my Shelly integration and add support for Gen3 devices, I installed matterbrige in an iHost docker. Added matterbridge-shelly via the web gui. It discovers all my Shelly devices. Before I add this matterbridge to my Apple Home, I noticed the two devices integrated via native iHost matter bridge (IKEA shade & Sonoff switch) stopped responding in Apple Home. I stopped the matterbridge docker and these two devices responded again. There seems to be a conflict between iHost Matter Bridge and matterbridge running in docker on iHost. The only log error in the matterbridge log is:
info - [10:14:16.700] [CaseServer]: Received pairing request from udp://fe80::1ccb:403f:2375:5f7%eth0:49956
error - [10:14:16.705] [CaseServer]: An error occurred during the commissioning Fabric cannot be found from destinationId at FabricManager.findFabricFromDestinationId (file:///app/node_modules/@matter/protocol/dist/esm/fabric/FabricManager.js:184:11) at CaseServer.handleSigma1 (file:///app/node_modules/@matter/protocol/dist/esm/session/case/CaseServer.js:115:36) at async CaseServer.onNewExchange (file:///app/node_modules/@matter/protocol/dist/esm/session/case/CaseServer.js:36:7) at async SecureChannelProtocol.onNewExchange (file:///app/node_modules/@matter/protocol/dist/esm/securechannel/SecureChannelProtocol.js:122:9) at async ExchangeManager.onMessage (file:///app/node_modules/@matter/protocol/dist/esm/protocol/ExchangeManager.js:207:9)
info - [10:14:16.710] [InsecureSession]: End insecure session insecure/9412610887785303301
The text was updated successfully, but these errors were encountered:
Allow me to elaborate on my environment and use case: I use a Sonoff iHost to integrate devices into Apple Home. iHost, in addition to native functionality which integrates a variety of Zigbee devices, it includes a docker hosting feature. iHost also includes a Matter Bridge for the devices it supports. For instance, I am using iHost to integrate Zigbee IKEA roller shade (without using an IKEA hub) and Zigbee Sonoff light controller and expose it to Apple Home via the integrated Matter Bridge. I am also running Homebridge in a iHost docker to integrate various WiFi devices to Apple Home. Shelly devices make up a large part of my home automation. I've integrated them via two Homebridge plugins but this does not seem to be a supported approach going forward (Shelly Gen3 devices are not supported by any Homebridge plugin.) Shelly recommends matterbridge and has a robust matterbridge-shelly plugin. In order to simplify my Shelly integration and add support for Gen3 devices, I installed matterbrige in an iHost docker. Added matterbridge-shelly via the web gui. It discovers all my Shelly devices. Before I add this matterbridge to my Apple Home, I noticed the two devices integrated via native iHost matter bridge (IKEA shade & Sonoff switch) stopped responding in Apple Home. I stopped the matterbridge docker and these two devices responded again. There seems to be a conflict between iHost Matter Bridge and matterbridge running in docker on iHost. The only log error in the matterbridge log is:
The text was updated successfully, but these errors were encountered: