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_-_Supported_IPv6_Features 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,   ... View more

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 ... View more