[Ray]

I am aware of the issue. Currently investigating. We’ve just released firmware 1.2.3, which has added support for email notifications. As most users have migrated to OTC, we will probably phase out Blynk soon, since iPhone users can no longer use the legacy Blynk app.

[Ray]

What version of firmware is running on your opengarage?

[Ray]

Yes, you can. Take a look at the OpenGarage API document for explanations of supported MQTT topics.

[Ray]

You can set up to 10 OpenGarage devices in the same account. There is no charge.

[Ray]

We are looking into this. It’s a server overload issue most likely.

[Ray]

https://github.com/openthingsio
You can follow the instructions in the Proxy repo to set up your own server.

[Ray]

We are looking into the issue and it should be fixed shortly today. Thanks for your understanding.

[Ray]

You can NOT use both at the same time. It should be obvious because the selection of Blynk and OTC are through a radio button so you can only select one of them. It’s by design. If you prefer OTC but want notification, you can use IFTTT notification.

• This reply was modified 2 years ago by Ray.

[Ray]

Yes you can do the same with blynk.openthings.io

[Ray]

Based on the picture, it should be upgradable to 1.2.0

[Ray]

Your picture isn’t attached correct. You can either shrink the picture or upload it to google drive or something and post a link

[Ray]

Google “DS18B20 ESP8266”.

[Ray]

Did you buy OpenGarage from us or did you build one yourself? I am not aware of this as a common problem. If you build it yourself, you need to be careful which GPIO pin you use for the relay — the official OpenGarage uses GPIO 15, which is pulled down at boot so shouldn’t trigger any action. If you used other pins, some of them will briefly go high which will trigger garage door action.

[Ray]

re: flash memory: even with 2MB flash, the firmware upgrade can still succeed, but there will be issues, most likely it never goes out of AP mode. Since yours is connected to your WiFi, I assume yours is 4MB flash. I should probably update the firmware to include the flash memory size as a controller variable or debug variable.

As I said, once in a while it may stop responding to ping, but it should recover after a while. Does yours stop responding and never recover? I am not sure what the openhab integration ping does, I can run a javascript locally to ping on a regular interval. When the local IP stops responding, does OTC API still work? I know the beta version had a problem where it can lost local connection permanently. I’ve fixed that issue in the OTC library so firmware 1.2.0 shouldn’t have that issue anymore.

[Ray]

Probably the only way to tell is to check the OpenGarage circuit board. If it looks like this: (ESP8266-WROOM2) then it’s an early version with only 2MB flash:
https://cdn.sos.sk/productdata/29/56/3f698269/esp-wroom-02.jpg

If it looks like the one below (ESP12-F or ESP-12E) then it has 4MB flash:
https://www.elecrow.com/pub/media/blog/cache/840×620/magefan_blog/_-1_04_3.jpg

Because this firmware is larger than 512MB, and support OTA firmware update requires twice as much space as the firmware itself, it needs at least 2MB for firmware storage, plus another 1MB for settings and log, so it needs a minimum of 3MB flash (the closest being 4MB as there is no version of ESP8266 with only 3MB flash).

The OpenThings API may occasionally have a hiccup or two due to the access rate limit set on the server (we will tweak this later) but usually after a while it recovers. I don’t recommend querying it too frequently, like using a script or other home assistant device. I’ve had two installed with OTC tokens and have tested them over a week and they continue to work just fine, both through local IP and through OTC API.

• This reply was modified 2 years, 3 months ago by Ray.
• This reply was modified 2 years, 3 months ago by Ray.

[Ray]

The best way is probably modify the firmware and recompile it yourself. The particular 15 second interval is here in the source code:
https://github.com/OpenGarage/OpenGarage-Firmware/blob/master/OpenGarage/main.cpp#L1304

[Ray]

Are you using the OpenGarage app? The latest OpenGarage app does support OTC token but it assumes the official release site (cloud.openthings.io instead of test.cloud.openthings.io), so the cloud server it’s connecting to is not the same as the beta test server. At the moment I suggest you follow the methods in:
https://tinyurl.com/otcbetadoc
to do remote access.

[Ray]

Make sure you download the Blynk legacy app. The new IoT app is very different and does not work with OpenGarage.

[Ray]

We are working on getting this firmware officially released (which will probably happen in another week or two). While the beta test described in the doc should still work (all the servers are still online), you might want to wait for a couple of weeks for the official release.

[Ray]

Firmware 1.1.2 is officially released, so the beta link is no longer available.
https://github.com/OpenGarage/OpenGarage-Firmware/tree/master/Compiled

[Ray]

An update: we’ve replicated the Blynk server at openthings.io. While we are still working on transitioning to our own OTC cloud server, at the moment you can continue using the Blynk (legacy) app by setting it to use our custom server:
https://openthings.freshdesk.com/support/solutions/articles/5000872170

• This reply was modified 3 years, 4 months ago by Ray.

[Ray]

We are just made aware of the fact that Blynk legacy app has removed new user registration, and we are working on transitioning to use our own cloud server. Here are some temporary work-arounds and notes:

0. Those who already have an account with Blynk legacy app are not affected at the moment.

1. Any new OpenGarage users: if you are using Android phones — the Blynk legacy app still allows you to log in using a facebook account; if you are using iOS: unfortunately this is not an option any more.

2. We do have a 2.0 beta version of our OpenGarage firmware that adopts our own cloud server, and it has been out for a while:

OpenThings Cloud (OTC) Beta Test Call for Help

Samer has been working to integrate this into the OpenGarage app, and once this is done, there is no longer need to use Blynk app. At the moment, remote access can be done through the web access described in the post. As soon as we finish the app integration, remote access can also be done through the app.

3. We will also be running a private Blynk server on our own cloud server as a backup plan. The Blynk legacy app still allows accessing using a private Blynk server (although the Blynk legacy app itself is probably on the way out so they may pull the plug completely at any time). This is only being prepared as a backup plan in case OpenGarage 2.0 has any major problems.

[Ray]

I don’t think so. The implemented sensors are all in the source code:
https://github.com/OpenGarage/OpenGarage-Firmware/blob/master/OpenGarage/OpenGarage.cpp#L353
I am not sure if SHT20 is similar to DHT11 or DHT22, but it can be easily added if not.

[Ray]

Thanks for the contribution!

[Ray]

You have to use a large flat surface, like a relatively large cardboard box. Paper is too small because ultrasonic waves are not lasers, they can’t pin point the distance to a small object. It has to be a relatively large flat surface.

[Author]

Posts