Yes, this was an issue in the 2.4 release, there was an REST call in the StateDescriptionProvider. But this is already fixed in the 2.5 release.
Yes, this was an issue in the 2.4 release, there was an REST call in the StateDescriptionProvider. But this is already fixed in the 2.5 release.