Gradually turn on lights.

[CatmanV2]

@gwp1
TrackerID is CM
DeviceID is catmaniphone
UserID is my configured username for my Mosquito server (so should be your Hive username)

Because all of my stuff is local I can see the messages being posted to the logs. Not sure if you can do that with your hive set up?

At a guess you are not connecting to the Hive server. Does the iPhone app say 'connected'. Can you see Reactor getting messages from the Hive server?

I'm not 100% sure that's the right location for the config file. I guess if you're running reactor from /home/reactor/Documents it's right though. Just an odd choice (although Windows is not my thing) !

C

[gwp1]

@catmanv2 yep, configured the Hive user and password and is shows as “connected” in the iOS app. I’ve not found anywhere in their dashboard to verify messages being received into the broker. I’ve not seen anything come in from the broker to msr.

I’m running a bare metal install on a RPi. Not a Linux expert so it ended up in an interesting folder structure but it works just fine so re-orging isn’t a priority.

[CatmanV2]

@gwp1 That's a Linux setup?!

OK, can you read the log from reactor?

Also, are you really sure that Reactor is able to connect to HiveMQ?

C

[gwp1]

@catmanv2 Back home now.

This leads me to believe it's connected to Hive:

I see nothing in the logs because a.) not entirely should what it would look like, and b.) there's nothing happening atm.

[CatmanV2]

Hmm, yes tough. I share your suspicion that it's Hive. No interest in firing up Mosquito on your Linux box? Takes about 10 minutes. OK there's an increase in your vulnerability but.....

C

[toggledbits]

The docs for MQTTController describe how to enable topic capture, so you can see if you are getting anything at all from Hive (this is probably preferable to turning up the log level in the log file for MQTTController). I'd suggest that as a start. See what, if anything, it's sending at all.

Ref: https://reactor.toggledbits.com/docs/MQTTController/#troubleshooting-and-debugging

[therealdb]

@catmanv2 I hope you’ll enjoy it as much as I am

[gwp1]

@toggledbits @CatmanV2 Unless I'm just not far enough thru coffee this morning, this is what I see in MSR's mqtt logs and it looks like it's data from my iPhone8 (which I fired up via wifi to use as a test phone.)

2022-12-12T14:02:02.896Z "owntracks/msrmqtt/iphone8" {"_type":"location","acc":35,"alt":10,"batt":100,"bs":1,"conn":"o","inregions":["Home"],"inrids":["adf34c"],"lat":32.94714,"lon":-80.013836,"m":1,"p":101.826,"t":"u","tid":"i8","tst":1670853720,"vac":15}
2022-12-12T14:02:02.998Z "owntracks/msrmqtt/iphone8" {"_type":"location","acc":10,"alt":10,"batt":100,"bs":1,"conn":"o","inregions":["Home"],"inrids":["adf34c"],"lat":32.946934,"lon":-80.013887,"m":1,"p":101.827,"tid":"i8","tst":1670853722,"vac":8,"vel":0}

So why isn't this showing here:

My entity config is:

        owntracks_iphone8: #entity ID - must be unique
          name: "iPhone8 location" # friendly name
          prefix: "iphone8"
          topic: "test_iphone"
          uses_template: owntracks_sensor
          homeRegionName: "Home"

I feel like I'm just "this close" and I just don't have something aligned properly.

[toggledbits]

Yes, your configuration of prefix and topic don't make a string that matches what is being received. Based on what it is coming in and how those fields template configuration are used, prefix should be msrmqtt and topic should be just iphone8.

Conspicuous give-away: your test_iphone value doesn't appear in the topic or payload of what you're receiving.

@therealdb this may need a bit more documentation, since the relevance of prefix and topic aren't immediately clear (at least, not to me) without looking at the template itself and seeing how they are used, and likely the phone configuration as well (i.e. describe how configuration fields on the phone may appear in the final event topic).

[CatmanV2]

I believe @toggledbits has it (unsurprisingly)

C

[gwp1]

@toggledbits I was just updating prefix when your response came in. Here's where I am now:

      entities:
        owntracks_iphone8: #entity ID - must be unique
          name: "iPhone8 location" # friendly name
          prefix: "msrmqtt"
          topic: "iphone8"
          uses_template: "owntracks_sensor"
          homeRegionName: "Home"

My template is in reactor/config/mqtt_templates which is where @therealdb directs. Do I need to modify the uses_template:?

[CatmanV2]

I think the template is in the correct place. Let's see what happens when you restart Reactor

C

[toggledbits]

@gwp1 Are you getting an error that the template owntracks_sensor doesn't exist?

[gwp1]

@toggledbits I am not receiving any errors.

Just not seeing anything populate the entity.

Is it something to do with the entity name by any random chance?

[toggledbits]

@gwp1 said in [MSR] reactor-mqtt-contrib package for additional MQTT templates:

@toggledbits I am not receiving any errors.

Then there's nothing wrong with uses_template.

I'll make the same comment/question to you that I made to @CatmanV2 earlier in this same thread: you're on the latest MQTTController, right?

[gwp1]

@toggledbits MQTTController-22326 (double-checked the CHANGELOG.md)

EDIT: ...which I now see is a version behind. You snuck one in on me. Updating to MQTTController-22340.

EDIT2: Nailed it.

[gwp1]

@toggledbits @therealdb @CatmanV2 Thank you all for your help here, this is a big step in my system. Really appreciate it!

[CatmanV2]

@therealdb what are your updates set to on the iPhone app? The data is going to be useful, but on 'Significant' I appear to be only getting updates on
string and region which makes sense.
I'm assuming that battery_power.level won't update more frequently unless the app is configured to 'Move'

Has anyone done that? Does it kill the iPhone battery?

Cheers

C

[CatmanV2]

@gwp1 how did you get the Driving Flag?

Cheers

C

[gwp1]

@catmanv2 move translates to any movement your phone is making - increases accuracy but kills battery life. significant is defined by OwnTracks as "traveling a distance of at least 500 meters in 5 minutes" which lets the app nap and is much easier on the battery.

Driving Flag is a virtual switch I created based on distance from Home. I believe I currently have it set to .1 mile so it trips as soon as I pull out of the neighborhood. I use it as a safety to the GPS reporting for when I'm not home. I have a second one called Driving Flag - Far Away that kicks in at two miles. This is for use when I'm obviously not just puttering about the neighborhood but going to be gone while. Can be used to trigger HVAC, etc.