Forum Replies Created

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • in reply to: OG Firmware 1.1.0 Released #1561

    vrbt150
    Participant

    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.

    in reply to: OG Firmware 1.1.0 Released #1539

    vrbt150
    Participant

    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?

    in reply to: reminder for open door at 10 p.m. #962

    vrbt150
    Participant

    I recently had a situation where my garage door nearly closed on my car while pulling into the drive way.

    I had the auto close setting set to UTC: 13; 21:00 my local time.
    I got home just before 21:00, opened the garage, went to drive in, and the garage door auto closed on me.

    This got me thinking, that maybe a delay or dismiss feature is needed when auto closing if the door has recently been opened.
    Hopefully in future versions 🙂

    I’ve since disabled the auto close in the firmware, and gone back to using my python script.
    I’ve modified it so it will check the current OG epoch time against the last door event.
    If the door is open, and the last door event was 5 minutes or less, it will skip running the auto close.

    #!/usr/bin/env python
    
    import requests
    
    og_address = 'opengarage.lan' # set OG IP or hostname
    og_password = 'opendoor' # set OG password
    og_doorwait = 300 # door auto close dismiss time (sec)
    
    og_jc = requests.get('http://%s/jc' % og_address).json()
    og_jl = requests.get('http://%s/jl' % og_address).json()
    door_status = og_jc['door']
    og_time = int(og_jl['time'])
    og_log = og_jl['logs']
    
    if door_status == 1 and og_time - og_log[len(og_log) - 1][0] >= og_doorwait:
        parameters = {'dkey':og_password,'close':'1'}
        request = requests.post('http://%s/cc' % og_address, params=parameters)
    in reply to: Announcing OpenGarage Firmware 1.0.7 #948

    vrbt150
    Participant

    Thanks Ray.

    I’ve been running 1.0.8 for 2 days now, and haven’t experienced anymore random Blynk notifications.

    in reply to: Announcing OpenGarage Firmware 1.0.7 #934

    vrbt150
    Participant

    If you’re like me, you’ve purchased the black box rather than the clear box early on. I was never able to get OTA working with it and had to update by USB. I had the same complaint as you that I had to get the ladder out just to update.

    On another note, I’ve been having Blynk issues with this firmware where I sometimes receive Blynk notifications indicating that my garage is open or has been open for an extended period of time. If you view the logs, the last log will still show it’s closed. So there may be an issue with the logic in determining whether the door is actually open.

    I also have the older black box. I’ve been having having similar issues with 1.0.7. I will get random Blynk notifications telling me my garage door is closed even tho it hasn’t been opened. Looking at the CVS data, it seems the sensor distance goes from ~122cm to about 50cm momentarily then back to ~122cm.
    I’ve since flashed back to 1.0.6 and problem has gone away, and the CVS data indicates a steady ~122cm, give or take.

    in reply to: Power OG from Garage Door transformer? #524

    vrbt150
    Participant

    My garage door has a 24VAC output off the main circuit board, so I purchased a 24VAC to 5VDC buck converter and soldered a USB connector on the output end to power my OG. They can be picked up cheap off eBay. I’ve been running it like this for over a year and never had any problems. It saves having to run a separate AC transformer to power the USB connection.

    Here is a link to the one I purchased.
    http://www.ebay.com.au/itm/Car-LED-Waterproof-DC-AC-DC-Buck-Converter-24V-12V-36V-8V-40V-to-5v-1A-5W-/281625925676?hash=item419236982c:g:i-sAAOSwopRYaPuu

    in reply to: reminder for open door at 10 p.m. #500

    vrbt150
    Participant

    Hi Chad, I’ve got a crontab (scheduled job) setup on my linux box that runs that script every night at 10pm. It communicates over http using the OG API.

    in reply to: reminder for open door at 10 p.m. #252

    vrbt150
    Participant

    Hi, I’ve created a Python script to check the door status that uses the OG API.

    It uses the Requests package for Python.

    #!/usr/bin/env python2
    
    import requests
    
    og_address = 'opengarage.lan' # set OG IP or hostname
    og_password = 'password' # set OG password
    
    response = requests.get('http://%s/jc' % og_address)
    data = response.json()
    status = (data['door'])
    
    if (status == 1):
        parameters = {'dkey':og_password,'click':'1'}
        response = requests.post('http://%s/cc' % og_address, params=parameters)
    • This reply was modified 8 years, 2 months ago by vrbt150.
Viewing 8 posts - 1 through 8 (of 8 total)