Forum Replies Created
-
Posts
-
@Scott: thank you very much for sharing!
I assume you are referring to the Blynk app notifications. I really don’t know — it could be due to a lot of possible reasons, for example, your phone may be delaying the notifications; if your phone is on power saving mode it delays notifications; there could be a connection issue between the Blynk server and your phone.
As I said, it’s very unlikely it’s bricked — the firmware you uploaded probably had a problem which caused it to not respond. But the chip can still be reprogrammed I am pretty sure.
Does pressing the button for 10 seconds recover it to factory default? If not, you may have to send it back to us for reflashing firmware through USB. I don’t think the chip is bricked — the bootloader is very robust that unless if the chip is physically damaged it’s almost not possible to brick it. The only thing is that the current version of OpenGarage no longer has built-in USB-serial chip, so if for whatever reason the OTA update doesn’t work, you will need to send it back to us as we have a special programmer to plug into the board to program it. You can also use your own USB-serial cable/adapter but it requires a bit of soldering.
The flashing blue light: is it relatively high frequency (like more than 2-3 times a second) or relatively low frequency (like once per second)?
You can perform a factory reset: when the device is powered on, press and hold the button for 10 seconds, then release. It should recovery to factory reset.
A while back we published an article about how to make OpenGarage work with Amazon Alexa:
“Alexa, Open Sprinkler Zone 1” — How to Use IFTTT with OpenSprinkler (and OpenGarage)
this is done through IFTTT which can connect Alexa or Google Home with your OpenGarage. The connection to OpenGarage can be done either through port forwarding or using the Blynk API (more secure). The steps are a bit technical, but try to see if the instructions make sense and if you need help we can provide more details.Since the sensor is based on ultrasonic, if there is anything nearby that’s generating ultrasonic signals, it could interfere with the sensor. Also, try to use a different USB adapter as the USB adapter quality may be a factor. If you suspect it’s the sensor’s problem, you can send email to:
[email protected]
for support. The freshdesk support system should work fine with your email address to log in, but if you can’t log in, just email me to get support.Please use your email address to log in. Somehow using user name to log in results in session expired error, still investigating.
If you haven’t done so, please submit a support ticket so we can send you diagnosis instructions and send a replacement if needed.
No, you don’t have to empty the log events: it’s set to the most recent 200 records, and when it’s full it overwrites the oldest record, so it’s on a rotating basis.
You said “Not everyone runs it internet connected” — but I don’t understand the point of using OpenGarage if it’s not Internet connected — I mean, without the ability to remotely monitor and control the door, how is this different from a standard, non-WiFi based garage door remote?
Glass should be fine because the sensor uses ultrasonic waves (not light) to detect the door, so optical reflection does not affect the sensing.
If blue light does not blink within 10 seconds (sometimes the logic is reversed, so it stays on, and blinks off every few seconds, that’s normal), it sounds like the software is getting stuck somewhere, which could be because of sensor reading or something. On the other hand, if you can still connect to it (albeit very slowly), that means it’s still running and the blue light should blink even if very infrequently. Something isn’t very consistent here, I feel.
We can probably add an option to customize the DNS IP as well. But generally we don’t recommend setting static IP on Opengarage — I know this is provided as an option, but we recommend you to use the DHCP reservation feature on your router to assign a fixed IP to the device. This way the DNS IP is assigned by the router and you don’t have to put it in manually on Opengarage.
What type of garage door do you have? If the logic is reversed, the simplest fix is to go to Settings and change the ‘Mount Type’ from Ceiling Mount to Side Mount. That reverses the logic.
The adapter is not made by us — it’s a standard LiftMaster security+2.0 door button. The only thing we do is to solder wires to the button so it can interface with OpenGarage. How do we know the schematic if the manufacturer doesn’t publish it?
Yes, as you have figured out, it does support control as well. Sorry that this is not well documented. We will add documentation to the user manual.
If OpenGarage is to function as HTTPS server, you need to install SSL certificate, which is a hassle. The Blynk way (through cloud server) is more efficient and scalable. Blynk gives 2000 points to begin with, and the OpenGarage Blynk app uses less than 2000 points.
@florian.zahn: for OpenGarage, since it supports Blynk, you shouldn’t need to use port forwarding so ipv6 doesn’t really matter.
The OpenGarage product page explains it:
Specifically: For Security+ 2.0 systems (with a yellow antenna and yellow learn button), please add a Security+ 2.0 adapter to your order.I am not: I have used Blynk for more than 3 years and it has always been quite reliable. What phone do you use?
The car present indicator currently is only available in the direct web interface, I think — it hasn’t been added to either Blynk app or OpenGarage app.
Because the controller currently does not detect or store your time zone, this time needs to be UTC time (i.e. Greenwich time). For example, if your time zone is UTC-4, and you want it to close at 10pm your time, you have to calculate the UTC time (which would be 2am).
