OG Firmware 1.1.0 Released

[Ray]

I’ve just pushed out firmware 1.1.0 (user manual and api documents are also updated accordingly). This firmware addresses the following:

• The issue that ‘options’ page becomes blank at some point. I suspect this has to do with the RAM usage as the options page is the largest in size among all pages. This has been addressed by sending program memory strings directly (instead of loading it to RAM and send it). I am not 100% certain if this completely fixes the issue, but it’s my best guess.
• Changed the flash profile to 2M (with 1M SPIFFS), as some early versions of OpenGarage has only 2M flash. As a result, flash layout will change and after updating to firmware 1.1.0, the controller will reset to AP mode. So make sure to copy the settings before you update firmware, and you will have to go through WiFi setup steps again after updating.
• Added a couple of more settings to hopefully improve distance sensor readings. One is ‘Distance Reading Interval’, which defines the time between two distance sensor readings. The default is 500ms and can be suitably increased if excessive sensor noise is observed. I suspect that if the garage is large or ceiling is very all, the ultrasonic waves may have multiple reflections. Increasing the gap between two readings can help reduce the impact of multiple reflections. The second setting is ‘Sensor Timeout Option’: previously if a sensor timeout event is encountered, it caps the reading to the maximum value (450cm). Now this has been changed to ‘Ignore’ — so if a timeout event is encountered, it doesn’t count into valid readings, again, this is done to hopefully reduce the sensor noise in the case of occasional timeout events.
• Added support for several types of temperature/humidity sensors (AM2320, DHT11, DHT22, DS18B20). All of them can be powered by VCC (3.3V) and GND, and the data pin should go to GPIO5 (G05). AM2320 is a I2C sensor, so it should be connected to SDA (G04) and SCL (G05). Also, some of them may need pull-up resistor (particularly DS18B20).

To try out firmware 1.1.0, follow the User Manual and download the compiled firmware from the address below. Again, please make sure to copy or write down settings before the update, as it will change the flash layout hence the controller will reset to factory default settings (including WiFi).
https://github.com/OpenGarage/OpenGarage-Firmware/tree/master/Compiled

• This topic was modified 5 years, 2 months ago by Ray.

[006fazer]

Hi Ray,

I’m a new user of the opengarage 🙂 thanks. All is working well.

I’ve just update firmware to 1.1.0, no reset was done, it reconnect to home wifi. Is it normal ?

best regards
Eric

[Ray]

If at the homepage you see firmware version 1.1.0, then you are all set. It’s possible that a previous firmware that was uploaded to your device used the same flash layout so it didn’t trigger a factory reset. In any case, if the homepage says 1.1.0 then the firmware has been correctly updated.

[jagos]

The new OGAPI1.1.0.pdf still states 1.0.9 API at the top with a date of Sep 10, 2018. The contents seem to be updated. So the in document title is confusing and should be corrected.

[Ray]

Good catch, will fix it right away.

[antibalascoder]

Hi Ray,

Is there a way to grab the temp/Humidity measurement via MQTT or in the blynk once we connect the sensor or it can only be seen on the web app?

[Ray]

@antibalascoder: not yet — for this firmware I just did the minimum needed to get several sensors supported. Once they are verified to work, in the next firmware I can make the readings available on MQTT and Blynk as well.

[antibalascoder]

Thanks Ray. I can confirm here that the added sensor support is working. I was able to connect a DHT22 and I’m getting temperature and humidity on the web app.

[Ray]

OK, thanks for letting me know.

[vrbt150]

I have recently upgraded to 1.1.0 and I’m getting random Blynk notifications telling me my garage door has either opened or closed even tho it hasn’t.
I checked the log and the distance sensor gets a reading of ~50cm, then back to around ~125cm.

The same problem I was experiencing back with firmware version 1.0.7.

Anyone else experiencing this?

[ktiedt]

Just updated and my OG is stuck with blue flashing led… never came back up 🙁

I am guessing I’ll have to do a manual reload, since OTA is now not an option :/

Edit: And after numerous attempts to reflash over USB I am hitting the exact same problems as this user here. (tried both MacOS and Ubuntu with same results)

• This reply was modified 5 years ago by ktiedt. Reason: More info
• This reply was modified 5 years ago by ktiedt. Reason: more info, yay

[Ray]

Blue flashing LED means it’s reset in AP mode. The release notes specifically said so:

https://github.com/OpenGarage/OpenGarage-Firmware/releases/tag/v1.1.0

Just follow the WiFi setup process and get it logged onto your WiFi network again.

[ktiedt]

It seems I should pay more attention to the Release notes instead of the updating docs. My apologies.

[vrbt150]

I have recently upgraded to 1.1.0 and I’m getting random Blynk notifications telling me my garage door has either opened or closed even tho it hasn’t.
I checked the log and the distance sensor gets a reading of ~50cm, then back to around ~125cm.

The same problem I was experiencing back with firmware version 1.0.7.

Anyone else experiencing this?

I must be the only one..

I have downgraded to 1.0.9 and the problem has gone away.

[Opengarageio]

I have had blynk issues since upgrading to 1.1.0.

In the superchart I was monitoring door status (V0), car status (based on V3) and distance (V3).

I have ‘connect missing data points’ setting turned off for each. On my previous firmware version I got a great graph that showed the distance reading as well as the door status (open or closed) and vehicle status (home or out).

Now I have intermittent gaps in the data. The LCD widget is blank. The distance reading on the graph is blank when the garage door is open. And while the door status LED works, the door status graph doesnt.

I tried to load the firmware via arduino via USB cable but I got ‘espcomm_sync failed’ messages. Is that normal? I thought I would be able to upload via USB if the OTA update didnt work. (update: Need to hold down the reset button while plugging in the USB cable to allow firmware upload via arduino)

Ill try downgrading my firmware to see if that resolves some of the issues. It kept all of my settings when moving to version 1.1.0, which makes me think it hasnt cleared the old settings properly. The homepage shows that it does have the new firmware version.

• This reply was modified 4 years, 12 months ago by Opengarageio.
• This reply was modified 4 years, 12 months ago by Opengarageio.

[Opengarageio]

Just a follow up. It seems in version 1.1.0 there has been a change to the way that the data is sent to blynk. This has only affected me because I have a few modifications and additional features that I have added in to blynk.

Instead of ….Blynk.virtualWrite(BLYNK_PIN_DIST, distance);
We have……..if(distance != old_distance) { Blynk.virtualWrite(BLYNK_PIN_DIST, distance); old_distance = distance; }

So it looks like we are now only sending updated data to blynk if the value changes. Which means that there is gaps in data being reported to blynk if the value doesnt change. I guess that means that typically less repeat data is being sent to blynk. That would be fine with the default settings, where blynk is configured to just join missing data points. But with my settings, I dont want to connect missing data points.

So I guess I have to either stick with the default blynk settings or modify the program to get opengarage to constantly send data again.

My modifications are to have the counter back in blynk as well as showing the car status.

[Opengarageio]

Just a follow up. I think I can just tinker with the blynk settings to get the output Im after. Or failing that I know now what part of the code I need to modify if I do want continuous readings. So there is no issue with 1.1.10, just messed with my custom setup a bit.

I also connected up a DHT22 sensor and confirmed thats working now too. I added another couple of lines of code to send the temp and humidity to blynk and that seems to be working well now too. Very happy to have been able to add the temp/humidity option. Thank you for adding that option for us.

[Opengarageio]

Sorry to keep replying. But I am still having problems with opengarage 1.1.0 on iOS with blynk and the chart.

The door status graph stops working after a few hours and the IP address also drops out from the LCD display after a few hours. I also graph the car status and that drops out after a few hours too.

I can see in the new code that the data is only being sent when it changes and Im thinking it might have something with blynk not pulling the data after a period of time. Like if the IP address hasnt been received after 6 hours, blynk seems to stop showing it. Anyone else??

[Ray]

Since you said you have the LCD widget, I assume you still have the older blynk project while in the new blynk QR code we have removed the LCD display because it’s not that useful and there is now an audible way to find out the IP address instead of having to rely on the LCD widget. Make sure you have the latest blynk project (QR code is in the user manual:
https://github.com/OpenGarage/OpenGarage-Firmware/tree/master/docs

The changes in 1.1.0 are indeed to reduce the web traffic to blynk, so that it only needs to send data when they change. In fact there was originally plan to use blynk more deeply for cloud connection (i.e. sending all status data to blynk server), and in the process of doing that, we want to reduce the amount of data to send to blynk server. But shortly before 1.1.0 was released we dropped this plan so it’s not sending all status data to blynk yet, but the changes to reduce web traffic has been preserved.

[trillian]

I have updated my FW to 1.1.0. I was getting the issue where the options screen would not load. The update seems to have resolved the issue.
I also added a DHT22 sensor which is working well.
Thanks for the update and new features.

[trillian]

I started logging the new sensor values from the DHT22, it’s looking quite good.
I have not used the sensor before and noticed that it returns some obviously erroneous errors from time to time. I didn’t add the pull up resistor as I believe the DHT22 does not need it, could that be the cause?

Could a filter algorithm be added to remove the odd spike?

I updated the Home Assistant OpenGarrage integration to graph the data. Image attached.

Attachments:

You must be logged in to view attached files.

[brendans]

Hi Trillian, how did you bring the temperature and humidity values through to Home Assistant? Does the default platform have the capability? I have the DHT22 working on the OG web server but want to show these in HA. Cheers

[tekbar7522]

Trillian, can you let me know how you added the temp and humidity into home assistant?
Brendans, were you able to figure it out?

[tekbar7522]

Nevermind, I figured it out. I did it like this just in case anyone else is interested. Just change the IP address of your opengarage.

sensor:
  - platform: rest
    resource: http://192.168.1.111/jc
    name: attic temp
    value_template: '{{ value_json.temp }}'
    unit_of_measurement: '°C'
  - platform: rest
    resource: http://192.168.1.111/jc
    name: attic humidity
    value_template: '{{ value_json.humid }}'
    unit_of_measurement: '%'

[brendans]

Thanks tekbar7522. I never got this sorted. Can confirm using your code works for me too, thanks!

[Author]

Posts