Different codes while learning... normal? #36
Comments
|
Hi. I assume from the context that you are using the tasker version, not the rm bridge. I always had trouble with the tasker plug-in and have used the rm bridge since trying them both and seetting it up. I understand there may be useful reasons to tie it all to tasker though. I may be a little rusty in helping and ask others who may be using the tasker plug-in to also assist if anyone has seen it and solved this. Are the learned codes shorter in tasker than in the bridge directly? There may be some sort of character limit cutoff problem. I can't imagine devices like these using rolling codes so I'd hope that's not it. I have only a couple of less than useful suggestions but we'll see if they help.First, thank you for narrowing down which step is different. It seems like the issue is when codes are recorded, not as they pass through the smart things handler. Does the author of the tasker plug-in also have a forum or help address? He may be better equipped to assist directly with that step. Also, some people with newer broadlink devices are having trouble with recent firmware working with these plug-in apps. I'm not sure if this applies to you or not, but unfortunately no one has solved that one yet. A couple other options may be to try the rm bridge version instead of tasker, or I think the author of the tasker plug-in also has added some direct compatibility to Alexa but not smart things. Lastly, if you're willing to get creative and call everything a tv power switch, the broadlink app can be forced to do more than you would expect - again with Alexa but not smart things. I'm not sure what you're trying to do so if it's not Alexa, getting this all working will be best for other smart things purposes.Sorry if this is not very helpful. Becky On Jan 2, 2018 6:49 AM, Anders Wasen <[email protected]> wrote:First of all Thank you!
I really appreciate all you hard work and this is way cool to play around with! :)
So, to my question... I have everything setup and it works for all IR stuff (this far) and some RF stuff.
I do have issues with my sunshades and projector lift though (433 MHz RF). The RM Pro learns the codes and seems to "get" the remotes. The sunshades works sometimes directly from the RM (but not through the Tasker).
I setup a few identical buttons in RM App and learned the RF code for the Projector lift and then exported the codes from the App to be able to view them.
I can them see that the codes differ a lot, out of the 5 "learnings" I did all codes are different and the shortest is 120 characters (hex) while the longest is 1100 characters and the rest somewhere in between.
Is this normal?
Or would it indicate that the Projector lift is using some "coded" signal that is altered each time?
The same happens for the sunshades but the strange thing is that they sometimes (1 of maybe 100 attempts) works from the RM App (but never through Tasker/Alexa).
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Thanks for getting back to me and I realize now that my question is a bit "fuzzy"... I want to hook up my Alexa with my RM Pro (rev. 3) eventually and have tested a few minor things like TV on/off which have worked fine. I have tried various solutions to hook up my RM Pro as a http bridge and will most likely stick with the RM Bridge moving forward... I also have setup Home-assistant.io to be able to extract the codes by learning. I too have a hard time beleiving the sunshades and the projector lift both would be using rolling codes... So, the problem is really with the RM box and why I get different codes for the same button when I "record" them. I would have expected that all buttons in the App then would have the same code recorded but exporting the buttons from the App using getBroadlinkSharedData.py (https://github.com/NightRang3r/Broadlink-e-control-db-dump) I can see that all five buttons from the App which should be the same si not... So the question I guess is; how can I get the correct code? |
|
I did some testing on the sunshades and these are the codes I get. They are all quite similar but differ each time... None of these works though... :( Samples from RM Bridge:
Samples from Home-assistant.io:
Sample from native RM App: |
|
But on the other hand I now tested another RF plug which have been working all along and the first time I do "learing" I get the code:
Then I do learning again on the same button and then I get:
Both of the codes ARE working! Clearly the codes does not need to be identical to work... :o |
First of all Thank you!
I really appreciate all you hard work and this is way cool to play around with! :)
So, to my question... I have everything setup and it works for all IR stuff (this far) and some RF stuff.
I do have issues with my sunshades and projector lift though (433 MHz RF). The RM Pro learns the codes and seems to "get" the remotes. The sunshades works sometimes directly from the RM (but not through the Tasker).
I setup a few identical buttons in RM App and learned the same RF code for the Projector lift and then exported the codes from the App to be able to view them.
I can them see that the codes differ a lot, out of the 5 "learnings" I did all codes are different and the shortest is 120 characters (hex) while the longest is 1100 characters and the rest somewhere in between.
Is this normal?
Or would it indicate that the Projector lift is using some "coded" signal that is altered each time?
The same happens for the sunshades but the strange thing is that they sometimes (1 of maybe 100 attempts) works from the RM App (but never through Tasker/Alexa).
The text was updated successfully, but these errors were encountered: