Copy that this issue is also reported earlier by @cliff and @andy.wolf, and we have received logs from Andy days ago and our engineers are on the way to addressing the issue. Let you know we have something.
Happy to let you know that our team has fixed this issue and planned to release new updates with next firmware in the middle of November.
Someone has tried these modules, yes the ihost accepts them but I wanted to get the measurement data, because these modules have that option for you, but with the ihost it does not give me values only the state of the switch.
We are adding the capabilities of this feature generally, based on users feedback, We are on some slightly changes coming with monthly updates, Please let me know what’s your issue specifically and we will check It to see if some improvement can taken.
The newest CUBE Version 1.11.0 brought support for Ikea Tradfri E1745 Motion Sensor. It works as expected. However, it is not present on the ZigBee Map or it is seen as not connected to anything (floating). Device’s battery status is shown as “unknown” but on its tile it is green.
Hi. I have some wall switch from MOES. They can be added to iHost but I can not control their channel separately. I can do that physically but on the UI when I turn on one of them, the other one will also turn on.
device id: a4c1386fa2f28b98
The zigbee map only shows the current connection between the zigbee device and the parent node along with the LQI value. It does not show the relationship between all neighbor tables of zigbee devices, but the zigbee network used by iHost’s actual zigbee is a mesh structure.
I had this discussion with their support and it is a mesh even if on their Zigbee map it looks not mesh like. You can get router to router connections only if they both don’t have direct good connections to the coordinator. So for example if router 1 connected to the coordinator then router 2 can connect to router 1 as long as it does not connect as well to the coordinator itself. I personally think they should incorporate a mesh appearance, like ZHA and Zigbee2MQTT do, so it is less confusing and encourages the use of more router devices rather than end-devices, but that is not how they have chosen to display it.
I tried to connect to iHost but it is not detected (after it is set in pairing mode).
Did I miss a step to pair it or it shouldn’t appear in the list (didn’t see any post on it so far ?) - pls advice.