[Solved] Dummy presence device for other purpose, how to?

---

I like to have a device that acts like a presence device showing a dot on or off.
The on status is when a certain proces is running and the off status is when that proces is not running.

Now I have a device that shows 1 or 0 indicating whether the proces is running or not.

I read something about a dummy precence device but I can’t find how to create one.

Is the way I want it possible?

Thanks…

@lschip See http://forum.pimatic.org/topic/455/dummy-present-absent-device/7

{
      "id": "runner1",
      "class": "DummyPresenceSensor",
      "name": "Apache"
 }

# In bash you can type the following. replace XXX with your pimatic password
curl admin:XXX@localhost/api/device/runner1/changePresenceTo?presence=true >/dev/null 2>&1

I have read the tread: “forum.pimatic.org/topic/455/dummy-present-absent-device/7”

But I don’t see how to configure this dummy device.
Your example shows id, class and name but I don’t see how the outcome of the bash script leads to a chacge of the dummy device.
Is it like?:
{
“id”: “IpCamrecording”,
“class”: “DummyPresenceSensor”,
“name”: “IpCamrecording”,
“command”: ps -ef | grep openRTSP | grep -v grep | wc -l
}

@lschip said:

“command”: ps -ef | grep openRTSP | grep -v grep | wc -l

Ah, ok. I got you wrong. I thought you have an external shell script to start and stop a service and you want to propagate the state to pimatic.

What you are looking for is the ShellSensor. See the last example at http://www.pimatic.org/docs/pimatic-shell-execute/

EDIT: Well, you’ll need both. The ShellSensor (or ShellSwitch) to get the Status of your service and map that to an variable. A DummyPresence device to dsplay the presence status. A Rule to map the variable to the DummayPresence state. Thinking about this it would be nice to extend pimatic-shell-execute with a ShellPresenceSensor.

Yes but I did use shellsensor but then I don’t know to get a dot.
Now I get 1 or 0:
{
“id”: “IpcamAchter”,
“name”: “IpcamAchter”,
“class”: “ShellSensor”,
“attributeName”: “IpCamAchter”,
“attributeType”: “number”,
“attributeUnit”: “Aan-uit”,
“command”: “ps -ef | grep openRTSP | grep -v grep | wc -l”
},

Maybe it is the attributetype?

@lschip See my “EDIT” on the previous post. I am happy to draft an extension for a “ShellPresenceSensor” as part of pimatic-shell-execute. Stay tuned.

Ok, thats clear. Thanks.

Can’t wait for a more direct solution

This item can be stated as Solved.

Sorry, still a problem:

I now have this rule for the dummerpresencesensor:

$IpcamOpname.IpCamOpname > 0 then set presence of IpCamOpnameDot present

So now when $IpcamOpname.IpCamOpname gets > 0 IpCamOpnameDot becomes present but only for a few seconds. Then it returns to absend (I have no other rules for this device and $IpcamOpname.IpCamOpname is still >0).

How can I solve this?

Thanks…

have you disabled the auto reset?

“autoReset”: false,

No, didn’t know, that helps

Thanks!

@lschip said:

Can’t wait for a more direct solution

Oh, this must be a serious business …

I have implemented it anyway and created a PR - https://github.com/pimatic/pimatic-shell-execute/pull/6

EDIT: btw, you can also check for openRTSP as follows

pgrep openRTSP  >/dev/null && echo 1 || echo 0

@lschip said:

Can’t wait for a more direct solution

Just to let you know. A new version of pimatic-shell-execute has been released which contains the ShellPresenceSensor

Great, thanks, I’ll give it a try!

This little change is very nice!

now i can have an presence Sensor which wakes my iPhone all 5 minutes off the no-wifi-sleep and then pings it:

{
     "id": "Joedummy",
     "name": "Joe Anwesend",
     "class": "ShellPresenceSensor",
     "command": "sudo hping3 -2 -c 3 -p 5353 192.168.1.11 >/dev/null 2>&1 || true; 
              sleep 5;  ping -c 1 -w 5 192.168.1.11 >/dev/null && echo 1 || echo 0",
     "interval": 300000,
     "autoReset": false
}

@mwittig Having some Issues. Is the <<“autoReset”: false >> and << "“interval”: 5000>> already implemented?

interval in ms is right, he?

@thymian The interval property is supported, value is milliseconds. However, I haven’t implemented autoReset.

@thymian i have tried your example with the shell presence and the hping3, but sometimes it shows abset, but the phone is still home. Any ideas? Does your example work for you?

As far as I know phones are unreachable sporadically if the phone system switches to deep sleep mode to extend battery life.

Hey, i know that, but the hping command should wake it up, then wait 5 sec. And then ping it. It should work, but sporadically i get 0.

@p4co86 May be some pings are not getting through. Do you see packet loss reported by hping3? Anyhow, I don’t think it is an issue with the ShellPresenceSensor. Can you please test you hping3 command/script independently from pimatic! For example, call in while loop with a sleep command and write the status to a file. Thanks

Background info for less enlightened readers, see https://github.com/pimatic/pimatic/issues/209

I get this:

root@raspberrypi:~# sudo hping3 -2 -c 3 192.168.0.21
HPING 192.168.0.21 (lo 192.168.0.21): udp mode set, 28 headers + 0 data bytes

--- 192.168.0.21 hping statistic ---
3 packets transmitted, 0 packets received, 100% packet loss
round-trip min/avg/max = 0.0/0.0/0.0 ms
root@raspberrypi:~#