Great News! The AM43 binding was just merged into the official 2.5.x codebase.
The AM43 is now an official binding!
3 Likes
Uninterrupted operation for 7 days, and counting…
Congrats with the ‘official’ binding reward! 
1 Like
Hi I have opneHAB version 2.5.3.1 but this AM43 binding is not there. do you know why? Thanks
It is included as part of the bluetooth binding. So just installing the bluetooth binding should allow you to discover am43 motors.
Hi I have A-OK and all I see is RSSI when I add blinds?
Bluetooth Binding:
RuuviTag SmartBeacon
bluetooth:ruuvitag_beacon
Bluetooth Device
bluetooth:beacon
Connected Bluetooth Device
bluetooth:connected
Bluetooth BlueZ Adapter
bluetooth:bluez
BlueGiga Bluetooth Dongle
bluetooth:bluegiga
Things
Obyvak L launch
trending_up
RSSI
-47 dBm
Is that the list of manually creatable bluetooth things available to you? The am43 should at least be able to be created manually if auto discovery doesn’t work.
I’m starting with openHAB, I haven’t created things manually yet. I’ll have to look somewhere on the net. Thanks
I think I found what went wrong, looks like I forgot to make a critical change in one of the bluetooth binding xml files. So looks like the AM43 binding won’t be included automatically with the bluetooth binding. My screw up. I’ll have it fixed for next release. In the meantime you should be able to download the binding jar from my initial post and copy the jar into the openhab addons directory. Assuming you are using openhabian this would be located at /usr/share/openhab2/addons/. Once you copy the jar everything should work.
so I recorded there but write in the log:
[ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing ‘openhab-binding-org.openhab.binding.bluetooth.am43, openhab-binding-anymore bindings here’
Is that the entire error message? Can you post the entire thing?
Hi, quick functional question. With the app that comes with the Zemismart roller blind engine the engine will stop after a couple of minutes, leaving my blinds less than halfway open or closed. The blinds are 240cm high. Before I buy myself a raspberry Pi and try your binding, does any of you already use this binding for blinds with similar height?
The blinds drive engine app is known for being very unreliable. But the AM43 devices themselves are very reliable, with the exception of the solar panel not being large enough to keep it charged.
I won’t necessarily blame the app the blinds not opening or closing completely, unless you are trying to command your blinds to be a percentage open/closed. From what I can tell the AM43 should be able to support blinds of up to 25 meters in size, not that I have experimented to see if it actually can but the bluetooth protocol seems to hint that it should.
If your blinds are only going halfway I would troubleshoot without using the app and try to confirm that you have the upper/lower limits of your AM43 configured correctly. You can configure it without using the app. Once you have the upper and lower limits set you should be able to raise or lower the blinds completely from just holding a direction button for a second and a half. If that doesn’t work then your AM43 might have hardware issues.
@cpmeister Many thanks for the binding 
I have been trying to make it work for sometime now with no success 
I have a bluegiga usb passed to openhab in a privileged container.
The motor device is showing as offline all the time.
I have the below configs in things:
Bridge bluetooth:bluegiga:adapter1 “BlueGiga Adapter” [ port=“/dev/ttyACM1”, discovery=false ]
Thing bluetooth:am43:adapter1:motor1 “AM43 Blind Drive Motor 1” (bluetooth:bluegiga:adapter1) [ address=“02:D2:12:B3:59:50”, refreshInterval=300, invertPosition=false ]
The bluegiga is online but the motor is always offline (device not connected).
Any suggestions?
Ok, im officially out of ideas :).
The bridge is online and working fine, but the motor thing is offline.
2020-08-07 11:13:42.462 [DEBUG] [.bluetooth.am43.internal.AM43Handler] - Unable to send command GetAllCommand to device 02:D2:12:B3:59:50: not connected
2020-08-07 11:13:42.463 [DEBUG] [.bluetooth.am43.internal.AM43Handler] - Unable to send command GetBatteryLevelCommand to device 02:D2:12:B3:59:50: not connected
2020-08-07 11:13:42.464 [DEBUG] [.bluetooth.am43.internal.AM43Handler] - Unable to send command GetLightLevelCommand to device 02:D2:12:B3:59:50: not connected
How can i make it connected!?
If you are having trouble connecting to the device I would suggest checking whether or not the device is turned on. If it is on and you still can’t connect to it then it might be frozen. If it is frozen then it wouldn’t respond to manual button inputs either. If it is frozen, then the only way to unfreeze it is to restart the device, which given that it is unresponsive to manual button inputs would require the device to shutoff by running out of power. You can either wait for it to run out of power (which might take a while) or you could take apart the motor cover and disconnect the battery from the rest of the circuit, wait 10 seconds, and then reconnect the battery.
Another reason that it might not be able to connect is because your bluegiga adapter is not close enough to the motors. I’ve found that the AM43 is rather picky about signal quality so it requires bluetooth adapter to be close by.
What would be the recommended bluetooth adapters for use in OH to reliably connect to the AM43?
I use a LM1010 and a +12db antenna, which might be overkill but I’ve found it to be the most reliable solution for my setup.
Will a bluegiga adapter work as well?
Will OH detect the this LM1010 adapter if my OH is a docker container?
A bluegiga adapter works as well, but it didn’t have the same range as the LM1010 gave me.
The LM1010 uses bluez so I don’t know if it would be recognized in a docker container or how to configure it to be recognized.
I just got the LM1010 and plugged it into the ubuntu server that host the OH docker, but its not shown under /dev/tty. I am not sure how to open the LM1010 to the OH docker as the zwave and zigbee2mqtt usb devices are seen in /dev/tty