# Node-red-contrib-broadlink-control v1.0.8

**URL:** <https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447>\
**Category:** Share Your Nodes\
**Created:** [22 March 2020 08:49 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447 "2020-03-22T08:49:31Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![mlfunston](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mlfunston/32/15841_2.png) [@mlfunston](https://discourse.nodered.org/u/mlfunston)\
**Post date:** [22 March 2020 08:49 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/1 "2020-03-22T08:49:31Z")

</div>

A set of node-red nodes to manage the Broadlink [http://www.ibroadlink.com/](http://www.ibroadlink.com/) RM series of IR Controllers and for home automation. A cost effective way to control Air Conditioners, TV's, Audio equipment and many more like a universal remote control unit.

[node-red-contrib-broadlink-control](https://flows.nodered.org/node/node-red-contrib-broadlink-control)

**Latest version released - v1.0.8**

- Enhancement: Add new device ID's for RM Pro 4 - Needs testing. May need additional headers for RM4
- Enhancement: Readme Updated to fix image links
- Enhancement: [ALPHA] Added RM IR Receiver Node for issue [#15](https://github.com/mlfunston/node-red-contrib-broadlink-control/issues/15) (Limited Functionality)
- Enhancement: Improve error handling in RMNode for issue [#12](https://github.com/mlfunston/node-red-contrib-broadlink-control/issues/12)
- BUGFIX: Possible fix for issue [#7](https://github.com/mlfunston/node-red-contrib-broadlink-control/issues/7) for incorrect energy reading on SP2 - Needs testing from users
- BUGFIX: Improve error handling in MP1Node for issue [#11](https://github.com/mlfunston/node-red-contrib-broadlink-control/issues/11) and add improved help text
- BUGFIX: Improve error handling in RMNode for data timeouts - issue [#14](https://github.com/mlfunston/node-red-contrib-broadlink-control/issues/14)
- BUGFIX: Fix typo on msg.payload.fix that is returned on send of data to RMNode

---

<div class="post-metadata">

**Author:** ![get-command](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/get-command/32/25038_2.png) [@get-command](https://discourse.nodered.org/u/get-command)\
**Post date:** [26 March 2020 07:59 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/2 "2020-03-26T07:59:31Z")

</div>

Thank you very much for this Release Update!

In the previous Version i can't learn RF 433 MHz signals. This function now with the new release 1.0.8 with most devices. but i have one 433 MHz devices, that not possiible to learn the RF-Code. The Code is very long, its end "43,6,6..." .why not everything is recorded/ learned and ends with "..."? do you have an idea what i can do?

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [26 March 2020 09:44 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/3 "2020-03-26T09:44:24Z")

</div>

where are you seeing the ... ? If in the debug window - it naturally truncates long messages - if you also send to the console you should see the whole message. If not in debug then... yes back to the author 🙂

---

<div class="post-metadata">

**Author:** ![get-command](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/get-command/32/25038_2.png) [@get-command](https://discourse.nodered.org/u/get-command)\
**Post date:** [26 March 2020 10:17 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/4 "2020-03-26T10:17:21Z")

</div>

this is in the debug window 😟

sorry - i'm not a NodeRed profi. How can I send this to the console so that I can see everything?

---

<div class="post-metadata">

**Author:** ![mlfunston](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mlfunston/32/15841_2.png) [@mlfunston](https://discourse.nodered.org/u/mlfunston)\
**Post date:** [26 March 2020 10:21 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/5 "2020-03-26T10:21:51Z")

</div>

Yes, the debug window will cut off the string.  
What do you want to do with the message once you receive it?  
Just pass it on to the next node in your flow and it should process fine.

---

<div class="post-metadata">

**Author:** ![get-command](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/get-command/32/25038_2.png) [@get-command](https://discourse.nodered.org/u/get-command)\
**Post date:** [26 March 2020 10:32 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/6 "2020-03-26T10:32:38Z")

</div>

> [@mlfunston](#):
>
> What do you want to do with the message once you receive it?

After recording the RF code, I link it to a trigger node, which I use to control a radio-controlled socket.

I will test that later. I just have to find out what kind of nodes can display the full text with the rf code.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [26 March 2020 11:06 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/7 "2020-03-26T11:06:25Z")

</div>

> [@get-command](#):
>
> How can I send this to the Konsolo so that I can see everything?

In the debug node select the checkbox for sending to the console.

---

<div class="post-metadata">

**Author:** ![get-command](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/get-command/32/25038_2.png) [@get-command](https://discourse.nodered.org/u/get-command)\
**Post date:** [26 March 2020 11:51 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/8 "2020-03-26T11:51:21Z")

</div>

![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/5/458cfb625c2871e5855d726502c30f7db73edc9e.png)

Thank you for Help

where can i see the console after i have activated it in the debug node?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [26 March 2020 12:18 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/9 "2020-03-26T12:18:41Z")

</div>

The command `node-red-log` should show it, though it does depend on how you installed and run node-red. Run that command and leave the terminal open and it will add the output to it.  
If you haven't got that command then stop node red and start it in a terminal (perhaps you already do that) in which case it will appear there.

---

<div class="post-metadata">

**Author:** ![get-command](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/get-command/32/25038_2.png) [@get-command](https://discourse.nodered.org/u/get-command)\
**Post date:** [26 March 2020 21:12 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/10 "2020-03-26T21:12:57Z")

</div>

great thanks! now it worked. 👍 👍 👍 👍 👍 👍 👍 👍 👍 👍

---

<div class="post-metadata">

**Author:** ![get-command](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/get-command/32/25038_2.png) [@get-command](https://discourse.nodered.org/u/get-command)\
**Post date:** [27 March 2020 10:49 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/11 "2020-03-27T10:49:30Z")

</div>

I have another question. Maybe someone knows:  
how can i integrate the motion sensor as a trigger in node red for example with alarm kit S1. Is that possible?

---

<div class="post-metadata">

**Author:** ![mlfunston](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mlfunston/32/15841_2.png) [@mlfunston](https://discourse.nodered.org/u/mlfunston)\
**Post date:** [27 March 2020 11:00 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/12 "2020-03-27T11:00:31Z")

</div>

As it is at the moment, you would need an inject node to query the S1 node every x seconds. It doesn't have a monitoring component built in.

---

<div class="post-metadata">

**Author:** ![get-command](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/get-command/32/25038_2.png) [@get-command](https://discourse.nodered.org/u/get-command)\
**Post date:** [27 March 2020 11:08 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/13 "2020-03-27T11:08:49Z")

</div>

do you know how to do that?

---

<div class="post-metadata">

**Author:** ![realjax](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/realjax/32/895_2.png) [@realjax](https://discourse.nodered.org/u/realjax)\
**Post date:** [14 April 2020 10:23 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/14 "2020-04-14T10:23:20Z")

</div>

Has anyone here found a workaround maybe for the timeout errors that suddenly occur with this node and the RM mini 3 ?

---

<div class="post-metadata">

**Author:** ![mlfunston](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mlfunston/32/15841_2.png) [@mlfunston](https://discourse.nodered.org/u/mlfunston)\
**Post date:** [22 April 2020 12:21 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/15 "2020-04-22T12:21:20Z")

</div>

I have made an update to this and re-published as v2.0.1 so this should now address these issues. Please update and see how it goes.

---

<div class="post-metadata">

**Author:** ![realjax](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/realjax/32/895_2.png) [@realjax](https://discourse.nodered.org/u/realjax)\
**Post date:** [22 April 2020 13:27 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/16 "2020-04-22T13:27:54Z")

</div>

Actually, the issue I had can only be resolved if the broadlink node now also supports a setup procedure so it can circumvent the cloud-operations-only-allowed mode. A mode that the Android Broadlink app forced upon my RM..

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [21 May 2020 08:49 UTC](https://discourse.nodered.org/t/node-red-contrib-broadlink-control-v1-0-8/23447/17 "2020-05-21T08:49:32Z")

</div>

This topic was automatically closed after 60 days. New replies are no longer allowed.