Having started from scratch with my smart blinds setup, a fully assembled kit received only a few days back, I got all the way through the instructions to the point of testing the motor using MQTT.fx. I was able to send instruction and see the response, including the motor actually moving. I then tried to connect The MQTT Mosquito server to OpenHAB 2 without any success. However, in trying to get this connection working something has gone wrong with the MQTT part, or possibly the motor (but I can’t see how to locate the problem). I need to get the motor responding again before attempting to connect to OpenHAB 2.
So, now from MQTT.fx I can see in the correct “Topic” (which I have cut/pasted from the web interface for the controller - this web page loads fine proving the controller is online at the expected IP). When the controller is powered off, and I publish anything to the Topic, I see it send but get no response (as expected). As soon as it is powered on, the Topic/Status appears, and it brings back the value 52. This suggests to me that the controller is successfully talking to my Mosquito broker. However, it doesn’t matter what command (number from 0-100) I send to the device, the status comes back each time as 52, and the motor does not move.
I’ve reset the config on the device (ie, wiped it via the jumpers, given it a different name, topic, even changed the speed), can still connect to it via it’s web page, and also still get the same responses via MQTT.fx. Also gone through the instructions to re-flash the controller with the v2 firmware, but this made no difference. I’ve also tried a new power supply for the motor/controller. I’m now thinking that the motor itself is the problem but wondering if that’s the kind of behaviour you’d expect to see if that was the case? Is there anything else I can do to test? I’ve tried everything I can find on this forum…
Thanks for any ideas, this is really frustrating!!