0.4.1i

[alienatedsec]

Breaking changes !!!

• There is a new baseline 0.4.1i, so you need to prepare your SD card for it - follow Specifics of the yi-hack-v5 firmware and flashing #267

• The camera web page is no longer under port 8080 but back to default port 80 - access your camera web page using its IP only. Those with proxy environments or Home Assistant integrations must amend their settings.

• The new baseline is needed to fix OTA upgrade OTA FW upgrade shows no value for "Available:" #326 - cameras on earlier versions cannot upgrade from the WebUi as there is an additional baseline check - it refers to 0.4.1 for the latest release - 23a96a5 - amend the file on your SD with your baseline version to bypass this check and upgrade via WebUI or copy the file over and change its name as per the guidance.

• Future non-baseline upgrades will be released without SD formatted to the FAT32 requirement.

• We need testers, so if you have no physical access to your camera - don't upgrade, as it may require fixing by downgrading etc.

What's Changed

• Fixed symlink to VI Missing a link to the binary on the sdcard ? #346
• Fixed the MQTT issue MQTT status changes many times per second (offline/online) when RTSP server is activated (0.4.1.e) #333
• Fixed no watermark in streams [0.4.1e] No timestamp watermark on stream #336 - thanks @Minims
• Amended config reading - seems to work quicker - thanks @Minims
• Added files versioning (future-proof)

What is still not working

• @roleoroleo 's 27US ;-)
• Whatever the community highlights

Full Changelog: 0.4.1h...0.4.1i

---

This discussion was created from the release 0.4.1i.

[roleoroleo]

@roleoroleo 's 27US ;-)

Tonight I will connect the uart.

[alienatedsec]

@roleoroleo please can you test this version?

Save those four files in the /tmp/sd/yi-hack-v5/wpa folder and reboot the camera. Then go back to your non-working WPA3 router config.

wpa.zip

I made a mistake and it will boot loop unless the file wpa_supplicant_upgrade is deleted after, so please amend to the below in system.sh before rebooting.

# Upgrade wpa_supplicant modules - after 0.4.1 baseline
if [ -f $YI_HACK_PREFIX/wpa/wpa_supplicant_upgrade ]; then
	ifconfig wlan0 up
    echo "---backing up wpa---"
    cp /home/base/tools/wpa_supplicant $YI_HACK_PREFIX/wpa/wpa_supplicant_backup
    cp /home/base/tools/wpa_cli $YI_HACK_PREFIX/wpa/wpa_cli_backup
    cp /home/base/tools/wpa_passphrase $YI_HACK_PREFIX/wpa/wpa_passphrase_backup
    killall watch_process
    killall wpa*
    mv /tmp/sd/yi-hack-v5/wpa/*.so* /home/lib/
    mv /tmp/sd/yi-hack-v5/wpa/wpa_supplicant /home/base/tools/
    mv /tmp/sd/yi-hack-v5/wpa/wpa_cli /home/base/tools/
    mv /tmp/sd/yi-hack-v5/wpa/wpa_passphrase /home/base/tools/
    rm $YI_HACK_PREFIX/wpa/wpa_supplicant_upgrade
    reboot
    echo "---wpa upgrade done---"
else
	echo "---no wpa upgrade---"
fi

[roleoroleo]

Sorry but I can't test it until Monday.

[alienatedsec]

@roleoroleo Not a problem at all. Enjoy the weekend. It feels like I need some break too.

[roleoroleo]

Sorry but I can't test it until Monday.

Tested :)
Unfortunately it doesn't work.
The same behavior.

[alienatedsec]

@roleoroleo This is the latest I have found https://wiki.archlinux.org/title/Wpa_supplicant#Connections_to_pure_WPA3-SAE_access_points

Make sure to define the following within the network block of the configuration to enable connections to pure WPA3 access points:

You will need to amend your config file before connecting.

ssid="network SSID"
key_mgmt=SAE
sae_password="the.literal.wifi.password"
ieee80211w=2

On top of the above....

One more thing is to check what settings are on both (the old one working with WPA3 and the new one that only connects with WPA2) supplicants by executing wpa_cli and running the command status

/home/yi-hack-v5 # wpa_cli
wpa_cli v2.10
Copyright (c) 2004-2022, Jouni Malinen <j@w1.fi> and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.


Selected interface 'wlan0'

Interactive mode

> status
bssid=xx:xx:xx:xx:xx:xx
freq=0
ssid=xxxxxxx
id=0
mode=station
pairwise_cipher=CCMP
group_cipher=CCMP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED
ip_address=192.168.x.x
address=xx:xx:xx:xx:xx:xx
uuid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx
>

[premiero]

My AV detects Trojan:Script/Wacatac.B!ml in yi_home_0.4.1i.tgz archive - there was no such issues with older versions.

[alienatedsec]

@premiero Which exactly is a Trojan script then?

[premiero]

It's marking whole *.tar archive, not specific file in it. Anyway if I decompress it under linux, and copy files to W10 - no alerts anymore.

[roleoroleo]

I tried to follow the instructions here
https://wiki.archlinux.org/title/Wpa_supplicant#Connections_to_pure_WPA3-SAE_access_points
but no luck.
Pure WPA3-SAE or mixed WPA2/WPA3.
It doesn't work.
And wpa_supplicant doesn't show any strange log.

[alienatedsec]

@roleoroleo
Mine works with mixed WPA2/WPA3 without any modifications. It does not work with WPA3, but I have no UART access to check the logs and try other settings.

[kknishev]

hi, sorry, please assist, why is the ONVIF Port not available on web currently?
and what port by default?

[alienatedsec]

@kknishev The ONVIF port shares the same port as the web server - port 80

[waleed-alharthi]

Every single version, 3.7 to 0.4.1h, sent my cameras into a boot loop by the 2nd day.

This version however, I'm 3 days in and all the cameras are still up and streaming RTSP! Fingers crossed! 🤞