Beacon MQTT [Android]

Hi Alex,

You have a nice day too!! Why would you think I’m not among you anymore?

Small question: would you consider adding HTTP(s) support instead of only MQTT support. I know Owntracks now also supports HTTP and this way I could make my MQTT server private again.

Cheers!
Ronald (still living :wink: )

@katsaplias, couple months ago I opened corresponding issue.

1 Like

@cyn, few days ago @philsson opened similar issue. Please attend to discussion

@rdehuyss I have to add HTTP(s) support. It would be done after multiserver mode. But I should be honest: I won’t do it soon

My current todo list for v0.3

New functions:

  • TLS support - Issue 20
  • Track params of beacon - Issue 26
  • Concurrent beacon mode - have some ideas, lets disscuss!

UI improvements:

Thank you very much, it works as I wanted: D

Hello guys! I’ve pushed v0.3 to Google Play last weekend. Unfortunately without TLS. It is so hard to implement for me. But I’m still working and it should be ready in 2019. :santa:

나는 지역 사회에 대한 질문이 있습니다. Google Play 통계에 따르면 많은 사용자가 한국인이라고합니다. 내가 한국어로 번역하는 것을 도와주고 싶은 사람이 있습니까? 말이 되나요? :rofl:

Many thanks to Ronald and Cyn. They helped me with English.

My current todo list for v0.4

New functions:

  • Add TLS support
  • Add checkbox for beacon-specific tracking
  • Add DnD time for vibtation

Improvements:

  • Bottom toolbar refactoring
    • Move “add beacon” to toolbar
    • Move server settings to toolbar
  • Push scanning of new beacons in backgroung
  • Add active and passive icons in notification area
  • Logs refactoring

@Turbo I just started using this app, and I love it!. My only concern is it is limited to 4 beacons, is that something that will change or is that a limitation of hardware?

Hi, James! Version 0.3 build 11 supports 10 beacons. You can install it from Google Play

2 Likes

Hi, I 5hink I know the answer to this question but does this app require my mqtt to be exposed to the internet? Otherwise how does it send the ‘not-home’ payload when I leave my home (and therefore am not connected to my home network)

As you pointed out, exposing MQTT on internet is the only way you can communicate with it.
You could try mixing with beacon transmission power (if doable) in order to recognize the “not found” event while still under your wifi in order to update the MQTT topic, but I think this could be so much prone to error

Yes, you are right. And TLS is not ready yet.

Ok thanks, could you help me with which ports to forward, is it just 1883 external to 1883 internal?

Edit: nevermind, opened that port and it’s working fine!

Is there anything else I should do to make it more secure or is that not possible until TLS is ready?

Advice from me: discover the range of IP (or ranges) of your mobile provider and make strong filter on your home GW. It works for me and it looks more safe.

Hello!
Does anybody interested in such solution: BLE to MQTT gateway mode?

Idea is very simple. BLE beacon can have some extra data fields. My app already has an infrastructure to process it. I can publish this data to predefined MQTT topic. It looks very useful for retransmitting some long-term telemetry from remote sites where you visit from time to time. Make sense?

Amazing work on this app. Question: whe I remove the mac address form the beacon definition it says invalid config. it says its an optional field ? The mac address keeps changing from the beacon (by design) so is there a way to not use it ?

Really, it looks like a bug. I’ll have a look.

Thanks. 1 more thing, is there any way to callibrate the distance … seems to be showing 1 meter when I am about 3 meters apart.

The distance also fluctuates when I am stationary. What could be causing that?

I also get a cannot connect message constantly on the phone when I am out of the house