Theengs mobile app

Third party integrations
1

I’m excited :grin: to announce the release of Theengs Android mobile application, the application uses Theengs Decoder to read data from BLE devices and display those to your mobile,

image

you can download it on Google Play (paid app)
Get it on Google Play

To stick with the spirit of OpenMQTTGateway the app can also be used as a gateway to an MQTT broker! So if you have an Android touch screen, you can install the app and configure it to read BLE sensor data and push it to Home Assistant.
Note that if you want to run the integration in the background this is possible as an experimental :test_tube: feature (we need your feedback on this)

More information on the app documentation:
https://app.theengs.io/

We came a long way :sweat_smile: from removing the decoding of BLE sensors from OpenMQTTGateway, creating a dedicated library, creating a gateway, a Home Assistant Addon a data explorer and now a mobile application!

And you know what, this is not the end, we have plans to release the app for other platforms :muscle:

Google Play and the Google Play logo are trademarks of Google LLC.

2

Now available for iOS also!

You can download it on App Store (paid app)

Download on the App Store

App Store and Apple logo are registered trademarks of Apple Inc.

3

New release v1.2 version with an impressive number of new compatible sensors:

  • Hydractiva Digital-Amphiro/Oras
  • April Brother-ABTemp
  • April Brother-N03
  • Oria/Brifit/SigmaWit/SensorPro-TH Sensor
  • Otio/BeeWi-Door & Window sensor
  • Qingping-CGDN1
  • SmartDry-Laundry Sensor
  • Switchbot-Motion Sensor
  • Switchbot-Contact Sensor
  • ThermoPro-TP357
  • ThermoPro-TP358
  • ThermoPro-TP359

The automatic creation of the sensors into Home Assistant through MQTT discovery, no need to manually create your entities and devices, they will appear directly into Configuration->Devices.

You can also Black List devices from the Device browser (click the + icon)

And finally, the application is now compatible with iOS!

Download on the App Store

What’s Changed

New Contributors

Full Changelog: Commits · theengs/app · GitHub

App Store and Apple logo are registered trademarks of Apple Inc.

1 Like
4

Hello! Thank you for working on this project. I’m trying to use the Android App with Mosquitto. How is one supposed to set up autodiscover with this arrangement?

5

Hello,

If you add your homeassistant ip, 1883 as a port, and a username/password you should see connected below:

Screenshot_20230404_153852
Screenshot_20230404_1538521080×2020 114 KB

Once done you can connect to your broker with a client like mqtt explorer to see the data coming.
With 1.2.0 version Home Assistant discovery is enable by default, so if you have compatible devices you should see them below home/TheengsApp with the real time data. And see the sensor definition into homeassistant topic.

If you get to this point, the sensor entities should be automatically created into HA and visible from the MQTT integration or the Settings->Devices page.

Let me know if you need more help.

6

Thank you for the quick reply! I have all that configured. I can see all my BLE devices in the app and in MQTT explorer. Just as you described.
However, the auto discovery isn’t occurring. Just to be clear, I’m using Mosquitto hosted in HA. I used my HA credentials in Theengs and in MQTT Explorer.
I also made sure to set the discovery prefix to “homeassistant” as per the mosquitto config.

Mosquitto log if that helps. The 10.1.40.18 address is my Android with Theengs. It looks like it times out the connection. Unsure why that is.

image
image993×1082 53.7 KB

7

In the system option of the MQTT integration do you have this activated:
image

8

Yes, that is enabled.

9

Do you

Do you see also the sensors definition into homeassistant topic ?

10

New release v1.4.0

:fire: Introducing Live BBQ Monitoring in Theengs App: Grill Like a Pro! :fire:

Theengs-app-bbq-red

What’s New:

  • Real-Time Grill Monitoring: Keep a close eye on your food temperature with live updates. Perfect for ensuring your meats are cooked exactly how you like them.
  • Customizable Alerts: Set temperature thresholds and receive notifications when your food hits the right temperature.
  • Versatile Sensor Compatibility: Live BBQ Monitoring works seamlessly with a range of popular sensors, including Govee H5055, Inkbird IBT-2X(S), IBT-4X(S/C), IBT-6X(S), and SOLIS_6.
  • Easy-to-Read Charts: Visualize your food’s temperature over time with our intuitive live charts. Make adjustments on the fly and achieve grilling mastery.

In the meantime, the temperature data can be pushed to HA thanks to the MQTT integration.

1 Like
11

Hey - I bought the app for my Android tablet. (Samsung Tab 7 FE)
It has found a Mi Flora sensor and does connect successfully to my Home assistant - but there are two major problems:

  1. It does not update any sensors, EXCEPT when I click on “update sensors”. In settings, the interval is 5 minutes (also had 30 min and 1h). This is since I installed it yesterday. When I open the app, it immediately finds the sensor.
    Any battery optimization is off and the app has full (also background BLE) permission.

  2. HA only parses / recognizes two out of 4 sensors. Just the Lux and °C, not the fertility and not the moisture. When manually updating, i can see in the protocols, that the sensors are submitted to HA.
    See also here for this behavior:
    Mi Flower Care sensor via MQTT (Theengs) has missing sensors

    image
    image1358×642 38.9 KB

Can you please help - I mean, the app is not super expensive - not at all, but I paid it and really want it to work properly.

12

Hey,

Thanks for your support, I appreciate it :slight_smile: !

Could tell me which version of Android are you using? We had less success with newer versions, this is why this function remains experimental

Let me check if I reproduce this issue.
If you want to create the sensors manually while I investigate you can use this message and this topic within mqtt explorer:

{"stat_t":"+/+/BTtoMQTT/5C857E135A0D","unit_of_meas":"%","name":"moi","uniq_id":"5C857E135A0D-moi","val_tpl":"{{ value_json.moi | is_defined }}","stat_cla":"measurement","device":{"ids":["5C857E135A0D"],"cns":[["mac","5C857E135A0D"]],"mf":"Xiaomi","mdl":"HHCCJCY01HHCC","name":"HHCCJCY01HHCC-135A0D","via_device":"020000000000"}}

Posted to the topic:

homeassistant/sensor/5C857E135A0D-moi/config

Tick the “retain” option

image
image432×471 25.4 KB

And for the fertility:

{"stat_t":"+/+/BTtoMQTT/5C857E135A0D","unit_of_meas":"µS/cm","name":"fer","uniq_id":"5C857E135A0D-fer","val_tpl":"{{ value_json.fer | is_defined }}","stat_cla":"measurement","device":{"ids":["5C857E135A0D"],"cns":[["mac","5C857E135A0D"]],"mf":"Xiaomi","mdl":"HHCCJCY01HHCC","name":"HHCCJCY01HHCC-135A0D","via_device":"020000000000"}}

Posted to the topic:

homeassistant/sensor/5C857E135A0D-fer/config

Let me know if it helps

1 Like
13

This has worked!
Another point is - I can not see that the battery-charge is submitted at all.
In tht theengs-app I see it in a symbol, but not in any MQTT-message…

1 Like
14

I reproduce the issue, we will fix it in the next version, thanks for pointing it!

1 Like
15

Unfortunately the battery is retrieved through a connection to the sensor, not a broadcast so the information is not part of the publication to the broker.

1 Like
16

Got one more issue - first - it was a pain to download from my Samsung-dashboard-tablet.
I needed to, since I got some sonoff-NSPanel Pro’s that shall relay BLE data.
Because it is a split-apk it took me some pain to get it onto the Sonoff (which has no Playstore).

However - this just aside. I have also entered the exact same data as in the (working) Samsung one. It also finds one new sensor, plus several others (seems BLE is good on the Sonoff).
But it does not properly report it - actually I found it via searching the MAC with the MQTT-explorer like this:

image
image1710×238 16.3 KB

But it is not added to the other sensors - no idea why.
The topic is also the same on both devices. Here is the code from MQTT-explorer:

{"id":"5C:85:7E:13:77:08","name":"Flower care","rssi":-68,"brand":"Xiaomi/VegTrug","model":"MiFlora","model_id":"HHCCJCY01HHCC","type":"PLANT","moi":38,"mac":"5C:85:7E:13:77:08"}

Any idea how this problem happens?
BTW: MQTT-explorer is connected to Home-Assistant and not the panel.

17

And in addition to my last topic: When will this new version come?
It is super annoying to add 50% of the sensors by editing the protocol manually.

And one more thing: In my HA theengs shows up as “unknown” without any data - like no ip or name or other information. Can you also change that to lets say “theengs-app Samsung Tablet” (like a proper identifier)

Looks like this right now:

image
image995×597 41.3 KB

18

You should not use homeassistant as the base topic, HA uses homeassistant for auto discovery.
Also it seems that the second topic is empty in your screenshot.
I would advise to have one base topic like home that can be the same accross your gateways/devices. And a second topic different for each, tablet, sonoff …

image
image252×105 11.8 KB

1 Like
19

I’m adding the feature request

I don’t have an ETA right now, but there will be a new version this year for sure.

1 Like
21

Can not edit the message I just sent :-/
I found the problem:
When using the same user on each theengs install, the latter ones will be disconnected.
I previously used “mqtt” on all of them. Now I have just added mqtt2 and it works…

Edit: Does not - will be disconnected after some minutes. Any idea why? I just completely disabled power-management in Android on the Sonoff.
And I have another issue:

Obviously my living-room (Wohnzimmer) sees all my 7 sensors.
But only 5 of them show-up in HA - any idea why?
Here is MQTT-explorer:

image
image1654×584 127 KB

Here’s HAs 5 devices:

image
image2232×620 42.9 KB

MQTT first settings:

image
image1220×1408 47.7 KB

Deeper settings:

image
image1116×1454 97.3 KB

(The last option is not in the screenshot, but it is off (keep last will message)