The need is surely there, but I guess the topic got dismissed as you asked for specific advice on overcoming the issue and I don't think there currently is any (using the built-in timeout at least). What I've done is that I've set the timeout to 10 days and if I need to get notified of some sensor sooner than that, I'll just setup a script that will send a notification after the specified idle time. If this kind of approach is something you'd be interested in, search the forum for "lua timedifference function" or check the wikikrizzz wrote:No one has the same need for this? Interesting!
Yeah, good advice. Thanks, problem is when you have a lot of sensor again it is a lot of scripting. But thanks for confirming that there are more people with this need!Nautilus wrote:The need is surely there, but I guess the topic got dismissed as you asked for specific advice on overcoming the issue and I don't think there currently is any (using the built-in timeout at least). What I've done is that I've set the timeout to 10 days and if I need to get notified of some sensor sooner than that, I'll just setup a script that will send a notification after the specified idle time. If this kind of approach is something you'd be interested in, search the forum for "lua timedifference function" or check the wikikrizzz wrote:No one has the same need for this? Interesting!
True. One possibility would be to adapt e.g. this script https://www.domoticz.com/wiki/Battery_l ... LUA_script (I'm using a bit modified version of that one to get a notification once a day if any battery operated device is below given threshold and then a weekly summary of all used battery devices) so that it would loop through all sensors (just need to be able to define them based on some of the available parameters) and then report as needed based on "LastUpdate". But definitely it would be nice to see custom timeouts (with a notification optionkrizzz wrote:Thanks, problem is when you have a lot of sensor again it is a lot of scripting.
) directly as a Domoticz feature! And where's the problem?GSV3Miac wrote: ↑Tuesday 09 October 2018 14:41 Late to the party but I'd like to be able to specify different timeout for some sensors too (as the OP says, virtual one in particular .. I can't even see a way to use a script fake out the lastupdate value for them,. unless I read and rewrite their actual values in LUA script).
Code: Select all
-- Script for "Holding active" an dummy Setpoint-Device
-- Stand: 29.10.2018
-- Set your thermostat here:
local thermostat = 'Thermostat Heizautomatik'
commandArray = {}
-- Calculating time:
function timedifference(timestamp)
y, m, d, H, M, S = timestamp:match("(%d+)-(%d+)-(%d+) (%d+):(%d+):(%d+)")
difference = os.difftime(os.time(), os.time{year=y, month=m, day=d, hour=H, min=M, sec=S})
return difference
end
local function updatenum(dev, value1)
local cmd = string.format("%d|0|%d", otherdevices_idx[dev], value1)
table.insert (commandArray, { ['UpdateDevice'] = cmd } )
end
-- Let's go:
for deviceName,deviceValue in pairs(otherdevices) do
if (deviceName== thermostat ) then
if tonumber(deviceValue) > 0 then
if timedifference(otherdevices_lastupdate[thermostat]) > 3500
then
print ("Das Thermostat wurde mit der identischen Temperatur aktualisiert.")
updatenum(thermostat, tonumber(otherdevices[thermostat]) + 0)
end
end
end
end
return commandArray