Server down?

[CristianR]

Hello,

Does anybody knows if the Viesmann server is down? My Vitoconnect OT2 has for 3 days the wifi led on red, no matter if I connected to the wifi, I attached a picture too.

I have talked with someone from local support and at last he told me about system issues....

Thank you!

I can't change any settings on my Vitodens 100, is working on auto mode....

[Chris34]

Hi

I have same issue. Please check Viessmann Climate Solutions Community - Viessmann Climate Solutions Community

I attached device logs too.

[Chris34]

I am using a Vitodens 100 with Vitoconnect OT2. For about a week, Vitoconnect has been unable to connect to Wi-Fi, indicated by a red Wi-Fi icon on the device.

I have tried the following troubleshooting steps:

Reinstalling the Android app
Clearing the app's data and cache
Resetting Vitoconnect (holding the button on OT2 for 30 seconds)
Powering Vitoconnect OT2 on and off
Connecting Vitoconnect OT2 to different Wi-Fi routers and networks
Re-adding Vitoconnect OT2 to my Viessmann account multiple times

I have also collected Vitoconnect logs, which I am attaching to this email. The log file contains multiple errors.

Jan 1 01:02:04 vitoconnect local1.info lightls::model[386]: Setting data (id='25', value='3fcd02', quality=0)
Jan 1 01:02:06 vitoconnect local1.info hb2networkcontrol[386]: Changed Network-Property = network.wlan.sta.credential_status
Jan 1 01:02:06 vitoconnect local1.info hb2networkcontrol[386]: Changed Network-Property-Value = correct
Jan 1 01:02:06 vitoconnect local1.info hb2app[386]: Storing system properties.
Jan 1 01:02:06 vitoconnect local1.crit hb2commonpropertieshb2common[386]: updating md5(/etc/hb2app.conf): 3489082ba206ec193ade0d4bd75c5784
Jan 1 01:02:06 vitoconnect local1.info hb2localhandling[386]: device_error_state_ = kErrorState_Active
Jan 1 01:02:06 vitoconnect local1.info hb2dceadapter_[386]: USING DEFAULT URL!
Jan 1 01:02:06 vitoconnect local1.info hb2dceadapter_[386]: Successfully requested connection to backend (code 0)
Jul 13 20:45:41 vitoconnect local1.info lightls::dhw[386]: Setting temperature setpoint (t=50.000000)
Jul 13 20:45:41 vitoconnect local1.info lightls::dhw[386]: Result=0
Jul 13 20:45:41 vitoconnect local1.err hb2dceadapter_[386]: ID TimeProgramActiveSetpointCh1 not sent: invalid size (7 bytes of max. 0)!
Jul 13 20:45:41 vitoconnect local1.err hb2dceadapter_[386]: ID HeatingCircuitStateCh1 not sent: invalid size (11 bytes of max. 0)!
Jul 13 20:45:42 vitoconnect local1.info llsadapter[386]: On data value (id='56', size=3)
Jul 13 20:45:42 vitoconnect local1.err hb2dceadapter_[386]: error: DCe connection reported error 8.
Jul 13 20:45:42 vitoconnect local1.info hb2dceadapter_[386]: Backend connection reported an error!
Jul 13 20:45:42 vitoconnect local1.info hb2localhandling[386]: device_error_state_ = kErrorState_Active
Jul 13 20:45:44 vitoconnect local1.err hb2dceadapter_[386]: error: DCe connection reported error 8.
Jul 13 20:45:44 vitoconnect local1.info hb2dceadapter_[386]: Backend connection reported an error!
Jul 13 20:45:46 vitoconnect local1.err hb2dceadapter_[386]: error: DCe connection reported error 8.
Jul 13 20:45:46 vitoconnect local1.info hb2dceadapter_[386]: Backend connection reported an error!
Jul 13 20:45:50 vitoconnect local1.err hb2dceadapter_[386]: error: DCe connection reported error 8.
Jul 13 20:45:50 vitoconnect local1.info hb2dceadapter_[386]: Backend connection reported an error!
Jul 13 20:45:51 vitoconnect local1.err hb2dceadapter_[386]: ID wifi_strength not sent: invalid size (1 bytes of max. 0)!
Jul 13 20:45:51 vitoconnect local1.err hb2dceadapter_[386]: ID wifi_channel not sent: invalid size (1 bytes of max. 0)!
Jul 13 20:45:54 vitoconnect local1.info hb2localhandling[386]: Toggle accesspoint mode (UI)
Jul 13 20:45:57 vitoconnect local1.err hb2dceadapter_[386]: error: DCe connection reported error 8.
Jul 13 20:45:57 vitoconnect local1.info hb2dceadapter_[386]: Backend connection reported an error!
Jul 13 20:46:01 vitoconnect local1.err hb2dceadapter_[386]: ID wifi_strength not sent: invalid size (1 bytes of max. 0)!
Jul 13 20:46:01 vitoconnect local1.err hb2dceadapter_[386]: ID wifi_channel not sent: invalid size (1 bytes of max. 0)!
Jul 13 18:46:02 vitoconnect user.info kernel: [ 146.865275] wlan.sta: deauthenticating from 36:e3:48:cc:df:f3 by local choice (Reason: 3=DEAUTH_LEAVING)
Jul 13 18:46:02 vitoconnect user.debug kernel: [ 146.902744] cfg80211: All devices are disconnected, going to restore regulatory settings
Jul 13 18:46:02 vitoconnect user.debug kernel: [ 146.902773] cfg80211: Restoring regulatory settings while preserving user preference for: DE
Jul 13 18:46:02 vitoconnect user.debug kernel: [ 146.902790] cfg80211: Kicking the queue
Jul 13 20:46:02 vitoconnect user.notice root: /usr/bin/cm/ap/././.. /common/destroy_wlan_interfaces.sh: WLAN wlan.sta interface destroyed.

[CristianR]

I have contacted the Viessmann representative for Romania (Adrian Popa) and he told me that he opened a case to Viessmann Germany, that is an issue on the system, many users have the same problem, but no update for a week....

I have also send an email to info@viessmann.com, nothing....

[Chris34]

It sounds like more users in Europe are affected. I analyzed my router logs and noticed that the OT2 is connecting to Wi-Fi, communicating with NTP (time) servers, and using my ISP's DNS. It successfully resolves mgmt.viessmann-platform.io and establishes an HTTPS session with Viessmann servers, but then the communication suddenly stops. As a result, I only see the "Updating" screen in the ViCare app (and red wifi icon)

10:05:18.767224 IP 192.168.0.158.55823 > nsx2.internetunion.pl.53: 42087+ A? mgmt.viessmann-platform.io. (44)
10:05:18.931380 IP nsx2.internetunion.pl.53 > 192.168.0.158.55823: 42087 2/0/0 CNAME mgmt-global-1-waf.northeurope.cloudapp.azure.com., A 52.164.255.195 (122)

[CristianR]

"only see the "Updating" screen in the ViCare app (and red wifi icon)"

This is the same for me, no matter what I do, restart module, reinstall, reset etc etc no solution, and Viessmann nothing...

This is not a customer orientated atttitude from Viessmann.....

[Chris34]

Hi,

Polish Viessmann support informed me that they had a very long maintenance window, but everything should be working now. I reset the OT2, but it's still not functioning correctly. This time, I was able to capture more logs and I see that the OT2 is trying to download firmware with the request GET /firmware/hb2/7637414_Vitoconnect-100_OTOL2.version, but the Viessmann server is closing the connection.

DHCP, DNS, NTP work so OT2 has internet access.

[Chris34]

It suddenly started working.