I am trying to use HS4 Windows on two different computers, primary and secondary, to monitor Bluetooth BLE beacons. I have HS4 setup on the primary to connect to the secondary, which is the broker. The primary Windows HS4 connects to this broker, but I am not getting any updates from the broker to the primary regarding beacons. I'm sure it is a setting that I have not got correct. Please advise. Thanks.
Announcement
Collapse
No announcement yet.
Setup help when using a remote Windows-based computer running mcsMQTT as broker
Collapse
X
-
Primary IP 192.168.1.2
Secondary IP 192.168.1.3
On Primary MQTT Broker setup as 192.168.1.3
On Secondary MQTT Broker setup as 127.0.0.1
Beacons on a Windows computer are not now being delivered as published MQTT messages. They are only processed internally as pseudo-topics. Let me look into adding option to publish these.
-
Originally posted by Michael McSharry View PostPrimary IP 192.168.1.2
Secondary IP 192.168.1.3
On Primary MQTT Broker setup as 192.168.1.3
On Secondary MQTT Broker setup as 127.0.0.1
Beacons on a Windows computer are not now being delivered as published MQTT messages. They are only processed internally as pseudo-topics. Let me look into adding option to publish these."Living with technology means living in a [constant] state of flux." S. Higgenbotham, 2023
"Reboot and rejoice!" F. Pishotta, 1989
Comment
-
Yes RPi Beacon information is transmitted via MQTT. Note other thread where the update was made to provide the same with Windows. The update is at mcsMQTT Change Log (HS4 & HS3) - HomeSeer Message Board with the dll zip going into the \bin\mcsMQTT subfolder of HS.
Comment
-
Originally posted by Michael McSharry View PostYes RPi Beacon information is transmitted via MQTT. Note other thread where the update was made to provide the same with Windows. The update is at mcsMQTT Change Log (HS4 & HS3) - HomeSeer Message Board with the dll zip going into the \bin\mcsMQTT subfolder of HS."Living with technology means living in a [constant] state of flux." S. Higgenbotham, 2023
"Reboot and rejoice!" F. Pishotta, 1989
Comment
-
Originally posted by Michael McSharry View PostYes RPi Beacon information is transmitted via MQTT. Note other thread where the update was made to provide the same with Windows. The update is at mcsMQTT Change Log (HS4 & HS3) - HomeSeer Message Board with the dll zip going into the \bin\mcsMQTT subfolder of HS."Living with technology means living in a [constant] state of flux." S. Higgenbotham, 2023
"Reboot and rejoice!" F. Pishotta, 1989
Comment
-
Did you do the following? The logic in 5.25.1.0 will work the same as prior versions unless an association is made with a beacon of interest and then the pub topic is defined to indicate that this beacon data is to be published via MQTT. If the pub topic remains blank then the beacon data will update the HS Device directly. If it is not blank then it will not longer update HS directly, but will do the update when the Broker echo's back the published topic.
With version 5.25.1.0 I added the ability to publish the BLE Beacon topics recognized in the Windows BLE stack. It is done by replicating the Sub Topic into the Pub Topic text box on the Edit tab or Association tab.
Comment
-
Originally posted by Michael McSharry View PostDid you do the following? The logic in 5.25.1.0 will work the same as prior versions unless an association is made with a beacon of interest and then the pub topic is defined to indicate that this beacon data is to be published via MQTT. If the pub topic remains blank then the beacon data will update the HS Device directly. If it is not blank then it will not longer update HS directly, but will do the update when the Broker echo's back the published topic."Living with technology means living in a [constant] state of flux." S. Higgenbotham, 2023
"Reboot and rejoice!" F. Pishotta, 1989
Comment
-
First step is to enable the BLE function from Local Page, Bluetooth Tab.
The discovered beacons will show up in the Association Table of the MQTT Page, Association Tab. Most easily found using the Topic 1 (T1) filter as Beacon. If you do not see Beacon in T1 then click Rebuild button in the filter heading.
The Beacons are listed by their MAC address. Find one that you are interested. Many will be fake/random ones generated by smart devices to protect privacy. In the example below I recognize the one ending in .2E as my long range beacon. I clicked the "A" column checkbox to create a HS device. Status of this beacon will now be reported in HS. If I want other MQTT clients to know about it then I copy the Sub and paste it in the Pub textbox.
Comment
-
Michael:
Thanks for taking the time to provide these instructions. I had already figured out most of this, but had been stymied on "... copy the Sub and paste it in the Pub textbox." It took me awhile to find it, but I finally located the "Pub textbox." As in your post, that Pub textbox was not visible to me, but looking where you pasted yours, moving my mouse over the area, I discovered the box. Now, on to the next challenge: trying to figure out why my primary HS4 set up disconnects from the broker that the secondary computer is running.
Elliott
"Living with technology means living in a [constant] state of flux." S. Higgenbotham, 2023
"Reboot and rejoice!" F. Pishotta, 1989
Comment
-
Originally posted by Michael McSharry View PostMake certain your MQTT clients all have unique Client Id's. In particular for mcsMQTT, the MQTT Page, General Tab, Client Id text box in the same area where you setup your Broker IP."Living with technology means living in a [constant] state of flux." S. Higgenbotham, 2023
"Reboot and rejoice!" F. Pishotta, 1989
Comment
-
It is not clear to me what your test environment is. Are the two HS4 computers close to each other so both will see the beacon via the Bluetooth interfaces? Are you publishing the beacon from Windows HS4 computer (i.e. has pub topic text box with Beacon/xxxx)? Am I not familiar with blueman-applet, but I will guess that it attaches to the Bluetooth hardware on RPi. If this is the case then I do not know if the hardware can be shared by two simultaneous users (blueman and mcsMQTT).
Comment
Comment