The current location device will not have anything in the string value if it has a value of 0 ("Home"), -1 ("None"), or -2 ("Multiple Locations"). When the value is 1-9999999, then the string value is updated to reflect the name of the known location that matches the current value. For example, if the value of the current location is 2 and you have a known location of "Starbucks near home" that has an ID of 2, then the string value of the current location device will contain "Starbucks near home". When you enter the home location, the string value goes to blank and the value changes to 0.
For me, this works ok since I'm using $$DSR to announce when I'm entering or leaving a known location as long as it's not home. I'm using another event to announce when I'm home. I got lucky with my event since it would not work correctly with the string being empty when entering the home location. I think if you update your event as I did, so that when you enter or exit a known location, as long as it's not home, then you should be able to use the $$DSR (again, not sure why this works since the status value is technically just 1-999999). Then, when entering or exiting the home location, you could do something else with a separate event.
For me, this works ok since I'm using $$DSR to announce when I'm entering or leaving a known location as long as it's not home. I'm using another event to announce when I'm home. I got lucky with my event since it would not work correctly with the string being empty when entering the home location. I think if you update your event as I did, so that when you enter or exit a known location, as long as it's not home, then you should be able to use the $$DSR (again, not sure why this works since the status value is technically just 1-999999). Then, when entering or exiting the home location, you could do something else with a separate event.
Comment