Hi, I have a MS105MYQ opener and unfortunately there is a green button that as far as I can tell has been hard wired or soldered into terminals 1/2 which I cannot remove. There is also no space to insert additional wires, again as far as I can tell/have tried. I have attached some photos. Do I have any other options here or am I unfortunately out of luck at this stage?
Did you work it out?
No I havent so far… Konnecrted still sitting on my garage bench 
Sorry I must have missed this. We’ve since learned more about the differences in the Australia/NZ models.
The red wire to the Konnected GDO blaQ should be connected to the green terminal labeled “0” and the white wire to the GDO blaQ should be connected to either of the white terminals labeled “2”.
Also note that apparently in Australia and New Zealand, not all garage openers have an IR safety beam (obstruction sensor). If your garage opener is NOT equipped with an obstruction sensor, you really should add one to be compliant with local regulations. As far as I know, the IR safety beam sensor is required when used with an automatic/unattended controller like the GDO blaQ. If not present, the motor may refuse to close the garage door when commanded. There is a workaround, however, which is to enable the Toggle only mode on the GDO blaQ (via its internal web page).
Hi @nate - I do not believe it is a strict requirement to have safety beams in Aus. If you have a solution for the Merlin garage door openers, can you post an install guide rather than leaving it in a blog post. Thanks
@nate - Please provide an update on Australian Merlin devices.
I’d like an update too - I have the same model, wired correctly, but facing the same issues that others have faced with issues like the device seemingly going to sleep, not tracking open/close states etc (running latest firmware and using HA > Homekit).
We’ve made a few attempts at trying to remotely debug and troubleshoot this, but so far it has been unsuccessful. I’ve also made a few attempts to acquire a AU/NZ model Merlin or Chamberlain DIY garage opener without success.
We strongly suspect that there are some regional differences with the Security+ protocol that are causing these issues with Merlin openers. In order for there to be any chance of a fix, we need to get one of these machines.
Is there anyone in Australia that could help us acquire a used but functional Merlin or newer-model AU/NZ Chamberlain DIY opener, and ship it to us in the U.S. or to @Ryan_P in Canada? We will pay for a shipping label, I just need somebody on the ground there to help us find one and pack it up and ship it for R&D. Maybe a used motor on eBay?
I might be able to help you out. I’m in Brisbane, Australia. I found a few different second-hand ones that could work.
Merlin:
https://www.facebook.com/marketplace/item/1339814224005823
or
https://www.facebook.com/marketplace/item/1617722588860890
Chamberlain & Merlin
https://www.facebook.com/marketplace/item/1196456385085310
If you let me know which one is the most helpful for you, I could purchase it and send it to you.
I’d love to see better support for the AU/NZ models. I also have a Merlin MS105MYQ and have found the blaQ not always reliable. It sometimes drops out, reports the wrong status or freezes. I also have weak wifi so not sure if that’s adding to the problem. Rebooting the GDO or blaQ usually resolves these issues but sometimes it only crashes when I actually go to open the door. Perhaps this is due to the differences in the security protocol and it’s causing it to crash?
Hi @Ben_Anderson,
Thanks for offering to help out here!
The Merlin Commander Essential looks like an ideal test unit because it’s relatively new model and has the round yellow learn button like the higher-end MS105MYQ.
I will DM you about buying it and shipping it overseas. We will reimburse of course for any costs!
1 Like
Hi @nate - it is model number MS65MYQ
Any further updates @nate
1 Like
We’re still waiting on our test motor from Australia to arrive.
I’m working on the issue currently but I’m not able to reproduce any issues so far. Would anyone like to show me their current setup that isn’t working? Some details about what does and doesn’t work would be helpful as well.
Here is my setup that works fine:
Thanks so much for taking a look for us!
I can’t manually re-produce the error, but just waiting over the course of days or even weeks it’ll typically occur for me. Here’s an example from today
None of these times I did anything. Some days there’s no issues.
Occasionally it’ll say it’s opening or closing but not actually doing anything. Other times I go to open it and then it becomes unavailable. Sometimes after a reboot of the GDO it’ll take a long time to find the rolling code. I found a way for it to more quickly recovered from being unavailable by using this ESPHome code on it
time:
- platform: sntp
id: sntp_time
timezone: Australia/Brisbane
servers:
- time.cloudflare.com
- pool.ntp.org
on_time:
# At specific time
- seconds: 0
minutes: 0
hours: 2
then:
- button.press: restart_button
Project version: 1.4.1
ESPHome Version: 2025.7.3
I also have this HA automation to re-sync it if it becomes unavailable under specific circumstances.
alias: Resync GDO if unavailable
description: ""
triggers:
- entity_id:
- cover.konnected_34b7da612768_garage_door
to: unavailable
for:
hours: 0
minutes: 0
seconds: 45
trigger: state
- entity_id:
- cover.konnected_34b7da612768_garage_door
to: opening
for:
hours: 0
minutes: 0
seconds: 30
trigger: state
- entity_id:
- cover.konnected_34b7da612768_garage_door
to: closing
for:
hours: 0
minutes: 0
seconds: 30
trigger: state
conditions: []
actions:
- action: button.press
metadata: {}
data: {}
target:
entity_id: button.konnected_34b7da612768_re_sync
- action: notify.mobile_app_pixel_8a
data:
message: GDO unavailable
mode: single
The last time this was triggered for me was 13th August at 07:42:46 and before that was 9th August at 10:09:45.
Thank you Ben! I guess I will just monitor this for a bit and see what I can find. Curious about the re-sync time, sounds like the rolling code last synced with didn’t get saved if it’s taking excessively long. How much time are we talking about? Any chance you could log this?
I’ll try to replicate the rolling code issue but actually it mostly happened when I briefly tested the unit that I sent to you. So perhaps if the blaQ is switched between two different Merlin’s then it doesn’t save properly.
That makes sense, it took mine a few mins to sync at first too and now resyncs in seconds after the initial.
So if I am understanding this correctly, when left for some amount of time it randomly loses sync and a reboot resolves it?
Yes something like that. My wifi signal is around -66 dBm, dunno if that contributes to it. At one point I set up a wifi range extender which did increase the signal strength but made it go unavailable way more.
Sometimes even a resync won’t work and it’ll need to be rebooted. Half the time it becomes unavailable without me doing anyting, other times I go to open it and it does nothing and then shows up as unavailable. Other times it opens succesfully but then gets stuck in opening or open state and won’t close without a resync or reboot. Some weeks there no problems and other weeks it happens every few days.
So perhaps in your testing you could set up an automation that randomly opens and closes it 0-8 times a day and monitor it for any unavailable states.