@WooBooung how dependent is AEB from google services? Any way to install directly via apk, without needing MicroG or Gbox on the phone?
My matepad has only 2gb RAM and no native google services/google play. Trying to save RAM 
AEB does not currently depend on Google Services. Therefore, it is entirely possible to run the app on your MatePad without needing MicroG or Gbox, which should help you save RAM.
However, there is a known issue with the current version (1.1.4). Version 1.1.4 was distributed as an Android App Bundle (AAB). This means that if you simply extract the APK from your phone, it will be missing necessary split files and will not work. Other users have tried extracting 1.1.4, and it did not install properly.
The good news is that version 1.1.5 will be released very soon, and it also includes the ‘White URL List’ feature that you suggested!
For this upcoming update, the app will be packaged as a universal, single APK. Since I don’t own those specific devices, I haven’t been able to test exactly which APK extraction method will work best for your setup.
Alternatively, since you want to save RAM, you could temporarily install Gbox, download and install AEB through it, and then completely uninstall Gbox afterward. Since AEB has no active Google dependencies, it should continue to work fine on its own.
I recently sent a standalone 1.1.5 APK directly to another user, and it installed and worked perfectly without any Google Services. Please look forward to the 1.1.5 update, as it should install seamlessly on your MatePad!
I see that the version has already been released and that it has MQTT, etc… Could you explain what the changes are?
I’m having trouble registering on the Korean SmartThings forum!
You can refer to the official release notes for full details:
Here is a quick summary of the key changes in version 1.1.5:
* **
General-purpose MQTT bridge (receive-only):** AEB can now receive device-status messages from external clouds (such as AWS IoT, LG ThinQ, etc.) over MQTT and relay them to a SmartThings Edge driver on the same local network.
* **
Forward allowlist (security):** You can now manage specific addresses that AEB is allowed to forward requests to. Any request to an address not on this allowlist is automatically blocked to enhance security.
* **
My Invitations:** A new feature that lets you view all your SmartThings channel invitations on a single screen and easily copy an invite link with one tap.
@WooBooung , can you make direct apk download available in the official page as an alternative to google play store?
Tried to install using Aurora Store on my Huawei Matepad, but keep getting this error on initializing:
Thank you for your suggestion.
I actually considered providing a direct APK download, but the APK signed for the website and the one on the Google Play Store have different signatures. This means they are not compatible, and you would have to rely on manual reinstalls for future updates if you install it this way.
Additionally, building and linking a separate APK for every new release would add too much overhead to my deployment process as a solo developer. For now, if you specifically need the APK file, I kindly ask that you extract it directly from your device in the future.
However, I have prepared the APK for this specific version (1.1.5) for you here:
https://aeb.dothesmartthings.com/data/AEB-1.1.5.apk
(Please note that this link will be deactivated in a few days.)
Thank you for your understanding.
Thanks, downloaded the direct apk and AEB is successfully running without Google Services.
I understand your reasons, though.
My Edge Weather device stopped working on June 7th after working as expected for 17days. I tried to add “*.weather.gov” to the allowed hosts. But then I hit ok after entering the host it never shows up in the allowed list.
@Paul_Oliver
I’ve added *.weather.gov to the default allowlist. This list is managed on our server and the app syncs it on every launch, so no app update is needed — just restart the app and it should appear in the allowlist as a default entry right away.
Also, if you haven’t updated to app version 1.1.6 yet, please update.
OK — as for the issue where tapping “Allow” didn’t actually add the host to the allowlist, understood. I’ll look into the code further and follow up.
I am not seeing *. weather.gov on the allowed list. And Edge weather is still not updating.
My phone automatically updated to v1.1.6, but my android tv box is still on v1.1.4. Is there any automatic or easy way to update the app on the TV box. I am currently out of town so I can do it from the tv screen.
Thanks for the details! Please try these in order — if one doesn’t work, move to the next:
1. Force-stop the app on your phone (v1.1.6)
Android Settings → Apps → AndroidEdgeBridge → Force stop, then open the app again (a phone reboot works too). The allowlist re-syncs on startup — check that *.weather.gov now appears.
2. Still blocked? Temporarily disable blocking
In the Block/Allow list screen, uncheck the blocking toggle (= allow all forwards) and confirm the warning. Edge weather should work immediately. You can turn it back on later.
3. Still not working? Send me the logs
Open the Logs tab (filter: error) and look for lines like [fwd-block] blocked host=... or allowlist defaults fetch skipped. Paste anything suspicious here — that tells me exactly what’s failing.
One more thing: which device’s address is your Edge weather driver pointing to — the phone or the TV box? The TV box on v1.1.4 has no allowlist feature at all, so it can’t be blocking anything. (And no, there’s sadly no reliable remote update for the TV box — Play Store should auto-update it within a day or so while it’s idle on Wi-Fi.)
======
About updating the TV box remotely — I’m sorry, I don’t know of a reliable way to do that. Google Play doesn’t support remotely triggering an update for an already-installed app (remote install from play.google.com only works for apps not yet installed). The good news is Android TV auto-updates apps on its own, usually within a day while the box is idle on Wi-Fi, so it should catch up by itself.
Also, you don’t actually need to update the TV box for this issue: v1.1.4 doesn’t have the allowlist feature at all, so it cannot be blocking weather.gov. If your Edge weather driver points at the TV box, the blocking isn’t coming from there.
FYI: The app on my TV updated this afternoon to 1.1.6 on its own.
Updates:
-
I was able to install Edge Drive app at my 2nd location using a Google Chromecast and it is working as expected. I was able to install it from the Google Play Store my phone, so I didn’t have to do it using the clunky Chromecast remote. I did need the Chromecast remote to push the “Start Server” button
-
Then I disconnected the power to the Chromecast to move it. When I checked the Edge Bridge device for my 2nd location in ST mobile App it showed disconnected and no ip address. I pulled down on the page to refresh it and it changed to connected and the IP address was displayed.
-
I went back to my 1st location on my phone and noticed the edge weather device had started updating around 11 PM last night with no action on my part.
-
I then went to the Edge Bridge device for my 1st location in ST mobile App and it showed disconnected and no ip address. I pulled down on the page to refresh it and it and changed to connected and the IP address was displayed.
-
In the android app security settings there is a display problem. The “Removed default” list starts to cover up the “Allowed hosts” list. As the “Removed” lists get longer it eventually covers the entire “Allowed” list. That is why I could not see “*.weather.gov” on the Allowed list yesterday. If part of the “Allowed” list is visible you can scroll through the list, but eventually nothing is visible so you can’t scroll. This was the case on both my phone and tablet.
Thanks so much for the detailed report — this is exactly the kind of feedback that helps.
The Security screen layout problem is confirmed and fixed for the next release. You nailed the cause: the
“Removed defaults (restorable)” list was growing without bounds and squeezing the “Allowed hosts” list down to
nothing, which is why you couldn’t see *.weather.gov or scroll. For the next version I’m removing that
“Removed defaults” list entirely — it was more clutter than value. The screen now shows just Allowed hosts
and Blocked list, each with the full space and independent scrolling, so nothing gets covered. If you ever
remove a default by mistake, you can bring it right back by adding the host again (built-in defaults like
*.weather.gov also stay protected behind the scenes).
On the Edge Bridge “disconnected / no IP” behavior: I’m glad it cleared up as soon as you pulled to refresh,
and that the weather device picked back up on its own. This one is genuinely hard for me to reproduce on my side,
so I appreciate your patience with it — I’ll keep an eye out and take another look at the driver’s status refresh
down the road. If you happen to catch it again, any details on timing would help.
In the meantime — have you tried the web admin in 1.1.6? Since the in-app Security screen is hard to read
right now, you don’t have to fight that screen at all. On the app’s home screen, set an admin PIN (4–12 digits).
Once the server is running, the home screen shows a URL like http://<device-ip>:8080/admin. Open that in any
browser on the same network, enter the PIN, and you get a clean dashboard where you can:
- View and edit the full allowlist — see every allowed host (including which are defaults), add a host,
delete one, or promote a blocked host to allowed — all without the cramped mobile UI. - Check server status, MQTT sessions, and the blocked-host list.
- Change settings, manage API keys, re-link SmartThings, and view logs.
So you can confirm *.weather.gov is there and manage everything from the browser today, while the on-device
screen fix ships in the next version. Thanks again for testing on the Chromecast setup and writing all this up!
Yes, I tried this earlier but I couldn’t get in. I was missing the “/admin” at the end of the IP address. Now that I added /admin it is working.
Thanks again for sharing your project and providing quick and excellent support.
Thank you for using the project and providing feedback! Please note that GUI-related improvements will be included in the upcoming 1.1.7 update.
I have switched for US National Weather Service (NWS) to “Open Weather” because it provides more data. Open Weather is working as expected.
Question: I see some Tuya APIs in the allowed list. Is there an Edge driver that can utilize this to connect Tuya to SmartThings instead of using the c2c integration.
Regarding OpenWeather, if you could share the specific API endpoints you are using, I would be happy to add them to the default whitelist for you.
As for Tuya, the Tuya APIs you saw in the allowed list were simply included as part of a general list of open APIs suggested by an AI when I was setting it up. I am personally not aware of any specific Edge driver that currently utilizes these to connect Tuya directly to SmartThings instead of using the standard c2c integration.
I am using “api.openweathermap.org” which is already on your Allowed list.
@WooBooung , tried to extract the apk from Aurora Store installed app in the tablet without google services support, but this doesn’t remove whatever verification/dependency of the app for google services. App installed from the extracted apk still crashes when started.
Do you know a reliable way to do this, so I don’t have to ask you for the APK on every update