Forum Replies Created
Holding the button for 10 seconds doesn’t work. OG isn’t connected to my wifi router and I can’t find an OG_ prefix AP in my phone’s wifi, so I guess it’s broken.
It’s showing blue light exactly once, not flashing/blinking. This happens to both normal power on and my attempt to power on to booatloading mode.
I did manage to compile my modified (different modification: https://github.com/OpenGarage/OpenGarage-Firmware/pull/26) firmware and it works fine, so I’m not sure that my esp8266 version is wrong…
When trying to compile the firmware with
BlynkSimpleEsp8266_SSL.h(this is with Arduino app, Using Makefile always complain that it can’t find Blynk header files), the compiler complained about:
In file included from /Applications/Arduino.app/Contents/Java/libraries/OpenGarage/main.cpp:28:0: /Applications/Arduino.app/Contents/Java/libraries/blynk-library/src/BlynkSimpleEsp8266_SSL.h:27:55: error: expected initializer before 'PROGMEM' static const unsigned char BLYNK_DEFAULT_CERT_DER PROGMEM = ^
I didn’t see
PROGMEMdefined in the whole blynk-library code, not sure what to expect…
- This reply was modified 2 years ago by fishy.
And I just finished the SmartThings integration here: https://github.com/fishy/SmartThings-OpenGarage
Additional question for 2: Is it implemented via direct open/close command from the relayed garage, or is it still switch, just the firmware code will check the current status first? If it’s the latter then I can implement that logic on SmartThings instead (and still use blynk).
1. It would be nice to have a switch on the web config ui so user can choose between http and https 🙂
2. Nice! Is it possible to expose open and close commands to blynk? I do have a linux box running in the house with nginx and let’s encrypt configured so I can use that to proxy to open garage API, but blynk would still be more user friendly.