Look at the UUIDs that are currently being generated and see if you can determine which type they are. You should avoid using a different type.

https://docs.python.org/3/library/__future__.html

Agreed. The anitpattern is the bare except: https://realpython.com/the-most-diabolical-python-antipattern/

Perhaps each iPhone is on-the-fly creating a UUID as the "public key" for each tag that it sees. This is easy to do with https://docs.python.org/3/library/uuid.html and it would keep the "hardware ID" of each tag out of the public data record. You would need to study up on the sensortag to see what they have for hardware IDs.

IncludedActivityTypes =[]
if f:
    for uuid in f.keys():
        if f[uuid]:
            IncludedActivityTypes.append(uuid)

# --->

IncludedActivityTypes = [key for key, value in f.items() if value]

I find the template and the info on how to use the template to be in Dropbox and scattered across numerous forum threads. It would be more helpful if the up-to-date template with docs and a few working examples were in a repo. https://github.com/omz/PythonistaAppTemplate or other.

The trailing triple backticks need to be on a line of their own.

:beer: :beers:

https://docs.python.org/3/library/timeit.html#timeit.timeit will give you a good sense of performance differences. My bet is that timeit.timeit() will reveal that the dict will be faster then the repeated if/else. However the reason that I suggested the dict approach for a widget is code size.

Also try timeit() on the string question but remember that the current code is not concatenating two strings. That innocent little call to str() effects performance as well. Let timeit() guide choices that really matter to you.

https://goo.gl/images/BNdGdm

Scene games are built using http://omz-software.com/pythonista/docs/ios/scene.html