Glad to hear it's working for you! I don't have a virtual station/AP device myself so I have to use a different hack with the Android app.
Since the auth token is temporary, we have to store and reuse the original credentials in the config right now. The token is just renewed and stored in memory every time the
pysesame.CandyHouseAccount instance is created (or when it expires). I and others have asked CANDY HOUSE add support for API keys so that you don't have to provide a username/password to access the API.
The friendly name option is the only consistent way to assign names to devices, so I'd rather not introduce a new option. I considered using the device ID as the entity ID, but it looks like most platforms prefer a user-assigned name for the entity, even though that means changing the visible name also changes the entity ID. The device ID is not easily discoverable by the user so using the assigned name makes writing automations easier, and I did not expect name changes to be frequent.
If this is a major issue I could add an option to use the device ID for all entity IDs.
There seems to be a bug in the API service right now where the
is_unlocked attribute is always reported as false, that needs to be fixed by CANDY HOUSE.