OK , found the problem in detail -
question is can you implement the solution??
Start sequence
Ignition on -
Wunderlinq goes live and starts the Bluetooth handshake cycle
If the handshake is successful , all well and good the unit functions
If the wunderlinq dosent handshake, it still thinks it has handshaked , and then is in a terminal lockout
no matter what you try, it wont reconnect, because it thinks its connected
Soloution.
It needs to be active and passive
It needs an active cycle to initiate handshake , but if it fails to handshake, it needs to go passive so it will accept handshakes from apps or hardware
the way to get it to connect now, is to get it to start and lockout, ( false connect)
then to disconnect it physically ( as theres no reboot or soft restart ) and then initiate pairing from the app , and plug the wunderlinq back into the cradle
then hope the two talk to each other ...
once they do, they get the pair request and all is ok ..
so as i said, it needs to let the app initiate the pairing, not the wunderlinq