Domoticz

BluesBro wrote: The error is now reduced to only:

2016-10-10 16:34:02.816 Error: EventSystem: in /home/pi/domoticz/scripts/lua/script_time_checkphones.lua: /home/pi/domoticz/scripts/lua/script_time_checkphones.lua:46: attempt to index field 'location' (a nil value)

patoo77 wrote:Nice work mate, always love to see what is being done using location positioning
The only downside I would see is huge battery drain, since polling for FindMyiPhone every 5 minute has to be huge in terms of battery ressources. Have you monitored how much battery it costs/hour?

I am always looking to improve the location on my own app, I have alrdy given a try to the "find my iphone" API a few years ago.
I wonder if your solution could be improved by coupling it with my own Pilot app: for example, trigger the "poll" only when the users enters a much wide radius (maybe a km around home). That way, less battery usage, and much better positioning.

Happy to speak with you all on that matter,
P

mvzut wrote:

BluesBro wrote: The error is now reduced to only:

2016-10-10 16:34:02.816 Error: EventSystem: in /home/pi/domoticz/scripts/lua/script_time_checkphones.lua: /home/pi/domoticz/scripts/lua/script_time_checkphones.lua:46: attempt to index field 'location' (a nil value)

Apparently the API call to the Find My iPhone service didn't result in location info. Can you add a print(result) just before the "output = json:decode(result)" line? Do you see your phone name in the (large) string that should now be printed every 5 minutes in your log? And do you see coordinates close to that name? Probably not, otherwise the location variable would not be nil, but maybe you find some hint in this string that could explain why.

lukev wrote:Peter, I can confirm the script can work on a Synology with domoticz installed. It does on mine

perese wrote:Thanks for the confirm. Since your seems to work, did you create the "text switch" as I described?

perese wrote:Can anyone confirm that a text switch is created by RMB on the Dummy switch and selecting the Text option of device? The switch/device appears in the utility tab and not in the Switches tab in Domoticz after created.

perese wrote:After a debugging and in same time do understand LUA and Domoticz event system and configuration I think I found a solution.

I cannot say why that needed for me but after changing

Line 54 from

Code: Select all

prev_distance_str = string.match(otherdevices['Position ' .. user], '%(.*%)') or '(1000 km)'

to

Code: Select all

prev_distance_str = string.match(otherdevices_idx['Position ' .. user], '%(.*%)') or '(1000 km)'

It suddenly worked. Maybe it is the version I'm at or something else, but the original code did not work.

Thanks lukev for your confirmation, helped a lot in my searches

if math.abs(prev_distance - distance) > radius then

mvzut wrote:

perese wrote:After a debugging and in same time do understand LUA and Domoticz event system and configuration I think I found a solution.

I cannot say why that needed for me but after changing

Line 54 from

Code: Select all

prev_distance_str = string.match(otherdevices['Position ' .. user], '%(.*%)') or '(1000 km)'

to

Code: Select all

prev_distance_str = string.match(otherdevices_idx['Position ' .. user], '%(.*%)') or '(1000 km)'

It suddenly worked. Maybe it is the version I'm at or something else, but the original code did not work.

Thanks lukev for your confirmation, helped a lot in my searches

The line you changed looks for text between parentheses in the text device named "Position <user>", where <user> is obviously replaced with your user name. If it can't find text between parentheses, it will return the value "(1000 km)". That way the next steps in the script will still function, even if the text device still contains the initial text "Hello World!", and since "prev_distance" is given such a high value, the later check

Code: Select all

if math.abs(prev_distance - distance) > radius then

is certainly true so that it will update the value of the text device.

Your change makes the script look for text between parentheses in the IDX of the device, which is a number, so it won't find such text. Therefore, in your new script "prev_distance_str" will always get the value"(1000 km)", so the text field will always be updated. If this causes things to start working for you that's great, but please note that it's maybe not ideal: The text field is now updated every minute, even if the value didn't change, which causes an unnecessarily large sensor log.

What could be the case is that you somehow can't read the values of your text device(s) with an "otherdevices[...]" command, I believe more people have reported this in this forum. Could be related to the Domoticz version. You could try to replace "otherdevices[...]" with "otherdevices_svalues[...]". Put a print(prev_distance_str) line after the string.match line to check if it actually gets a value different than "(1000 km)".

Nautilus wrote:Hmm, strange. The following has happened now a couple of times. If the phone is off (or unreachable) the dummy text sensor gets deleted. Cannot see any traces about this in the log either. How can this be - and has it happened to anyone else?

position_text = string.gsub(address, ', Finland', '') .. '<br>(' .. drivedistance .. ' / ' .. drivetime ..')<br><iframe width="300" height="260" frameborder="0" style="border:0" src="https://www.google.com/maps/embed/v1/place?key=APIKEY&q=' .. lat .. ',' .. lon .. '" allowfullscreen></iframe>'

mvzut wrote:

perese wrote:After a debugging and in same time do understand LUA and Domoticz event system and configuration I think I found a solution.

I cannot say why that needed for me but after changing

Line 54 from

Code: Select all

prev_distance_str = string.match(otherdevices['Position ' .. user], '%(.*%)') or '(1000 km)'

to

Code: Select all

prev_distance_str = string.match(otherdevices_idx['Position ' .. user], '%(.*%)') or '(1000 km)'

It suddenly worked. Maybe it is the version I'm at or something else, but the original code did not work.

Thanks lukev for your confirmation, helped a lot in my searches

The line you changed looks for text between parentheses in the text device named "Position <user>", where <user> is obviously replaced with your user name. If it can't find text between parentheses, it will return the value "(1000 km)". That way the next steps in the script will still function, even if the text device still contains the initial text "Hello World!", and since "prev_distance" is given such a high value, the later check

Code: Select all

if math.abs(prev_distance - distance) > radius then

is certainly true so that it will update the value of the text device.

Your change makes the script look for text between parentheses in the IDX of the device, which is a number, so it won't find such text. Therefore, in your new script "prev_distance_str" will always get the value"(1000 km)", so the text field will always be updated. If this causes things to start working for you that's great, but please note that it's maybe not ideal: The text field is now updated every minute, even if the value didn't change, which causes an unnecessarily large sensor log.

What could be the case is that you somehow can't read the values of your text device(s) with an "otherdevices[...]" command, I believe more people have reported this in this forum. Could be related to the Domoticz version. You could try to replace "otherdevices[...]" with "otherdevices_svalues[...]". Put a print(prev_distance_str) line after the string.match line to check if it actually gets a value different than "(1000 km)".

print(prev_distance_str)

prev_distance_str = string.match(otherdevices['Position ' .. user], '%(.*%)') or '(1000 km)'