As you can see above the Lat/Long is not detected properly from syslocation. I managed to figure out what it was and resolve it by changing the syslocation but it appears to be a bug. When you have the + it doesn’t work, when i removed the + and did a rediscover it fixed it and now lat/long is correct
I never saw it written with a +.
Have you wrote it on your own (e.g. on a Linux system)?
it’s a sysLocation it’s manually set, normally we don’t have the + but this time one of the engineers must have put a + when configuring and it broke the detection, so figured i should report that a + character breaks the detection, probably due to the regex being used to detect it i’d imagine.
Basically just need a commit to fix parse_location to be
/([)([+|-]?[0-9. ]+),[ ]([+|-]?[0-9. ]+)(])/
instead of… /([)(-?[0-9. ]+),[ ](-?[0-9. ]+)(])/
would make the parse work even if their is a +
So just make a PR.