Hi
how to I avoid the status of ESP devices in FHEM shown as absent
ESP device is available
It is only logging the right value if I do send a command like GPIO 0,1 etc.
Mainly the logis showing status absent, but not the status of the GPIO
Thanks T
espeasy and fhem controller showing absent even it is available
Moderators: grovkillen, Stuntteam, TD-er
-
- Normal user
- Posts: 344
- Joined: 26 Dec 2017, 18:02
-
- Normal user
- Posts: 344
- Joined: 26 Dec 2017, 18:02
Re: espeasy and fhem controller showing absent even it is available
Discussed this also in fhem forum.
looks like esp easy is not sending anything to fhem.
only when I did send a gpio command.
but after I while it is not answering a get precence from fhem
looks like esp easy is not sending anything to fhem.
only when I did send a gpio command.
but after I while it is not answering a get precence from fhem
-
- Normal user
- Posts: 1156
- Joined: 03 Sep 2016, 23:27
- Location: Bielefeld / Germany
Re: espeasy and fhem controller showing absent even it is available
fhem has an absence check for ESPEasy devices.
If a device does not send data for a defined time fhem assumes it is absent.
There are two possible ways to handle this with fhem:
fhem's ESPEasy interface gives two parameters for every device, one is the time threshold - after this time a device is called "absent".
Second parameter is a setting if presence should be checked at all.
You may switch the presence check off - bad idea in my eyes, it exists for a good reason. This is good only for battery/deepsleep items.
It might be possible to set the timeout to a long time... not really good as an "absent" message might be very late.
A better way: Use one task in ESPEasy, set it to system info -> RSSI and set delay to 60 seconds. This sends RSSI value to fhem once per minute.
Set the timeout in the ESPEasy-device (not in the bridge!) to 300...600 seconds. This should be really long enough. So if one or two RSSI-data are missing,
nothing happens, but if they are missing loger then 5...10 minutes fhem will show an "absent".
My ESPEasy devices are configured using RSSI, a reading group in fhem shows all RSSI values accumulated in one "box".
Works nicely for long time now.
Regards
Shardan
If a device does not send data for a defined time fhem assumes it is absent.
There are two possible ways to handle this with fhem:
fhem's ESPEasy interface gives two parameters for every device, one is the time threshold - after this time a device is called "absent".
Second parameter is a setting if presence should be checked at all.
You may switch the presence check off - bad idea in my eyes, it exists for a good reason. This is good only for battery/deepsleep items.
It might be possible to set the timeout to a long time... not really good as an "absent" message might be very late.
A better way: Use one task in ESPEasy, set it to system info -> RSSI and set delay to 60 seconds. This sends RSSI value to fhem once per minute.
Set the timeout in the ESPEasy-device (not in the bridge!) to 300...600 seconds. This should be really long enough. So if one or two RSSI-data are missing,
nothing happens, but if they are missing loger then 5...10 minutes fhem will show an "absent".
My ESPEasy devices are configured using RSSI, a reading group in fhem shows all RSSI values accumulated in one "box".
Works nicely for long time now.
Regards
Shardan
Regards
Shardan
Shardan
Who is online
Users browsing this forum: Anthropic Claude Bot [bot], Google [Bot] and 14 guests