@themillhousegroup Hi, John. Do you have any updates? could i assist you?
G
@themillhousegroup Hi, John. Do you have any updates? could i assist you?
G
Hi @nakh_Home,
Sorry about the delay!
Please try out BETA-17 with support for ignoreFailedUpdates
:
https://dl.bintray.com/themillhousegroup/generic/org.openhab.binding.broadlink-2.4.0-BETA-17.jar
Using text-file thing
definitions should be fine - just put the config parameters in [square brackets]
,
e.g.:
Thing broadlink:sp3:34-ea-34-51-44-fb "SP Mini 3 1" @ "Bathroom"
[ pollingInterval=180,
ipAddress="10.240.0.243",
port=80,
staticIp=true,
mac="34:ea:34:51:44:fb",
authorizationKey="097628343fe99e23765c1513accf8b02",
iv="562e17996d093d28ddb3ba695a2e6f58",
retries=0,
ignoreFailedUpdates=true
]
Thanks @themillhousegroup, i have replaced the addon
i have enabled it for all the devices expect mini
Please:
Thing broadlink:sp2:34-ea-34-f5-ae-aa "txtBroadlink SP2 [192.168.1.105] SP2_3" [ ipAddress="192.168.1.105", port=80, mac="34:ea:34:f5:ae:aa", authorizationKey="097628343fe99e23765c1513accf8b02", iv="562e17996d093d28ddb3ba695a2e6f58", pollingInterval=120, retries=0, ignoreFailedUpdates=true] Thing broadlink:sp2:b4-43-0d-ee-d6-04 "txtBroadlink SP2 ilot [192.168.1.103]-SP2_2" [ ipAddress="192.168.1.103", port=80, mac="b4:43:0d:ee:d6:04", authorizationKey="097628343fe99e23765c1513accf8b02", iv="562e17996d093d28ddb3ba695a2e6f58", pollingInterval=120, retries=0, ignoreFailedUpdates=true] Thing broadlink:sp2:34-ea-34-bd-47-9b "txtBroadlink SP2 Chauffage[192.168.1.108]-SP2_1" [ ipAddress="192.168.1.108", port=80, mac="34:ea:34:bd:47:9b", authorizationKey="097628343fe99e23765c1513accf8b02", iv="562e17996d093d28ddb3ba695a2e6f58", pollingInterval=120, retries=0, ignoreFailedUpdates=true] Thing broadlink:a1:34-ea-34-b2-ba-7c "txtBroadlink A1 [192.168.1.120]" [ ipAddress="192.168.1.120", port=80, mac="34:ea:34:b2:ba:7c", authorizationKey="097628343fe99e23765c1513accf8b02", iv="562e17996d093d28ddb3ba695a2e6f58", pollingInterval=120, retries=0, ignoreFailedUpdates=true] Thing broadlink:mp1:34-ea-34-c9-9d-33 "txtBroadlink MP1 [192.168.1.106]" [ ipAddress="192.168.1.106", port=80, mac="34:ea:34:c9:9d:33", authorizationKey="097628343fe99e23765c1513accf8b02", iv="562e17996d093d28ddb3ba695a2e6f58", pollingInterval=120, retries=0, ignoreFailedUpdates=true] Thing broadlink:rm2:34-ea-34-c7-c9-15 "txtBroadlink RM2-Salon [192.168.1.101]-RM_1" [ ipAddress="192.168.1.101", port=80, mac="34:ea:34:c7:c9:15", authorizationKey="097628343fe99e23765c1513accf8b02", iv="562e17996d093d28ddb3ba695a2e6f58", mapFilename="RM_1_c.map", pollingInterval=120 , retries=0, ignoreFailedUpdates=true]
Thing broadlink:rm3:78-0f-77-19-fe-31 "txtBroadlink RM3-Nat[192.168.1.112]-mini_4" [ ipAddress="192.168.1.113", port=80, mac="78:0f:77:19:fe:31", authorizationKey="097628343fe99e23765c1513accf8b02", iv="562e17996d093d28ddb3ba695a2e6f58", mapFilename="mini_4_c.map", pollingInterval=120, retries=0, ignoreFailedUpdates=false] Thing broadlink:rm3:78-0f-77-18-3e-c4 "txtBroadlink RM3-Doudou [192.168.1.113]-mini_3" [ ipAddress="192.168.1.112", port=80, mac="78:0f:77:18:3e:c4", authorizationKey="097628343fe99e23765c1513accf8b02", iv="562e17996d093d28ddb3ba695a2e6f58", mapFilename="mini_3_c.map", pollingInterval=120, retries=0, ignoreFailedUpdates=false] Thing broadlink:rm3:34-ea-34-51-2d-bc "txtBroadlink RM3-Nono [192.168.1.107]-mini_2" [ ipAddress="192.168.1.107", port=80, mac="34:ea:34:51:2d:bc", authorizationKey="097628343fe99e23765c1513accf8b02", iv="562e17996d093d28ddb3ba695a2e6f58", mapFilename="mini_2_c.map", pollingInterval=120, retries=0, ignoreFailedUpdates=false] Thing broadlink:rm3:34-ea-34-c7-76-86 "txtBroadlink RM3-Parents[192.168.1.102]-mini_1" [ ipAddress="192.168.1.102", port=80, mac="34:ea:34:c7:76:86", authorizationKey="097628343fe99e23765c1513accf8b02", iv="562e17996d093d28ddb3ba695a2e6f58", mapFilename="mini_1_c.map", pollingInterval=120, retries=0, ignoreFailedUpdates=false]
it looks that it’s working
2019-06-17 11:35:22.904 [WARN ] [handler.BroadlinkSocketModel2Handler] - sp2:b4-43-0d-ee-d6-04[^]: Problem getting status. Not marking offline because configured to ignore failed updates ...
2019-06-17 11:37:27.946 [WARN ] [handler.BroadlinkSocketModel2Handler] - sp2:b4-43-0d-ee-d6-04[^]: Problem getting status. Not marking offline because configured to ignore failed updates ...
2019-06-17 11:39:32.986 [WARN ] [handler.BroadlinkSocketModel2Handler] - sp2:b4-43-0d-ee-d6-04[^]: Problem getting status. Not marking offline because configured to ignore failed updates ...
2019-06-17 11:41:38.024 [WARN ] [handler.BroadlinkSocketModel2Handler] - sp2:b4-43-0d-ee-d6-04[^]: Problem getting status. Not marking offline because configured to ignore failed updates ...
2019-06-17 11:43:43.085 [WARN ] [handler.BroadlinkSocketModel2Handler] - sp2:b4-43-0d-ee-d6-04[^]: Problem getting status. Not marking offline because configured to ignore failed updates ...
2019-06-17 11:45:48.122 [WARN ] [handler.BroadlinkSocketModel2Handler] - sp2:b4-43-0d-ee-d6-04[^]: Problem getting status. Not marking offline because configured to ignore failed updates ...
2019-06-17 11:52:07.256 [WARN ] [handler.BroadlinkRemoteModel2Handler] - rm2:34-ea-34-c7-c9-15[^]: Problem getting status. Not marking offline because configured to ignore failed updates ...
2019-06-17 11:54:12.284 [WARN ] [handler.BroadlinkRemoteModel2Handler] - rm2:34-ea-34-c7-c9-15[^]: Problem getting status. Not marking offline because configured to ignore failed updates ...
2019-06-17 11:56:17.311 [WARN ] [handler.BroadlinkRemoteModel2Handler] - rm2:34-ea-34-c7-c9-15[^]: Problem getting status. Not marking offline because configured to ignore failed updates ...
2019-06-17 11:58:22.330 [WARN ] [handler.BroadlinkRemoteModel2Handler] - rm2:34-ea-34-c7-c9-15[^]: Problem getting status. Not marking offline because configured to ignore failed updates ...
2019-06-17 12:00:27.354 [WARN ] [handler.BroadlinkRemoteModel2Handler] - rm2:34-ea-34-c7-c9-15[^]: Problem getting status. Not marking offline because configured to ignore failed updates ...
2019-06-17 12:02:32.381 [WARN ] [handler.BroadlinkRemoteModel2Handler] - rm2:34-ea-34-c7-c9-15[^]: Problem getting status. Not marking offline because configured to ignore failed updates ...
2019-06-17 12:17:19.715 [WARN ] [handler.BroadlinkSocketModel2Handler] - sp2:34-ea-34-bd-47-9b[^]: Problem getting status. Not marking offline because configured to ignore failed updates ...
i can already see that the mini are getting more offline (comparatively to the previous milestone) even with ignoreFailedUpdates=false
```
|June 17, 2019 at 11:21AM|mini_1|OFFLINE|
|June 17, 2019 at 12:15PM|mini_1|ONLINE|
|June 17, 2019 at 12:41PM|mini_4|ONLINE|
|June 17, 2019 at 12:52PM|mini_4|ONLINE|
|June 17, 2019 at 01:06PM|mini_4|OFFLINE|
|June 17, 2019 at 01:08PM|mini_4|ONLINE|
|June 17, 2019 at 01:12PM|mini_4|OFFLINE|
|June 17, 2019 at 01:17PM|mini_2|OFFLINE|
|June 17, 2019 at 01:19PM|mini_2|ONLINE|
|June 17, 2019 at 01:31PM|mini_2|OFFLINE|
|June 17, 2019 at 01:37PM|mini_2|ONLINE|
Please find here the trace logs
Hi @nakh_Home,
Haven’t got time to have a look at the logs right now (I will get to them … soon) but to answer your questions:
staticIp
is a boolean
which you can set true
if you can guarantee that this device will always have the same IP address (i.e. you’ve allocated it a fixed address via DHCP). Why would you set this? So that the binding will know immediately if the device is not found, that is it gone. If you leave it false
, the binding will go into a “rediscovery” mode to attempt to find the device, based on the assumption that it may still be there, but just got allocated a new IP address. Judging from your logs I’ve seen in the past, you are using fixed IPs for each Broadlink device, so you should set this to true
You are right, the config variable is definitely pollingInterval
- apologies for the misleading code snippet in my previous post (I’ll edit that). If you ever want to see the definitive list of config variables you can always see it on Github at: https://github.com/themillhousegroup/openhab2-addons/blob/master/addons/binding/org.openhab.binding.broadlink/ESH-INF/thing/thing-types.xml
Thank for your explanation
Since the IP and MAC were required, i did not use the static IP.
but in fact, yes, that’s Static IP
please do not have a look on the logs, it seems to be promising with the last updates.
another remark, (not that’s important) but i think that the power consumption do not work for SP2
it got never updated
Will keep you updated
Thanks
Hi!
I have installed the newst jar, and tried to search the thing, but cant find.
Broadlink rm3 is on the same network. I would try to add manuall but what are the auth code and iv?
Thans
See at post 589
Thanks @themillhousegroup
it’s stable
All the items SP are defined as SP2 (see the icons)
i think that the power consumption do not work for SP2
Hi!
Thank you! I missed that post previously.
Its working now.
Could you help me (or someone) how can I Switch on and off my air conditional with amazon alexa?
This is my config now:
ITEM
String BedroomAirConditional "Bedroom Air Conditional" { channel="broadlink:rm3:348d2600:command"}
SITEMAP
Switch item=BedroomAirConditional label=“Parents AirCond” mappings=[ParentAirOn=“On”, ParentAirOff=“Off”]
Thank you in advance
Hello, I think about buying a Broadlink RM Pro to control my 433MHz roller shutters.
Does this work with this binding?
Regards
Bernd
hi, i would love to try the binding, can u pls send me the instructions.
regards
Mike
I think it would be necessary to create a new post with precise instructions. because it’s incomprehensible lol
Hello Chef!
Here’s a short version that I hope could help you on the way:
Check Cato’s Post 56: Broadlink binding for RMx, A1, SPx and MP. Any interest?
Download the latest version of the binding with thanks to John @themillhousegroup
https://dl.bintray.com/themillhousegroup/generic/org.openhab.binding.broadlink-2.4.0-BETA-17.jar
Place the JAR file in your Addons folder:
The IV & Vector Key:
Key = 097628343fe99e23765c1513accf8b02
Vector =562e17996d093d28ddb3ba695a2e6f58
Lets see how far you get withe this info…
Ray
Thank you @X-Ray181 .
For the moment, I used Black Bean control , there is the self-learning of IR and it works perfectly, but there is little delay, 6 or 7 seconds to launch the IR command. Two question:
thx
Yes & Yes
cool thx , last question : you think I can keep Black bean control on the raspberry and install this binding, because the self-learning is really useful
Think that should be posible, I also have an android device with the RM Plugin online that can do Mqtt & http , they don’t bite eachother, so make a good backup and give it a try! and with the Pi thats easy to do (OpenHabian)
thank you again @X-Ray181
please see this…
its windows way to copy codes… i found it most easy than all other methodes
Hi there, do you guys know about RM code generator to generate random RF and IR command? I find it promising, however it is developed with HomeAssistant in mind and it is not optimized for this binding.
Can anybody take a look on result code and give enlightenment to convert it to be put on broadlink.map?
TIA