the issue i am seeing specifically is not down to range etc. it seems that it gets into a state when the contact opens/closes the LED doesn’t flash but then a few days later it starts to work again where the LED flashes when the contact opens/closes
I think that IS range, Stuart. I’ve seen exactly the same here.
What you might not have twigged is that you only get the green ring flash if the device has communicated the state charge successfully with the ST hub.
It sounds as if, like me, you are working just at the extreme of the range. Some days it works, some days it doesn’t.
Extending the mesh using some UK power outlets (and re-pairing the Orvibo, in situ, once this was done) completely cured the problem.
If it is range and there is only one repeater nearby (or only one known to the sensor) it can happen that the repeater is busy when the sensor tries to send a message and so the message fails for that reason.
Changing the heartbeat reporting has zero effect on battery. All I am doing is revealing in the event when there’s a zigbee handshake between device and hub. All devices talk but most dth choose not to reveal it.
I see the same behaviour, I came to this topic to ask exactly what you did. I doubt I have a range issue because this sensor is closer than other devices what work reliably. If I press the button on the sensor it starts working immediately, it seems to me that it goes into a sleep state and ignores the open/close state change until is waken up by button press.
Catch 22, the device only goes into a sleep state if it is not able to handshake with the hub after a few hours. Pressing the button wakes it up. I would not be able to explain why the device is struggling to see the hub when others further away are fine.
Try swapping the devices around and see if the problem follows as the devices are very simple to remove from it’s fitting.
If the problem does follow the move then it’s a fault with the device or battery.
If it doesn’t then it’s probably a signal quality issue rather than range.
I also had major issues caused by light bulbs repeating signals badly on my mesh. Since removing these from smartthings my stability has been excellent and battery life also improved dramatically.
I currently have 27of these devices and due to the recent stability improvements have ordered another 10.
Yep, same for me too. I’ve got three of these and they all just work when the feel like it. Seems totally random to me. As someone else said, IMO they’re a bit of a false enconomy being “cheap”. The official sensors have been absolutely rock solid for me (and some are positioned further away than some of these three). I’ve had trouble with mine since day one.
I have had two of these Orvibo sesnsors for a week now and one of them seems to be working fine, but the other one is now just dead, with no signs of life.
I have changed the battery but still dead.
Has anyone else had problems with them just suddenly going dead?
Can they be reset at all ?
I have 6 of these Orvibo contact sensors and they are working great for me.
Only 1 is a bit clunky but that is because it is a bit too far away from the ST hub. The signal on these sensors aren’t that great.
Batteries go dead very quickly as soon as the device has trouble connecting. If the connectivity is good it lasts a few months. If it loses connectivity it can go down from 70% to flat in a couple of days. Seems to kill the battery when it cannot connect. Have no idea how to stop this behaviour.
Hub reboots are a common cause of loss of connectivity even among native sensors. When smartthings sensors get stuck you only need to worry about reseating the battery. With these sensors if the same thing happens you need to get to it quickly to prevent it draining all the power. Hence me adding the heatbeat to the DTH to monitor connectivity.