# Bond Bridge v4.6 Firmware Now in Beta

**URL:** <https://forum.bondhome.io/t/bond-bridge-v4-6-firmware-now-in-beta/4728>\
**Category:** BETA\
**Created:** [June 14, 2024, 12:07pm UTC](https://forum.bondhome.io/t/bond-bridge-v4-6-firmware-now-in-beta/4728 "2024-06-14T12:07:36Z")\
**Posts on this page:** 9\
**Page:** 2

<div class="post-metadata">

**Author:** ![merck](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/merck/32/1238_2.png) [@merck](https://forum.bondhome.io/u/merck)\
**Post date:** [July 9, 2024, 1:20pm UTC](https://forum.bondhome.io/t/bond-bridge-v4-6-firmware-now-in-beta/4728/21 "2024-07-09T13:20:02Z")

</div>

> [@residualimages](#):
>
> ZZ that was on 4.6beta, and which refuses to go up to 4.6.3beta (uncertain if this one needs to go back to 3.21.6.15-alpha first or not)? […] seems to fail somewhere between 26% - 31%, but eventually either stalls or goes into Error 109

Above I was talking about some logic that impacts whether an upgrade is available or not, but if the upgrade is offered but is stalling out, that’s an issue independent of the thread here so far. – Is this just happening on one ZZ unit?

It _could_ be a HW issue with the flash, but I don’t think we’ve ever seen that outside of open-case engineering units.

---

<div class="post-metadata">

**Author:** ![JLI](https://avatars.discourse-cdn.com/v4/letter/j/ecb155/32.png) [@JLI](https://forum.bondhome.io/u/JLI)\
**Post date:** [August 16, 2024, 2:13am UTC](https://forum.bondhome.io/t/bond-bridge-v4-6-firmware-now-in-beta/4728/22 "2024-08-16T02:13:56Z")

</div>

Any progress on resolving this issue?

---

<div class="post-metadata">

**Author:** ![merck](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/merck/32/1238_2.png) [@merck](https://forum.bondhome.io/u/merck)\
**Post date:** [August 23, 2024, 2:10pm UTC](https://forum.bondhome.io/t/bond-bridge-v4-6-firmware-now-in-beta/4728/23 "2024-08-23T14:10:29Z")

</div>

Yes, actually. The latest beta fixes an issue that we’ve had in BD-1000 `v4.x` firmware that caused all kinds of instability that we finally tracked down. It had to do with memory configuration rather than a specific coding issue, so it took a very deep dive to resolve, and we have finaly

---

<div class="post-metadata">

**Author:** ![JLI](https://avatars.discourse-cdn.com/v4/letter/j/ecb155/32.png) [@JLI](https://forum.bondhome.io/u/JLI)\
**Post date:** [August 23, 2024, 2:20pm UTC](https://forum.bondhome.io/t/bond-bridge-v4-6-firmware-now-in-beta/4728/24 "2024-08-23T14:20:07Z")

</div>

Thank you! That’s great to hear. I know these issues can be a major pain to track down. I appreciate your effort. I’m trying the latest firmware now and will let you know how it goes.

---

<div class="post-metadata">

**Author:** ![davidabuch](https://avatars.discourse-cdn.com/v4/letter/d/e47774/32.png) [@davidabuch](https://forum.bondhome.io/u/davidabuch)\
**Post date:** [September 3, 2024, 5:02am UTC](https://forum.bondhome.io/t/bond-bridge-v4-6-firmware-now-in-beta/4728/25 "2024-09-03T05:02:09Z")

</div>

Regarding HomeKit, are you still working on improving the integration and its stability? It’s gotten better but I still run into issues where the Bond Pro goes into a weird power cycle turning itself off and on with the only remedy to turn off HomeKit integration on the bond app and ultimately do a factory reset of Bond Pro to re-connect to HomeKit. This happens every few months. Just happened today.

---

<div class="post-metadata">

**Author:** ![merck](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/merck/32/1238_2.png) [@merck](https://forum.bondhome.io/u/merck)\
**Post date:** [September 3, 2024, 1:20pm UTC](https://forum.bondhome.io/t/bond-bridge-v4-6-firmware-now-in-beta/4728/26 "2024-09-03T13:20:35Z")

</div>

> […] HomeKit support. Too complex for us to support. Hoping we can bring in Matter for native Apple Home integration in the future, but Matter is—at least right now—also very complex from a development perspective.

Sorry, David, but there’s been no change here. We are just not able to support HomeKit properly before eventually bringing in Matter. The third-party SDK that we are using for HomeKit support is now totally unmaintained, so we cannot really bring anything new there.

---

<div class="post-metadata">

**Author:** ![davidabuch](https://avatars.discourse-cdn.com/v4/letter/d/e47774/32.png) [@davidabuch](https://forum.bondhome.io/u/davidabuch)\
**Post date:** [November 9, 2024, 4:49pm UTC](https://forum.bondhome.io/t/bond-bridge-v4-6-firmware-now-in-beta/4728/27 "2024-11-09T16:49:56Z")

</div>

Any updates on HomeKit compatibility? Almost every other shade company is HomeKit compatible now …

---

<div class="post-metadata">

**Author:** ![merck](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/merck/32/1238_2.png) [@merck](https://forum.bondhome.io/u/merck)\
**Post date:** [November 13, 2024, 1:31pm UTC](https://forum.bondhome.io/t/bond-bridge-v4-6-firmware-now-in-beta/4728/28 "2024-11-13T13:31:49Z")

</div>

I suggest you look into HomeBridge.

---

<div class="post-metadata">

**Author:** ![davidabuch](https://avatars.discourse-cdn.com/v4/letter/d/e47774/32.png) [@davidabuch](https://forum.bondhome.io/u/davidabuch)\
**Post date:** [November 13, 2024, 3:34pm UTC](https://forum.bondhome.io/t/bond-bridge-v4-6-firmware-now-in-beta/4728/29 "2024-11-13T15:34:42Z")

</div>

Tried that awhile ago. Very unreliable and also doesn’t allow for opening shades partway.

[Previous page](https://forum.bondhome.io/t/bond-bridge-v4-6-firmware-now-in-beta/4728.md?page=1)
