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.
433 range testing
![mranderson](https://secure.gravatar.com/avatar/cfc6deaa4e6cd94d54746e9d2dd0deae/?default=https%3A%2F%2Fvanillicon.com%2Fcfc6deaa4e6cd94d54746e9d2dd0deae_50.png&rating=g&size=50)
Hi @Reinier
I've now methodically tested my 433 remote on Homey VS 433 doorbell receiver to see if there were any differences in reception.
Homey and doorbell placed right next to each other, and then used skype on a phone to check when signal was not received.
No.11 on this map is my home, and I've drawn the internal walls (wood), and a few points of interest.
![](https://forum.athom.com/uploads/editor/aw/z8obsn1x2q4f.jpg)
A: Homey and doorbell placed on a shelf here. Both responds to remote nicely when standing right next to them.
B: Still inside, by the end of the couch.
Doorbell OK
Homey already struggles with reception (10-20% success on button presses, though I did not spam the remote button).
C: Front door
Doorbell OK
Homey no reception
D : Out in the street
Doorbell works great until this point
Homey no reception
I'm no expert, but I guess the doorbell listens on a smaller spectrum than Homey (less noise), but when I'm struggling with remote presses 3-4 meters away from Homey, thats's not a good consumer experience. I remember a video where Emile demonstrated an impressive 433 range in their office, so I'm wondering if I can expect Homey to be on par with my doorbell in the future? (At least to work with the doorbell button by the front door)
I've now methodically tested my 433 remote on Homey VS 433 doorbell receiver to see if there were any differences in reception.
Homey and doorbell placed right next to each other, and then used skype on a phone to check when signal was not received.
No.11 on this map is my home, and I've drawn the internal walls (wood), and a few points of interest.
![](https://forum.athom.com/uploads/editor/aw/z8obsn1x2q4f.jpg)
A: Homey and doorbell placed on a shelf here. Both responds to remote nicely when standing right next to them.
B: Still inside, by the end of the couch.
Doorbell OK
Homey already struggles with reception (10-20% success on button presses, though I did not spam the remote button).
C: Front door
Doorbell OK
Homey no reception
D : Out in the street
Doorbell works great until this point
Homey no reception
I'm no expert, but I guess the doorbell listens on a smaller spectrum than Homey (less noise), but when I'm struggling with remote presses 3-4 meters away from Homey, thats's not a good consumer experience. I remember a video where Emile demonstrated an impressive 433 range in their office, so I'm wondering if I can expect Homey to be on par with my doorbell in the future? (At least to work with the doorbell button by the front door)
Comments
Same issue here, i also have a poor 433 range, i'm on firmware 0.10.1
The Video was very impressive, but results in real live are totally different.
@ Athom, is this a known issue?
https://github.com/athombv/homey/issues/951
I did a small test to , red is homey and yellow is where the range ends 12-14m
concrete walls and did use a battery wall switch to tell homey to start milight.
Very poor distances not even close compared with the video where they test the 433 range
My github is still untouched - not even a tag, so I'm just curious on what to expect.
The youtube video's show just a single setup on where the range could be great but it all depends on the environment.
i think kaku and 433 would be no solution in my home automation.
And you may be correct, but all I'm asking for is an official statement (not you
That seems to be a big problem.
somebody same results with KAKU Remote control? regards to Homey?
Because to overcome interference of the sending from night sensor against the sending from Homey is there a 3 sec delay. Now I waiting for clouded weather and see of Homey can follow the night sensor even good.
When I received the Homey all the KaKu's en thermometers worked fine.
After the some update's (do not know which update) just 1 TS32, two contacts and 2 switches work distance 3 meters, the rest do nothing anymore.
If I place them closer to the homey they works fine again. So there is something changed.
But it's still beta :-)
And I was not demanding a athom statement that "your range will be 10 meters minimumin the future!", as some here misread me to believe. And when I only got silence from my first post and github, I really want some heads up if they have some tweaking planned for the 433 receiving range (acknowledging the problem) - or if they're satisified with listening range as it is. Anyways, added my remote/ wall switches info to the github now, looking forward to the progress
Homey is 70cm below the ceiling and 5 meter cross to under that sensor that's switching two lanterns in the garden for a long time now.
My globe is the test lamp in the living room. Now waiting for the darkness to come.
This moment to my surprise the test lamp went on again. Looking outside the window I saw that is was right.
The two lanterns in the garden where on too. There are very dark clouds that are coming and going.
A nice test opportunity this way.
Normal it is that you can see on the device page if a wall-switch has used. If you remote paired that way.
Now there was only one that was doing that but it was 50 cm from Homey.
The second nearest, on 2 meter distant, has a well/not reaction on Homey.
When I remove a device and again remote pair it was it very difficult to do. Distant to Homey: 3 meter.
Pairing was sometimes accepted but no switching possible. After a lots of trying I had luck.
This way you can't use a remote paired device as a trigger in a flow.
Edit
This morning, 08:00, it is a little better. The 2 meter range is OK and the 3 meter a well/not reaction.
It looks like https://github.com/athombv/homey/issues/951 is to hot to handle.