Blank Zigbee Map with eWeLink CUBE

After the new update 2.3.3 the zigbee map is completely gone.

1 Like

After updating to version 2.3.3, the zigbee map is still not displayed.
Feedback: ID220308

1 Like
  1. Triggering the scenes didn’t update the LQI;
  2. Pressing the button to power it on/off manually didn’t update the LQI;
  3. Clicking on “Refresh” to update the Zigbee Map resulted the map to disappear. Now I don’t have any zigbee map anymore. It’s totally empty :frowning:

Tested on firmware 2.3.2 and 2.3.3
iHost is always connected by LAN
Rebooted many times and clicked on “Refresh” 3 times (before and after rebooting)

Log sent once again (feedback 220164)

It’s incredible how eWelink manage to damage the software with every new release.

You should conduct more extensive testing.
Developers should have access to hardware at home for daily use, rather than relying solely on controlled lab environments.
Consider releasing beta firmwares prior to “stable” releases.

2 Likes

Sorry for the inconvenience. Our team has been working on this issue and will keep you updated.

Sorry about what we cause.
By your description, is the device itself fail to report any LQI.
And for the zigbee map problem, we already pinpoint the problem and will fix it soon.

i-HOST updated with v.2.3.3: all Zigbee topology is missing. Any device are displayed.

Is there any workaround to force the device to report the LQI?
It was working before the upgrade.

I found the problem. The problem stems from the human presence sensor. When I disconnect SNZB-06P, the map works without any problems and returns to normal on other Zigbee devices.

I don’t have the SNZB-06P in my network :frowning:

Any device is definitely locking you.

But my devices are exactly the same…
The problem started when I updated the iHost

I confirm that the SNZB-06P is causing the problem. I also had the problem with the ZBBASICR3 device.

Deleting the device from ihost and re-pairing the device solved the problem. You need to look at the devices that are acting as a router.

Hey

The cause was due to the inability to render nodes with two parent nodes. It’s not caused by specific devices like SNZB-06P.

Our team has been working on a fix.

Thanks for your feedback.

1 Like

Zigbee Map is back on 2.3.4, thanks @SuiKa @ward

But this device is powered off by some months and should not appear connected to another router.

It should appear alone, not connected to anything, similar to the Philips-Office, because they are both powered off (not plugged to the mains)

This door sensor Sonoff SNZB-04 is not supposed to be offline…

This info is reported by the routers, and may need time to sync and clear; Other zigbee maps like one in Zigbee2MQTT also display offline devices in this way.

The recent explainer detailed the issue:

As for the unmatched states between the map and device tile, do you mind sending us logs for a look?