This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Closed Official Zigbee SDK2
[App] Xiaomi-mi ZigBee - Main discussion topic (v0.4.1)
This discussion has been closed.
Comments
That's indeed what I tried: after the LED blinks three times I keep pressing the button every second, but in the end I get a 'no Zigbee device found' message. Same procedure works perfect for all my other Xiaomi sensors, but for some reason it doesn't for the cube. Is there some way to further debug what is happening?
I have the power socket (3 of them) and some battery powered switches a cube an a sensor. I placed the power sockets around the house to strengthen the mesh but they do not create a mesh. They all connect directly to Homey. Now my lights upstairs don't switch because the battery powered switches are out of range and the socket switch only sometimes when I use the app.
Can I do something about it. I restarted Homey a couple of times, hoping it would rebuild the mesh.
greetings,
Aaron
My setup looks like yours; it has 3 powered Zigbee devices and 5 battery equiped onces.
I once saw that a connection was via a router to Homey, but after a while all poin straight to Homey, and routing via powered Zigbee devices does not happen. I too have a node that stays offline.
I will check and see if a Github issue is filed.
Yes, lets hope it wil be fixed soon. Thats one of the basic things devices with the zigbee protocol should do, Otherwise we could use kaku instead.
But the last known route shows if it is a mesh or not does it not? A mesh is a route to?
And, I did have a via route via a router once, but that stopped and all ZIgbee devices are now 'straight to Homey'. This happened without a change to the Zigbee setup.
Today a colleague who also has a Homey will try if he can register the cube to rule out that it is a problem with the cube itself. He also ordered a cube, so once that has arrived I can also try with that.
Today I tried to include a Aqara wireless switch. The first attempt failed: it stoppend the inclusion process with "no device found'. Same as you describe.
I pulled the plug on Homey, waited 10 minutes and plugged Homey in again. Waited about 10 minutes and tried including again. This time (and very slowly in going thru the clusters) it included.
So, it is added. Problem is that it now is not controllable:
I will leave the switch next to Homey and press it now and then, to see if it comes online.
UPDATE:
It is controlleble now (great @TedTolboom !)
And I also see routing happening (albeit a curious route; Homey is closer to the Cube than the curtain controller):
Nice! I wil try the steps you took. Now that you have routing, is it also working better. More reliable?
So, no. So far adding routers has not improved my Zigbee mesh (and that was one of the reasons I bought routing devices).
Also, adding a second switch failed twice.... seems hit and miss... I have to do other stuff now, so can't experiment more.
Good luck!
Would it be possible to use the cards in the second and 3rd colom?
If i want to add a temp/hum sensor, and update the status in a later flow i cannot get that done? Because i cannot add the temp/hum sensor in 2 and 3 rd colom only for the battery status..
thnx in advance
#Solved, found another way, with the Tags it does work
Near everything shows 0 - 1 or 0 - 12 i.e. Homey -> Device
However, my HBS's just show their number - i.e 10 (plus one of the contact sensors)
It just so happens I'm having some trouble with my HBS's functioning some but not all the time
Nothing is using my innr bulb as a router despite that being closer than Homey to a lot of things...
Any thoughts?
It also seems that one of those devices is using a lot of storage (about 20%!) according to insights...
Seems something funky going on...
The interesting thing is that my colleague was able to pair my cube yesterday to his Homey with exactly the same Homey firmware and Xiaomi app release without any trouble??
Maybe it's in some way related to the (large number of) other Zigbee devices that I have (although no other device has had problems at initial registration) or this particular cube is in some way at the edge of specification.
Maybe I'll retry with a different cube later.