iobroker-community-adapters / iobroker.broadlink2 Goto Github PK

Dear,

I'd like to put the devices in a separated IoT network segement (IP range/VLAN) to prevent any negative impact of these. The challange is that the iobroker is in another network segment than the devices and so it scans only it's own subnet - means the devices will not be found.

I'd like to rise the feature request, to be able to define the subnet(s) where broadlink devices can be so that the scanning is extended to all defined subnets. This will increase IT security dramatically because I can put the Broadlink devices in a separted network with limited firewall access.

Thanks a lot!

Rainer

Hello,

I bought a BroadLink RM PRO+, some kind of latest version.

According to this youtube video there are some issues with sending, learning etc. RF signals with this Broadlink version. https://www.youtube.com/watch?v=FWRrQ-_uwEs

And indeed, infrared signals are learned by this adapter here but nothing from 433Mhz.

Does somebody has a clue how to fix this?

Thanks for your Help

Hallo, ich habe 2 Broadlink A1 EAIR im ioBroker. Einer davon ist immer unerreichbar. Obwohl er über die App bzw. per Ping erreichbar ist.
Ich lasse den Adapter jetzt jede Stunde neu starten. Da sind beide online. Kurz darauf dann nur noch einer.

Das erscheint dann im Log
- �[33mwarn�[39m: broadlink2.0 Device A1:Broadlink-EAIR-c7-60-82 not reachable

Wobei nicht immer der gleiche offline geht.

Gibt es da etwas besseres ausser den Adapter immer neu starten zu lassen?

Besten Dank für deine Hilfe

Hi there,
I´ve got some problems with my broadlink2 Adapter.

I´ve learnd many devices. Since cupple of days, it´s no more possible to learn new devices. If I use "Learn" or "RFLearn" and press any button in my broadlink-App nothing happens.
The App is working without problems.

I´ve restated the iobroker and reinstalled the Adapter several times.
Version 1.9.1 is installed. I also tried to downgrade but when I import the folder "L" the adapter updates to 1.9.1

Can you help using the learn function?

THX!

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/frankjoke/ioBroker.broadlink2

• [E106] Title should not have word "adapter" in the name. It is clear, that this is adapter. Now: Broadlink2 (RM++, SP++, A1) Adapter for multiple W-Lan devices
• [E115] No license found in io-package.json
• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.broadlink2"

ERR:["E106","E115","E201"]:ERR

Thanks,
your automatic adapter checker.

Sometimes broadlink RM temperature is 249. It's unreal temperature.

Hi all,

When learning and sending signals with the plugin I frequently get the below error, and the adapter restarts itself.

Device: Broadlink RM Pro +
Adapter Version : 1.9.0
OS: Ubuntu 16.04.3 LTS

Let me know if more info is needed to reproduce.

broadlink2.0 | 2018-02-15 15:07:58.718 | info | Adapter broadlink2.0 started and found 1 devices named 'RM:'.
-- | -- | -- | --
broadlink2.0 | 2018-02-15 15:07:53.827 | info | Device RM: dedected: 192.168.5.234,IPv4,80,128,10141,rm,RM:,RM3 Pro Plus,9d:27:ea:5:a8:c0
broadlink2.0 | 2018-02-15 15:07:53.666 | info | Discover UDP devices for 10sec on broadlink2.0
broadlink2.0 | 2018-02-15 15:07:53.550 | info | starting. Version 1.9.0 in /opt/iobroker/node_modules/iobroker.broadlink2, node: v6.12.2
host.monolith-nas | 2018-02-15 15:07:53.186 | info | instance system.adapter.broadlink2.0 started with pid 12005
mqtt.0 | 2018-02-15 15:07:28.912 | info | send2Server broadlink2.0.RM:.L.Mute[broadlink2/0/RM:/L/Mute]
mqtt.0 | 2018-02-15 15:07:28.911 | info | send2Server broadlink2.0.RM:.L.Mute[undefined]
host.monolith-nas | 2018-02-15 15:07:23.168 | info | Restart adapter system.adapter.broadlink2.0 because enabled
host.monolith-nas | 2018-02-15 15:07:23.168 | error | instance system.adapter.broadlink2.0 terminated with code 0 (OK)
Caught | 2018-02-15 15:07:23.168 | error | by controller[0]:     at processImmediate [as _immediateCallback] (timers.js:617:5)
Caught | 2018-02-15 15:07:23.168 | error | by controller[0]:     at tryOnImmediate (timers.js:645:5)
Caught | 2018-02-15 15:07:23.168 | error | by controller[0]:     at runCallback (timers.js:672:20)
Caught | 2018-02-15 15:07:23.168 | error | by controller[0]:     at Immediate. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3194:38)
Caught | 2018-02-15 15:07:23.167 | error | by controller[0]:     at Adapter.emit (events.js:191:7)
Caught | 2018-02-15 15:07:23.167 | error | by controller[0]:     at emitTwo (events.js:106:13)
Caught | 2018-02-15 15:07:23.167 | error | by controller[0]:     at Adapter.adapter.on.on.on.on.on (/opt/iobroker/node_modules/iobroker.broadlink2/myAdapter.js:114:98)
Caught | 2018-02-15 15:07:23.164 | error | by controller[0]: TypeError: Cannot read property 'then' of undefined
broadlink2.0 | 2018-02-15 15:07:23.149 | info | terminating
broadlink2.0 | 2018-02-15 15:07:23.144 | error | at processImmediate [as _immediateCallback] (timers.js:617:5)
broadlink2.0 | 2018-02-15 15:07:23.144 | error | at tryOnImmediate (timers.js:645:5)
broadlink2.0 | 2018-02-15 15:07:23.144 | error | at runCallback (timers.js:672:20)
broadlink2.0 | 2018-02-15 15:07:23.144 | error | at Immediate. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3194:38)
broadlink2.0 | 2018-02-15 15:07:23.144 | error | at Adapter.emit (events.js:191:7)
broadlink2.0 | 2018-02-15 15:07:23.144 | error | at emitTwo (events.js:106:13)
broadlink2.0 | 2018-02-15 15:07:23.144 | error | at Adapter.adapter.on.on.on.on.on (/opt/iobroker/node_modules/iobroker.broadlink2/myAdapter.js:114:98)
broadlink2.0 | 2018-02-15 15:07:23.144 | error | TypeError: Cannot read property 'then' of undefined
broadlink2.0 | 2018-02-15 15:07:23.143 | error | uncaught exception: Cannot read property 'then' of undefined
mqtt.0 | 2018-02-15 15:07:23.127 | info | send2Server broadlink2.0.RM:.L.MD[broadlink2/0/RM:/L/MD]

Guten Tag,
ursprünglich wurde mein broadlink rm Pro mit dem namen RM:Broadlink_RMPROPLUS-f4-3c-47 erkannt
aber jetzt erkennt er nur noch die ip RM:192-168-3-140 was natürlich dazu führt das er die befehle nicht mehr ausführen kann da sie unter einem anderen gerät sind.
wie kann ich das wieder beheben das er statt die ip den mac adressen teil nimmt?

Log:

Screenshot

Can you help me, please?

For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268

Manche SC1 lassen sich schalten, manche nicht.
Habe aktuell 5 Stück davon. 2 funktionieren, die anderen 3 tauchen entweder nicht im iobroker auf oder die states reagieren nicht

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/frankjoke/ioBroker.broadlink2

• [E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.broadlink2"

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Hi,

I just bought the "Broadlink RM Pro+ Wi-Fi" from Amazon to use with iobroker.

Here is the link of the device on amazon: https://www.amazon.de/gp/product/B07KZP7PZJ

I configured it via the supplied app and it's I can ping it in my network. It says the firmware version is "v52" via the app.

Via the app I can also control any IR devices I have.

Sadly when I try to discover the device via iobroker it isn't found. The broadlink is also in the same network as my iobroker installation.

How exactly is the device discovered? Is there anything I can do to troubleshoot it?

Thank you!

Iam trying to use this adapter with javascript engine and i get the following error in my log

I am using setState(..., true); in ma Javascript to trigger a learned state

Let me know if you need some further information

Hallo,

allem Anschein nach ist das genau der Adapter den ich brauche, leider nach Stunden langem rumprobieren, konnte ich keine Erfolge verzeichnen.

Mir fehlt etwas an Grundverständnis. Meine Steckdose wird einfach nicht erkannt, bzw nicht gefunden.

Mein Vorgehen:

• Ich halte lange die Taste an der Steckdose gedrückt, bis diese anfängt schnell zu blinken.
• ich lasse die Taste los und starte den Adapter, damit die Suche aktiviert wird
• nach 10 Sekunden sehe ich, dass nichts gefunden wurde

Frage:

Wie muss ich es machen, damit die Steckdose endlich gefunden wird?

Die Buttons type: 'string' führen zu einer Warnung im Javascript-Adapter

javascript.0 | 2017-09-22 07:38:51.977 | warn | Wrong type of broadlink2.0.RM2:fernbedienung-wz.LearnedStates.TV aus: "boolean". Please fix, while deprecated and will not work in next versions.
-- | -- | -- | --
javascript.0 | 2017-09-22 07:38:50.473 | warn | at Object. (script.js.Gerätezustände.TV_an_oder_aus:9:5)
javascript.0 | 2017-09-22 07:38:50.464 | warn | Wrong type of broadlink2.0.RM2:fernbedienung-wz.LearnedStates.TV exit: "boolean". Please fix, while deprecated and will not work in next versions.

Ich habe die Buttons schon immer so Betätigt:

setState("broadlink2.0.RM2:fernbedienung-wz.LearnedStates.TV anschalten"/*TV anschalten*/, true);

Dadurch, dass der type nicht mehr boolean ist, erscheint die Warnung immer wieder. Warum wurde das geändert?

Grüße,
ldittmar

If you use the switching status in a javascript trigger, the trigger is triggered even if the notReachable status is changed. It would be better if the switching status is not the folder node but a separate object in the folder.

Examples: https://github.com/ioBroker/ioBroker.discovery/tree/master/lib/adapters

And change io-package.json => common.type of ioBroker.xs1 to iot-systems

You can write a support email to github to the remove fork link to ioBroker.template.
https://github.com/contact

Hi,

I just received my broadlink RM pro+ and tried to connect it to the adapter; I had previously bought an rm mini 3, which I returned because I couldn't pair it.

After installing the adapter, I can only fill these fields

• Poll switches every x seconds (0 = no polling)
• Neues Gerätetype(n) definieren: devicetype=class, ... (class = A1,MP1,RM,RMP,S1C,SP1,SP2,SP3P,T1)
• Geräte umbenennen: 'SP:0x7547_34:ea:34:bd:67:a1=SteckdoseHeizung, ...'
• Szenen können aus gelernten States, Szenen, Sender.CODE_xxx oder einer Verzögerung in Millisekunden bestehen.
• add Szenen-Definition:
• Name der Szene Szene, Kommandos mit ',' getrennt
• delete
• add
• States die mit gelernten Daten oder Sequenzen Ein/Aus geschaltet werden. Kann eine Liste mit ',' getrennt sein wo das 1. signal gesendet wird aber alle schalten
• Name des States Ein-Signale Aus-Signale
• delete

I didn't find a way to enter my broadlink's IP address. Downloaded the system.adapter.broadlink2.0.json file and inspected it, but there doesn't seem to be a way to manually add the IP, either.

I tried entering the IP in native: new and native:rename, just to see if that would work (even though I didn't think it would). It didn't.

Do I have to do something to my broadlink before using this adapter (flash some alternative firmware or similar)? I have used their app to add the device to my network. I was able to learn codes via the app and control my device, but those new commands do not show up under objects > broadlink.2.0 -> ....

The adapter itself is both connected and alive.

Sorry if this is a stupid question, but I just can't figure out how to connect my device and then control it via ioBroker. I don't know if it matters, but the broadlink is in a VLAN that does not have internet connection. I thought that it might refuse to work without internet (for broadlink spying on their users reasons), but temporarily allowed internet and could still not use it in ioBroker. Also, learning and sending IR codes works when internet access is forbidden for this device.

Can you please help me? Thanks for your support.

EDIT: weirdly enough, ioBroker tells me that I have installed version 2.0.0 and that 1.8.0 is the current version..?!

Hi,

I would propose "bradlink2" as active one and broadlink is the inactive one.

Your adapter has the wrong type in the io-package. It must be "multimedia". Please fix.

Addition it would be a great idea to check the discovery implementation in the discovery adapter, update it and let it install broadlink2 instead of broadlink currently. What you think?

Ingo

The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466

Hallo,
das Umbenennen Feature kann den JSON-Baum zerstören,
habe aus versehen anstelle von XX-XX-XX.... XX.XX.XX verwendet.

Danach ging nix mehr. Sollte vlt. abgefangen werden.

mit der aktuellen V2Beta beendet sich iobroker nach einem scan, der broadlink2 Adapter findet auch ganz viele Geraete auf einmal..
019-03-25 19:26:50.696 - info: host.iobroker instance system.adapter.broadlink2.0 started with pid 26263 2019-03-25 19:26:51.041 - debug: broadlink2.0 objectDB connected 2019-03-25 19:26:51.055 - debug: broadlink2.0 statesDB connected 2019-03-25 19:26:51.068 - info: broadlink2.0 starting. Version 1.9.9 in /opt/iobroker/node_modules/iobroker.broadlink2, node: v8.15.1 2019-03-25 19:26:53.711 - info: broadlink2.0 broadlink2 initialization started... 2019-03-25 19:26:53.711 - info: broadlink2.0 broadlink2 starting main... 2019-03-25 19:26:53.716 - info: broadlink2.0 UDP socket listening on 0.0.0.0:15001 2019-03-25 19:26:53.717 - info: broadlink2.0 Discover Broadlink devices for 10sec on broadlink2.0 2019-03-25 19:26:53.910 - info: broadlink2.0 Device RM:0x272a_34:ea:34:c7:c0:bb dedected: address=192.168.178.87, mac=34:ea:34:c7:c0:bb, typ=rmp, id=0x272a devtype=RM2 Pro Plus 2019-03-25 19:26:54.315 - info: broadlink2.0 Device RM:0x2737_34:ea:34:41:45:14 dedected: address=192.168.178.88, mac=34:ea:34:41:45:14, typ=rm, id=0x2737 devtype=RM Mini 2019-03-25 19:26:54.511 - info: broadlink2.0 Device SP:0x2728_b4:43:0d:f0:d0:67 dedected: address=192.168.178.177, mac=b4:43:0d:f0:d0:67, typ=sp2, id=0x2728 devtype=OEM branded SPMini2 2019-03-25 19:27:08.794 - info: Adapter broadlink2 still running 2019-03-25 19:27:09.956 - info: broadlink2.0 Close all connections... 2019-03-25 19:27:09.957 - info: broadlink2.0 Adapter disconnected and stopped with dostop(false) and callback(true) 2019-03-25 19:27:09.958 - warn: broadlink2.0 Adapter will exit in latest 1 sec with code false! 2019-03-25 19:29:18.014 - info: history.0 enabled logging of broadlink2.0.RM:Broadlink-RMMINI-41-45-14.Temperature (Count=153), Alias=false 2019-03-25 19:29:18.014 - info: history.0 enabled logging of broadlink2.0.RM:Broadlink-RMPLUS.Temperature (Count=154), Alias=false 2019-03-25 19:29:30.132 - info: host.iobroker object change system.adapter.broadlink2.0 2019-03-25 19:29:30.173 - info: host.iobroker instance system.adapter.broadlink2.0 started with pid 27304 2019-03-25 19:29:30.749 - debug: broadlink2.0 objectDB connected 2019-03-25 19:29:30.883 - debug: broadlink2.0 statesDB connected 2019-03-25 19:29:30.923 - info: broadlink2.0 starting. Version 1.9.1 in /opt/iobroker/node_modules/iobroker.broadlink2, node: v8.15.1 2019-03-25 19:29:30.948 - debug: broadlink2.0 Adapter broadlink2.0 starting. 2019-03-25 19:29:35.621 - debug: broadlink2.0 broadlink2 received 13339 objects with config ip,scenes,switches,poll,new,lang,latitude,longitude 2019-03-25 19:29:35.626 - info: broadlink2.0 Discover UDP devices for 10sec on broadlink2.0 2019-03-25 19:29:35.627 - debug: broadlink2.0 Config IP-Address end to remove: .fritz.box 2019-03-25 19:29:35.768 - debug: broadlink2.0 Change _NewDeviceScan to true with ack: true 2019-03-25 19:29:35.887 - info: broadlink2.0 Device SP:BroadLink-SPmini-T1-2 dedected: 192.168.178.178,IPv4,80,128,10024,sp2,SP:BroadLink-SPmini-T1-2,SPMini2,28:27:c0:a8:b2:b2 2019-03-25 19:29:35.898 - info: broadlink2.0 Device RM:Broadlink-RMPLUS dedected: 192.168.178.87,IPv4,80,128,10026,rm,RM:Broadlink-RMPLUS,RM2 Pro Plus,2a:27:57:b2:a8:c0 2019-03-25 19:29:36.300 - info: broadlink2.0 Device RM:Broadlink-RMMINI-41-45-14 dedected: 192.168.178.88,IPv4,80,128,10039,rm,RM:Broadlink-RMMINI-41-45-14,RM Mini,37:27:58:b2:a8:c0 2019-03-25 19:29:41.966 - debug: broadlink2.0 Change _NewDeviceScan to false with ack: true 2019-03-25 19:29:42.041 - debug: broadlink2.0 Adapter has 79 old states! 2019-03-25 19:29:42.047 - warn: broadlink2.0 device SP:BroadLink-SPmini-T1-1 not found, please rescan later again or delete it! It was: 192.168.178.177,IPv4,80,128,10024,sp2,SP:BroadLink-SPmini-T1-1,SPMini2,28:27:c0:a8:b2:b1 2019-03-25 19:29:42.053 - warn: broadlink2.0 device RM:0x272a_34:ea:34:c7:c0:bb not found, please rescan later again or delete it! It was: 192.168.178.87,80,7,10026,[object Object],34:ea:34:c7:c0:bb,rmp,RM:0x272a_34:ea:34:c7:c0:bb,0x272a,RM2 Pro Plus 2019-03-25 19:29:42.054 - warn: broadlink2.0 device RM:0x2737_34:ea:34:41:45:14 not found, please rescan later again or delete it! It was: 192.168.178.88,80,7,10039,[object Object],34:ea:34:41:45:14,rm,RM:0x2737_34:ea:34:41:45:14,0x2737,RM Mini 2019-03-25 19:29:42.066 - debug: broadlink2.0 Change SendScene to ' ' with ack: true 2019-03-25 19:29:42.068 - debug: broadlink2.0 Poll every 30 secods. 2019-03-25 19:29:42.068 - info: broadlink2.0 Adapter broadlink2.0 started and found 3 devices named 'SP:BroadLink-SPmini-T1-2', 'RM:Broadlink-RMPLUS', 'RM:Broadlink-RMMINI-41-45-14'. 2019-03-25 19:29:42.068 - info: broadlink2.0 3 were not found: SP:BroadLink-SPmini-T1-1,RM:0x272a_34:ea:34:c7:c0:bb,RM:0x2737_34:ea:34:41:45:14 2019-03-25 19:29:42.145 - info: history.0 enabled logging of broadlink2.0.RM:Broadlink-RMPLUS.Temperature, Alias=false 2019-03-25 19:29:42.150 - debug: broadlink2.0 Change RM:Broadlink-RMPLUS.Temperature to 21.4 with ack: true 2019-03-25 19:29:42.213 - info: history.0 enabled logging of broadlink2.0.RM:Broadlink-RMMINI-41-45-14.Temperature, Alias=false 2019-03-25 19:29:44.065 - debug: broadlink2.0 Change SP:BroadLink-SPmini-T1-2.notReachable to false with ack: true 2019-03-25 19:29:44.165 - debug: broadlink2.0 Change RM:Broadlink-RMMINI-41-45-14.notReachable to false with ack: true 2019-03-25 19:29:44.215 - debug: broadlink2.0 Change SP:BroadLink-SPmini-T1-1.notReachable to false with ack: true 2019-03-25 19:29:44.265 - debug: broadlink2.0 Change RM:0x272a_34:ea:34:c7:c0:bb.notReachable to false with ack: true 2019-03-25 19:29:44.315 - debug: broadlink2.0 Change RM:0x2737_34:ea:34:41:45:14.notReachable to false with ack: true 2019-03-25 19:30:04.730 - debug: broadlink2.0 system.adapter.admin.0: logging true 2019-03-25 19:30:14.221 - warn: broadlink2.0 Device SP:BroadLink-SPmini-T1-1 not reachable 2019-03-25 19:30:14.234 - debug: broadlink2.0 Change SP:BroadLink-SPmini-T1-1.notReachable to true with ack: true 2019-03-25 19:30:14.276 - warn: broadlink2.0 Device RM:0x272a_34:ea:34:c7:c0:bb not reachable 2019-03-25 19:30:14.278 - debug: broadlink2.0 Change RM:0x272a_34:ea:34:c7:c0:bb.notReachable to true with ack: true 2019-03-25 19:30:14.321 - warn: broadlink2.0 Device RM:0x2737_34:ea:34:41:45:14 not reachable 2019-03-25 19:30:14.323 - debug: broadlink2.0 Change RM:0x2737_34:ea:34:41:45:14.notReachable to true with ack: true 2019-03-25 19:30:16.737 - debug: broadlink2.0 system.adapter.admin.0: logging false 2019-03-25 19:30:16.873 - debug: broadlink2.0 system.adapter.admin.0: logging true 2019-03-25 19:30:27.885 - info: host.iobroker object change system.adapter.broadlink2.0 2019-03-25 19:30:27.887 - debug: broadlink2.0 Adapter disconnected and stopped with dostop(false) and callback(true) 2019-03-25 19:30:27.885 - info: host.iobroker "system.adapter.broadlink2.0" disabled 2019-03-25 19:30:27.885 - info: host.iobroker stopInstance system.adapter.broadlink2.0 2019-03-25 19:30:27.885 - info: host.iobroker stopInstance system.adapter.broadlink2.0 killing pid 27304 2019-03-25 19:30:27.915 - info: host.iobroker instance system.adapter.broadlink2.0 terminated with code 0 (OK)

Hi,

Gerät wird nicht mehr erkannt, früher ging es, nach dem Neuaufsetzen wird das Gerät wohl erkannt, es erscheint aber kein entsprechendes Objekt.

LOG:
Device Un:RMPROPLUS-43-10-57 dedected: 192.168.178.60,IPv4,80,128,10141,unknown,Un:RMPROPLUS-43-10-57,9d:27:3c:b2:a8:c0

Der workaround mit 0x27A9: 'RM3 Pro Plus' in broadlink_fs.js ist wol nicht mehr valide, da ich nur broadlink_fj.js finde und hier keine Referenzewerte drinstehen - oder ich sie nicht sehe.

Using version 1.6.0, it is not possible to work with a Broadlink RM-Pro OEM device. This device will be identified with "unknown", therefore further configuration and usage is not possible.

It seems, that this device (10135) is not defined in the broadlink_fj.js

Please add 0x2797: 'RM Pro (OEM)' to broadlink_fj.js

No export-import of the config is possible, Material not implemented, etc..

Guten Tag,
in der App von broadlink ist es möglich klimageräte komplett anzulernen wird das irgendwann auch für dein adapter rauskommen ?

würde mich sehr über eine antwort freuen

Hi All,
I found the Beok TGR 87 (https://www.aliexpress.com/item/Beok-TGR87-WiFi-Smart-Thermostat-Electric-Floor-Heating-16A-Temperature-Controller/32933138700.html) thermostat and I am wondering if anyone knows if it is working with the broadlink2 adapder, too?
Cheers,
Dominik

Hi,
Unfortunately i've found a problem with my RM3 Pro plus since a few days. The adapter don't find it anymore afte a few seconds. If i put it from power an repower the unit. Everything went well. After a short time the adapter lost the connection. If i restart the adapter i got the following log

It is not usefull to unplug the unit every few minutes. It will be nice if this could be fixed.

Thanks a lot in advance.

Mir ist in den letzten Tagen aufgefallen, dass der Broadlink Morgens die Lampen nicht mehr schaltet...dann lade ich das Backup vom Vortag und dann schaltet er ganz normal...das ganze funktioniert bis zum nächsten Tag...dann geht das Spiel von Vorne los...kann mir jemand Helfen?

Mit freundlichem Gruß

Hamtaro

Guten Tag,
sobald ich versuche den gerätename zu ändern kommt folgendes:

Eintrag : RM:0x272a_34:ea:??:??:??:???=RM:192-168-3-140

iobroker stürzt komplett wiederholt ab, wenn der neue Adapter läuft.
Die Version 1.9.1 hatte bisher keine solche Probleme verursacht.

Hi, can you please have a look at this post, I think the adapter needs your expertise for an extension.

http://forum.iobroker.net/viewtopic.php?f=24&t=7376&start=100#p117892

Nepomukl

Hi,
Clas Ohlshon is selling an smart Wifi bulb thats I think is an broadlink device.

Norway: https://www.clasohlson.com/no/Clas-Ohlson-Home,-WiFi-Smart-Bulb,-lysp%C3%A6re/38-8774
Sweden: https://www.clasohlson.com/se/WiFi-Smart-Bulb-Clas-Ohlson-Home/38-8774
German: https://www.clasohlson.com/de/WLAN-Smart-LED-Clas-Ohlson-Home/38-8774

IHC app is calling this device SB800TD

Data from the scripts:

broadlink_discovery
###########################################
Unknown
broadlink_cli --type 0x5043 --host 10.0.0.XX --mac 9efbd6770f78

Device file data (to be used with --device @filename in broadlink_cli) :
0x5043 10.0.0.XX 9efbd6770f78

###########################################

from broadlink:

<broadlink.device instance at 0x7fa5e4138200>

V. 1.9 installiert ohne Fehlermeldung
RM Pro+ mit SNr. 34xxxxx
Findet lt. Log ein unbekanntes Objekt namens UN:, kann weder anlernen noch erstellt er Datenpunkte. Möglicherweise hat Broadlink da wieder am Gerät geschraubt.
Mit der IOS App geht Anlernen und Bedienen einwandfrei.

Hi
Auch bei mir gleiches Problem. Ich vermute, dass es das letzte Update war - entweder IoBroker Adapter oder Broadlink. Leider erst zu spät gemerkt.
Interessant ist folgendes:

1. Weise IP via MAC zu -> IP ist unverändert.
2. WLAN Access Control auf die IP -> Bei Mac Änderung kein Zugriff aufs LAN
   Vorher Erkennung über IP, jetzt Erkennung über Mac (IP kommt nicht mehr vor. Im Namen stammt sie von mir). Die Mac am alten Adapter A9:... kenne ich nicht. Sie ist im Router weder für DHCP noch für Access Control frei. Definitiv würde diese Adresse nicht ins WLAN kommen. Keine Ahnung wo die her kommt.

Alt: ====================================
{
"from": "system.adapter.broadlink2.0",
"ts": 1559719136672,
"user": "system.user.admin",
"common": {
"name": "RM:192-168-2-39",
"state": "state",
"role": "level",
"type": "boolean",
"read": true,
"write": true
},
"native": {
"host": {
"address": "192.168.2.39",
"family": "IPv4",
"port": 80,
"size": 128,
"devtype": 10153,
"type": "rm",
"name": "RM:192-168-2-39",
"devname": "RM3 Pro Plus",
"mac": "a9:27:27:2:a8:c0"
}
},
"acl": {
"object": 1636,
"owner": "system.user.admin",
"ownerGroup": "system.group.administrator",
"state": 1636
},
"_id": "broadlink2.0.RM:192-168-2-39",
"type": "state"
}

Neu: =======================================
{
"common": {
"name": "RM:192-168-2-39",
"read": true,
"write": true,
"state": "state",
"role": "level",
"type": "boolean"
},
"type": "state",
"_id": "broadlink2.0.RM:0x27a9_34:ea:34:55:38:bb",
"from": "system.adapter.broadlink2.0",
"user": "system.user.admin",
"ts": 1559719838083,
"acl": {
"object": 1636,
"state": 1636,
"owner": "system.user.admin",
"ownerGroup": "system.group.administrator"
},
"native": {}
}

Ich habe keine Weg gefunden, die learned Codes einfach zu verschieben. Am einfachsten geht, mit dem alten Namen ein neues Objekt anlegen, und den Code dort reinkopieren. Das funktioniert und geht schneller als neu anlernen. Ich hoffe nur, dass das nicht die Regel wird ;-)

Wie sich bei diesem Adapter Request rausgestellt hat hat, basieren die Thermostate auf Broadlink Devices.
Ein Scan zeigt das sie auch tatsächlich schon vom Broadlink2 Adapter bereits erkannt, nur noch nicht unterstützt werden:

Sie werden aber mittlerweile von der Broadlink Python Library unterstützt.
Da es mittlerweile einige Leute mit baugleichen Thermostaten gibt, wird dich sicher eine Muster-Spende finden wenn ein Programmierer das implementieren mag :-)

I now started to implement my Multimedia control and there it can happen that because of one action multiple IR commands needs to be send out.
In this case I send the relevant states to true:

log:

2018-02-05 00:22:46.040  - info: broadlink2.0 Content RM:Broadlink-RMMINI3-Wohnzimmer.L.PhilipsTV-POWERTOGGLE is true
2018-02-05 00:22:46.048  - info: broadlink2.0 Content RM:Broadlink-RMMINI3-Wohnzimmer.L.Technisat-POWERTOGGLE is true

As you can see the time between the recognition is not that long.
I have the effect that often the first command is not really received, only the second one.

What happens when a second command is sent to the broadlink device while the first is maybe not send out already ?! Can it happen that the first IR is sent incomplete?!

Would it make sense to implement a kind of queing in the adapter with e.g. 100ms or such delay between multiple commands?

I have the problem that two of these adapter will not work at the same time. When i power off
one of them the other one works. When both are on one off them will not reachable.
I have made a logfile:

broadlink2.0 2018-10-22 20:06:05.183 debug Change RM:192-168-0-190.notReachable to true with ack: true
broadlink2.0 2018-10-22 20:06:05.178 warn Device RM:192-168-0-190 not reachable
broadlink2.0 2018-10-22 20:05:35.101 debug Change RM:192-168-0-192.notReachable to false with ack: true
broadlink2.0 2018-10-22 20:05:33.093 info 1 were not found: RM:192-168-0-190
broadlink2.0 2018-10-22 20:05:33.093 info Adapter broadlink2.0 started and found 1 devices named 'RM:192-168-0-192'.
broadlink2.0 2018-10-22 20:05:33.091 debug Poll every 30 secods.
broadlink2.0 2018-10-22 20:05:33.074 warn device RM:192-168-0-190 not found, please rescan later again or delete it! It was: 192.168.0.190,IPv4,80,128,10039,rm,RM:192-168-0-190,RM Mini,37:27:be:0:a8:c0
broadlink2.0 2018-10-22 20:05:33.060 debug Adapter has 16 old states!
broadlink2.0 2018-10-22 20:05:32.951 debug Change _NewDeviceScan to false with ack: true
broadlink2.0 2018-10-22 20:05:27.880 info Device RM:192-168-0-192 dedected: 192.168.0.192,IPv4,80,128,10039,rm,RM:192-168-0-192,RM Mini,37:27:c0:0:a8:c0
broadlink2.0 2018-10-22 20:05:27.694 debug Change _NewDeviceScan to true with ack: true
broadlink2.0 2018-10-22 20:05:27.495 debug Config IP-Address end to remove: .fritz.box
broadlink2.0 2018-10-22 20:05:27.495 info Discover UDP devices for 10sec on broadlink2.0
broadlink2.0 2018-10-22 20:05:27.494 debug broadlink2 received 2328 objects with config ip,scenes,switches,poll,lang
broadlink2.0 2018-10-22 20:05:25.071 debug Adapter broadlink2.0 starting.
broadlink2.0 2018-10-22 20:05:25.070 info starting. Version 1.9.0 in C:/ioBroker/node_modules/iobroker.broadlink2, node: v8.12.0
host.DESKTOP-006CT2J 2018-10-22 20:05:20.988 info instance system.adapter.broadlink2.0 started with pid 6240
host.DESKTOP-006CT2J 2018-10-22 20:05:18.501 info instance system.adapter.broadlink2.0 terminated with code null ()
host.DESKTOP-006CT2J 2018-10-22 20:05:18.501 warn instance system.adapter.broadlink2.0 terminated due to SIGTERM
host.DESKTOP-006CT2J 2018-10-22 20:05:18.424 info stopInstance system.adapter.broadlink2.0 killing pid 1300
host.DESKTOP-006CT2J 2018-10-22 20:05:18.424 info stopInstance system.adapter.broadlink2.0
host.DESKTOP-006CT2J 2018-10-22 20:05:18.423 info object change system.adapter.broadlink2.0
broadlink2.0 2018-10-22 20:05:10.590 debug system.adapter.admin.0: logging true
admin.0 2018-10-22 20:05:10.579 warn Disable logging, because no one socket connected
broadlink2.0 2018-10-22 20:04:21.003 debug system.adapter.admin.0: logging false
broadlink2.0 2018-10-22 20:02:50.914 debug Change RM:192-168-0-190.Temperature to 13.8 with ack: true
broadlink2.0 2018-10-22 20:02:22.906 debug Change RM:192-168-0-192.notReachable to true with ack: true
broadlink2.0 2018-10-22 20:02:22.898 warn Device RM:192-168-0-192 not reachable
broadlink2.0 2018-10-22 20:02:20.921 debug Change RM:192-168-0-190.Temperature to 13.9 with ack: true
broadlink2.0 2018-10-22 20:01:52.839 debug Change RM:192-168-0-190.notReachable to false with ack: true
broadlink2.0 2018-10-22 20:01:51.299 debug Change RM:192-168-0-190.Temperature to 13.8 with ack: true
broadlink2.0 2018-10-22 20:01:50.848 info 1 were not found: RM:192-168-0-192
broadlink2.0 2018-10-22 20:01:50.847 info Adapter broadlink2.0 started and found 1 devices named 'RM:192-168-0-190'.
broadlink2.0 2018-10-22 20:01:50.845 debug Poll every 30 secods.
broadlink2.0 2018-10-22 20:01:50.813 warn device RM:192-168-0-192 not found, please rescan later again or delete it! It was: 192.168.0.192,IPv4,80,128,10039,rm,RM:192-168-0-192,RM Mini,37:27:c0:0:a8:c0
broadlink2.0 2018-10-22 20:01:50.807 debug Adapter has 14 old states!
broadlink2.0 2018-10-22 20:01:50.692 debug Change _NewDeviceScan to false with ack: true
broadlink2.0 2018-10-22 20:01:45.898 debug Change RM:192-168-0-190.SendCode to ' ' with ack: true
broadlink2.0 2018-10-22 20:01:45.854 debug Change RM:192-168-0-190.Learn to false with ack: true
broadlink2.0 2018-10-22 20:01:45.824 debug Change RM:192-168-0-190 to false with ack: true
broadlink2.0 2018-10-22 20:01:45.806 info Device RM:192-168-0-190 dedected: 192.168.0.190,IPv4,80,128,10039,rm,RM:192-168-0-190,RM Mini,37:27:be:0:a8:c0
broadlink2.0 2018-10-22 20:01:45.564 debug Change _NewDeviceScan to true with ack: true
broadlink2.0 2018-10-22 20:01:45.338 debug Config IP-Address end to remove: .fritz.box
broadlink2.0 2018-10-22 20:01:45.337 info Discover UDP devices for 10sec on broadlink2.0
broadlink2.0 2018-10-22 20:01:45.332 debug broadlink2 received 2323 objects with config ip,scenes,switches,poll,lang
broadlink2.0 2018-10-22 20:01:42.368 debug Adapter broadlink2.0 starting.
broadlink2.0 2018-10-22 20:01:42.356 info starting. Version 1.9.0 in C:/ioBroker/node_modules/iobroker.broadlink2, node: v8.12.0
broadlink2.0 2018-10-22 20:01:42.181 debug statesDB connected
broadlink2.0 2018-10-22 20:01:41.985 debug objectDB connected
host.DESKTOP-006CT2J 2018-10-22 20:01:36.716 info instance system.adapter.broadlink2.0 started with pid 1300
host.DESKTOP-006CT2J 2018-10-22 20:01:34.226 info instance system.adapter.broadlink2.0 terminated with code null ()
host.DESKTOP-006CT2J 2018-10-22 20:01:34.225 warn instance system.adapter.broadlink2.0 terminated due to SIGTERM
host.DESKTOP-006CT2J 2018-10-22 20:01:34.156 info stopInstance system.adapter.broadlink2.0 killing pid 4780
host.DESKTOP-006CT2J 2018-10-22 20:01:34.156 info stopInstance system.adapter.broadlink2.0
host.DESKTOP-006CT2J 2018-10-22 20:01:34.155 info object change system.adapter.broadlink2.0
admin.0 2018-10-22 20:00:37.121 warn Disable logging, because no one socket connected
broadlink2.0 2018-10-22 20:00:34.560 info Adapter broadlink2.0 started and found 1 devices named 'RM:192-168-0-192'.
broadlink2.0 2018-10-22 20:00:29.585 info Device RM:192-168-0-192 dedected: 192.168.0.192,IPv4,80,128,10039,rm,RM:192-168-0-192,RM Mini,37:27:c0:0:a8:c0
broadlink2.0 2018-10-22 20:00:29.185 info Discover UDP devices for 10sec on broadlink2.0
broadlink2.0 2018-10-22 20:00:23.486 info starting. Version 1.9.0 in C:/ioBroker/node_modules/iobroker.broadlink2, node: v8.12.0

Die Namen der erkannten Adapter ändern sich. Die bisherigen Adapter werden nicht erkannt.

I have an RM3 mini and tried some codes I found for my Philips TV.
Code is: 000000730000000B0020002000400020002000200020002000200040002000200040002000200020002000400040002000200CC5

So I put in "CODE_000000730000000B0020002000400020002000200020002000200040002000200040002000200020002000400040002000200CC5" into the "SendCode" state.

Result is strangely:

2017-12-24 00:05:07.384  - warn: broadlink2.0 Code to send to RM:Broadlink-RMMINI-cc-4b-bb needs to start with CODE_
2017-12-24 00:05:07.387  - warn: broadlink2.0 Error in StateChange for broadlink2.0.RM:Broadlink-RMMINI-cc-4b-bb.SendCode = 'Code to send to RM:Broadlink-RMMINI-cc-4b-bb needs to start with CODE_'

?! ;-)

I added one debug log and the stat.val has ad additional " " (space" at the beginning) which is definitively not coming from Admin or from my data. Any idea?

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/frankjoke/ioBroker.broadlink2

• [E140] width and height of logo are not equal
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2019 Frank Joke [email protected]" at the start of LICENSE

I have also found warnings that may be fixed if possible.

• [W113] Adapter should support compact mode

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Guten Tag,
ich habe seit dem Patch das Problem das zeitweise die Befehle mehrfach gesendet werden.
Das bedeutet wenn ich meine Lampe vom Ventilator anschalte. schaltet sie sich erst ein und kurz danach wieder aus.

eine Fehlermeldung habe ich in den Log´s keine gesehen

mit freundlichem Gruß
eXplOiD

Ich hbae den Broadlink RM Pro und habe erfolgreich die Codes menes Ventilators angelernt. Will ich nun per Button als auch per Alexa schalten kommt im log "not reachable" und der Vorgang braucht mehr als eine Minute bis er ausgeführt wird. Wird der Broadlink vom Strom genommen, danach neu eingesteckt und initialisiert funktioniert es ein paar mal ohne Einschränkung. Adapter Version: 1.9.0, dieser zeigt auch grün in in Instanzen Bildschirm.

At ther time I can only add IR cods to ioBroker. It would be cool to add also RF codes to it. Here is an example how to do this.

https://github.com/lprhodes/homebridge-broadlink-rm/blob/master/helpers/learnRFData.js

Hi,
bei der 1.9.1 hatte ich mit einer von 2 SP1 Mini das Problem, dass sie meist als unreachable angezeigt wurde, aber mit der App problemlos funktionierte. Setzte ich in iobroker das object auf true oder false, dann resettete sich die broadlink instanz nach dem schalten.
Das ist jetzt in der V1.9.9 nicht mehr, läuft prima ( viel besser! )

Das einzige, was mich noch stoert, ist dass ein Datenkanal ein Schaltpunkt ist, das ist nicht nach iobroker-Philosophie. Schoener waere es, wenn es ein Objekt "Power" gaebe, das man schalten koennte, und nicht den Datenkanal.... :-)

I have an RM3 mini

I had the problem that I learned a code, the white light on the device turned off, but the adapter still thought it is in learning mode. Should not the adapter disable learning more with the successfull learning of a code?

Guten Tag,
ich habe ein Problem mit den Szenen ich bekomme sie einfach nicht angelegt.
beim ausführen bekomme ich einen fehler aber ich habe mich da irgendwie ein wenig festgefahren.
`

`

so habe ich die szene eingestellt.

{ "common": { "name": "Scenes.Wohnzimmer Licht 2", "read": true, "write": true, "state": "state", "role": "button", "type": "boolean" }, "type": "state", "_id": "broadlink2.0.Scenes.Wohnzimmer Licht 2", "native": { "scene": "SP:sd3=1, RM:RM:Broadlink_RMPROPLUS-f4-3c-47.L.w_licht2_on, RM:RM:Broadlink_RMPROPLUS-f4-3c-47.L.w_licht2_off" }, "acl": { "object": 1636, "state": 1636 } }

ich hoffe hier kann mir jemand helfen vielen dank schonmal im vorraus.

I only see device scan button, pressing it does nothing. I use the old Boadlink adapter and it works fine but since its not maintained anymore I wanted to check if this one works.
Anyone got ideas to help?
Thanks in advance!