If you want to try the binding out, you can either install via the Add-ons store or download the jar file from the post and save it in the openHAB-addons folder on your OH server.
Appreciate any feedback you have to help improve this binding!
Using your examples I was able to create the controller thing and the items for the doors. The controller shows online but the doors show as NULL in the item explorer. Any idea why that is?
Octavio, can you provide a bit more details so I can help you?
Which method did you use to configure the Tailwind Thing; auto discovery or manual configuration commands?
Were you able to determine the URL for the Tailwind controller or are you using the IP address? (instructions can be found in the other considerations section here: Other Considerations
Were you able to create an authorization token using your account on the website for your Tailwind controller?
Are you seeing any messages in the Openhab log regarding the Tailwind controller that you can share?
How many doors are you controlling?
Is this the only Openhab server your running the Tailwind Thing on, for this specific door controller?
What platform are you running Openhab on? RPI, Linux, Windows…
Anything else you can share that may help is appreciated.
I use the manual method because I find it more flexible. The things and items are defined in files.
Yes I have the correct URL discovered using both the auto discovery method and dns-sd. I use the URL so I do not need to assign a fixed IP for the controller.
Yes I do have the correct token and the controller shows up online in openhab and I can also control the doors using curl.
The log does not show anything special but it does show temporary failure in name resolution. The message is:
[WARN ] [ind.internal.handler.TailwindHandler] - There was an error communicating to the TailWind controller! Error msg: Rest call failed: statusCode=-1, message=java.util.concurrent.ExecutionException: java.net.UnknownHostException: tailwind-xxxx.local: Temporary failure in name resolution
We have two doors.
Yes, there is only one Openhab server running in our home. It is running in docker under linux and the current version we have is 4.3.5, latest docker image openhab/openhab:latest.
Should you need any more information, please do let me know, Dave.
The warning message seems to indicate that the URL being used cannot be found on your network. I assume the URL you have configured in the Tailwind Thing is correct - the message lists it as tailwind-xxxx.local which would not work, but it may just be masking out the actual part following the “-”.
Auto discovery should have created a thing with a list of thing properties. Those will include: firmwareVersion, hardwareVersion, maxDoors,
numberOfDoorsConnected, macAddress, modelId, httpServerUrl and vendor.
The URL is basically tailwind-[mac-address].local
One way to find out if the URL works is to execute a curl command from the Linux server running the docker container. I assume your container is bridged to the server’s network.
The following command will return the controller status.
If you get a response back, then we know the server can find the controller on your network. If not, then there’s a problem resolving the url to find your controller on the network and perhaps try to replace the URL with the Tailwind Controller’s IP and see it that works.
The xxxx was just to hide the actual MAC of our device.
As I mentioned, I can control the device through curl on the command line. I can get the status, I can open and close the doors. But everything still shows as NULL in the items.
My system was at 4.3.4 so I’ve updated it to 4.3.5 - When I did that all marketplace bindings, I had running, including the tailwind binding were no longer installed and I had to install them again. With that, the tailwind binding is still working for 4.3.5 release.
Wondering if my instructions for creating items may not be correct…
Couple things we could try.
Completely remove the tailwind binding and any items that were configured for it. Then install the binding. Use Auto discover to find the controller, configure it.
Turn on debug for the Tailwind binding.
Then using the UI, create the door channel items your having issues with.
Review the log to see more details about the binding.
Someday I will try it again. Thank you for all the help, but I decided to go the HTTP Binding route and have it now working completely with that existing binding.
