Some of the devices not working from Smartthings

[sapstar]

Hi Becky,

Thanks for creating this wonderful device type for smartthings and the detailed instruction. I have setup the RM Bridge on an Android TV box and configured 2 devices, 1 RF based and 1 IR based. They both have been working well when added in Smartthings.

This weekend I wanted to add one more device. It is a RF controlled plug. I created added the commands to the e-control app and the RM bridge. I am able to control the plug fine when controlled from e-control app or the http://rm-bridge.fun2code.de website.

Now I added a new device to Smartthings with devicetype RM Bridge Switch LAN which I already had installed and working well with two other devices.

I have named the two commands "Cooker on" and "Cooker off" in RM-Bridge and the switch is called "Cooker" in Smartthings.

The two old devices I had continue to work, but this newly added device doesn't work through Smartthings. I restarted the Android TV box and RM Bridge app, but no luck. I also tried deleting and re learning the on off commands. But still no luck.

I checked live logging under smartthings and there is nothing displayed for this device. I could only see on and off commands in the event logs, but can't find any errors any where.

Can you please help me troubleshoot this problem? I don't understand what I am doing wrong as some of my devices are working fine using the same approach.

[sapstar]

Just a quick update. I tried with another device type available for SmartThings and RM Bridge which seems to work without any issues. https://github.com/af950833/Smartthings-for-Broadlink-RM-Pro

[beckyricha]

This is odd. I thought I'd started to see all the same issues but this one is new. If the to of my head all i can think is to make sure that your device is set up in the right location and uses the right hub. It's easiest to check all that in the smart things ide web site rather than in the app. You might also want to compare the device fields between one that's working and the new cooker to see if anything is different.  Lastly make sure cooker is upper case in the bridge if it is in smart things. It is case sensitive.If that's not it let me know and I'll think harder.  BeckyOn Apr 30, 2017 3:06 PM, sapstar notifications@github.com wrote:Hi Becky, Thanks for creating this wonderful device type for smartthings and the detailed instruction. I have setup the RM Bridge on an Android TV box and configured 2 devices, 1 RF based and 1 IR based. They both have been working well when added in Smartthings. This weekend I wanted to add one more device. It is a RF controlled plug. I created added the commands to the e-control app and the RM bridge. I am able to control the plug fine when controlled from e-control app or the http://rm-bridge.fun2code.de website. Now I added a new device to Smartthings with devicetype RM Bridge Switch LAN which I already had installed and working well with two other devices. I have named the two commands "Cooker on" and "Cooker off" in RM-Bridge and the switch is called "Cooker" in Smartthings. The two old devices I had continue to work, but this newly added device doesn't work through Smartthings. I restarted the Android TV box and RM Bridge app, but no luck. I also tried deleting and re learning the on off commands. But still no luck. I checked live logging under smartthings and there is nothing displayed for this device. I could only see on and off commands in the event logs, but can't find any errors any where. Can you please help me troubleshoot this problem? I don't understand what I am doing wrong as some of my devices are working fine using the same approach.

—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

[sapstar]

Hi Becky, my device name is defined as "Cooker" in SmartThings and the commands defined are "Cooker on" and "Cooker off" I made sure the case matches. The device is attached to the right location and hub as I only have 1 location and hub, I just selected them. Same for all the other devices.

[magickarle]

Greetings. I have a similar issue. Well, all was working great until couple of months ago. No devices on RM Bridge Switch LAN handler are working anymore.

They still work under http://rm-bridge.fun2code.de with the test button.

in the live logging : The a33da9c3-49a9-4081-8747-123456789000 is my device which the rm bridge app is installed. I use the LAN version.

a33da9c3-49a9-4081-8747-123456789000 8:57:03 PM: debug running todos a33da9c3-49a9-4081-8747-123456789000 8:57:03 PM: debug HEADER: [content-length:48, http/1.1 200 ok:null, content-type:text/plain; charset=UTF-8, server:RM Bridge/1.3.1, date:Tue, 19 Dec 2017 01:57:02 GMT+00:00] a33da9c3-49a9-4081-8747-123456789000 8:57:03 PM: trace Response Received (with Headers and Body) a33da9c3-49a9-4081-8747-123456789000 8:57:02 PM: debug running todos a33da9c3-49a9-4081-8747-123456789000 8:57:02 PM: debug HEADER: [content-length:48, http/1.1 200 ok:null, content-type:text/plain; charset=UTF-8, server:RM Bridge/1.3.1, date:Tue, 19 Dec 2017 01:57:02 GMT+00:00] a33da9c3-49a9-4081-8747-123456789000 8:57:02 PM: trace Response Received (with Headers and Body)

I have even removed all devices, handler and stared from the handler installation step.

[beckyricha]

Have you double-checked that your devices are linked to your hub? I am on a phone and can't go through the details yet but usually when I start seeing null errors that is it. Also sometimes gets to device naming but if it worked then didn't that shouldn't be it. Did anything change when you noticed the issue (e.g. Hub former update, router update or similar?) Change analysis often helps for me.BeckyOn Dec 18, 2017 9:00 PM, magickarle notifications@github.com wrote:Greetings. I have a similar issue. Well, all was working great until couple of months ago. No devices on RM Bridge Switch LAN handler are working anymore. They still work under http://rm-bridge.fun2code.de with the test button. in the live logging : The a33da9c3-49a9-4081-8747-123456789000 is my device which the rm bridge app is installed. I use the LAN version. a33da9c3-49a9-4081-8747-123456789000 8:57:03 PM: debug running todos a33da9c3-49a9-4081-8747-123456789000 8:57:03 PM: debug HEADER: [content-length:48, http/1.1 200 ok:null, content-type:text/plain; charset=UTF-8, server:RM Bridge/1.3.1, date:Tue, 19 Dec 2017 01:57:02 GMT+00:00] a33da9c3-49a9-4081-8747-123456789000 8:57:03 PM: trace Response Received (with Headers and Body) a33da9c3-49a9-4081-8747-123456789000 8:57:02 PM: debug running todos a33da9c3-49a9-4081-8747-123456789000 8:57:02 PM: debug HEADER: [content-length:48, http/1.1 200 ok:null, content-type:text/plain; charset=UTF-8, server:RM Bridge/1.3.1, date:Tue, 19 Dec 2017 01:57:02 GMT+00:00] a33da9c3-49a9-4081-8747-123456789000 8:57:02 PM: trace Response Received (with Headers and Body) I have even removed all devices, handler and stared from the handler installation step.

—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.