Forum Replies Created
-
Posts
-
The built-in WiFi chip on our OpenGarage does not have external antenna plug. However, if you want you can place a custom order so that we can use the ESP-07S module instead, which has an external antenna plug. This is what the module looks like:
Ah, sorry, I probably mis-read your original message. What are the specs of the two phones, specifically what’s the phone model, version, and what’s the android version of each phone?
Remote control requires Blynk app. It sounds like you were trying to access it remotely with the built-in web interface, and that won’t work. It needs to be through the Blynk app.
500mA should be ok, but I would recommend 1amp. Most USB adapters these days are rated at least 1amp, so should be easy to find.
While it can integrate a safety sensor, I am not sure how to use that information to trigger garage door action. Specifically, it’s not easy to tell whether the door is in the process of ‘closing’ — I guess one thing you can do is to keep track of the time stamp when the door changes from ‘open’ to ‘close’ state, and give an estimate of how many seconds it takes for the door to fully close. During that time period, if the safety sensor is triggered, stop the door from closing. This will be a fair amount of work, including adding sensor wires to the circuit board, modifying the firmware etc.
OK. Sounds like the distance sensor is still having a problem. If you want you can submit a support ticket and arrange for a replacement. In the next batch we will try some different distance sensors to see if that makes any difference.
OK that’s really strange but interesting to know. I would think that raising the lid should cause problems for the sensor as it’s more likely to be partially occluded. What happens if you completely remove the lid, is the problem gone or still there?
Sure, that’s certainly possible. In fact, that’s what we do with our OpenSprinkler product — there the UI files add up to several MB so can’t be stored locally on the controller, and hence are hosted on opensprinkler server. In comparison, the OG UI files are much smaller. Generally we prefer to host them locally on the controller, because this way the system is self-contained, and even if you lose Internet you can still access the UI.
In the case of OpenSprinkler, we have customers who use it in a remote location with no Internet at all, so they will have to either use the OpenSprinkler mobile app (which has UI files built-in), or host the UI on a local server on their network. In any case, it just feels the system is not self-contained and relies on the existence of Internet. For that reason, when I designed OG, I chose to host files on the controller.
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.
Open up the remote, locate the button on the circuit board, generally a button has either 2 pins or 4 pins. If 2 pins, that’s pretty obvious; if 4 pins, usually the pair of pins on the same row are internally connected together, so solder the two wires one onto each row.
I haven’t tried Core 2.5.0 yet so I don’t really know what the issue is. I may have to take a look at the 2.5.0 documentation to see what are the main changes.
It’s possible that maybe it changed flash memory layout. In that case, try to perform a factory reset (while the device is powered on, press and hold the on-board button for at least 10 seconds and release). It will go back to AP mode, and it might work after reset.
ESP8266 has a particular version (ESP-07) which supports external antenna. If you need you can make a custom order so that we can solder the ESP-07 module onto the board, which has a connector for external antenna.
Another solution is to add a WiFi range extender somewhere between your router and the device.
Sorry for being so late on responding — I was out of the country last week for an emergency trip. You are right that it basically just requires 4 wires: 5V, GND, TX, RX. Glad to hear that you figured it out on your own.
Yes, your image shows that the board does NOT have a built-in USB-serial chip. If you have a USB-serial converter, you can flash the firmware yourself. Otherwise, send a support ticket and arrange for it to be shipped back to us, so we can flash the firmware for you.
Depending on what version of OG you have, it may or may not have on-board USB-serial chip (CH340G). You can certainly use an external USB serial adapter to flash the firmware.
Before you do that, I am not entirely sure why OTA update doesn’t work: sure you downgraded to 1.0.4, but all firmwares support OTA update. Did you get any specific error message or something?
What browser are you using? I don’t recognize from its interface. In any case, I’ve asked others to check the links too and they observe the same as I did. So I can’t reproduce this issue on my side.
I am confused by the last part of your message: it looks like calling the API on the token I gave you worked (gave a value), and calling it on the token you created returned invalid token (what you said was the reverse). I really don’t know why this is happening, as I scanned the same QR code. I think this is a blynk token problem and not a problem of the OpenGarage app. Did you happen to delete the project after you created it? Note that once if the project is deleted or you refresh the token the old one will be invalid. The other thing is to make sure you have the latest version of the Blynk app. In any case, this seems not an issue of the OpenGarage app.
Thanks for reporting this: I think those options were there and we planned to make them available but the feature was not fully implemented or tested. We can remove it next time we update the firmware.
Well, the problem is that without seeing the token you pasted, it’s hard to tell whether you pasted the correct token or maybe it was wrong. Try this token:
f7e0aeff238446cfbfc07ddbbc1e547c
it’s not actually hooked up to any real OpenGarage so is good for testing purpose. I just tried it on my android phone and there is no problem with this token.I can’t reproduce this issue: I just tried the OpenGarage app on my Google pixel 2, an iPhone X, and an iPad 2. Adding controller using Blynk token worked fine on all three of them. What device did you use, and what iOS version?
@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.
