To further address this issue, I opened a new topic to explain why SWV behaves differently across recent versions.
We’ve updated SWV support since CUBE 2.1 for its built-in features.
The changes mean it is no longer an ON/OFF Switch in the CUBE and won’t be supported by Matter Bridge.
If you have paired SWV before version 2.1 and prefer to use Matter instead of the built-in features like schedule. Please DO NOT remove the device from eWeLink CUBE/iHost.
We prioritized maintaining the experience for previous versions so the core abilities should not break. So, it would work as long as you leave it unchanged.
In the meantime, we will seek a workaround to get it through Matter Bridge.
If you happened to have removed it or paired it after version 2.1, you can not directly use it via Matter Bridge. However, you can still use an extra switch (physical or virtual) to sync both statuses to gain control via Matter.
I recently added a SWV to my iHost, everything seems fine there, but the device has not automatically carried through to Google Home.
My ihost and Google home are connected via matter and all devices usually carry though automatically when added to the iHost.
Any idea or reason why the SWV hasn’t and home I could get it to, without removing and reading the matter bridge?
I don’t wish to reconfigure names, room allocations and automations in Google Home for all my devices again.
Just seen your post - I found the same problem with a Tuya leak detector, which had paired perfectly with the iHost. As the capability is { "detect": { "detected": true }, the same with a leak sensor or a motion sensor, then a virtual motion sensor served for the Matter bridge to my Smartthings hub. Functions great, with a leak icon but ‘Motion detected’
Presumably for control, if you need that, you will need to create another device, a switch I would imagine.
Hello,
I have Sonoff SWV connect to my ihost and link to my Google home by matter and it works well. Installed since 1 month. Automatically synchronize.
It seems to work like simple swith on/off.
I understand the situation and thank you @ward for replying and consolidating the threads.
I paired it after I had updated to 2.1. I have set up a virtual switch in Node Red but even that has proven to be a buggy solution.
It is quite frustrating through as this is a newly released device and the box is labelled up as working with Google etc.
I don’t plan to set it up again but I guess it might work better if I paired it with my old Z-bridge pro but the whole point of getting the iHost was to stop using that.
