Forum Replies Created
-
Posts
-
You can use your OpenThings / OpenSprinkler login to log into freshworks. Does it not work? You can also use your Google account to log in, or Facebook, Twitter account. Finally you can also email to [email protected]
So I finally sat down to look at what was wrong with the HC-SR04 sensors, and the discovery was quite interesting: it turns out it’s a capacitor on the circuit board that went bad, replacing that capacitor fixed the defective sensors. My suspicion is that this batch of sensors are technically HC-SR04P, rated for 3.3V to 5V (the original HC-SR04 is rated for 5V only). My guess is that the manufacturer assumed anyone who buy these are only using it under 3.3V (otherwise you would have chosen the original HC-SR04, which is the same price). As a result, they may have used subpar capacitors which are not rated for 5V. On OpenGarage the power pin of the distance sensor is still connected to 5V, so that may have resulted in the capacitor failing over time. This is really annoying, but at least we figured out what went wrong. We had several returned OG that had similar symptoms (distance stuck at 3 to 5cm). After replacing that capacitor they all went back to function normally. A small capacitor makes a huge deal…
Sure, adding another field for NTP is pretty straightforward.
I haven’t had time to update the API document. The added option name is ‘dns1’:
https://github.com/OpenGarage/OpenGarage-Firmware/blob/dev-1.1.1/OpenGarage/defines.h#L148
the reason it’s called dns1 is that the ESP8266 library can accept 3 DNS servers, so in the firmware we left dns1 as user-configurable, and the other two default DNS server IPs. The format of this parameter is the same as other similar parameters (i.e. dvip and gwip).In the blog post where I initially announced OpenGarage, I shared a Tinkercard link to the 3D enclosure:
Introducing OpenGarage: an Open-Source WiFi Garage Door Opener
That’s for the first version of OpenGarage. The current version is slightly modified, and we now use laser-cut acrylic enclosure. The laser-cut design is embedded in the EagleCAD files of the PCB, in the ‘Enclosure’ layer.This feature has been implemented in firmware 1.1.1, as described here:
A new firmware (1.1.1) has been committed to github (it’s in dev-1.1.1 branch, not yet merged with master). You can download and try the compiled firmware 1.1.1:
https://github.com/OpenGarage/OpenGarage-Firmware/tree/dev-1.1.1/CompiledIt added DNS parameter which should fix the NTP time sync issue when using static IP. It also includes another option to disable alarm when opening door (thus alarm is only effective when closing the door, per request from another thread).
You can order the adapter separately here:
What type of garage door system do you have? Maybe you need the security+ 2.0 adapter — this is required if your system comes with a yellow antenna or yellow learn button.
Thanks, yes I did pretty much make the same changes and that indeed fixed the issue. I haven’t got around time to push the code out yet but should be able to do so this weekend. Thanks.
Probably not — the current MQTT implementation does not incorporate HTTPS connection. If you want to enable user name and password, most likely that’s going to require HTTPS connection, and this is not implemented in the firmware yet.
As the release note of firmware 1.1.0 says: upgrading to 1.1.0 will restore the controller in AP mode — this is because 1.1.0 uses a different flash layout, so it will not preserve the WiFi settings. If you hear beeping sound, that means it’s in AP mode (it’s not bricked, otherwise you won’t even hear the beeping sound), you just have to repeat the WiFi setup step to get it log on to your WiFi router again.
Yes, this is most likely a DNS issue — the current firmware 1.1.0 does not accommodate custom DNS. I’m already working on firmware 1.1.1 which will allow custom DNS and should fix this issue. In the meantime, as suggested earlier in the thread, you can use your router’s DHCP reservation feature to bind a fixed IP address to the controller — there is no need to set static IP on OpenGarage, instead, leave it in DHCP but use your router to set a fixed IP to it.
OK, will update document. Actually, where did you see the instructions for firmware update using USB? The current OG user manual only mentions OTA update, does not mention anything about USB firmware update:
https://github.com/OpenGarage/OpenGarage-Firmware/blob/master/docs/OGAPI1.1.0.pdfLet me first answer your second set of questions:
Blynk App Questions:
What device type do you choose for the OG? My Blynk app just lists it as Generic Board. Does it even matter? This is what it chose after I scanned the QR code for OG.===> It doesn’t matter. Generic Board is fine.
My blynk app shows no history values, an incorrect distance value and generally looks useless. Clicking Door Button does nothing. Do you Blynk Apps control the OG and show real useful data?
===> Are you sure the Blynk project is in ‘running’ state? Do you see a green triangle button at the top-right? If so, that means you have not run the project yet. By default, right after scan, the project is in ‘stopped’ state.
The zener diode is actually not necessary — the only diode you need is the one for the relay, which serves as a flywheel diode.
Any 5mm/5.08mm terminal block would fit (or you don’t really need a terminal block, you can just solder two wires onto the terminal block pins).
Relay: the one we use is HK23F-5V. Pretty much any relay would work fine — garage door systems actually use fairly low voltage (often 12VDC) while typical relays are rated for at least 110V, so the requirement on the relay is very low.
You can use your opensprinkler.com account to log in. Or you can log in by using your Gmail or social media account such as facebook or twitter.
No idea — I haven’t received such notification actually. Just checked their website, there is indeed a beta version of the new app. Will try that out shortly.
I suggest that you submit a support ticket so we can arrange to get it back to us for some testing. It could be the problem of the distance sensor, or maybe some other sources in your garage that interferes with the ultrasonic sensing.
It may be easier to get an off-the-shelf 433 relay module, which comes with a remote and a receiver that has a relay built-in. It’s basically a RF controlled switch. The receiver can be powered y 5VDC. This should probably be the easiest solution for you as it does not require any software changes.
I’ve never done this but I am curious: why not just use a garage door remote that’s compatible with your garage door system? OpenGarage does not interfere with any existing remote that works with the garage door system, it just provides another way to control the system.
It depends on the type of automatic gate. The basic features of OpenGarage is that it has a distance sensor to sense the door status, and a relay to trigger a button click that simulates someone pressing on the garage door button. You can leverage the features to use it creatively on other types of garage doors.
Out of curiosity: could you try to install the Blynk app on the phone that doesn’t work, and log in (using the same Blynk account as the other phone), and see if you could remotely control the door using the Blynk app?
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/docsThe 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.
