Deconz-rest-plugin: All sensors takes a while to be reachable .

[MattL0]

Or i need to mannually activate them by passing in front of them.. or closing doors etc..

I am on deconz .73 . Was on .75 when i saw this...

I can't remember what build didn't have this problem.

[MattL0]

what is the last stable version? do not want to be on beta

[Smanar]

You mean after a restart ?
Or all the time, when you have triger one, it stay reachable for a long time ?

[MattL0]

After restarting deconz only.

[Smanar]

Ok so it's something normal.
For exemple Xiaomi device send notification only every hour or if you have a state change, the rest of time they are sleeping.
So if the device have already send its notification and nothing change for him, the conbee need 1 hour for the next notification and set the device in reachable state.

Sensor can send request, but they don't answer to the gateway.

[MattL0]

Ha ok thanks a lot! So the xiaomi sensors will stay in the network, even if they are unreachable since one hour?

[MattL0]

Will have to modify some automation here. But it is weird that it was no behaving like that before... the last time I saw this was in the .35-50 deconz version

[Smanar]

Warning, I m say that, just if you restart deconz.
You will not have this problem if deconz stay online.

Or i need to mannually activate them by passing in front of them.. or closing doors etc..

If the device was realy out of the network, you will not see it when you activate them using them.

Ha ok thanks a lot! So the xiaomi sensors will stay in the network, even if they are unreachable since one hour?

No, it just mean the gateway can't know if the device is reachable before having a notification from him. In reality the device is reachable, but the conbee can't be sure of that.
After the first notification, the conbee will mark it as reachable for long time, it will wait lonnnng time before mark it "unreachable" again, lot of more than 1h.

[MattL0]

Then deconz should mark them as reachable ...and if there is no sign of then after 2 hours then it should set them as unreachable . @manup

Sent from an Iphone

---

From: Smanar [e-mail]
Sent: Saturday, March 14, 2020 4:24:01 PM
To: dresden-elektronik/deconz-rest-plugin [e-mail]
Cc: MattL0 [e-mail]; Author [e-mail]
Subject: Re: [dresden-elektronik/deconz-rest-plugin] All sensors takes a while to be reachable . (#2584)

Warning, I m say that, just if you restart deconz.
You will not have this problem if deconz stay online.

Or i need to mannually activate them by passing in front of them.. or closing doors etc..

If the device was realy out of the network, you will not see it when you activate them using them.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/dresden-elektronik/deconz-rest-plugin/issues/2584#issuecomment-599130780, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGRZIWPMTQUHYOTFQYACQ6LRHPRWDANCNFSM4LHRCBSA.

[Smanar]

Only 2 hours ?
I was sure it was at least 24h.

BTW.
Are you looking for reachable state on phoscon or on third application ?

Because I have just make a fast try (reboot deconz), and reachable state havent moved on Phoscon. But was realy short off line.

[ebaauw]

reachable is utterly useless and best ignored. See #2590.

[MattL0]

Only 2 hours ?
I was sure it was at least 24h.

BTW.
Are you looking for reachable state on phoscon or on third application ?

Because I have just make a fast try (reboot deconz), and reachable state havent moved on Phoscon. But was realy short off line.

I am using it on homeseer (via norered deconz ) . And my sensors becomes unreacheable. But saw it on phoscon too.

I will just remove the automation that use the unreachable state to send me a pushover message . Thanks guys.

Hope it will be removed for last seen !

[MattL0]

did a little test today because this time the sensors were not unreacheable ( deconz v.72) at restart of deconz in phoscon

• on restart of deconz sensors are not unreacheable
  -on restart of computer sensors are not unreacheable
  -updating to deconz v.2.05.75 : sensors are not unreachable.

So.. i guess it was some sort of ''healing'' or just a coincidence yesterday?

[Smanar]

Coincidence for me ^^, I think it's a timing situation.

Perhaps the off line time was longer, perhaps something happen to the database, ...
Like he have said, it's not something precise.