Forum Replies Created
-
Posts
-
Hi, slow flashing means it’s attempting to connect. You can reset it by pressing the button for more than 5 seconds, until the LED turns solid on, and then release the button. Is your Cisco 3602i by any chance a 5G-only router? Also, could you try a different router, or create an Hotspot on your phone and let OG connect to the hotspot? If nothing works, you can submit a support ticket to get it replaced.
OpenSprinkler firmware started several years ago, and back then IP reservation wasn’t as prevalent. On today’s routers, IP reservation is pretty much a standard feature.
OK, this has been added to todo list. I have previously rebooted my router multiple times and didn’t encounter any problem with OG reconnecting, so I didn’t think this is an issue (i.e. I assume the ESP8266 library automatically handles reconnection). But now I will add some more explicit code to handle reconnection.
I will look into this. How often do you upgrade the firmware on your access point? i assume it’s not very often?
What router do you use? I’ve not seen a router that does not have IP reservation (or DHCP reservation) feature.
It’s definitely possible to change the firmware to support static IP. It’s just that using static IP that way is not recommended because it can result in IP conflicts. It’s best to have the router manage static IP for you.
The best way to set static IP is to use the router’s DHCP reservation (or called IP reservation) feature, which binds a specific IP to the MAC address. This way, if OpenGarage reboots, or router reboots, the IP assigned to it will remain the same.
I am not very familiar with MQTT (followed a few tutorials and so on). Please share what you have, and we are definitely interested in incorporating MQTT into future firmwares. I am sure many users would appreciate it too.
You are right — the read_distance() function expects a working ultrasonic distance sensor is connected on the specified pins. Without the sensor, the read_distance() function will time out causing ESP to reboot.
As you know, there is a built-in web interface which is basically a simple web app. You can use it when you are at home, or use it remotely if you set up port forwarding. The point of Blynk is that it provides cloud service so that you can access the device remotely without setting up port forwarding.
You can customize the Blynk app by first stopping it (clicking the stop icon), then click on widgets that you don’t want and delete them. For example, the LCD widget may be confusing so you can just delete it.
OK, let me know if there is any further issue. Basically, if you have put in Blynk token when you set up the device (i.e. while it’s in AP mode), it will automatically boot up in Direct + Cloud mode. If you put in Blynk token after setup, you will need to reboot the device afterwards for it to take effect (without rebooting, it won’t perform the Blynk initialization code).
I don’t think it supports WPS2-Enterprise. This is more of a general question for ESP8266 module — I don’t think I’ve read its support for WPA2-Enterprise, or 5G anywhere, so I assume it doesn’t.
Hi Dave,
To get DHT22 to work, you just need the DHT22 library:
https://github.com/adafruit/DHT-sensor-library
and it requires a spare GPIO pin. On OpenGarage, GPIO 4 and 5 are spare pins and are mapped out, so you can use either of them.Alternatively, there are I2C versions of DHT22 (for example, AM2320). GPIO 4 and 5 happen to be the hardware I2C SDA and SCL pins respectively, so you can also use AM2320. The library for AM2320 can be found here:
https://github.com/thakshak/AM2320The begin() method can take optional parameters such as your custom server IP. Specifically, check the begin() function’s parameter list
https://github.com/OpenGarage/OpenGarage-Firmware/blob/master/Modifications/BlynkSimpleEsp8266.h#L65
the second and third parameters provide your custom server and port number (if it’s different from the default).If you can access the pushbutton on the wall controller (you will need to open the enclosure of the wall controller to access the two pins of the pushbutton), you can solder two wires onto the pushbutton pins. That way, the relay click on OpenGarage will simulate pressing the pushbutton.
This is how we make the Security+ 2.0 adapter — we buy off-the-shelf Security+ 2.0 door buttons, and and solder two wires onto the pushbutton, and connect these two wires to the orange terminal block on OpenGarage.
Note that many pushbuttons have four pins, however, it’s really just two pins (the two pins on the same horizontal line are internally wired together and hence count as 1 pin). The easiest way to check is to use a multimeter to check the connectivity. When button is released, the two pins appear as open circuit; when the button is clicked, the two pins appear as short circuit.
Actually I am wondering if this might have to do with either your Blynk app is outdated, or the firmware is outdated. A couple months ago Blynk had a service break and after it’s back online, it can’t communicate with older Blynk libraries any more. We immediately updated the firmware to use the latest library, but if you purchased OG before that you may still have older firmware (specifically, if you have the original firmware 1.0.0). The solution is to follow instructions here:
http://rayshobby.net/introducing-opengarage/#update_firmware
to update the firmware.@brian: when using the Blynk app, you shouldn’t need any port forwarding: the way Blynk works is that the device (OG) communicates with the Blynk cloud server, sends status and receives commands from the server. Your mobile phone / app also communicates with the cloud server and so all communicates are through the cloud server. There is no need to set up port forwarding.
One thing to double check is that the Blynk token you set on OG matches the token in the Blynk app.
Setting port forwarding would be useful if you don’t want to use Blynk app, and instead want to directly access the native web interface of OG. Once port forwarding is set up, you can type in your router’s external IP address and access the built-in web interface directly. This way it doesn’t go through Blynk app.
Actually the first design of OpenGarage did have a temperature sensor on board, but it was dropped in the final design. It’s nice to have extra sensors, but it’s hard to know how many users need them, and DHT22 is quite expensive honestly, so we would rather not have to include such components if most users don’t need them.
Sorry, I need to sit down and write the API document. For the moment, you can take a quick look at the source code:
https://github.com/OpenGarage/OpenGarage-Firmware/blob/master/OpenGarage/main.cpp#L654
to find out all HTTP GET commands that the firmware supports and go to the corresponding callback functions to see the return value of each command.
