Is your TRVZB connected to iHost?
According to the description on the website, R5 can only be added to one ewelink-remote gateway.
But we donât know whether it was intentional or a mistake in ihost?
Not! I want to keep control of TRVZB via the eWeLink app!
You need to install and use the paral-sync add on then.
I have installed paral-sync, but TVRZB and SNZB-02P are not supported!
Good morning
letâs say that we are 50% there with the conversation between matter Alexa and Nest-Hub.
With Alexa and Nest-hub all devices with one channel remain connected;
Instead, all devices with multiple channels connected still disconnect, an example
I ask you (please) when in your route map do you plan to program the management of the roller shutters
Grazie
Hello, in version 1.13.0, will you reboot again without this problem (not the reboot of that upgrade to 1.13.0)?
1 Like
I have rebooted 5 times since upgrading to 1.13.0. The device names are still lost.
1 Like
hi, did you update the Paral-sync add-on? please update it on its info page.
Matter Hib or Bridge too? I have an iHost. Itâs be nice if they could be on the same matter network in case my local wifi breaks down.
If your WLAN is down, Matter communication will not be possible, unless your Matter devices are LAN or Thread capable. Matter devices use one of the following three options to communicate: Ethernet/LAN, WiFi/WLAN, or Thread (low-rate wireless personal area network, the same protocol as Zigbee). To use Thread, you need a Thread border router.
Matter does not require an internet connection to operate, but it does require a controller to control Matter devices. Most Matter controllers you can presently buy are cloud dependent. So donât count on it working properly without WLAN.
My Raspberyy Pi 4 running Home Assistant is currently the thread/matter controller, so local. On its network is the iHost - I think as a border router and bridge? when/If the NSP-P can do thread/matter will I be able to add it to this network as bridge/router like the iHost or will it only be a second controller?
I donât know.
You say that your Raspberry runs Home Assistant. You should revert to HA documentation then.
Note that Thread and Matter are not the same. iHost is a Matter gateway.
The Home Assistant documentation will not say how the Sonoff NS Panel Pro works. Will the NS Panel Pro insist on creating a new matter over thread network or join the one created by home assistant and already joined by the iHost?
I did not say matter and thread were the same thing but both need to be said as matter can exist without thread and thread can exist without matter.
Why do you think that iHost documentation will say anything about Home Assistant platform integration?
I donât know about NS Panel. Matter Hub is currently under development and expected to be launched in early 2024. Itâs unlikely that your iHost joined any Matter network, especially Thread-based. As for now, you can synchronize various devices within iHost to other platforms using the (still experimental) Matter bridge. This way you make the non-Matter protocol devices to be used with platforms that supports Matter standard.
In a nutshell, Thread (protocol) does not exist without Matter (connectivity standard). It is a mesh networking technology designed specifically for Matter IoT products and is not used elsewhere. Matter uses Thread as one of its supported transport layers. You donât use Thread for other communication purposes. In this respect, it is like Zigbee or Z-Wave and is not like WiFi or Bluetooth.
After updating the Paral-sync add-on during the evening (27.12.), the devices were not supported, but after this evening (28.12), the update worked! Thank you!
Why do you think that the Home Assistant documentation will say anything about how the NS Panel Pro integrates into a pre-existing matter network?
Yes it does. To quote a google employee on a google community page before matter existed:
[quote] Very glad to see your interest in Thread, OpenThread, and Nest.
Today, the Nest Learning Thermostat makes use of Thread technology primarily for controlling our HeatLink products in Europe. It does not expose any APIs for control or introspection over Thread right now. If you want to interact with the Thermostat, youâll need to use our Works with Nest (cloud) APIs.
As you know, Thread (and OpenThread which implements it) provides only a network layer, but for meaningful interactions, youâll need an application layer on top of it. Nest products use our Weave protocol suite for this purpose. Weâre not quite ready to provide full third-party interactions directly to our products quite yet, but you can begin exploring Weave technology over at http://openweave.io/ â watch that space for more to come.
Rob[/quote]
There are two parts to my Google Nest Learning aThermostat 3rd Generation. They can talk to each other wirelessly using Weave over thread. The Google Nest Protect fire alarm in the kitchen joins their network. I think the newer google nest thermostats use matter over thread but the older stuff is âWeaveâ over thread, but they have largely given up on that implementation. I donât think the Google Nest Protect smoke alarms use matter yet. Google also released Openthread.
Matter support on the iHost was introduced on the iHost a while ago. I can see iHost devices in Home Assistant inside their matter integration since I flashed openthread routing capability on a Sonoff Dongle E. It is matter support on the NS Panel Pro that I donât think has been realised yet.
If you know, why do you ask?
Why do you reply to a question you imagined with incorrect information?
Seems like you didnât notice, but this is a forum. This may be impossible for you to comprehend, but any forum is a public meeting or assembly for open discussion.
It would be best if you answered your own questions because everything else is untrue and inconsistent with your understanding. I recommend that you run a blog so others can admire your incredible awesomeness.