OpenGarage Forums OpenGarage Firmware Firmware 1.2.0 pre-release, supports both Blynk and OTC

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #2487

    Ray
    Keymaster

    Hi, after a long time, we’ve finally getting ready to release firmware 1.2.0, which includes supports for both Blynk and OTC cloud connections. Currently the firmware is at the development branch in the OpenGarage github:
    https://github.com/OpenGarage/OpenGarage-Firmware/tree/dev-1.2.0
    Specifically, the compiled .bin file is in the Compiled folder, and the user manual and API document for firmware 1.2.0 have both been added. The main change in this firmware is that you can choose to use either Blynk or OTC as cloud option. Each has its own pros and cons (for example, Blynk supports push notification but the Blynk legacy app has been discontinued, at least for iOS users, if you don’t already have this app installed, it’s no longer available; for android users, you can still find the Blynk legacy app apk online. On the other hand, Blynk doesn’t support changing options or view log data remotely, while OTC allows access to the entire built-in web interface remotely etc.). We have added a support article describing how to create and use either of them:
    https://openthings.freshdesk.com/support/solutions/articles/5000878722-opengarage-cloud-connection-for-remote-access

    Please note that firmware 1.2.0 only works on ESP8266 WiFi chips with 4MB flash. All recent OpenGarage devices (e.g. v1.4, v2.0 etc) have 4MB flash; the earlier versions (v1.0 and v1.1) have only 2MB flash so this firmware won’t work on those.

    We will leave the firmware in the development branch for a couple of weeks to gather some feedback, once all potential issues have been ironed out we will move it to the master branch. Thanks.

    If you have previously seen the OTC beta call for help post:

    OpenThings Cloud (OTC) Beta Test Call for Help


    Please note that the official OTC server is now at cloud.openthings.io and OTC token creation is done at openthings.io (which shares the same login as opensprinkler.com). The beta test server was at test.cloud.openthings.io (and the OTC token create was done at test.openthings.io). While the beta test server is still available, it will probably be discontinued at some point. So those who are currently using the OTC beta test version should update your firmware to 1.2.0 and create new OTC token at openthings.io

    I know there is some confusion about the numbering of the firmware (the beta test firmware was numbered 2.0.0, but I’ve decided not to jump that far so numbered the official release as firmware 1.2.0).

    #2488

    psmedley
    Participant

    Hi Ray,

    Installed this build this morning – not 100% sure what OG version it is – but I’ve had it for at least 5 years – perhaps longer. I don’t remember if it’s one I brought from our old house, or if I ordered a new one when we moved here.

    With the previous 2.0.0 build I had issues where after a period of time, the OG became unresponsive on it’s local IP – seems I’m having that issue again.

    Initially I connected it to the new openthings API – after an hour or so, I couldn’t access the web ui (which I use in conjunction with OpenHAD). I’ve now reset the unit to defaults, and have configured WITHOUT the openthings API to see if it changes anything.

    Is there an easy way to tell which OG hardware revision I have?

    Cheers,

    Paul

    #2490

    Ray
    Keymaster

    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 3 months, 4 weeks ago by Ray.
    • This reply was modified 3 months, 4 weeks ago by Ray.
    #2493

    psmedley
    Participant

    Hi Ray,

    My OG has been stable for > 24 hours now running the latest firmware and NOT connecting to openthings.io

    I’m querying the local IP every 60 seconds for openhab integration – but with openthings.io it stops responding after a while.

    re: the flash memory – I’m assuming that if the flash succeeded all is well?

    Cheers,

    Paul

    #2495

    Ray
    Keymaster

    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.

    #2496

    psmedley
    Participant

    Hi Ray,

    I’ll try connecting it to openthings.io again. My recollection from testing the 2.0 firmware was that OTC API keeps working, but port 80 stops responding. Openhab just polls the web interface every minute to check the door status.

    When I updated on Friday morning, I was periodically trying to refresh the webui on my laptop, and couldn’t get it to load at all…

    Cheers,

    Paul

    #2514

    Chad
    Participant

    I’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.

    #2516

    Ray
    Keymaster

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

    #2517

    Chad
    Participant

    Trying this again!
    Ray, can you please check out this photo https://1drv.ms/u/s!Asjb9_Aw9XW1nbc6wV0TRfJXGXBtOQ?e=CopLXK

    #2519

    Ray
    Keymaster

    Based on the picture, it should be upgradable to 1.2.0

    #2520

    Chad
    Participant

    Thank you! For my reference, can you tell what version of OG I have?

    #2525

    Chad
    Participant

    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.

Viewing 12 posts - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.

OpenGarage Forums OpenGarage Firmware Firmware 1.2.0 pre-release, supports both Blynk and OTC