Cisco Meraki Wireless and Tado X devices

[Royv]

Hey all, 

I recently bought myself a smart thermostat with valves. I am having trouble to set the devices up with wifi (Using an MR33). 

besides the bridge for thread and matter devices the rest just wont connect. 

Using the same equipement in another wireless environment is making it a breeze to install, which to me says something in the meraki is making the connectivity issues appear. 

My network consists of a meraki firewall, switch and AP. I have upgraded the devices, changed radio settings and checked the other devices of possible misconfigurations, but it all is not helping me connect those devices to the wireless Network. 

typical installation of those devices are a bluethooth connection from phone to device so it can push the wireless settings. But it just wont connect and i am wondering if ppl came across these kind of challenges. 

Kind regards,

Roy

[VivekT]

Hi,

Can you please tell me how are you setting up thermostat ? Is it with some app ? Please check the following 

it should be disable if two devices want talk to each other on same wifi. 

Wireless>>>>>Firewall & traffic shaping

Block IPs and ports

Enabled               (bridge mode only)

Layer 2 LAN isolation

Disabled

[Royv]

Hey VivekT, 

Thnx for the reply! configuration of those devices indeed happen via mobile app (Tado). the app briefly makes an bluetooth connection to the device in order to push the settings of the wlan. it is a thread and matter device which uses a bridge device thats connected with wifi. The bridge itself connects fine, however the thermostat and valves not. 

About the client isolation:

i double checked but thats indeed how it is configured. 

Kind regards 

Royv

[VivekT]

ould you please perform a packet capture on the Meraki access point to check if there is any communication between the thermoset and the AP? I understand this is unrelated to Air Marshal, but please verify if there are any blocks. Additionally, confirm whether the 2.4 GHz band is enabled and if your device operates only on 2.4 GHz

[Royv]

Hey VivekT, 

Thnx for reaching out again. I have been digging around and found some things. First of to answer your questions, yes 2.4ghz is enabled and it operates on that. Further more packet captures have made me look deeper into the matter because i was seeing some unexpected IPv6 traffic. 

Thread / matter makes use of the 802.15.4 standard (6lowPAN). It connects the bridge via IPv6 to the IOT devices. Seeing meraki doesnt not have a radio for this, the bridge x (How tado calls them is being used as thread router. Also not entirely sure if im describing it technically correct, but it works for me to get the point)

Meraki reports you need to enable a certain Setting under general in the network wide settings. Namely: wireless IPv6 bridiging. At first it didnt resolve anything and didnt even change anything. So i then configured IPv6 on the network and suddenly i dont get the error message anymore that the device cannot be reached. Now it is checking the wireless connectivity for ages till it times out. 

References:

documentation.meraki.com/MR/Other_Topics/IPv6_Support_on_MR_Access_Points#MR_27.X_Firmware_Release_-...

documentation.meraki.com/General_Administration/Other_Topics/IPv6_Device_Compatibility

also i came across a few older threads on this forum and on others with uses with the same issues, but sadly no solution to this. 

Kind regards,

[ESLORD]

Hey everyone, I know I’m replying to an old thread, but it looks like no one really found a solid solution. I bought a Tado system last week and ran into the same issue while setting it up.

In my case, the Bridge connected to my Meraki Wi-Fi without any problems. However, whenever I tried to connect and pair the wireless temperature controller, it failed every single time. I was pulling my hair out trying to figure out how the thing communicates.

I went through this thread and applied everything that was suggested,  a dedicated 2.4 GHz IoT network, disabled Layer 2 isolation, and even created a rule in the Meraki Wireless Firewall & Traffic Shaping section to allow IPv6 traffic from “any” to the local LAN. None of that worked.

What finally solved it for me was enabling Bonjour and adding a rule to allow Bonjour discovery for all services. As soon as I applied that, the wireless Tado temperature controller paired without any issues.

I don’t use VLANs on my local network, so when creating the Bonjour rule, just select VLAN 1, which is the default in most cases.

Hopefully, this helps someone else dealing with the same problem.

[CarolineS]

Thank you so much for providing this info, @ESLORD!  I'm certain your advice will help future community visitors (and the people using AI chatbots using info scraped from the community... 🤖)