Order subscription attributes should be the same each run
Currently with each run of the code the Subscriptionhandlers (both MQTT and HTTP) produce a different order each time the code runs. This is likely because the attributes are put into a set when deciding which one to add for the subscription condition. Since a set is hashed in the background it is subject to the python hash seed, that is randomized each time.
Simply sorting them in alphabetical order should solve that problem!
For Entities:
For Devices: