-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command Syntax for friendly topics #73
Comments
I don't think it's a bug, probably just poor documentation that could probably be more clear. The documentation does hint at the right thing to do in the example:
Basically, the expectation is the the template defines topics with the suffix of _state, and the engine automatically creates corresponding _command topics, so in your example it should be (just did one for and example):
And then you can get state at tuya/waermepumpe/SetTemp_state and send commands to tuya/waermepumpe/SetTemp_command. |
Thank you, that's it! So I just added _state to all of my topics and it works now "as expected" ;-) I read the example several times and misunderstood the description. On the other hand now that you explained it in other words the documentation seems quite clear. Thank you for your unbelievable fast support! |
Glad you got it working. |
I cannot figure out how to send commands to friendly topics that I have defined with a Generic Device Template. There is no clue in the documentation either.
First of all, I have set up a Fairland Inverter Heat Pump (for my pool) and this is my devices.conf file:
What is working:
What is not working:
So is this a bug? I had a look into the code and the function processDeviceCommand is only called when topicLength is 3 AND there is the word "command" in the command topic. I cannot figure out how to do this with topicLength 3. "tuya/waermepumpe/SetTemp/command" has a length of 4 ...
Btw. sorry to hear that this project is in maintenance mode. I am quite new to Tuya devices and I really appreciate this for communicating to my heat pump and integrating into FHEM - it already works quite well! I am aware that this project depends on tuyapi - but as long as it is working I will stick to it (I tried cloud API, but my device does not support all functions yet) and appreciate all the work done! Thank's a a lot!
The text was updated successfully, but these errors were encountered: