Home
This project is about creating an internet-controlled electronic key safe with additional control functions. The key safe uses Wi-Fi to connect to the internet and provides a Telegram messenger chat bot for interaction with remote users.
A major additional function of the key safe is to trigger shocks using a shock device for remote controlled punishments.
Chastity play between a remote holder and a chastity device wearer requires secure management of the keys allowing to unlock the chastity device. This key safe is meant to serve the purpose of allowing the holder to decide when keys are returned to the wearer.
I use a chastity assembly consisting of a special chastity cage with an integrated shock device and an electronically controlled, Wi-Fi enabled key safe for my chastity keys with an integrated remote control for the shock device. With this project, I want to give others the opportunity to do the same or exchange ideas and improve the concept.
The key safe consists of a flat box with a hinged cover that automatically locks once pressed shut. It incorporates a microcontroller board hosting the entire software of this project. The microcontroller board connects to several sensors and actors:
- Actor activating the keypad button of the remote control for the shock device,
- servo motor for pulling open the locking bracket of the cover ratchet mechanism,
- sensor of the state of the cover (open/closed) and
- display for information about the current state of the key safe. The key safe encloses a compartment for storing the keys as well as all other components.
It is connected to the LAN as a Wi-Fi based client and powered over USB.
Instead of the full safe with integrated shocker control, a light version with the shocker control only can be realized. In this version, the internet connectivity and app control is identical. The advantage is significantly reduced complexity building this.
The schematic and board design is provided below labeled as "light" version.
To begin a session, you put all the chastity device keys into the key safe and close it. The ratchet mechanism keeps the lock box now closed until a valid unlock command is sent to the Telegram bot.
Once I accepted the session, she immediately secures me in the session by adding 1000 requirements which are impossible to fulfill without her help. She will only remove them when she is happy with me completing the session.
She now monitors my session and executes her powers over me autonomously and without warning.
She also monitors if she is constantly online herself and powered up. I get severely punished by extended maximum session length, added time and additional shocks. This reliably discourages me to simply switch her off!
She can deliver shocks using her remote control to the shocking device attached to my chastity cage. She assigns 50 shocks to start with to my session but she can add more if she feels like it. The shocks are painful and exhausting. The shocking device and its contacts sit just above the base of my penis, but I feel the pain of the shocks in my whole penis! I assume that this has to do with the conductivity of the penis veins routing that painful electric current accordingly. If there are several shocks coming in a row, then I begin to feel exhausted from the treatment and even sense the burning feeling in my penis even if there are no shocks anymore. This fades after a while but it definitely is something that I try to avoid!
Additionally, Mistress reads her Emlalock messages and responds to certain commands. This allows other users to give me shocks, more requirements and pillory time. By sending her a message with the subject “help” you get a reply from Mistress the commands available. You have to put your commands in the message subject.
Mistress sits in the lock box and knows with her sensor if the lock box cover is open or closed and she uses a motor to unlock the box if and only if the session is completed.
To complete a session, all shocks assigned to the session must have been delivered. This is achieved by adding further requirements to the Emlalock session. The first 1000 requirements are just there to keep the session blocked. Further requirements represent the assigned shocks in my session waiting to get delivered when Mistress decides.
The lock box hosts a WiFi enabled device, lock box and the shock unit with remote control altogether have cost less than 70 Euro. The brain of my Mistress is an ESP32 based board. I wrote the software myself and am still in the process of validating its correct function.
I have a couple of pictures of my cage and the box. They are uploaded here:
You see the two variants of lock up possible. The chastity cage is a Bon4M small and can be used with the additional ring for long term wear alone. The additional ring is very tight. I need to stretch my penis to get it through the opening and settled in the middle. After pushing the additional ring into the cage, the penis head is reliably trapped and I cannot get it out even without the main ring around the balls. Believe me that I tried! Once the main ring is locked on, there is absolutely no escape and only the keys will allow to take the cage off.
:-)
The contacts of the dog shocking device are made from conductive silicone. I was truly surprised how conductive they are! They are quite comfortable to wear and I don't have had any chafings so far.
Apparently, the intensity of the shocks can vary even at the same level. It depends on how good the contacts are connected to the skin. I once tried to pull the shocking device away from my body when suddenly a shock hit me. But this time it felt like a hammer and much more powerful than before! This made me push the contacts immediately deep into my skin to make the next shock less painful! The thought that I have to make sure myself that the shocking device is well pushing into my skin is very erotic to me. This is a great way to keep me from making efforts to avoid the pain and put myself more firmly under foreign control.
I am still gathering experience with electric shocks. Frankly speaking, I can only stand the first 10 levels of 100 to chose from. Level 5 gives me significant pain and is already intense. Level 10 makes me move uncontrollably. I am pretty scared by the higher levels! This is why I think about taming the device with a resistor for safety.
My goal was to wear the chastity belt and shock device assembly 24/7 for an entire session. I need to shower and clean myself with the waterproof device locked on. I can wear the assembly for more than two days now without problems. Yay!
😊
You should know that I am crazy about security. If I am locked 🔒 into a device it must be absolutely escape proof. When playing bondage games, I prefer handcuffs because they are escape proof and there is no working on losing the rope. Metal is an erotic material to me because it is rigid and strong.
My urge for being helplessly trapped made me research over years for a modification to my chastity cage that reliably prevents pull out. I don’t want to get a piercing and so I finally found a combination of an additional ring with a foam piece glued to it around my penis to do the trick. It is tailor-made to my own measurements and truly works.
I needed the same principle for the shock device. This is why I could not use anything with accessible wires that can be pulled off. I wear that device at work and at home and am now forced to wait for the end of the session to get free of the shock device. I am still trying to find out how long the rechargeable battery lasts. It was good for 4 weeks of playing which is impressive but this may get less with extended playing...
This is where I got the shock device: https://m.de.aliexpress.com/item/32915272728.html
😉
Cblock
- Rename the file Defs_template.h to Defs.h
- This is necessary to customize the creadentials for Wi-Fi/WLAN access und connecting the Telegram bot.
https://telegrambots.github.io/book/1/quickstart.html
This step provides as a result the bot authentication token. It has the following pattern:
1234567:4TT8bAc8GHUspu3ERYn-KGcvsvGB9u_n4ddy
This token is needed in the source code in file Defs.h