Feature request, with a question attached in case there’s a way already.
Our hotel has 5 robots now: 3 room-service delivery robots and 2 floor cleaners. I’d like a board that shows which floor and which part of the floor each one is on, and an alarm if a cleaner ends up in the kitchen corridor (it has happened, twice). No cameras, guests wouldn’t like it and the robots go through corridors anyway.
I put cheap BLE tags on the wall in each zone (12 so far) and each robot carries an ESP32 that already reports battery and status to Hermetry. I looked at the personnel tracking solution and the docs say Hermetry doesn’t work out zones from tags or positions, and there are no geofence polygons. So: could Hermetry take tag IDs + RSSI and decide the zone itself? And polygons on the map card for forbidden areas?
+1 from a food plant. Same wish for our forklifts, especially the polygon part for the allergen area.
For real positions you’d want UWB anchors, BLE RSSI jumps around a lot. Pricey though.
UWB was quoted at about 10x the BLE tags for our floors, so not this year. Zone level is enough for me, I don’t need it to the metre.
Until something like that exists, do the zone decision on the robot. That’s also what the personnel tracking solution expects: the tracker or its gateway reports the zone name, and Hermetry’s rules work on that. I run exactly this for carts in a warehouse, ESP32 scanning fixed BLE tags.
every 2 s: scan 1.5 s, keep RSSI per known tag (EMA, alpha 0.3)
best = tag with highest smoothed RSSI
switch zone only if best beats the current zone's tag by 6 dB
for 3 scans in a row (stops flapping at borders)
publish on change and every 60 s:
{"zone": "F3-east", "zone_id": 32, "zone_rssi": -71}
Send both: zone as text for tables and the alarm, zone_id as a number because text keys have no chart history and you’ll want «where was it at 14:00».
For the kitchen corridor: give each cleaner a server attribute forbiddenZone = «F0-kitchen» and an alarm rule on the robot profile where zone equals that attribute. Per-device thresholds from attributes work for text too with ==. Same pattern the tracking solution uses, described on Personnel tracking.
Polygons: no workaround on the map that I know of. Map the polygon to tag zones instead, one zone per forbidden area.
Running on 2 robots since last week. The 6 dB rule was necessary, without it the zone flickered every few seconds in the lift lobby. The kitchen alarm fired once already, a cleaner took a wrong turn after a map update on the robot, and housekeeping caught it in a minute. Still would like the request though, doing it in every robot’s firmware is work.
Stealing the zone_id idea for the forklifts, thanks.
- Debes estar registrado para responder a este debate.
Únete a la conversación
Inicia sesión para preguntar y responder, dar me gusta a las publicaciones útiles y marcar la respuesta que resolvió tu problema. Cada aportación suma puntos y niveles.