yi-hack-Allwinner-v2 is a modification of the firmware for the Allwinner-based Yi Camera platform.
Table of Contents
- Table of Contents
- Installation
- Contributing
- Features
- Performance
- Supported cameras
- Is my cam supported?
- Home Assistant integration
- Build your own firmware
- Unbricking
- License
- Disclaimer
- Donation
Installation
Backup
It's not easy to brick the cam but it can happen. So please, make your backup copy: https://github.com/roleoroleo/yi-hack-Allwinner-v2/wiki/Dump-your-backup-firmware-(SD-card)
Anyway, the hack procedure will create a backup for you.
Install Procedure
If you want to use the original Yi app, please install it and complete the pairing process before installing the hack.
Otherwise, follow this wiki: https://github.com/roleoroleo/yi-hack-Allwinner-v2/wiki/Install-the-hack-without-the-Yi-app
- Format an SD Card as FAT32. It's recommended to format the card in the camera using the camera's native format function. If the card is already formatted, remove all the files.
- Download the latest release from the Releases page.
- Extract the contents of the archive to the root of your SD card. Your card should appear with this structure:
|-- Factory/
|-- yi-hack/
|-- lower_half_init.sh
- Insert the SD Card and reboot the camera
- Wait a minute for the camera to update.
- Check the hack opening the web interface http://IP-CAM (where IP-CAM is the IP address of the cam assigned by your router).
- Don't remove the microSD card (yes this hack requires a dedicated microSD card).
- Check the FAQ if you have a problem: https://github.com/roleoroleo/yi-hack-Allwinner-v2/wiki/FAQ
Online Update Procedure
- Go to the "Maintenance" web page
- Check if a new release is available
- Click "Upgrade Firmware"
- Wait for cam reboot
Optional Utilities
Several optional untilies are avaiable, some supporting experimental features like text-to-speech.
Contributing and Bug Reports
See CONTRIBUTING
Features
This custom firmware contains features replicated from the yi-hack-MStar project and similar to the yi-hack-v4 project.
- FEATURES
- RTSP server - allows a RTSP stream of the video (high and/or low resolution) and audio (thanks to @PieVo for the work on MStar platform).
- rtsp://IP-CAM/ch0_0.h264 (high res)
- rtsp://IP-CAM/ch0_1.h264 (low res)
- rtsp://IP-CAM/ch0_2.h264 (only audio)
- ONVIF server (with support for h264 stream, snapshot, ptz, presets and WS-Discovery) - standardized interfaces for IP cameras.
- Snapshot service - allows to get a jpg with a web request.
- http://IP-CAM/cgi-bin/snapshot.sh?res=low&watermark=yes (select resolution: low or high, and watermark: yes or no)
- http://IP-CAM/cgi-bin/snapshot.sh (default high without watermark)
- Timelapse feature
- MQTT - Motion detection and baby crying detection through mqtt protocol.
- Web server - web configuration interface.
- SSH server - dropbear.
- Telnet server - busybox.
- FTP server.
- FTP push: export mp4 video to an FTP server (thanks to @Catfriend1).
- Authentication for HTTP, RTSP and ONVIF server.
- Proxychains-ng - Disabled by default. Useful if the camera is region locked.
- The possibility to change some camera settings (copied from official app):
- camera on/off
- video saving mode
- detection sensitivity
- motion detections (it depends on your cam and your plan)
- baby crying detection
- status led
- ir led
- rotate
- ...
- Management of motion detect events and videos through a web page.
- View recorded video through a web page (thanks to @BenjaminFaal).
- PTZ support through a web page (if the cam supports it).
- PTZ presets.
- The possibility to disable all the cloud features.
- Swap File on SD.
- Online firmware upgrade.
- Load/save/reset configuration.
- RTSP server - allows a RTSP stream of the video (high and/or low resolution) and audio (thanks to @PieVo for the work on MStar platform).
Performance
The performance of the cam is not so good (CPU, RAM, etc...). Low ram is the bigger problem. If you enable all the services you may have some problems. For example, enabling snapshots may cause frequent reboots. So, enable swap file even if this will waste the sd
Supported cameras
Currently this project supports only the following cameras:
Camera | Firmware | File prefix | Remarks |
---|---|---|---|
Yi 1080p Home BFUS | 9.0.19* | y21ga | - |
Yi 1080p Home BFUS | 12.1.19* | y21ga | - |
Yi 1080p Home IFUS | 9.0.19* | y21ga | - |
Yi 1080p Home IFUS | 12.1.19* | y21ga | - |
Yi 1080p Home IFUS | 9.0.36* | y211ga | - |
Yi 1080p Home IFUS | 12.0.37* | y211ga | - |
Yi 1080p Home QFUS | 9.0.36* | y211ga | - |
Yi 1080p Home QFUS | 12.0.37* | y211ga | - |
Yi 1080p Home RFUS | 9.0.36* | y211ga | - |
Yi 1080p Home RFUS | 12.0.37* | y211ga | - |
Yi 1080p Home RFUS | 9.0.35* | y291ga | - |
Yi 1080p Home RFUS | 12.0.35* | y291ga | - |
Yi Outdoor 1080p IFUS | 9.0.26* | h30ga | - |
Yi Outdoor 1080p IFUS | 11.1.26* | h30ga | - |
Yi Outdoor 1080p RFUS | 9.0.26* | h30ga | - |
Yi Outdoor 1080p RFUS | 11.1.26* | h30ga | - |
Yi 1080p Dome *FUS | 9.0.05* | r30gb | beta version (check this issue #484) |
Yi 1080p Dome *FUS | 12.1.05* | r30gb | beta version (check this issue #484) |
Yi Dome Camera U BFUS (Full HD) | 9.0.22* | h52ga | - |
Yi Dome Camera U BFUS (3K) | 9.0.21* | h51ga | - |
Yi Dome U Pro 2K LFUS | 9.0.27* | h60ga | - |
Yi Outdoor 1080p QFUS | 9.0.45* | r40ga | - |
Yi Home Y4 IFCN | 9.0.09* | y29ga | - |
Yi Dome Guard QFUS | 9.0.46* | r35gb | - |
Yi Dome Guard QFUS | 12.1.47* | r35gb | - |
Yi Dome Guard YRS | 9.0.46* | r35gb | - |
Yi Dome Guard YRS | 12.1.47* | r35gb | - |
Kami mini home IFUS | 9.0.20* | y28ga | - |
MIBAO G1 1296p dome | 9.0.04* | qg311r | - |
BLITZWOLF BW-YIC1 | 9.0.41* | b091qp | - |
ESCAM PT202 | 9.0.41* | b091qp | #624 (reply in thread) |
YS-QC-02 | 9.0.41* | b091qp | roleoroleo/yi-hack_ha_integration#84 |
Flood Light Camera Outdoor L850Y-US | 9.0.41* | b091qp | - |
Tovendor Mini Smart Home Camera | 9.0.41* | b091qp | - |
USE AT YOUR OWN RISK.
Do not try to use a fw on an unlisted model
Do not try to force the fw loading renaming the files
Is my cam supported?
If you want to know if your cam is supported, please check the serial number (first 4 letters) and the firmware version. If both numbers appear in the same row in the table above, your cam is supported. If not, check the other projects related to Yi cams:
- https://github.com/TheCrypt0/yi-hack-v4 and previous
- https://github.com/alienatedsec/yi-hack-v5
- https://github.com/roleoroleo/yi-hack-MStar
- https://github.com/roleoroleo/yi-hack-Allwinner
Home Assistant integration
Are you using Home Assistant? Do you want to integrate your cam? Try these custom integrations:
You can also use the web services in Home Assistant -- here's one way to do that. (This example requires the nanotts optional utility to be installed on the camera.) Set up a rest_command in your configuration.yaml to call one of the web services.
rest_command:
camera_announce:
url: http://[camera address]/cgi-bin/speak.sh?lang={{language}}&voldb={{volume}}
method: POST
payload: "{{message}}"
Create an automation and use yaml in the action to send data to the web service.
service: rest_command.camera_announce
data:
language: en-US
message: "All your base are belong to us."
volume: '-8'
Build your own firmware
If you want to build your own firmware, clone this git and compile using a linux machine. Quick explanation:
- Download and install the SDK as described here
- Clone this git:
git clone https://github.com/roleoroleo/yi-hack-Allwinner-v2
- Init modules:
git submodule update --init
- Compile:
./scripts/compile.sh
- Pack the firmware:
./scripts/pack_fw.all.sh
Instead of installing the SDK on your host machine, there's also the option to use a devcontainer
from within Visual Studio Code. Please ensure you have the Remote - Containers
extension installed for this to work.
Unbricking
If your camera doesn't start, no panic. This hack is not a permanent change, remove your SD card and the cam will come back to the original state. If the camera still won't start, try the "Unbrick the cam" procedure https://github.com/roleoroleo/yi-hack-Allwinner-v2/wiki/Unbrick-the-cam.
License
DISCLAIMER
NOBODY BUT YOU IS RESPONSIBLE FOR ANY USE OR DAMAGE THIS SOFTWARE MAY CAUSE. THIS IS INTENDED FOR EDUCATIONAL PURPOSES ONLY. USE AT YOUR OWN RISK.