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.

Sign up for GitHub

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

Jump to bottom

Cam blocked #280

Closed
mcgnai opened this issue Nov 23, 2020 · 24 comments
Closed

Cam blocked #280

mcgnai opened this issue Nov 23, 2020 · 24 comments

Comments

@mcgnai
Copy link

mcgnai commented Nov 23, 2020

Hi, I have 8 Y3 cams and it has been running for over 5 months with no problems. ( Now with fw 0.3.7) One day I realized that one of these was no longer sending the video and I realized that it was constantly in reset (it turned on, it ticked and then the yellow led started to flash and then it stayed again). I took it. I removed the SD card and reset it using the reset button. I started the procedure to add a new cam on the "YI Home" app from the beginning but it was not successful. I also tried to flash the firmware again (0.3.6) but it does not read the sd because the cam must first be initialized with the YI Home app. I wrote to the supplier who replaced the cam. A month has passed and the same problem has occurred. Can you help me solve?
@roleoroleo
Copy link
Owner

Try to restore the original firmware and check if it works.

@mcgnai
Copy link
Author

mcgnai commented Nov 24, 2020

Thanks for the reply. Can you help me get the original firmware back? where can i download the original fw? what is the procedure? Thanks

@roleoroleo
Copy link
Owner

What's your model suffix?

@mcgnai
Copy link
Author

mcgnai commented Nov 24, 2020 via email

@roleoroleo
Copy link
Owner

I need to know if your cam is y203c, h201c, etc...

@janekjelonek
Copy link

janekjelonek commented Nov 25, 2020 •
edited
Loading

Hi, i believe I've just experienced the same issue. I was on 0.3.6 y203c (Yi Home 1080p / 9FUSY21ZZS). It happened excactly the same way, out of a sudden after a months of service, the cam led turned yellow. I removed SD and performed camera reset. Then I tried to pair it with YiHome App. The pairing process fails after the cam announces 'Wifi Connected'. The cam is indeed connected to wifi but pairing process fails.
What is interesting, if I input SD card with yi-hack and perform hardware reset via button (version 0.3.6 or 0.3.7) it boots up to yi-hack and yi-hack works fine. But the state is somewhat like this:

  • cam is on
  • wifi connected
  • yi hack working,
  • unable to pair with yi home app,
  • cam not visible in app,

in this scenario, after power loss the cam goes back to 'welcome ti yi home camera, waiting to connect...' message as it looses wifi config and credentials. If i want to use it again, I need to perform a reset and start unsuccessful pairing process with yi home app till it connects to wifi.

Saving wifi settings for good would probably give the cam another life as you can still use it without Yi Home App.
Yi Customer Service (helpdesk) doesn't know how to solve pairing problems and offers cam replacement.
Regards, Janek

edit 1
// I decided to keep 'broken' cam so i can do more testing if needed.

edit2
I wasn't aware of roleoroleo's guide 'Change WiFi credentials' - i will give it a try and post back the results.

@mcgnai
Copy link
Author

mcgnai commented Nov 25, 2020 via email

@roleoroleo
Copy link
Owner

I think your problem could be similar to this one: #226
When the cam is "blocked" please check the free space.
But if you upload a different hack version (or restore the original fw) the cam MUST start to work again.

@mcgnai
Copy link
Author

mcgnai commented Nov 25, 2020 via email

@roleoroleo
Copy link
Owner

Try to change the sd card.
The upgrade procedure is made by the bootloader, before the setup procedure could start.

@mcgnai
Copy link
Author

mcgnai commented Nov 25, 2020 via email

@mcgnai
Copy link
Author

mcgnai commented Nov 25, 2020 via email

@mcgnai
Copy link
Author

mcgnai commented Nov 25, 2020 via email •
edited
Loading

@mcgnai
Copy link
Author

mcgnai commented Nov 26, 2020

I need to know if your cam is y203c, h201c, etc...

ok, the cam model is y25 . I have already tried to flash the cam with the
version. y25_0.3.6 but when I insert the sd to start the cam, this does not
start the firmware update but begins with the setup procedure to be done
with the YI Home app that does not go well.
Thank's

@roleoroleo
Copy link
Owner

@mcgnai
Here it is:
y25.tar.gz
But I think this will not solve your problem.

@denven
Copy link
Contributor

denven commented Nov 30, 2020 •
edited
Loading

Device:

  • Yi Dome 1080p
  • BFUS**
  • Firmware: 4.6.0.0A 201908271549 ---> this hack v0.3.8

I have the same issue since last night, the problem came after I fixed a google drive uploading issue:

  • My video files failed to upload to google drive again(I used another gdrive hack), at first I thought I didn't solve the issue, however, when I use my own computer(Linux) and use the same script to upload video files, it works.
  • So I tried to reconfigure google API settings, but I found curl not working, I can ping google DNS IP from the SSH console, but the camera cannot resolve a name service, and there is no /etc/resolv.conf file for me to set name service manually.
  • Then I reset my camera and hope I could get a brand new environment, however, I can never connect my phone App to the camera again, the App cannot pair with the camera.
  • Currently, the camera cannot be connected and managed from the Yi App. I checked the video files in record directory, it stopped to record since the time when network broke.
  • And I cannot re-install this hack from the SD card.

I thought why the Yi App cannot pair with the camera is due to the camer is:

  • kind of offline because of camera network issue (cannot resolve name service)
  • or blocked

Fix:

  • The way I think it may fix this issue: downgrade the firmware to the official one, but I am not able to find a matched new version.
  • After I read @roleoroleo mentioned issue in this topic, I got my camera working again by downgrade this hack to 0.3.7, then I upgrade it to the latest again.

Note: Use another version of this hack to resuce your camera from blocking or pairing failure issue.

Thus, for my case, it's not a true block issue from Yi official.

I am not sure if it is caused by a full SD space status, as I cleaned my sd card after reset. But I found this from the log file in log directory in sd card when it cannot be paired, path is /log/bind-timeout.tar.gz --extracted to-> **/log/tmp/sd/bind_timeout/df.txt**

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/block/mtdblock3     12480     10976      1504  88% /home
Filesystem           1K-blocks      Used Available Use% Mounted on
**/dev/root              1920      1904        16  99% /**

Although my sd has been already cleaned up, but I had a rootfs /dev/root 99% space status, this may be the reason of this issue.
It results in some file loss, e.g. /etc/resolv.conf and makes device offline(fail to do the DNS resolution) to pair with phone application which not using pure IP address.

Hope it will be fixed in the next version.

@roleoroleo
Copy link
Owner

I don't know if I can fix this problem.
I already removed all unnecessary applets from busybox and I can't increase the free space on /.

@vkoskela
Copy link

vkoskela commented Dec 2, 2020

I had also the app pairing problem and downgrade to 0.3.7 worked for me 👍

@roleoroleo
Copy link
Owner

I moved all variable files to /home partition.
I think it should fix the problem.
Try 0.3.9

@denven
Copy link
Contributor

denven commented Dec 4, 2020 •
edited
Loading

I moved all variable files to /home partition.
I think it should fix the problem.
Try 0.3.9

/home # df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 1.9M      1.9M     16.0K  99% /
tmpfs                    29.7M      1.8M     27.9M   6% /dev
/dev/block/mtdblock3     12.2M     10.8M      1.4M  89% /home
tmpfs                    32.0M    100.0K     31.9M   0% /tmp
/dev/block/mmcblk0p1     29.7G     47.9M     29.7G   0% /tmp/sd

Thanks, I just upgraded the new version. The /dev/root free space is 16KB, is this right?
Before my upgrading, the free space is only 4K left after 3 days running.

@roleoroleo
Copy link
Owner

Free space depends on the specific model (suffix).
In my case (y203c) is about 30KB.
But I moved to /home all variable files:

  • /etc/TZ
  • /etc/hostname
  • /etc/passwd

And I removed back.bin from the original fw.

@roleoroleo
Copy link
Owner

Could you send me a feedback about this issue?
Is it still present in version 0.3.9?

@roleoroleo
Copy link
Owner

News about this issue?

@Rh9no
Copy link

Rh9no commented Mar 18, 2021 •
edited
Loading

Just wanted to say I have just encountered a similar issue and downgrading from 0.3.9 to 0.3.7 and then back to 0.3.9 fixed it for now. (Yi 1080p Dome BFUS h201c). Was running 0.3.9 since December 2020 and only encountered issue since yesterday.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@Rh9no @denven @vkoskela @mcgnai @roleoroleo @janekjelonek