search

beckyricha / Broadlink-RM-SmartThings-Alexa

Control RF and Ir devices using SmartThings and Alexa.
151 stars 115 forks source link

RM bridge with alexa #21

Open bubagump opened 7 years ago

bubagump commented 7 years ago

Hello, I have the RM bridge on a old samsung galaxy S3 working well with broadlink and Alexa to control several etekcity modules. However, I always have to say a command to alexa twice and the devices respond only on the second command even though alexa says 'ok' both times. I need to say the command twice only if about an hour or more has elapsed since the last command to broadlink otherwise it works the first time I say the command. Is it possible to fix this issue? Thanks

beckyricha commented 7 years ago

Does it do this with smart things as well or only Alexa? Which version of the code are you using (cloud or LAN)?  Sounds like something off with Alexa, or maybe you tried at a time when smart things was having an issue. I've never come across anything like that before.  You might also try disconnecting and reconnecting your smart things account from Alexa.  Do you use any other smart things devices and if so do they also have this trouble? It might be something weird in the connection between the two.  Did your echo ever give you any other issues? I've found if they are not connected to a very strong wifi they can't act weird sometimes. I am working on an Alexa skill that would work directly without smart things. Still needs the Android bridge for now though. It should be ready in the next couple of weeks. Maybe that might work better for you if this doesn't solve it. On Feb 10, 2017 3:57 PM, bubagump notifications@github.com wrote:Hello, I have the RM bridge on a old samsung galaxy S3 working well with broadlink and Alexa to control several etekcity modules. However, I always have to say a command to alexa twice and the devices respond only on the second command even though alexa says 'ok' both times. I need to say the command twice only if about an hour or more has elapsed since the last command to broadlink otherwise it works the first time I say the command. Is it possible to fix this issue? Thanks

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

bubagump commented 7 years ago

It seems to happen only through Alexa. If I watch the broadlink after I give a voice command to alexa, the yellow light on the broadlink blinks only after I repeat the command the second time and then it works. Do you think it might have something to do with the galaxy s3 I am using for the RM bridge? I have several z wave dimmer switches which work fine with alexa through smartthings and do not have this issue. Eagerly awaiting the alexa skill!

beckyricha commented 7 years ago

That helps a bit. If it works the first time when you control it from smart things then it's probably not your galaxy device, but again it's not something I've seen so I'm guessing.  Are you using the LAN or cloud version of the smart things device handler? Also likely unrelated but some people have odd issues if the broadlink firmware is not up to date. Do you know what version you are on?

On Feb 10, 2017 6:27 PM, bubagump notifications@github.com wrote:It seems to happen only through Alexa. If I watch the broadlink after I give a voice command to alexa, the yellow light on the broadlink blinks only after I repeat the command the second time and then it works. Do you think it might have something to do with the galaxy s3 I am using for the RM bridge? I have several z wave dimmer switches which work fine with alexa through smartthings and do not have this issue. Eagerly awaiting the alexa skill!

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

bubagump commented 7 years ago

I am using LAN version of the DTH and broadlink firmware version is V20025. So I am at my wit's end with this issue. It always works when I repeat the command to Alexa the second time because the broadlink device only responds on the second attempt. I will check again if this issue exists when trying to control directly from smartthings app after a gap of not using the device for a couple of hrs. If the switches do not respond right away with the smartthings app, would that be an issue with the galaxy timing out?

On Fri, Feb 10, 2017 at 4:18 PM, Becky Onuschak notifications@github.com wrote:

That helps a bit. If it works the first time when you control it from smart things then it's probably not your galaxy device, but again it's not something I've seen so I'm guessing. Are you using the LAN or cloud version of the smart things device handler? Also likely unrelated but some people have odd issues if the broadlink firmware is not up to date. Do you know what version you are on?

On Feb 10, 2017 6:27 PM, bubagump notifications@github.com wrote:It seems to happen only through Alexa. If I watch the broadlink after I give a voice command to alexa, the yellow light on the broadlink blinks only after I repeat the command the second time and then it works. Do you think it might have something to do with the galaxy s3 I am using for the RM bridge? I have several z wave dimmer switches which work fine with alexa through smartthings and do not have this issue. Eagerly awaiting the alexa skill!

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21#issuecomment-279101759, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi-RVG2c4cKKcytFrF7OFGHbms0MqOks5rbP5jgaJpZM4L92H7 .

beckyricha commented 7 years ago

So the firmware is not the issue.  I don't know anything about the galaxy. Only way to check it that i can think of is to try a different Android like a phone.  Did the galaxy stay awake all the time?  If not that could be it.  One workaround would be to edit the device handler to send the code twice,  with a pause between if necessary.  The "multi switch" version has the pieces you could use but if you need help let me know.  Also this should work fine with etekcity outlets, as it's fine if they get the command twice but would cause problems with any toggle switches. On Feb 10, 2017 8:48 PM, bubagump notifications@github.com wrote:I am using LAN version of the DTH and broadlink firmware version is V20025. So I am at my wit's end with this issue. It always works when I repeat the command to Alexa the second time because the broadlink device only responds on the second attempt. I will check again if this issue exists when trying to control directly from smartthings app after a gap of not using the device for a couple of hrs. If the switches do not respond right away with the smartthings app, would that be an issue with the galaxy timing out?

On Fri, Feb 10, 2017 at 4:18 PM, Becky Onuschak notifications@github.com wrote:

That helps a bit. If it works the first time when you control it from smart things then it's probably not your galaxy device, but again it's not something I've seen so I'm guessing. Are you using the LAN or cloud version of the smart things device handler? Also likely unrelated but some people have odd issues if the broadlink firmware is not up to date. Do you know what version you are on?

On Feb 10, 2017 6:27 PM, bubagump notifications@github.com wrote:It seems to happen only through Alexa. If I watch the broadlink after I give a voice command to alexa, the yellow light on the broadlink blinks only after I repeat the command the second time and then it works. Do you think it might have something to do with the galaxy s3 I am using for the RM bridge? I have several z wave dimmer switches which work fine with alexa through smartthings and do not have this issue. Eagerly awaiting the alexa skill!

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21#issuecomment-279101759, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi-RVG2c4cKKcytFrF7OFGHbms0MqOks5rbP5jgaJpZM4L92H7 .

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

bubagump commented 7 years ago

First of all, many thanks for developing this code and your prompt help. I truly appreciate it. I will try a different phone and might also setup a tasker routine to wake up the phone periodically.

I agree that having the DTH send the quote twice might create problems with some toggle switches that I might want to add. Perhaps the Alexa skill will fix this strange issue. Will you be sending an announcement when the skill is ready?

On Fri, Feb 10, 2017 at 6:30 PM, Becky Onuschak notifications@github.com wrote:

So the firmware is not the issue. I don't know anything about the galaxy. Only way to check it that i can think of is to try a different Android like a phone. Did the galaxy stay awake all the time? If not that could be it. One workaround would be to edit the device handler to send the code twice, with a pause between if necessary. The "multi switch" version has the pieces you could use but if you need help let me know. Also this should work fine with etekcity outlets, as it's fine if they get the command twice but would cause problems with any toggle switches. On Feb 10, 2017 8:48 PM, bubagump notifications@github.com wrote:I am using LAN version of the DTH and broadlink firmware version is V20025. So I am at my wit's end with this issue. It always works when I repeat the command to Alexa the second time because the broadlink device only responds on the second attempt. I will check again if this issue exists when trying to control directly from smartthings app after a gap of not using the device for a couple of hrs. If the switches do not respond right away with the smartthings app, would that be an issue with the galaxy timing out?

On Fri, Feb 10, 2017 at 4:18 PM, Becky Onuschak notifications@github.com

wrote:

That helps a bit. If it works the first time when you control it from smart things then it's probably not your galaxy device, but again it's not something I've seen so I'm guessing. Are you using the LAN or cloud version of the smart things device handler? Also likely unrelated but some people have odd issues if the broadlink firmware is not up to date. Do you know what version you are on?

On Feb 10, 2017 6:27 PM, bubagump notifications@github.com wrote:It seems to happen only through Alexa. If I watch the broadlink after I give a voice command to alexa, the yellow light on the broadlink blinks only after I repeat the command the second time and then it works. Do you think it might have something to do with the galaxy s3 I am using for the RM bridge? I have several z wave dimmer switches which work fine with alexa through smartthings and do not have this issue. Eagerly awaiting the alexa skill!

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21# issuecomment-279101759, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- RVG2c4cKKcytFrF7OFGHbms0MqOks5rbP5jgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21#issuecomment-279114507, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi-dEXFBNKO0Q0Pw23pbSdv34hfrS9ks5rbR1YgaJpZM4L92H7 .

beckyricha commented 7 years ago

When I get it done, I will post an update on the readme here, and also on the announcements page of the forum. Subscribing on the forum might be easiest so you don't get every other thread or update. That is at beckyricha.github.io and there is a forum link on the left edge. The skill works already for just turning devices on and off, but i am finalizing a web page that will ease the device setup. Devices you already set up the smart things way will still work but i also plan to add an easy multi-command device setup and control (e.g. a "tv" that turns on your TV, cable box, and turns off a light, etc) and easier Tv channel controls.  The only potential drawback is it uses your Google drive to store your ip address and any multi device commands. That's the only secure way i could think of that was straightforward and didn't save it anywhere that i or anyone else had access since the echo doesn't have its own storage. I am having occasional issues where if you don't use it often enough you need to re- authorize the Google handshake. Still seems easier than smart things though. I will put it out first as a beta that anyone can install and play with but hopefully will also get it published by Amazon, making the installation far easier. I have 2 other skills published so I think I can get past that step.

On Feb 11, 2017 1:43 PM, bubagump notifications@github.com wrote:First of all, many thanks for developing this code and your prompt help. I truly appreciate it. I will try a different phone and might also setup a tasker routine to wake up the phone periodically.

I agree that having the DTH send the quote twice might create problems with some toggle switches that I might want to add. Perhaps the Alexa skill will fix this strange issue. Will you be sending an announcement when the skill is ready?

On Fri, Feb 10, 2017 at 6:30 PM, Becky Onuschak notifications@github.com wrote:

So the firmware is not the issue. I don't know anything about the galaxy. Only way to check it that i can think of is to try a different Android like a phone. Did the galaxy stay awake all the time? If not that could be it. One workaround would be to edit the device handler to send the code twice, with a pause between if necessary. The "multi switch" version has the pieces you could use but if you need help let me know. Also this should work fine with etekcity outlets, as it's fine if they get the command twice but would cause problems with any toggle switches. On Feb 10, 2017 8:48 PM, bubagump notifications@github.com wrote:I am using LAN version of the DTH and broadlink firmware version is V20025. So I am at my wit's end with this issue. It always works when I repeat the command to Alexa the second time because the broadlink device only responds on the second attempt. I will check again if this issue exists when trying to control directly from smartthings app after a gap of not using the device for a couple of hrs. If the switches do not respond right away with the smartthings app, would that be an issue with the galaxy timing out?

On Fri, Feb 10, 2017 at 4:18 PM, Becky Onuschak notifications@github.com

wrote:

That helps a bit. If it works the first time when you control it from smart things then it's probably not your galaxy device, but again it's not something I've seen so I'm guessing. Are you using the LAN or cloud version of the smart things device handler? Also likely unrelated but some people have odd issues if the broadlink firmware is not up to date. Do you know what version you are on?

On Feb 10, 2017 6:27 PM, bubagump notifications@github.com wrote:It seems to happen only through Alexa. If I watch the broadlink after I give a voice command to alexa, the yellow light on the broadlink blinks only after I repeat the command the second time and then it works. Do you think it might have something to do with the galaxy s3 I am using for the RM bridge? I have several z wave dimmer switches which work fine with alexa through smartthings and do not have this issue. Eagerly awaiting the alexa skill!

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21# issuecomment-279101759, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- RVG2c4cKKcytFrF7OFGHbms0MqOks5rbP5jgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21#issuecomment-279114507, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi-dEXFBNKO0Q0Pw23pbSdv34hfrS9ks5rbR1YgaJpZM4L92H7 .

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

bubagump commented 7 years ago

Excellent. Subscribed to the announcements. Look forward to the beta..

On Feb 11, 2017 1:15 PM, "Becky Onuschak" notifications@github.com wrote:

When I get it done, I will post an update on the readme here, and also on the announcements page of the forum. Subscribing on the forum might be easiest so you don't get every other thread or update. That is at beckyricha.github.io and there is a forum link on the left edge. The skill works already for just turning devices on and off, but i am finalizing a web page that will ease the device setup. Devices you already set up the smart things way will still work but i also plan to add an easy multi-command device setup and control (e.g. a "tv" that turns on your TV, cable box, and turns off a light, etc) and easier Tv channel controls. The only potential drawback is it uses your Google drive to store your ip address and any multi device commands. That's the only secure way i could think of that was straightforward and didn't save it anywhere that i or anyone else had access since the echo doesn't have its own storage. I am having occasional issues where if you don't use it often enough you need to re- authorize the Google handshake. Still seems easier than smart things though. I will put it out first as a beta that anyone can install and play with but hopefully will also get it published by Amazon, making the installation far easier. I have 2 other skills published so I think I can get past that step.

On Feb 11, 2017 1:43 PM, bubagump notifications@github.com wrote:First of all, many thanks for developing this code and your prompt help. I truly appreciate it. I will try a different phone and might also setup a tasker routine to wake up the phone periodically.

I agree that having the DTH send the quote twice might create problems with some toggle switches that I might want to add. Perhaps the Alexa skill will fix this strange issue. Will you be sending an announcement when the skill is ready?

On Fri, Feb 10, 2017 at 6:30 PM, Becky Onuschak notifications@github.com wrote:

So the firmware is not the issue. I don't know anything about the galaxy. Only way to check it that i can think of is to try a different Android like a phone. Did the galaxy stay awake all the time? If not that could be it. One workaround would be to edit the device handler to send the code twice, with a pause between if necessary. The "multi switch" version has the pieces you could use but if you need help let me know. Also this should work fine with etekcity outlets, as it's fine if they get the command twice but would cause problems with any toggle switches. On Feb 10, 2017 8:48 PM, bubagump notifications@github.com wrote:I am using LAN version of the DTH and broadlink firmware version is V20025. So I am at my wit's end with this issue. It always works when I repeat the command to Alexa the second time because the broadlink device only responds on the second attempt. I will check again if this issue exists when trying to control directly from smartthings app after a gap of not using the device for a couple of hrs. If the switches do not respond right away with the smartthings app, would that be an issue with the galaxy timing out?

On Fri, Feb 10, 2017 at 4:18 PM, Becky Onuschak notifications@github.com

wrote:

That helps a bit. If it works the first time when you control it from smart things then it's probably not your galaxy device, but again it's not something I've seen so I'm guessing. Are you using the LAN or cloud version of the smart things device handler? Also likely unrelated but some people have odd issues if the broadlink firmware is not up to date. Do you know what version you are on?

On Feb 10, 2017 6:27 PM, bubagump notifications@github.com wrote:It seems to happen only through Alexa. If I watch the broadlink after I give a voice command to alexa, the yellow light on the broadlink blinks only after I repeat the command the second time and then it works. Do you think it might have something to do with the galaxy s3 I am using for the RM bridge? I have several z wave dimmer switches which work fine with alexa through smartthings and do not have this issue. Eagerly awaiting the alexa skill!

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21# issuecomment-279101759, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- RVG2c4cKKcytFrF7OFGHbms0MqOks5rbP5jgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21# issuecomment-279114507, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- dEXFBNKO0Q0Pw23pbSdv34hfrS9ks5rbR1YgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21#issuecomment-279176291, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi-Rcuy6PAA1Nlext3TD4Y-y2EtM0oks5rbiUEgaJpZM4L92H7 .

beckyricha commented 7 years ago

I have started having this trouble lately as well. Wondering if it is related to the hub update they ruled out a week or 2 ago.  I'll try to dig in but if it's the hub acting oddly is not always an easy fix. On Feb 11, 2017 1:43 PM, bubagump notifications@github.com wrote:First of all, many thanks for developing this code and your prompt help. I truly appreciate it. I will try a different phone and might also setup a tasker routine to wake up the phone periodically.

I agree that having the DTH send the quote twice might create problems with some toggle switches that I might want to add. Perhaps the Alexa skill will fix this strange issue. Will you be sending an announcement when the skill is ready?

On Fri, Feb 10, 2017 at 6:30 PM, Becky Onuschak notifications@github.com wrote:

So the firmware is not the issue. I don't know anything about the galaxy. Only way to check it that i can think of is to try a different Android like a phone. Did the galaxy stay awake all the time? If not that could be it. One workaround would be to edit the device handler to send the code twice, with a pause between if necessary. The "multi switch" version has the pieces you could use but if you need help let me know. Also this should work fine with etekcity outlets, as it's fine if they get the command twice but would cause problems with any toggle switches. On Feb 10, 2017 8:48 PM, bubagump notifications@github.com wrote:I am using LAN version of the DTH and broadlink firmware version is V20025. So I am at my wit's end with this issue. It always works when I repeat the command to Alexa the second time because the broadlink device only responds on the second attempt. I will check again if this issue exists when trying to control directly from smartthings app after a gap of not using the device for a couple of hrs. If the switches do not respond right away with the smartthings app, would that be an issue with the galaxy timing out?

On Fri, Feb 10, 2017 at 4:18 PM, Becky Onuschak notifications@github.com

wrote:

That helps a bit. If it works the first time when you control it from smart things then it's probably not your galaxy device, but again it's not something I've seen so I'm guessing. Are you using the LAN or cloud version of the smart things device handler? Also likely unrelated but some people have odd issues if the broadlink firmware is not up to date. Do you know what version you are on?

On Feb 10, 2017 6:27 PM, bubagump notifications@github.com wrote:It seems to happen only through Alexa. If I watch the broadlink after I give a voice command to alexa, the yellow light on the broadlink blinks only after I repeat the command the second time and then it works. Do you think it might have something to do with the galaxy s3 I am using for the RM bridge? I have several z wave dimmer switches which work fine with alexa through smartthings and do not have this issue. Eagerly awaiting the alexa skill!

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21# issuecomment-279101759, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- RVG2c4cKKcytFrF7OFGHbms0MqOks5rbP5jgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21#issuecomment-279114507, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi-dEXFBNKO0Q0Pw23pbSdv34hfrS9ks5rbR1YgaJpZM4L92H7 .

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

bubagump commented 7 years ago

Interesting..if it helps in troubleshooting, this problem does not occur for any z wave switches connected through smartthings..

On Feb 14, 2017 6:00 AM, "Becky Onuschak" notifications@github.com wrote:

I have started having this trouble lately as well. Wondering if it is related to the hub update they ruled out a week or 2 ago. I'll try to dig in but if it's the hub acting oddly is not always an easy fix. On Feb 11, 2017 1:43 PM, bubagump notifications@github.com wrote:First of all, many thanks for developing this code and your prompt help. I truly appreciate it. I will try a different phone and might also setup a tasker routine to wake up the phone periodically.

I agree that having the DTH send the quote twice might create problems with some toggle switches that I might want to add. Perhaps the Alexa skill will fix this strange issue. Will you be sending an announcement when the skill is ready?

On Fri, Feb 10, 2017 at 6:30 PM, Becky Onuschak notifications@github.com

wrote:

So the firmware is not the issue. I don't know anything about the galaxy. Only way to check it that i can think of is to try a different Android like a phone. Did the galaxy stay awake all the time? If not that could be it. One workaround would be to edit the device handler to send the code twice, with a pause between if necessary. The "multi switch" version has the pieces you could use but if you need help let me know. Also this should work fine with etekcity outlets, as it's fine if they get the command twice but would cause problems with any toggle switches. On Feb 10, 2017 8:48 PM, bubagump notifications@github.com wrote:I am using LAN version of the DTH and broadlink firmware version is V20025. So I am at my wit's end with this issue. It always works when I repeat the command to Alexa the second time because the broadlink device only responds on the second attempt. I will check again if this issue exists when trying to control directly from smartthings app after a gap of not using the device for a couple of hrs. If the switches do not respond right away with the smartthings app, would that be an issue with the galaxy timing out?

On Fri, Feb 10, 2017 at 4:18 PM, Becky Onuschak < notifications@github.com>

wrote:

That helps a bit. If it works the first time when you control it from smart things then it's probably not your galaxy device, but again it's not something I've seen so I'm guessing. Are you using the LAN or cloud version of the smart things device handler? Also likely unrelated but some people have odd issues if the broadlink firmware is not up to date. Do you know what version you are on?

On Feb 10, 2017 6:27 PM, bubagump notifications@github.com wrote:It seems to happen only through Alexa. If I watch the broadlink after I give a voice command to alexa, the yellow light on the broadlink blinks only after I repeat the command the second time and then it works. Do you think it might have something to do with the galaxy s3 I am using for the RM bridge? I have several z wave dimmer switches which work fine with alexa through smartthings and do not have this issue. Eagerly awaiting the alexa skill!

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM- SmartThings-Alexa/issues/21# issuecomment-279101759, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- RVG2c4cKKcytFrF7OFGHbms0MqOks5rbP5jgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21# issuecomment-279114507, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- dEXFBNKO0Q0Pw23pbSdv34hfrS9ks5rbR1YgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21#issuecomment-279714189, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi-cf5lokvp8FrtRsowzHoUmF5td4Kks5rcbOIgaJpZM4L92H7 .

beckyricha commented 7 years ago

It doesn't happen for me all the time but does sometimes. On Feb 14, 2017 3:17 PM, bubagump notifications@github.com wrote:Interesting..if it helps in troubleshooting, this problem does not occur for any z wave switches connected through smartthings..

On Feb 14, 2017 6:00 AM, "Becky Onuschak" notifications@github.com wrote:

I have started having this trouble lately as well. Wondering if it is related to the hub update they ruled out a week or 2 ago. I'll try to dig in but if it's the hub acting oddly is not always an easy fix. On Feb 11, 2017 1:43 PM, bubagump notifications@github.com wrote:First of all, many thanks for developing this code and your prompt help. I truly appreciate it. I will try a different phone and might also setup a tasker routine to wake up the phone periodically.

I agree that having the DTH send the quote twice might create problems with some toggle switches that I might want to add. Perhaps the Alexa skill will fix this strange issue. Will you be sending an announcement when the skill is ready?

On Fri, Feb 10, 2017 at 6:30 PM, Becky Onuschak notifications@github.com

wrote:

So the firmware is not the issue. I don't know anything about the galaxy. Only way to check it that i can think of is to try a different Android like a phone. Did the galaxy stay awake all the time? If not that could be it. One workaround would be to edit the device handler to send the code twice, with a pause between if necessary. The "multi switch" version has the pieces you could use but if you need help let me know. Also this should work fine with etekcity outlets, as it's fine if they get the command twice but would cause problems with any toggle switches. On Feb 10, 2017 8:48 PM, bubagump notifications@github.com wrote:I am using LAN version of the DTH and broadlink firmware version is V20025. So I am at my wit's end with this issue. It always works when I repeat the command to Alexa the second time because the broadlink device only responds on the second attempt. I will check again if this issue exists when trying to control directly from smartthings app after a gap of not using the device for a couple of hrs. If the switches do not respond right away with the smartthings app, would that be an issue with the galaxy timing out?

On Fri, Feb 10, 2017 at 4:18 PM, Becky Onuschak < notifications@github.com>

wrote:

That helps a bit. If it works the first time when you control it from smart things then it's probably not your galaxy device, but again it's not something I've seen so I'm guessing. Are you using the LAN or cloud version of the smart things device handler? Also likely unrelated but some people have odd issues if the broadlink firmware is not up to date. Do you know what version you are on?

On Feb 10, 2017 6:27 PM, bubagump notifications@github.com wrote:It seems to happen only through Alexa. If I watch the broadlink after I give a voice command to alexa, the yellow light on the broadlink blinks only after I repeat the command the second time and then it works. Do you think it might have something to do with the galaxy s3 I am using for the RM bridge? I have several z wave dimmer switches which work fine with alexa through smartthings and do not have this issue. Eagerly awaiting the alexa skill!

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM- SmartThings-Alexa/issues/21# issuecomment-279101759, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- RVG2c4cKKcytFrF7OFGHbms0MqOks5rbP5jgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21# issuecomment-279114507, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- dEXFBNKO0Q0Pw23pbSdv34hfrS9ks5rbR1YgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21#issuecomment-279714189, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi-cf5lokvp8FrtRsowzHoUmF5td4Kks5rcbOIgaJpZM4L92H7 .

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

bubagump commented 7 years ago

So a new issue has arisen. I had an outage of my router today and had to reboot it. Now all the RM bridge LAN devices are showing up as 'inactive' in the smartthings IDE and they are not working. All other Z wave switches are working fine. How can I fix it?

On Tue, Feb 14, 2017 at 6:33 PM, Becky Onuschak notifications@github.com wrote:

It doesn't happen for me all the time but does sometimes. On Feb 14, 2017 3:17 PM, bubagump notifications@github.com wrote:Interesting..if it helps in troubleshooting, this problem does not occur for any z wave switches connected through smartthings..

On Feb 14, 2017 6:00 AM, "Becky Onuschak" notifications@github.com wrote:

I have started having this trouble lately as well. Wondering if it is related to the hub update they ruled out a week or 2 ago. I'll try to dig in but if it's the hub acting oddly is not always an easy fix. On Feb 11, 2017 1:43 PM, bubagump notifications@github.com wrote:First of all, many thanks for developing this code and your prompt help. I truly appreciate it. I will try a different phone and might also setup a tasker routine to wake up the phone periodically.

I agree that having the DTH send the quote twice might create problems with some toggle switches that I might want to add. Perhaps the Alexa skill will fix this strange issue. Will you be sending an announcement when the skill is ready?

On Fri, Feb 10, 2017 at 6:30 PM, Becky Onuschak < notifications@github.com>

wrote:

So the firmware is not the issue. I don't know anything about the galaxy. Only way to check it that i can think of is to try a different Android like a phone. Did the galaxy stay awake all the time? If not that could be it. One workaround would be to edit the device handler to send the code twice, with a pause between if necessary. The "multi switch" version has the pieces you could use but if you need help let me know. Also this should work fine with etekcity outlets, as it's fine if they get the command twice but would cause problems with any toggle switches. On Feb 10, 2017 8:48 PM, bubagump notifications@github.com wrote:I am using LAN version of the DTH and broadlink firmware version is V20025. So I am at my wit's end with this issue. It always works when I repeat the command to Alexa the second time because the broadlink device only responds on the second attempt. I will check again if this issue exists when trying to control directly from smartthings app after a gap of not using the device for a couple of hrs. If the switches do not respond right away with the smartthings app, would that be an issue with the galaxy timing out?

On Fri, Feb 10, 2017 at 4:18 PM, Becky Onuschak < notifications@github.com>

wrote:

That helps a bit. If it works the first time when you control it from smart things then it's probably not your galaxy device, but again it's not something I've seen so I'm guessing. Are you using the LAN or cloud version of the smart things device handler? Also likely unrelated but some people have odd issues if the broadlink firmware is not up to date. Do you know what version you are on?

On Feb 10, 2017 6:27 PM, bubagump notifications@github.com wrote:It seems to happen only through Alexa. If I watch the broadlink after I give a voice command to alexa, the yellow light on the broadlink blinks only after I repeat the command the second time and then it works. Do you think it might have something to do with the galaxy s3 I am using for the RM bridge? I have several z wave dimmer switches which work fine with alexa through smartthings and do not have this issue. Eagerly awaiting the alexa skill!

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM- SmartThings-Alexa/issues/21# issuecomment-279101759, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- RVG2c4cKKcytFrF7OFGHbms0MqOks5rbP5jgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM- SmartThings-Alexa/issues/21# issuecomment-279114507, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- dEXFBNKO0Q0Pw23pbSdv34hfrS9ks5rbR1YgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21# issuecomment-279714189, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- cf5lokvp8FrtRsowzHoUmF5td4Kks5rcbOIgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21#issuecomment-279900386, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi-bDRnp9_jRdUMp06Jv04oV94-4d2ks5rcmPigaJpZM4L92H7 .

beckyricha commented 7 years ago

I have never encountered this issue. It seems most likely to be something that requires debugging on your router. On Feb 15, 2017 9:34 PM, bubagump notifications@github.com wrote:So a new issue has arisen. I had an outage of my router today and had to reboot it. Now all the RM bridge LAN devices are showing up as 'inactive' in the smartthings IDE and they are not working. All other Z wave switches are working fine. How can I fix it?

On Tue, Feb 14, 2017 at 6:33 PM, Becky Onuschak notifications@github.com wrote:

It doesn't happen for me all the time but does sometimes. On Feb 14, 2017 3:17 PM, bubagump notifications@github.com wrote:Interesting..if it helps in troubleshooting, this problem does not occur for any z wave switches connected through smartthings..

On Feb 14, 2017 6:00 AM, "Becky Onuschak" notifications@github.com wrote:

I have started having this trouble lately as well. Wondering if it is related to the hub update they ruled out a week or 2 ago. I'll try to dig in but if it's the hub acting oddly is not always an easy fix. On Feb 11, 2017 1:43 PM, bubagump notifications@github.com wrote:First of all, many thanks for developing this code and your prompt help. I truly appreciate it. I will try a different phone and might also setup a tasker routine to wake up the phone periodically.

I agree that having the DTH send the quote twice might create problems with some toggle switches that I might want to add. Perhaps the Alexa skill will fix this strange issue. Will you be sending an announcement when the skill is ready?

On Fri, Feb 10, 2017 at 6:30 PM, Becky Onuschak < notifications@github.com>

wrote:

So the firmware is not the issue. I don't know anything about the galaxy. Only way to check it that i can think of is to try a different Android like a phone. Did the galaxy stay awake all the time? If not that could be it. One workaround would be to edit the device handler to send the code twice, with a pause between if necessary. The "multi switch" version has the pieces you could use but if you need help let me know. Also this should work fine with etekcity outlets, as it's fine if they get the command twice but would cause problems with any toggle switches. On Feb 10, 2017 8:48 PM, bubagump notifications@github.com wrote:I am using LAN version of the DTH and broadlink firmware version is V20025. So I am at my wit's end with this issue. It always works when I repeat the command to Alexa the second time because the broadlink device only responds on the second attempt. I will check again if this issue exists when trying to control directly from smartthings app after a gap of not using the device for a couple of hrs. If the switches do not respond right away with the smartthings app, would that be an issue with the galaxy timing out?

On Fri, Feb 10, 2017 at 4:18 PM, Becky Onuschak < notifications@github.com>

wrote:

That helps a bit. If it works the first time when you control it from smart things then it's probably not your galaxy device, but again it's not something I've seen so I'm guessing. Are you using the LAN or cloud version of the smart things device handler? Also likely unrelated but some people have odd issues if the broadlink firmware is not up to date. Do you know what version you are on?

On Feb 10, 2017 6:27 PM, bubagump notifications@github.com wrote:It seems to happen only through Alexa. If I watch the broadlink after I give a voice command to alexa, the yellow light on the broadlink blinks only after I repeat the command the second time and then it works. Do you think it might have something to do with the galaxy s3 I am using for the RM bridge? I have several z wave dimmer switches which work fine with alexa through smartthings and do not have this issue. Eagerly awaiting the alexa skill!

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM- SmartThings-Alexa/issues/21# issuecomment-279101759, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- RVG2c4cKKcytFrF7OFGHbms0MqOks5rbP5jgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM- SmartThings-Alexa/issues/21# issuecomment-279114507, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- dEXFBNKO0Q0Pw23pbSdv34hfrS9ks5rbR1YgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21# issuecomment-279714189, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- cf5lokvp8FrtRsowzHoUmF5td4Kks5rcbOIgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21#issuecomment-279900386, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi-bDRnp9_jRdUMp06Jv04oV94-4d2ks5rcmPigaJpZM4L92H7 .

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

beckyricha commented 7 years ago

None of my bridge devices worked this morning either. I will check the ide for their status. Sometimes these hub updates really wreck lesser used features like the hubaction command used to send http locally. May or may not be related but will check when I can. On Feb 15, 2017 9:34 PM, bubagump notifications@github.com wrote:So a new issue has arisen. I had an outage of my router today and had to reboot it. Now all the RM bridge LAN devices are showing up as 'inactive' in the smartthings IDE and they are not working. All other Z wave switches are working fine. How can I fix it?

On Tue, Feb 14, 2017 at 6:33 PM, Becky Onuschak notifications@github.com wrote:

It doesn't happen for me all the time but does sometimes. On Feb 14, 2017 3:17 PM, bubagump notifications@github.com wrote:Interesting..if it helps in troubleshooting, this problem does not occur for any z wave switches connected through smartthings..

On Feb 14, 2017 6:00 AM, "Becky Onuschak" notifications@github.com wrote:

I have started having this trouble lately as well. Wondering if it is related to the hub update they ruled out a week or 2 ago. I'll try to dig in but if it's the hub acting oddly is not always an easy fix. On Feb 11, 2017 1:43 PM, bubagump notifications@github.com wrote:First of all, many thanks for developing this code and your prompt help. I truly appreciate it. I will try a different phone and might also setup a tasker routine to wake up the phone periodically.

I agree that having the DTH send the quote twice might create problems with some toggle switches that I might want to add. Perhaps the Alexa skill will fix this strange issue. Will you be sending an announcement when the skill is ready?

On Fri, Feb 10, 2017 at 6:30 PM, Becky Onuschak < notifications@github.com>

wrote:

So the firmware is not the issue. I don't know anything about the galaxy. Only way to check it that i can think of is to try a different Android like a phone. Did the galaxy stay awake all the time? If not that could be it. One workaround would be to edit the device handler to send the code twice, with a pause between if necessary. The "multi switch" version has the pieces you could use but if you need help let me know. Also this should work fine with etekcity outlets, as it's fine if they get the command twice but would cause problems with any toggle switches. On Feb 10, 2017 8:48 PM, bubagump notifications@github.com wrote:I am using LAN version of the DTH and broadlink firmware version is V20025. So I am at my wit's end with this issue. It always works when I repeat the command to Alexa the second time because the broadlink device only responds on the second attempt. I will check again if this issue exists when trying to control directly from smartthings app after a gap of not using the device for a couple of hrs. If the switches do not respond right away with the smartthings app, would that be an issue with the galaxy timing out?

On Fri, Feb 10, 2017 at 4:18 PM, Becky Onuschak < notifications@github.com>

wrote:

That helps a bit. If it works the first time when you control it from smart things then it's probably not your galaxy device, but again it's not something I've seen so I'm guessing. Are you using the LAN or cloud version of the smart things device handler? Also likely unrelated but some people have odd issues if the broadlink firmware is not up to date. Do you know what version you are on?

On Feb 10, 2017 6:27 PM, bubagump notifications@github.com wrote:It seems to happen only through Alexa. If I watch the broadlink after I give a voice command to alexa, the yellow light on the broadlink blinks only after I repeat the command the second time and then it works. Do you think it might have something to do with the galaxy s3 I am using for the RM bridge? I have several z wave dimmer switches which work fine with alexa through smartthings and do not have this issue. Eagerly awaiting the alexa skill!

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM- SmartThings-Alexa/issues/21# issuecomment-279101759, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- RVG2c4cKKcytFrF7OFGHbms0MqOks5rbP5jgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM- SmartThings-Alexa/issues/21# issuecomment-279114507, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- dEXFBNKO0Q0Pw23pbSdv34hfrS9ks5rbR1YgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21# issuecomment-279714189, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- cf5lokvp8FrtRsowzHoUmF5td4Kks5rcbOIgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21#issuecomment-279900386, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi-bDRnp9_jRdUMp06Jv04oV94-4d2ks5rcmPigaJpZM4L92H7 .

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

beckyricha commented 7 years ago

Mine are not marked inactive. May have been an usually smart things hiccup. However my devices all seem to be marked as active or inactive based on when last used, not anything about whether smart things recognizes them. On Feb 15, 2017 9:34 PM, bubagump notifications@github.com wrote:So a new issue has arisen. I had an outage of my router today and had to reboot it. Now all the RM bridge LAN devices are showing up as 'inactive' in the smartthings IDE and they are not working. All other Z wave switches are working fine. How can I fix it?

On Tue, Feb 14, 2017 at 6:33 PM, Becky Onuschak notifications@github.com wrote:

It doesn't happen for me all the time but does sometimes. On Feb 14, 2017 3:17 PM, bubagump notifications@github.com wrote:Interesting..if it helps in troubleshooting, this problem does not occur for any z wave switches connected through smartthings..

On Feb 14, 2017 6:00 AM, "Becky Onuschak" notifications@github.com wrote:

I have started having this trouble lately as well. Wondering if it is related to the hub update they ruled out a week or 2 ago. I'll try to dig in but if it's the hub acting oddly is not always an easy fix. On Feb 11, 2017 1:43 PM, bubagump notifications@github.com wrote:First of all, many thanks for developing this code and your prompt help. I truly appreciate it. I will try a different phone and might also setup a tasker routine to wake up the phone periodically.

I agree that having the DTH send the quote twice might create problems with some toggle switches that I might want to add. Perhaps the Alexa skill will fix this strange issue. Will you be sending an announcement when the skill is ready?

On Fri, Feb 10, 2017 at 6:30 PM, Becky Onuschak < notifications@github.com>

wrote:

So the firmware is not the issue. I don't know anything about the galaxy. Only way to check it that i can think of is to try a different Android like a phone. Did the galaxy stay awake all the time? If not that could be it. One workaround would be to edit the device handler to send the code twice, with a pause between if necessary. The "multi switch" version has the pieces you could use but if you need help let me know. Also this should work fine with etekcity outlets, as it's fine if they get the command twice but would cause problems with any toggle switches. On Feb 10, 2017 8:48 PM, bubagump notifications@github.com wrote:I am using LAN version of the DTH and broadlink firmware version is V20025. So I am at my wit's end with this issue. It always works when I repeat the command to Alexa the second time because the broadlink device only responds on the second attempt. I will check again if this issue exists when trying to control directly from smartthings app after a gap of not using the device for a couple of hrs. If the switches do not respond right away with the smartthings app, would that be an issue with the galaxy timing out?

On Fri, Feb 10, 2017 at 4:18 PM, Becky Onuschak < notifications@github.com>

wrote:

That helps a bit. If it works the first time when you control it from smart things then it's probably not your galaxy device, but again it's not something I've seen so I'm guessing. Are you using the LAN or cloud version of the smart things device handler? Also likely unrelated but some people have odd issues if the broadlink firmware is not up to date. Do you know what version you are on?

On Feb 10, 2017 6:27 PM, bubagump notifications@github.com wrote:It seems to happen only through Alexa. If I watch the broadlink after I give a voice command to alexa, the yellow light on the broadlink blinks only after I repeat the command the second time and then it works. Do you think it might have something to do with the galaxy s3 I am using for the RM bridge? I have several z wave dimmer switches which work fine with alexa through smartthings and do not have this issue. Eagerly awaiting the alexa skill!

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM- SmartThings-Alexa/issues/21# issuecomment-279101759, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- RVG2c4cKKcytFrF7OFGHbms0MqOks5rbP5jgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM- SmartThings-Alexa/issues/21# issuecomment-279114507, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- dEXFBNKO0Q0Pw23pbSdv34hfrS9ks5rbR1YgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21# issuecomment-279714189, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi- cf5lokvp8FrtRsowzHoUmF5td4Kks5rcbOIgaJpZM4L92H7 .

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

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/beckyricha/Broadlink-RM-SmartThings-Alexa/issues/21#issuecomment-279900386, or mute the thread https://github.com/notifications/unsubscribe-auth/AXHi-bDRnp9_jRdUMp06Jv04oV94-4d2ks5rcmPigaJpZM4L92H7 .

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