Forum Replies Created
-
Posts
-
Newer update to this… I cut IFTTT out of the picture completely. I setup MQTT and that updates the switch in HomeSeer. Loving my expanded hobby into Home Automation.
Thank you for the help. Figured it out.
For reference: https://github.com/OpenGarage/OpenGarage-Firmware/blob/master/docs/fw1.2.0/OGAPI1.2.0.pdfJust a quick follow-up in case anyone is interested…
I made this work by running HomeSeer HQ4 and tied a virtual switch to my OpenGarage via IFTTT. IFTTT updates the switch. HQ4 events send web requests to OpenGarage when the switch is toggled.
Alexa integration with HS4 shows the switch which enables me to control my door. I set routines up in Alexa to respond to “Open Garage Door” and “Close Garage Door” to toggle the switch.Just a quick update that I updated from 1.08 to 1.20 without any problems. Furthermore, I was pleasantly surprised that my settings were not reset. I switched over to OTC + IFTTT which works great.
I’ve been controlling my OpenGarage for years via IFTTT going through http://cloud.blynk.cc and activating pin V1 to simulate clicking the garage open/close button. With this shutting down in a few weeks, I’m curious if the same functionality will work once I migrate over the blynk.openthings.io? I have an Android device and I’m hoping that once I reset the Legacy Blynk app, I’ll be able to set up the customer server per https://openthings.freshdesk.com/support/solutions/articles/5000872170-using-blynk-legacy-app-with-openthings-blynk-token
Trying this again!
Ray, can you please check out this photo https://1drv.ms/u/s!Asjb9_Aw9XW1nbc6wV0TRfJXGXBtOQ?e=CopLXKI’m trying to figure out which OG I have to know of it is compatible with 1.20. Can someone please help me understand from the picture. I’ve had it for about 5 years now.
Yeah, I can’t reproduce it anymore either.
I hear what you’re saying and I am going to leave it with the audible warning. With that said, one could argue that a standard remote control for a garage door also doesn’t give any audible warning (ex. I’m in the garage when my wife pulls up in her car). I’m not sure how this is any different.
Update: I somehow managed to fiddle enough with the wires and push the button on the device enough to fix it. However, I’m still baffled as to what the LED signifies. I’d love some explanation of that.
Mine is new. Just got it last November and it had a clear case.
Are there some logs I can pull that can help the developers understand why this is failing to update?
Maybe it’s just me but I can’t get this to upload. It always fails for OTA update. I haven’t tried the USB route yet simply because it’s a bit more effort to get on a ladder and unscrew the device from my ceiling.
Thanks. I installed Blynk and following what was mentioned here:
I was able to very easily modify the WebRequests I had in IFTTT to perform the open/close of the door and close off the external access to the OpenGarage hardware. I think the instructions should never suggest port forwarding if the device doesn’t have the proper security in place to handle outside access.
Yes, via port forwarding. I am using IFTTT plus apilio.io to do things like close my garage when my garage has been open for 20 and it’s after 10pm. If it’s before 10, send me an SMS if it’s open for more than 20 min. I can also use IFTTT with my Amazon Echo to “trigger close garage door” or “trigger open garage door” and it will close/open it checking the current state as opposed to just a reversal of the last state.
I’m not sure if Blynk can work with IFTTT. I was not only trying to avoid depending on another app and another service, but also it looked like IFTTT was to some degree integrated. It looks like only to send. To receive, the device had to be exposed publicly (hence the port forwarding).
