I think it’s just a kill-switch in the fireplace that turns it off if either it can’t communicate with the remote at all (batteries out) or if it’s getting commands that don’t match or originate from the remote.
I’ve given up trying to work around it – it’s just not that big of a need for us anyway.
This does seem to have fixed it for me. Neither of my fireplaces turn off by themselves with the batteries removed from the remotes. Sorry that doesn’t seem to have fixed it for you also.
Does the fireplace run indefinity though? After 2 hours without any signal from the remote my fireplace turns off, apparently by design since the Bond Hub is not replicating the keep alive signal.
TBH, I don’t think I could tolerate having the fireplace on that long to find out. It’s possible.
I’m new to Bond and I’m also trying to hook up my skytech II remote where it will just turn my fireplace on and off. Has Bond fixed this or has anyone figure out how to do yet?
Did anyone find a solution for you?
With fireplace remotes, we find that the remote controls often transmit at regular intervals some kind of “keep-alive” transmission.
For some fireplaces, it is enough to remove the batteries from the factory remote, and then Bond Bridge works just fine, transmitting only when you want to change the state of the fireplace.
However, there are some fireplaces which will shut off by themselves after some brief period if they do not receive a keep-alive. These we can sadly not support.
I am unsure which of the two above cases applies to your fireplace, but by using Bond with the batteries out of the factory remote you can determine this.
Well there’s several threads in your help section that pertain to my problem. Bond never came up with a better solution then sadly we don’t support this remote? This is the only reason I bought the Bond