Broadlink RM pro and rm mini not discovered, worked until 2 days ago. #270
Comments
|
This is all the log after loading homebridge: *** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi. Or enter this code with your HomeKit app on your iOS device to pair with Homebridge: [2018-2-25 18:13:07] Homebridge is running on port 37657. [Important!] We've discovered an unknown Broadlink device. Please raise an issue in the GitHub repository (https://github.com/lprhodes/homebridge-broadlink-rm/issues) with details of the type of device and its device type code: "2722" so that we can handle it correctly and prevent this message from appearing. Discovered Broadlink RM device at 10.0.0.5 (0d:43:b4:dc:90:5b) [Important!] We've discovered an unknown Broadlink device. Please raise an issue in the GitHub repository (https://github.com/lprhodes/homebridge-broadlink-rm/issues) with details of the type of device and its device type code: "2722" so that we can handle it correctly and prevent this message from appearing. [Important!] We've discovered an unknown Broadlink device. Please raise an issue in the GitHub repository (https://github.com/lprhodes/homebridge-broadlink-rm/issues) with details of the type of device and its device type code: "2722" so that we can handle it correctly and prevent this message from appearing. [Important!] We've discovered an unknown Broadlink device. Please raise an issue in the GitHub repository (https://github.com/lprhodes/homebridge-broadlink-rm/issues) with details of the type of device and its device type code: "2722" so that we can handle it correctly and prevent this message from appearing. [Important!] We've discovered an unknown Broadlink device. Please raise an issue in the GitHub repository (https://github.com/lprhodes/homebridge-broadlink-rm/issues) with details of the type of device and its device type code: "2722" so that we can handle it correctly and prevent this message from appearing. |
|
Hi, The error isn't that it's not been discovered it's that we don't know exactly how to treat the device. Is it the RM mini that's causing the error or the Pro? Can you please provide details about which version of the device it is and whether it's meant to support RF. |
|
I have also 3 RM mini and also an RM Pro and all worked well for a few
months!
I just had today a problem that the home bridge did not load and I deleted
the persist and accessories folders in .homebridge folder and left only the
config file in that folder.
Then started this error.
Can you please give me instructions how to uninstall completely all
homebridge and re install again?
I tried my self to uninstall and re install but it did not help. I think I
am missing something.
I think that homebridge is expecting some cache files that are missing.
My RM Pro is on version v20028
And my rm minis are on v20029
But again I am saying that it worked for a long time with this setup so it
is not a version issue I think.
Thanks for the help!!!
Refael.S
On Sun, 25 Feb 2018 at 23:27 Luke Rhodes ***@***.***> wrote:
Hi,
The error isn't that it's not been discovered it's that we don't know
exactly how to treat the device.
Is it the RM mini that's causing the error or the Pro?
Can you please provide details about which version of the device it is and
whether it's meant to support RF.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#270 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABgGRXSGVK9KpSCsJ3jZ8Z8zqgqbL0pqks5tYdAlgaJpZM4SSV_Z>
.
--
בברכה,
רפאל זומר
0526222068
|
|
The error is simply a way of reporting devices to us that we don't yet know how to handle. I need to know which of your devices is the one causing the error to show |
|
I have disconnected all devices from their power and left only my RM Pro
connected and I get the same error.
Looks like all devices are getting this error.
My Rm Pro sn is RM030003xxxx
On Sun, 25 Feb 2018 at 23:41 Luke Rhodes ***@***.***> wrote:
The error is simply a way of reporting devices to us that we don't yet
know how to handle.
I need to know which of your devices is the one causing the error to show
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#270 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABgGRT_4PIYDpgMemIgfNbJXaraQdmBsks5tYdOTgaJpZM4SSV_Z>
.
--
בברכה,
רפאל זומר
0526222068
|
|
But also tried now without the RM pro connected to the power and only the 3 RM minis connected and still get the error, there is nothing changed in the setup of my house, I want to have a fresh re install of home bridge so I can try and fix the problem, can you please instruct me what commands should I type in my Raspberry PI to re install? I will then put my config file and try again. |
|
I uninstalled home bridge and deleted all homebridge packages and files, I re installed and still same error. Thanks, |
|
I also downgraded home bridge and didn't help, still same error. |
|
Yes, it's because of the latest versions of this plugin which I added the error for. It looks like device 2722 is for a Broadlink S1 (SmartOne Alarm Kit). Do you have one of these? |
|
Yes I do, if I will disconnect it all will work?
I will disconnect now and update you.
On Mon, 26 Feb 2018 at 2:14 Luke Rhodes ***@***.***> wrote:
Yes, it's because of the latest versions of this plugin which I added the
error for.
It looks like device 2772 is for a Broadlink S1 (SmartOne Alarm Kit). Do
you have one of these?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#270 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABgGRZQQuwhBdVLLDHwuPSQZBfzGvCePks5tYfdbgaJpZM4SSV_Z>
.
--
בברכה,
רפאל זומר
0526222068
|
|
It will simply stop the error from appearing. As for making the other devices work...your logs show that they are being discovered: Discovered Broadlink RM device at 10.0.0.5 (0d:43:b4:dc:90:5b) |
|
I've just released v2.6.10 which will hide the error you were seeing when the S1 was connected |
|
Yes, disconnecting the sc1 works and no errors.
Can you please add a fix so I can use homebridge without disconnecting the
sc1?
I looked at your profile and I see you developed the GMGridView (:
I am an iOS developer and I use the GMGridView a lot in my apps!
Great code! Greate 3rd party.
Thanks!
Refael.S
On Mon, 26 Feb 2018 at 2:20 Luke Rhodes ***@***.***> wrote:
It will simply stop the error from appearing. As for making the other
devices work...your logs show that they are being discovered:
Discovered Broadlink RM device at 10.0.0.5 (0d:43:b4:dc:90:5b)
Discovered Broadlink RM device at 10.0.0.10 (0d:43:b4:ca:be:24)
Discovered Broadlink RM device at 10.0.0.14 (0d:43:b4:dc:8b:a8)
Discovered Broadlink RM device at 10.0.0.11 (0d:43:b4:dc:90:5f)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#270 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABgGRRkpKmSAFqRGIJFPh-LvYySWL_bHks5tYfi0gaJpZM4SSV_Z>
.
--
בברכה,
רפאל זומר
0526222068
|
|
But the HomeKit app shows all devices with no response.
Something is still not right
On Mon, 26 Feb 2018 at 2:22 רפאל זומר ***@***.***> wrote:
Yes, disconnecting the sc1 works and no errors.
Can you please add a fix so I can use homebridge without disconnecting the
sc1?
I looked at your profile and I see you developed the GMGridView (:
I am an iOS developer and I use the GMGridView a lot in my apps!
Great code! Greate 3rd party.
Thanks!
Refael.S
On Mon, 26 Feb 2018 at 2:20 Luke Rhodes ***@***.***> wrote:
> It will simply stop the error from appearing. As for making the other
> devices work...your logs show that they are being discovered:
>
> Discovered Broadlink RM device at 10.0.0.5 (0d:43:b4:dc:90:5b)
> Discovered Broadlink RM device at 10.0.0.10 (0d:43:b4:ca:be:24)
> Discovered Broadlink RM device at 10.0.0.14 (0d:43:b4:dc:8b:a8)
> Discovered Broadlink RM device at 10.0.0.11 (0d:43:b4:dc:90:5f)
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#270 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABgGRRkpKmSAFqRGIJFPh-LvYySWL_bHks5tYfi0gaJpZM4SSV_Z>
> .
>
--
בברכה,
רפאל זומר
0526222068
--
בברכה,
רפאל זומר
0526222068
|
|
I managed to fix my problem by removing the homebridge accessory from
HomeKit and re adding it again.
Thanks a lot
On Mon, 26 Feb 2018 at 2:25 רפאל זומר ***@***.***> wrote:
But the HomeKit app shows all devices with no response.
Something is still not right
On Mon, 26 Feb 2018 at 2:22 רפאל זומר ***@***.***> wrote:
> Yes, disconnecting the sc1 works and no errors.
>
> Can you please add a fix so I can use homebridge without disconnecting
> the sc1?
>
> I looked at your profile and I see you developed the GMGridView (:
> I am an iOS developer and I use the GMGridView a lot in my apps!
> Great code! Greate 3rd party.
>
> Thanks!
> Refael.S
>
> On Mon, 26 Feb 2018 at 2:20 Luke Rhodes ***@***.***> wrote:
>
>> It will simply stop the error from appearing. As for making the other
>> devices work...your logs show that they are being discovered:
>>
>> Discovered Broadlink RM device at 10.0.0.5 (0d:43:b4:dc:90:5b)
>> Discovered Broadlink RM device at 10.0.0.10 (0d:43:b4:ca:be:24)
>> Discovered Broadlink RM device at 10.0.0.14 (0d:43:b4:dc:8b:a8)
>> Discovered Broadlink RM device at 10.0.0.11 (0d:43:b4:dc:90:5f)
>>
>> —
>> You are receiving this because you authored the thread.
>> Reply to this email directly, view it on GitHub
>> <#270 (comment)>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/ABgGRRkpKmSAFqRGIJFPh-LvYySWL_bHks5tYfi0gaJpZM4SSV_Z>
>> .
>>
> --
> בברכה,
> רפאל זומר
> 0526222068
>
> --
בברכה,
רפאל זומר
0526222068
--
בברכה,
רפאל זומר
0526222068
|
[Important!] We've discovered an unknown Broadlink device.
Please raise an issue in the GitHub repository (https://github.com/lprhodes/homebridge-broadlink-rm/issues) with details of the type of device and its device type code: "2722" so that we can handle it correctly and prevent this message from appearing.
The text was updated successfully, but these errors were encountered: