IFUS y211ga home: hack version 0.2.5 and fw base 12 (problem)

[Giuserver]

Hello!
My camera IFUSY65****** HOME 1080p (model y21ga) rebooting it self continuously after upgrade to version 0.2.5. and FW Base 12.0.19***

@roleoroleo any idea's or it's possible back to 9.0.19* ?

Thanks,
Giuseppe

[roleoroleo]

About reboot check the faq page in the wiki. Maybe you can fix.
Or you can downgrade to the previous fw following the unbrick guide.

[Giuserver]

if I format the SD and reinsert into camera, work fine. Also, i can enter into camera with telnet port (23), maybe can help?

[roleoroleo]

At the moment y21ga with 12.x is not supported.
I don't know how to fix the problem.

[roleoroleo]

Try to remove the file /tmp/sd/yi-hack/bin/cloudAPI_real
And overwrite /tmp/sd/yi-hack/bin/mqttv4 with this one:
mqttv4.gz

[Giuserver]

Try to remove the file /tmp/sd/yi-hack/bin/cloudAPI_real And overwrite /tmp/sd/yi-hack/bin/mqttv4 with this one: mqttv4.gz

First of all, i got the wrong version. This camera is y211 (always IFUS) really sorry.
Anyway, i tried:

1. formatted the SD
2. extracted and copied in the SD the version 0.2.5 y211ga. Still work for a few seconds, after that starting rebooting
3. deleted the file /tmp/sd/yi-hack/bin/cloudAPI_real and overwrite the mqttv4 file whit yours in /tmp/sd/yi-hack/bin/mqttv4
   The camera continue with rebooting each 10 seconds approximately.

Good for you @lohacker84

Really thanks for your help @roleoroleo and sorry again.
the actually (really bad) base version is: 12.0.37.0_202211241030

[lohacker84]

I used your files that I will never stop thanking you for this and I went back to 9.0.19.02_202007141512 because it couldn't be seen well at night. it all worked perfectly! Thank you so much for all the work you do for us! you are great!

[roleoroleo]

I will release a new beta version to support new 12 firmwares.

[Giuserver]

So,
I found the base version 11.0.36.7_202202170022 on the kami site.
I downloaded the original firmware from https://s3.us-west-1.wasabisys.com/firmware-release/y211ga/11.0.36.7_202202170022/one_y211ga.bin
from "original" link https://kamihome.com/firmware-release/y211ga/11.0.36.7_202202170022/one_y211ga.bin

formatted SD.
copy one_y211ga.bin into SD
inserted SD into camera
wait 3 minutes...Firmware 11 recoverd.
formatted SD
installed 0.25 hack..Perfect.
So, now I have base version: 11.0.36.7_202202170022
hack: 0.25

(of course no motion detection for Yi/Kami app but I don't care anymore from that apps..) anyway...i recover all services (thank to your hack) BUT:

the motion detection doesn't work correctly. This output from motion detection (I get it repeatedly new connection from camera)

1672247284: New connection from 192.168.1.6:52100 on port 1883.
1672247284: New client connected from 192.168.1.6:52100 as camera2 (p2, c1, k120).
1672247285: New connection from 192.168.1.6:52102 on port 1883.
1672247285: New connection from 192.168.1.6:52104 on port 1883.
1672247285: New client connected from 192.168.1.6:52102 as camera2_c (p2, c1, k15).
1672247285: Client camera2 already connected, closing old connection.
1672247285: New client connected from 192.168.1.6:52104 as camera2 (p2, c1, k120).
1672247285: Client camera2_c closed its connection.
1672247286: New connection from 192.168.1.6:52110 on port 1883.
1672247286: Client camera2 already connected, closing old connection.
1672247286: New client connected from 192.168.1.6:52110 as camera2 (p2, c1, k120).

Of course, the best would be recover 9.0.36 version but I can't find file .bin on Internet

Also, I noticed that .mp4 files recording like
/record/2022Y12M28D17H/E114M18S42.mp4
The time zone seems wrong and the files are not 60 seconds long but always minus (between 45 and 60 seconds).
(I am in Rome, so i set +1 just in App, no time zone set in hack page) If I change the time zone in App (for example universal time zone) the file change name like: /record/2022Y12M28D17H/E015M18S47.mp4 But the problem I described before still remain

Giuseppe
and THANKS

[roleoroleo]

Motion detection problem is a know issue of the fw 11.x
I think I will not support this version because it's a long task and version 12 is already released.
If you want to try a new beta for fw 12 please let me know.
Motion detection should be fixed, about time zone I need to check.

[Giuserver]

@roleoroleo yes, sendme beta version, I'll try just right now

[roleoroleo]

This is the official update to fw 12.
12.0.37.0_202211241030home_y211gam.zip

This is the last beta.
y211ga_0.2.5.tar.gz

[roleoroleo]

Please, try again with this new file:
y211ga_0.2.5.tar.gz

[Giuserver]

So, i restart all procedures.
reset camera
Formatted sd
copy inside camera the new firmware.
Reboot and boom, everything come back normal.
Seems all services restored normally: rtsp, snapshot, motion detections ecc.

Bro you're on fire 🔥

I will update you. I will do many tests for you.

Thank you

[MaryCam1]

This is the official update to fw 12. 12.0.37.0_202211241030home_y211gam.zip

This is the last beta. y211ga_0.2.5.tar.gz

works also for y21ga ?

[Giuserver]

This is the official update to fw 12. 12.0.37.0_202211241030home_y211gam.zip
This is the last beta. y211ga_0.2.5.tar.gz

works also for y21ga ?

NO. but you come back to 9.0, just follow this comment #547 (comment)
After that, download the original hack 0.2.5 from https://github.com/roleoroleo/yi-hack-Allwinner-v2/releases

[MaryCam1]

This is the official update to fw 12. 12.0.37.0_202211241030home_y211gam.zip
This is the last beta. y211ga_0.2.5.tar.gz

works also for y21ga ?

NO. but you come back to 9.0, just follow this comment #547 (comment) After that, download the original hack 0.2.5 from https://github.com/roleoroleo/yi-hack-Allwinner-v2/releases

Thnx to Giuserver

@roleoroleo; will there also be an update to version 12 / y21ga in the future without having to downgrade to 9?

[evider2002]

@roleoroleo I tested your last version of the hack on fw 12, and indeed you miraculously fixed both the boot loop and no motion issues!!!
There is though one more tweak necessary to make it perfect.
In the oem fw of 9, 11 and 12, you need to choose either motion or AI, you cant have both, its either or.
For example, in 9 when you turn on person detection, you are turning off any other motion, so if there is a non person motion, it won't come through. The same is with 12, when you turn on AI (person, vehicle, animal) you are turning off all the remaining non AI motion. This is a problem, because I want the benefit of AI but not at the expense of losing all the remaining non AI motion.
This was not an issue with the hack on 9, somehow the way you had it set up, I was getting person AI alerts plus all the remaining non person alerts were coming through as "motion tracking triggered" alerts. It was the best of both worlds, I was able to have the cake and eat it.
Please reimplement this into the 12 hack. Perhaps you can add an option to Motion Detection (0.0.0.0:8080/?page=camera_settings) something like "Motion + AI". Or maybe you can put back the "Motion Tracking sensor" option, so that I can still get motion alerts that way.

Thank you!

[evider2002]

I spend some more time testing, and I think I can explain how I was getting simultaneously AI and motion alerts with the hack on fw 9.

The alert name for regular motion is called "motion detected".
There is another similar motion called "motion tracking triggered", this is the motion alert intended for the YI Dome Camera, which can move and follow the motion.
When AI is turned on (either "person" in 9, or "person, animal, vehicle" in 12) then it only shuts off "motion detected" alerts but it does not shut off "motion tracking triggered" alerts.
The unit I have is not the Yi Dome, what I have is the Yi home 1080p ai+.
However, in the public released hack for 9, you kept available the "motion tracking triggered" option.
So even though its not an official alert available for my unit, but since you included it in the hack, I selected it anyway.
By selecting it, I am able to get motion alerts (motion tracking triggered) even when AI is turned on.

The problem is, that on the beta version for 12, you took out the "motion tracking triggered" option.
Please put that option back in.
Or maybe even better, you can figure out how to get "motion detected" alerts to work together with AI, just like "motion tracking triggered" works with AI.

As it stands now, I prefer 9 - motion with only person AI, rather than 12 - no motion with all 3 AI.
I am not willing to sacrifice motion for animal and vehicle AI.

Thank you.

Here is a screenshot of both motion alerts in fw 9 (when AI is off).

And here is a screen shot of simultaneous AI and motion alerts in fw 9.

[roleoroleo]

Motion tracking is not removed, it's simpy hidden.
If Yi didn't remove it, you can try to enable it manually, editing the file /tmp/sd/yi-hack/etc/camera.conf
MOTION_TRACKING=yes
and running the command
ipc_cmd -o ON
But if it doesn't work, it means that Yi removed the feature and you need to come back to fw 9.

[Giuserver]

@roleoroleo
So i do many tests, like promise:
Maybe my problems coming from time zone but the camera try to connect continuously with mosquitto.
So the motion detection doesn't work properly (I tried with private mode too (disabling cloud) same problem)

[roleoroleo]

When there is a disconnection problem with mosquitto, probably you are use 2 client with the same client id.
Check if this is your case: 2 cams or 2 processes with the same client id.

[Giuserver]

When there is a disconnection problem with mosquitto, probably you are use 2 client with the same client id.
Check if this is your case: 2 cams or 2 processes with the same client id.

I always use 1 camera at time for testing. Anyway, I changed default name but same problem, like you see the camera trying to connect with two different name at broker .

1672845680: mosquitto version 2.0.15 running
1672845735: New connection from 192.168.124.119:43736 on port 1883.
1672845735: New connection from 192.168.124.119:43738 on port 1883.
1672845735: New client connected from 192.168.124.119:43736 as camera1 (p2, c1, k120).
1672845735: New client connected from 192.168.124.119:43738 as camera1_c (p2, c1, k15).
1672845735: Client camera1_c closed its connection.
1672845737: New connection from 192.168.124.119:43744 on port 1883.
1672845737: New client connected from 192.168.124.119:43744 as camera1_c (p2, c1, k15).
1672845737: Client camera1_c closed its connection.
1672845737: New connection from 192.168.124.119:43746 on port 1883.

What about for videos recording so bad?
If I can do something for help i do, just tell me which classes use them.
I have another camera IFUS y211ga with fw base 9.0 and 0.2.5 hack, maybe can help (by the way this camera also record video like E100M01S60.mp4 but correctly 1 minute long).
If for you is more easy and you have 9.0 fw base, just send me. It will be great too.

Thank you.
Giuseppe

[roleoroleo]

Please try this new beta:
y211ga_0.2.5.tar.gz

I changed many many lines of code.
This fw 12 is not so easy to understand...

[Giuserver]

I understand. so, If you need something like backup, output command etc. Write here. I have another one camera y211ga with fw base 11 and hack 0.2.5. but for now i avoid to update that camera too for these reasons.

Thanks

[roleoroleo]

I'm close to completing a stable release.
I will send a new release to test asap.

[Giuserver]

When you ready. No rush.
Thanks

[blfriedman]

I also have an IFUS v11.0.36.7_202202170022 1080p cam. It came with the v11 software (refurb), so I don't have a v9 to downgrade to, and it shows an upgrade available to v12.0.37.0_202211241030 which I have not updated to (yet).

I am willing to be an additional tester for whichever version (v11 or v12) you plan to release for hack 0.2.5.

My platform is to disable the yi cloud, disable motion detection and recording, and just to use ssh, ntp, http, and rtsp (no ftp, no telnet, no mqtt, no onvif).

[roleoroleo]

I will not support version 11; Only 9 or 12.
You can upgrade to version 12 if you want.