Update: my OPTO1 is back online. A full power cycle (power supply unplugged for 60 s) fixed it. After the reboot the device synced NTP, completed the TLS handshake with mgmt.viessmann-platform.io, and was then pointed to a new endpoint: dc1-1-iothub-02.azure-devices.net (Azure IoT Hub). It never contacted the old production-7-10-rmq-broker host again, so my .0 workaround was never needed. Back online in ViCare within a couple of minutes. You can read the firmware version through the API, even when the device is offline: GET /iot/v2/equipment/gateways (I used PyViCare with my developer client ID). Mine shows: - version: 2.8.0.0 - targetRealm: DC - autoUpdate: false - aggregatedStatus: WorksProperly My guess is that Viessmann is migrating OPTO1 units from the RabbitMQ/CloudAMQP broker to Azure IoT Hub ("DC" realm), and the device only picks up the new endpoint from mgmt during a fresh boot. So it may be worth checking your targetRealm, and trying a real power cycle (not just a Wi-Fi reconnect) to see whether you also get moved to IoT Hub and skip the .0 broker entirely. Thanks again for the packet analysis, it helped a lot.
... Mehr anzeigen