Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

y211ga Cameras. Was it a bad idea to update to 11.0.36.7_202202170022? Motion detection is completely silent. #388

Closed
dreimer1986 opened this issue Mar 6, 2022 · 24 comments

Comments

@dreimer1986
Copy link

I got two cams of the type y211ga. Before I installed the hack 0.2.0 I read through the discussions and as suggested there updated the cams with the official app first. Now I am at 11.0.36.7_202202170022 on both and have one problem. Motion detection is dead silent. I tried the official addin and MQTT and both say nothing when I hop around in my room. Detection is active in the official app, no paid service was chosen.

I made shots of the whole config. Maybe I am just too stupid: https://photos.app.goo.gl/Eur5NTmZDA2zyu1y7

Any idea?

@dreimer1986
Copy link
Author

backup QFUSY65V64.zip

Full Backup script made dump off the new firmware. Maybe useful? This one was made BEFORE hacking.

@dreimer1986
Copy link
Author

dreimer1986 commented Mar 9, 2022

A friend bought the same cameras and yet did not update or hack anything. This is the firmware in v9 range (9.0.36.02_202105081647 according to mtdblock3.bin/homever)
backup_v9.zip

@roleoroleo
Copy link
Owner

About the comparison between the 2 versions above, it's not clear.
For sure home and backup partitions are upgraded (mtdblock3 and mtdblock4 are different).
But the other partitions are also different, and I think that nobody would do the OTA update of the bootloader, kernel, etc...
I don't know...

@HolgerOnGithub
Copy link

Is there a possibility of downgrading the firmware? I also have the 11.0.36.7_202202170022 and no motion detection after the hack. Of course I only have a backup with version 11.0.36.7_202202170022, but here is a zip with version 9.0.36.02_202105081647. How do I get it into my YI 1080p Home IFUS?
Thanks in advance

@dreimer1986
Copy link
Author

There is the way the former unbrick hard way says... Soldering and Serial on UBoot. I have no clue if it's doable to use DD command via telnet to overwrite the partitions. Likely it will die while doing that. RAW Overwriting the OS from the OS sounds like a terrible idea... I think if you don't want to solder (I would prefer not to) we have to wait until it's supported. That's why I passed over my 11.x backup and the 9.x one from my friend.

@roleoroleo
Copy link
Owner

The soft unbrick is possible without soldering.
Check the wiki and this thread:
#305

@dreimer1986
Copy link
Author

Sure, but we have more than just partition4 aka Backup changed...

@roleoroleo
Copy link
Owner

You can use the soft method for all partition.
But avoid to use it for u-boot.

@dreimer1986
Copy link
Author

dreimer1986 commented Mar 18, 2022

Hmm, OK. Then I need to tinker a bit with that on weekend. I just read of the backup dump there, so I thought that's it. So it does use all dumps I give to it on recovery file creation?

EDIT: OK, nvm. I think I understand now. Will try tomorrow

EDIT2:
So I throw these files onto a SD, right?

backup_y211ga
env_y211ga
home_y211ga
kernel_y211ga
rootfs_y211ga

Preferred one at a time, but I dont know how to see when I can power off and replace the file. Thus these files at once should do the trick?

@roleoroleo
Copy link
Owner

You have to copy these files on your SD and reboot the cam (and wait 10 minutes).
Start with backup, then home.
Probably kernel and rootfs are not necessary.
Avoid env and uboot.

@dreimer1986
Copy link
Author

Alright, so one file only and then two 10 minute sessions for the two partitions. I will keep you updated. ^^

@dreimer1986
Copy link
Author

dreimer1986 commented Mar 18, 2022

So, good news. I did as you said, first backup, then home AND skipped the kernel image. Result:

image

The app now detects movements and sometimes even sounds, without the Kami Cloud paid for. But the sensors MQTT and official addin do not do much yet... Likely my MQTT settings are wrong? https://photos.app.goo.gl/Eur5NTmZDA2zyu1y7 Pics off the old non downgraded one and 0.2.0 Hack, but the settings I took 1:1 of these again. Do you see any stupidity here? Or is the kernel maybe still the problem here?

P.S: The 0.2.1 hack reduced the lag from RTSP down to less of a second :D

system

{
"HTTPD":"yes",
"TELNETD":"yes",
"SSHD":"no",
"FTPD":"no",
"BUSYBOX_FTPD":"no",
"DISABLE_CLOUD":"no",
"REC_WITHOUT_CLOUD":"no",
"MQTT":"yes",
"RTSP":"yes",
"RTSP_ALT":"no",
"RTSP_STREAM":"high",
"RTSP_AUDIO":"no",
"SPEAKER_AUDIO":"yes",
"SNAPSHOT":"yes",
"ONVIF":"no",
"ONVIF_WSDD":"yes",
"ONVIF_PROFILE":"high",
"ONVIF_NETIF":"wlan0",
"ONVIF_WM_SNAPSHOT":"yes",
"NTPD":"yes",
"NTP_SERVER":"pool.ntp.org",
"PROXYCHAINSNG":"no",
"SWAP_FILE":"no",
"RTSP_PORT":"554",
"ONVIF_PORT":"80",
"HTTPD_PORT":"8080",
"USERNAME":"",
"PASSWORD":"",
"TIMEZONE":"CET-1CEST,M3.5.0,M10.5.0/3",
"FREE_SPACE":"0",
"FTP_UPLOAD":"no",
"FTP_HOST":"",
"FTP_DIR":"",
"FTP_DIR_TREE":"no",
"FTP_USERNAME":"",
"FTP_PASSWORD":"",
"FTP_FILE_DELETE_AFTER_UPLOAD":"yes",
"SSH_PASSWORD":"",
"CRONTAB":"",
"HOSTNAME":"Cam-2",
"NULL":"NULL"
}

mqtt

{
"MQTT_IP":"192.168.181.42",
"MQTT_PORT":"1883",
"MQTT_CLIENT_ID":"Cam-2",
"MQTT_USER":"mqtt",
"MQTT_PASSWORD":"12341234",
"MQTT_PREFIX":"yicam-2",
"MQTT_PREFIX_CONFIG":"",
"TOPIC_BIRTH_WILL":"status",
"TOPIC_MOTION":"motion_detection",
"TOPIC_MOTION_IMAGE":"motion_detection_image",
"MOTION_IMAGE_DELAY":"0.5",
"TOPIC_MOTION_FILES":"motion_files",
"TOPIC_AI_HUMAN_DETECTION":"ai_human_detection",
"TOPIC_BABY_CRYING":"baby_crying",
"TOPIC_SOUND_DETECTION":"sound_detection",
"BIRTH_MSG":"online",
"WILL_MSG":"offline",
"MOTION_START_MSG":"motion_start",
"MOTION_STOP_MSG":"motion_stop",
"AI_HUMAN_DETECTION_START_MSG":"human_start",
"AI_HUMAN_DETECTION_STOP_MSG":"human_stop",
"BABY_CRYING_MSG":"crying",
"SOUND_DETECTION_MSG":"sound",
"MQTT_KEEPALIVE":"120",
"MQTT_QOS":"1",
"MQTT_RETAIN_BIRTH_WILL":"1",
"MQTT_RETAIN_MOTION":"0",
"MQTT_RETAIN_MOTION_IMAGE":"0",
"MQTT_RETAIN_MOTION_FILES":"0",
"MQTT_RETAIN_AI_HUMAN_DETECTION":"0",
"MQTT_RETAIN_BABY_CRYING":"0",
"MQTT_RETAIN_SOUND_DETECTION":"0",
"NULL":"NULL"
}

camera

{
"SWITCH_ON":"yes",
"SAVE_VIDEO_ON_MOTION":"yes",
"SENSITIVITY":"medium",
"AI_HUMAN_DETECTION":"no",
"FACE_DETECTION":"no",
"MOTION_TRACKING":"yes",
"SOUND_DETECTION":"yes",
"SOUND_SENSITIVITY":"80",
"LED":"no",
"ROTATE":"no",
"IR":"yes",
"NULL":"NULL"
}

@dreimer1986
Copy link
Author

OK, I disabled all the advanced advertisement and now... IT WORKS !!!!! No clue why, but it works great :D
OK, so I have to decide between motion and human detection, right?

Btw, the 11.X firmware claims to add animal, vehicle and improved person detection. (And Activity Zone for these and timestamps for the videos) Just to let you know that maybe the new firmware might be interesting to add somewhere in far future.

@roleoroleo
Copy link
Owner

OK, so I have to decide between motion and human detection, right?

Yes.

Btw, the 11.X firmware claims to add animal, vehicle and improved person detection. (And Activity Zone for these and timestamps for the videos) Just to let you know that maybe the new firmware might be interesting to add somewhere in far future.

I'm not sure but I think that new feature are "server side".

@dreimer1986
Copy link
Author

Alright. In this case. First: THANKS for help! All is fine now and this way to downgrade can be used to get back to a working state for others. I will close this one now.

@Minims
Copy link

Minims commented Aug 8, 2022

Alright. In this case. First: THANKS for help! All is fine now and this way to downgrade can be used to get back to a working state for others. I will close this one now.

@dreimer1986 How did you success a Revert to 9.0.36 ? I am trying to use the unbrick procedure, but nothing append, i am still in 11.xx version

@dreimer1986
Copy link
Author

dreimer1986 commented Aug 8, 2022

Of course you are. You need a v9 backup of the same camera type and flash the partitions off it back on yours. That's what I did.
The backup to use here is in the report, too.

@Minims
Copy link

Minims commented Aug 8, 2022

@dreimer1986 I have the backup v9 on my own camera.
I have build the files via the unblock Readme.
I have :

backup_y211ga.gz
home_y211ga.gz
rootfs_y211ga.gz

Then I have :

gunzip backup_y211ga.gz
gunzip home_y211ga.gz
gunzip rootfs_y211ga.gz

Format SDCARD to FAT32
Paste backup_y211ga, and the start camera.
Led blinks one time in yellow and then it start normally after 15sec. (Longer than normal boot)

Once done, I make the same with home & rootfs. But I am still in v11. I tried with the backup file on this thread, but same behavior. I might miss something :-/

@dreimer1986
Copy link
Author

dreimer1986 commented Aug 8, 2022

I used the WIndows tool found there a bit hidden (#305 (comment)) for making the files and I even skipped rootfs. Only backup and home on my cams was reverted. All fine here. And ALWAYS do ONE AT A TIME. Not all of them thrown on SD and boom!. DO one, WAIT 10 min!, remove it, do next AND WAIT AGAIN!

@meluvalli
Copy link

meluvalli commented Aug 9, 2022

@dreimer1986 - So to confirm, you have NOTHING on the flash drive except the 1 file? Example: backup_y211ga? How does the camera know to pick up the file and process it?

@Minims
Copy link

Minims commented Aug 9, 2022

I have finally be able to revert.

  1. I have format SDCARD via FAT32 with Pi Imager. (If I format with the Yi Home App, it fails)
  2. I need to use the file files from the backup_v9, use backup and then home file. (revert works)
  3. I made the same with my own backup file, I have a newer 9.0.36 than the one on backup_v9
  4. I reapplied the hack.
  5. All is OK now.
    It was a long journey

@meluvalli
Copy link

@Minims
Hmm... I must be doing something wrong :(

I downloaded the v9 zip file you posted in #388 (comment).
I downloaded the mkimg file from #305 (comment)
I then ran the command in windows:

mkimg.EXE -A arm -O linux -T filesystem -C none -a 0x0 -e 0x0 -n "xiaoyi-backup" -d mtdblock4.bin backup_y211ga

I used Pi Imager as you did just incase to Format the SD Card FAT32.
I then copied the backup_y211ga to the root of the SD card. This is the ONLY file on the SD camera.
I inserted it into the camera, plugged it in and waited 10 minutes! (Yes, I set a timer)...
Then unplugged it.
I then copied the home_y211ga file and deleted the the backup_y211ga file to the SD card. Again, only left with ONE file on SD Card called home_y211ga
I inserted it into the camera, then booted it. Waited 10 minutes! (Yes, I set a timer again!)...
Then unplugged it.
Removed the SD Card, plugged the camera in.

YI Home still says I'm on version 11. I don't think it did ANYTHING! Am I missing something?

@Minims
Copy link

Minims commented Aug 9, 2022

@meluvalli does the yellow led has blink one time just after the boot ?

  • I have remove the camera from Yi Home App
  • I have clean the application cache too (try this every time you update a file backup, home or rootfs)
  • Then I have rest the camera via reset button and had it again.

@meluvalli
Copy link

Got it. I think reset was the key :)

Thank you!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants