Das hat schon einen Grund warum ich das schreibe. Man kann mit Home Assistant auch den Accesspoint steuern, dass kann man aber niemanden Empfehlen, weil eq3 Ihre API nur Technologiepartner uneingeschränkt zur Verfügung stellt. Andere Community Projekte werden beschränkt, wenn die Abrufe ein Limit übersteigen.
Kommt natürlich drauf an, wie oft man an die Homematic Cloud sendet. Bei einem reinen Sensorabruf kann das klappen, aber das würde ich einem Unternehmen nicht als Lösung empfehlen.
Das ist die aktuelle Situation:
HomematicIP (EQ-3) blocks public IP addresses, if access to the Cloud is too frequent.
Since Dec 1, 2020, HomematicIP (EQ-3) has started to block public IP addresses of Home Assistant installations, if they access the Homematic IP Cloud too often. In this case, the Homematic IP Cloud can only be reached from a cellular network. Further plans to completely block the non-partner apps from the Homematic IP Cloud cannot be ruled out.
Official partners such as Mediola and Smartha are still permitted. The same issue has also been reported for other smart home platforms, like ioBroker, which use different code to access the Homematic IP Cloud.
The Homematic IP Cloud Integration is based on the cloud push principle, by which status updates are transmitted from the cloud to the local installation as an event, so this should not be the problem.
Reducing calls to the cloud might help not to be blocked. The following activities in Home Assistant make calls to the cloud (not complete):
Switch/dim light or power plug
Set target temperature or the active profile on a thermostat
Activate Eco/Vacation mode
Activate/deactivate alarm
Alternative Integration
Quelle:
https://www.home-assistant.io/integrati ... cip_cloud/