airbnk_mqtt
airbnk_mqtt copied to clipboard
How can I link two devices using this wonderful integration?
Greetings! The M521 lock is linked to the integration. The ESP 32 is stitched under the M521, like ESPHome. I got a new Airbnk B100 lock, went through the same ESP 32 as ESP Home, tied it to the Home Assistant, but when I add it to the integration, when filling in all the parameters and with my own unique topic, I get a message that the lock is not tied, since "The integration is already configured." Please help me - how can I link two devices using this wonderful integration?
Hey. Are you by any chance trying to use same ESP32 for both locks? It won't work, unfortunately.
Hey. Are you by any chance trying to use same ESP32 for both locks? It won't work, unfortunately.
Hi, @formatBCE! No, I used the second ESP32 module. I remember about the features of wifi and Bluetooth in ESP32. I managed to flash the second module and I see the data in mqtt, but I can't use it in integration.
Hey. Are you by any chance trying to use same ESP32 for both locks? It won't work, unfortunately.
Hi, @formatBCE! No, I used the second ESP32 module. I remember about the features of wifi and Bluetooth in ESP32. I managed to flash the second module and I see the data in mqtt, but I can't use it in integration.
Oh... In that case, I guess @rospogrigio probably has some clues.
Are you using the same account? If not, you should. If you do want to use different accounts, you should probably use the Add Entry button. You also should use two different topics for MQTT I believe (not sure, however).
Are you using the same account? If not, you should. If you do want to use different accounts, you should probably use the Add Entry button. You also should use two different topics for MQTT I believe (not sure, however).
Hi, @rospogrigio ! I use the same login (record for getting data in airbnk), but I write in two different mqtt topics. Tuning one after another, skipping the S100(contact sensor) adds only one entry. Setup in turn - first m521, skipping b100 and s100, the message comes out, as I indicated above, and adds m521. Then I add it again, specify the same entry and try to enter b100, skipping the already added m521 and s100, but the message comes out as I indicated and only m521 remains.
But what is this B100? Are you sure it is even supported? What if you delete the Integration and try to add only that one, does it even work? Nobody has ever reported to have tested it yet, it may behave differently or have different payload messages than the other locks...
"The integration is already configured."
Hi, @rospogrigio !
Yes, the B100 is a key safe lock, and it is not supported, although if you connect it as a single device, it fully connects while the door is open (it apparently falls asleep when closed), but the opening commands do not pass. From the W100 gateway, both locks are wonderfully controlled, but only one at a time. The S100 door sensor, which was previously addressed, also behaves. Thus, the B100 and S100 are unsupported devices. It's a pity, but so far so.
I took the second lock M521 (and I have it) and tried the whole experiment again. The first M521 connects easily, the second does not want to and writes "The integration is already configured".
I change the sequence of connecting the locks and get the same thing.Thus, it is impossible to connect a second device to the integration, even a supported one. Please help me solve the problems with connecting the second device to the integration. It is possible to implement support for the S100 contact sensor and the B100 lock of the AirBnk / Where key safe.