Differences

This shows you the differences between two versions of the page.

--- remote [2017/01/18 21:06]
liz [Safe API]
+++ remote [2018/07/12 18:50] (current)
zavijava bad link
@@ Line 3: / Line 3: @@
 If you have not done it yet I would recommend using a remote controlled device linked to Jennifer! We hope to make it easy for anyone to easily link a device in. This will take time. The easiest way at the moment is an [[remote_audio|Audio controlled e-stim]] but that costs a lot. We hope to have a simple solution that anyone can put together or buy off the shelf for under £20 soon.
-If you are too scared to join Jennifer the device API is also available by getting an ID from [[https://play-link.com/devices.html]] Once you have linked your device to the API directly or via the controller program you can test it at [[https://play-link.com/jen/devices.php?id=XXXX]] either by directly triggering the device or a random chance of being triggered.
+If you are too scared to join Jennifer the device API is also available by getting an ID from [[https://play-link.com/devices.html]]
+Once you have linked your device to the API directly or via the controller program you can test it at [[https://play-link.com/jen/devices.php?id=XXXX]] either by directly triggering the device or a random chance of being triggered. This link also allows you to play with a keysafe or chastity device that are linked to the SafeAPI.
 ==== API ====
@@ Line 55: / Line 57: @@
 (For safes and chastity locks)
-Details for the safe API will appear here...
+Over the last year we have had several calls to extend the api to control a safe, lockbox or chastity device. To help prevent people from hacking their device the SafeAPI also has an additional key code system. An example use will be as follows:
-With this in mind I was thinking it is probably better to use a different API (web link) for the safe so we can basically make it however we like. my thoughts were along this line...
-Before the safe is locked it will ping the address /jen/safe.php?id=1XXX&cmd=status&locked=0
-This will return the line (where locked is the current safe status to check matches with Jen)
-opened
-Until the safe should be locked where it will return 2 line (The second being an upload code
+) Before the safe is locked it will ping the address https://play-link.com/jen/safe.php?id=1XXX&cmd=status&locked=0
+This will return the line (where locked is the current safe status to check matches with API):
+<code>
+unlocked
+</code>
+) Until the safe should be locked where it will return 2 line (The second being an unlock code)
+<code>
 close
 BKJG989hBJG
-This code is only given once (to save people grabbing it after the safe is locked) so any more calls with "status" will just return:
+</code>
+This code is only given **ONCE** (to save people grabbing it after the safe is locked) - **YOUR CODE WILL be DIFFERENT** to above! Currently mod have no way of resetting if you forget the code (will probably put an override in at some stage). Subsequent calls with "status" will just return:
-closed
+<code>
+locked
+</code>
 When Jennifer thinks the safe can be opened the next time(s) status is called it will return:
+<code>
 open
+</code>
 To complete the open the safe will then need to send:
+<code>
 /jen/safe.php?id=1XXX&cmd=open&code=BKJG989hBJG
+</code>
 if the code is correct it will return:
+<code>
+releasing
+</code>
+The safe/device can then unlock itself and is essentially back to the start position - if the wrong code is given it will flag as a tamper warning (and add time till unlock)
-opened
+Devices also have the command:
-The save can then unlock itself and is essentially back to the start position - if the wrong code is given it will flag as a tamper warning (and may add time till unlock?)
-Hope that makes sense, can also have the command:
+<code>
 /jen/safe.php?id=1XXX&cmd=tamper&text=motion
+</code>
 That would log suspected tamper attempts as would using the wrong key to unlock and the locked status not matching the server.
-Tamper feedback: (will add to time)
+Other tamper feedback available e.g. for devices that detect a pulse in the device: (will add to time)
-"/jen/safe.php?id=XXXXX&cmd=tamper&text=safteykey";
+<code>
+/jen/safe.php?id=1XXXXX&cmd=tamper&text=no pulse
+</code>
+=== Setting Times ===
+At the moment your lock status is not linked to your chastity status in Jennifer. To test your device or if you are not part of Jennifer you can lock your device for a specific time in days,hours,mins as following (if you don't specify a value for days, hours or mins they will default to 0):
+<code>
+/jen/safe.php?id=1XXX&cmd=lock&days=0&hours=3&mins=0&
+</code>
+Once we have some devices using this out there, your locked status will relate to your chastity status (if in Jennifer). But can message Liz for ways to test if developing a device. You can also use this API with the ID you get from devices https://play-link.com/devices.html if you don't want to be under Jennifer in Control.
+As well as physical devices it will also be easy to develop some software that takes a picture of a combination lock and only reveals it once the API says so.
 ==== Control ====
 Instead of having to workout how to use the API you can download a controller program.
-The controller program is available at [https://play-link.com/jen/controller.zip] you can download this and after updating the ini file will allow you to run commands to trigger devices. An example ini file would be as follows
+The controller program is available at [[https://play-link.com/jen/controller.zip]] you can download this and after updating the ini file will allow you to run commands to trigger devices. An example ini file would be as follows
 <code>

PlayLink

User Tools

Site Tools

Differences

Page Tools