![]() If I manually change the HS "Fence / Beacon Id" to match the actual UUID of the iBeacon, I then get another new HS device created the next time I hit the entry or exit big blue test buttons. It has the same format of the real iBeacon UUID: -, but completely random. It's some completely new, different ID I don't see asociated with the iBeacon anywhere but in HS. When I go into the new HS device's PHLocation2 tab, the "Fence / Beacon Id" does not match the UUID I set for the iBeacon. ![]() The Homeseer device page refreshes and I see the new device. When I am setting up an iBeacon for the first time w/Homeseer, I enter the URLs and hit the big blue test entry button. The iBeacons are tracked perfectly in geofency. I have iBeacon & Altbeacon enabled for 3 of the iBeacons and iBeacon, Altbeacon, Eddystone & eddystoneURL enabled for 1 (have since changed this one to just have iBeacon enabled with no change in reliability). All three numbers together give me unique devices. I then set the Major # to represent a geo-location and the Minor # to represent a room within that location. I created one UUID that I use for all of my iBeacons, like a company id sorta thing. ![]() I initially programed the iBeacons using the RadBeacons iPhone app. I have also installed iOS 13 beta 3 via Apple dev site (not the public beta), so it could be that that is the source of the issues outlined below. ![]() I've been using the MyHS portal for enter/exit URLs in geoFency and it's been working fine for geofences but hasn't been nearly as reliable for iBeacons. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |