Can connect Daikin Altherma MMI to home network but not the cloud

I have a newly Octopus installed Daikin Altherma 3 system. I’ve been able to connect the MMI to my home network but can’t connect to the cloud using ONECTA-Daikin on IOS 18.0.1.

The “Add your first unit” flow always successfully connects to the Daikin-AP then switches across to my home network but fails “Device not found on network” and there is no unit shown on the app. The MMI then reports connected to local network but not to cloud. The device shows up correctly in my router configuration.

Things I’ve checked:

  • Not using a VPN on my IOS device
  • WPA2 set on the router
  • 2.4 Ghz connection,
  • Strong Wi-fi signal where the MMI is located
  • IOS latest version
  • MMI firmware latest version (happened automatically the first time I tried all this)
  • ONECTA-Daikin app latest version
  • Nothing in my firewall or DHCP to prevent connection
  • Tried disabling mobile service on IOS device while trying to connect

Questions:

  1. How can I get a successful cloud connection?
  2. Do I need ONECTA-Daikin at all or can I get access to control and telemetry through Home Assistant or similar?

I think that to use HA you’d need the daikin to be on the cloud - there’s no direct local (network) control. (Not yet sure about bluetooth…) There is a 3rd-party interface which lets you plug into the local p1/p2 bus and control things that way.

On the MMI, on the home screen, in top-left corner I have both a wifi icon and a cloud showing a tick. Do you have the same ?

On the MMI, in the ‘wlan gateway’ page, there’s an option to enable the local AP - you may need to do that in order for the app to be able to find the device on the local network. The help for that page points to a web page that might contain useful information ?

Or give Octopus a call and get someone round to do this. They did this for my as part of the handover. May as well take advantage of their aftercare package.

Thanks for your advice. As it happens Octopus gave me a post-install call yesterday and they’re going to have someone talk to me about the issue.

The thing that really puzzles me is how I have a successful connect to my Wifi but not to the cloud. Surely one allows the other. Anyway I’ll report back once I’ve spoken to Octopus in case there are pearls of wisdom to be shared.

I had issues when first trying to connect the MMI to the cloud. I’m going on memory because I’m not keen to repeat it.

My phone (Android, but is probably the same) was not keen to stay connected to the Daikin-AP WiFi. It could connect fine, long enough to find the device on the network, but then it would (correctly) detect that the Daikin-AP network didn’t have internet access so would revert to connecting to my home WiFi which does have internet access. I think I got round this my telling my phone to forget my home WiFi before starting the process.

Once the MMI had failed part way through the connecting process it appeared to get stuck, and I made several attempts that should have worked that didn’t. In the end I cleared out all of the settings in the MMI for the cloud, I can’t remember the option but its fairly obvious.

Once I had cleared out all of the settings it then connected first time and was dead straight forwards.

Yes, a wifi connection would be necessary, but not sufficient, to get cloud access - would also need things like name resolving to work, and correct credentials to connect to your online account.

I had similar problems connecting my MMI to the cloud via WiFi. I vaguely recall needing to enable UPnP on my router, though I wouldn’t necessarily swear to it.

A good suggestion. Gave it a shot but alas no :neutral_face:

I had to create a Daikin online account when installiing the app. I’d assume that those credentials would be available when the app tries to set up a device. I’m asked for my wi-fi password as part of the workflow but not a Daikin account password.

I ended up reporting it to Daikin and got a phone call from their IT support after a few weeks. I went through all the things the lady on the phone suggested without much optimism, but it was resolved in the end. I wish I’d made notes so I could share the solution :slightly_frowning_face:

So on the morning that Octopus were coming round to have a look at the problem I pulled the ONECTA-Daikin app up on my phone so that it would be ready for the engineer to peruse.

It had logged itself out so I logged back in and was immediately met with”new device found”. And it’s all just working.

So I’ve no idea what resolved this. Was it as simple as log out and in again?