# Location and Presence App Broker Unavailable intermittently

**URL:** <https://community.homey.app/t/location-and-presence-app-broker-unavailable-intermittently/46905>\
**Category:** Questions & Help\
**Created:** [April 30, 2021, 3:27pm UTC](https://community.homey.app/t/location-and-presence-app-broker-unavailable-intermittently/46905 "2021-04-30T15:27:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hannes85](https://avatars.discourse-cdn.com/v4/letter/h/e79b87/32.png) [@Hannes85](https://community.homey.app/u/Hannes85)\
**Post date:** [April 30, 2021, 3:27pm UTC](https://community.homey.app/t/location-and-presence-app-broker-unavailable-intermittently/46905/1 "2021-04-30T15:27:04Z")

</div>

Hi all,

got an interesting “problem” that I’d like your thoughts on. Every day at random intervals I see the Location and Presence App logging “The MQTT Broker is UNAVAILABLE” and anywhere from seconds to minutes after it says “the MQTT broker is AVAILABLE again”. The broker is running on homey too.

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/1/6/16dd9f6d760bafaa47f1233b58e6e8465a981667.jpeg)

Last occurrence (today, April 30th) was at 16:19:00 (unavailable) and it came back again at 16:21:34 (available). Checking my router logs shows no general or specific Homey (wifi) issues during this time (I actually was having a video call during that time without any issues). Then I started checking the Broker app logs.

Broker logs;

> 20210430-16:16:26 client disconnected: J  
> 20210430-16:16:26 Packet published J  
> **20210430-16:18:30 mqttjs\_xxxx has unsubscribed from topic owntracks/#**  
> 20210430-16:18:30 client disconnected: mqttjs\_xxxx  
> 20210430-16:18:30 Packet published {“clientId”:“mqttjs\_xxxx”,“topic”:“owntracks/#”}  
> 20210430-16:18:30 Packet published mqttjs\_xxxx  
> 20210430-16:21:34 client connected: mqttjs\_xxxx  
> 20210430-16:21:34 Packet published mqttjs\_xxxx  
> **20210430-16:21:34 mqttjs\_xxxx has subscribed to topic owntracks/#**  
> 20210430-16:21:34 Packet published {“clientId”:“mqttjs\_xxxx”,“topic”:“owntracks/#”}  
> 20210430-16:22:32 client connected: B  
> 20210430-16:22:32 Packet published B  
> 20210430-16:22:32 Packet published  
> 20210430-16:22:32 Packet published  
> 20210430-16:22:34 client disconnected: B  
> 20210430-16:22:34 client connected: B

The location and Presence App unfortunately gets its logfile overwritten incredibly fast so all I have from that side is the following;

> 20210430-16:19:32 Broker State: RECONNECTING  
> 20210430-16:20:02 MQTT Closed  
> 20210430-16:20:02 Broker State: DISCONNECTED  
> 20210430-16:20:03 MQTT Reconnect  
> 20210430-16:20:03 Broker State: RECONNECTING  
> 20210430-16:20:33 MQTT Closed  
> 20210430-16:20:33 Broker State: DISCONNECTED  
> 20210430-16:20:34 MQTT Reconnect  
> 20210430-16:20:34 Broker State: RECONNECTING  
> 20210430-16:21:04 MQTT Closed  
> 20210430-16:21:04 Broker State: DISCONNECTED  
> 20210430-16:21:05 MQTT Reconnect  
> 20210430-16:21:05 Broker State: RECONNECTING  
> **20210430-16:21:34 The MQTT broker is AVAILABLE again**  
> 20210430-16:21:34 MQTT client connected  
> 20210430-16:21:34 Connected Topics: owntracks/#  
> 20210430-16:21:34 Broker State: CONNECTED

These appear to indicate that the Location and Presence app unsubscribed and then subscribed again a couple of minutes later. Would that mean that the Location and Presence app… restarted\ suffered from problems?

This behavior has been bugging me for a while now and I cannot figure out where it is coming from so any thoughts are welcome.