![]() ![]()
#RADBEACON NOT WORKING DRIVERS#Outdoor RTLS like GPS have demonstrated widespread impact and utility they can help drivers avoid traffic on the road, help emergency responders pinpoint distress signals, and provide valuable location data to countless use cases. Not sure on that tho as I’m still very new to package building.ĮDIT: I built this so i could hide the card with multiple devices in it and display a single presence icon/status in my Presence view.Over the past decade, Real Time Location Systems (RTLS) have become more common and consumer-accessible through smartphones and mobile applications. With a little work I may be able to build this sensor into a package that loops across a specific groups such as ‘users’ to auto build these sensors when HA starts. The icon template will flip from a blue user icon if home to an outlined icon if not home. And finally it gives up and displays Away. If a zone is found then that will be displayed. If not home it will check for the status of the Owntracks device. ![]() I haven’t done a ton of testing on it yet but basically it checks the group status for home first. Reviving this to say thanks and share a quick template sensor i threw together. It’s virtual – a kludged on/off to keep track of who’s home and who’s not.) (Not to confuse the issue but in the above, that’s not really a “light” in my system. Here’s what’s in my automations.yaml that acts on the state of entity_id: group.all_devices: - alias: Group is away #RADBEACON NOT WORKING CODE#That’s not anything that you have to code it’s an entity provided by HA. The presence of all users together – so all users, and all of their devices – is then handled by entity_id: group.all_devices. That’s thanks to these entries in groups.yaml: user1: device_er1_owntracks, device_er1_nmap Those cards technically aren’t a “group,” though I suppose it makes sense to think of them that way since the user’s devices are… um… grouped. In the config I describe, you’ll wind up with a card in the HA UI for each user, and each user will have the devices “belonging” to them under their names. This example toggles a light when all users are home/away: - alias: Group is away (8) Create automation in automations.yaml based on the group’s presence. This example toggles a light when User 1 is home/away: - alias: User 1 is away (7) Create automation in automations.yaml based on a user’s presence. Power on your iBeacons, configure them as instructed by the manufacturer, and then add a zone for each iBeacon in Owntracks. One or more iBeacons can be used with Owntracks to help ‘anchor’ your Home location. User3: device_er3_owntracks, device_er3_nmap ![]() User2: device_er2_owntracks, device_er2_nmap (5) Create a groups.yaml file and in it list the trackers for each user: user1: device_er1_owntracks, device_er1_nmap (4) Edit configuration.yaml to refer to groups.yaml and automations.yaml: group: !include groups.yaml If just one tracker reports that it is home, then HA will regard the device as being at home. Leaving trackers separate in known_devices and then creating a group of trackers for each device allows the trackers to individually contribute to the device’s location. #RADBEACON NOT WORKING MAC#Note: Other examples suggest combining the device’s MAC address with Owntracks. Example entries for User 1’s phone: user1_owntracks: Home Assistant will create and populate a known_devices.yaml based on discovery that you can edit as apporpriate. The three IP addresses above are examples for three mobile devices. # Highly recommended: assign IP address for devices you want to track so you can know where to find them. (3) Edit configuration.yaml for Owntracks, discovery, and Nmap # Discover some devices automatically This method prevents false ‘away’ states. Going that route, just one ‘away’ condition’ from a tracker causes the device to be ‘away.’ In the configuration below, if just one tracker reports a ‘home’ condition, the user’s device is considered to be ‘at home.’ This configuration works a lot better for me because my phone’s Owntracks position tends to periodically drift outside of my Home zone. I found examples that suggested including a device’s MAC addresses within the MQTT tracker. #RADBEACON NOT WORKING HOW TO#So I hope this is helpful.įor me, the wrinkle that made the difference was figuring out how to use individual trackers in known_devices.yaml and then grouping them in groups.yaml. I gathered the information in bits and pieces thanks to the wealth of information I gathered from others, but nothing seemed to be clearly spelled out in one place. I thought I’d share what’s working well for me using multiple trackers for presence (in this example, Owntracks, Nmap, and iBeacons). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |