-
Notifications
You must be signed in to change notification settings - Fork 343
F.A.Q
This happens when the watchdog-timer module (snx_wdt) isn't unloaded. Some people have reported this on the old firmware. Since there's no way to downgrade, it's difficult to develop a fix. Upgrading the firmware is much easier and should resolve the issue.
The default password is ismart12
The cloud apps don't cooperate with the RTSP server, you can't use both at the same time. Check the process list on the status page to determine if the cloud apps (iCamera or iSC3S) or RTSP server (snx_rtsp_server) are running.
There's a chance you've hit a bug, but most likely your sd-card is corrupt. Either it is defective, or the filesystem is messed up. Try to login using ssh and manually run a script, i.e. /media/mmcblk0p2/data/etc/scripts/20-rtsp-server. Check for mmcblk0p2 related errors using 'tail /var/log/messages' and 'dmesg'. Not succesfully completing the filesystem resize operation is often the cause of a messed up filesystem.
The timezone for uClibc should be specified in POSIX.1 (Olson) format. You can set it using the status page or by changing /etc/TZ directly. For more info and examples see:
- http://www.di-mgt.com.au/wclock/tz-syntax.txt
- http://svn.fonosfera.org/fon-ng/trunk/luci/modules/admin-fon/root/etc/timezones.db
In most cases, people have already setup the camera using the Mi Home app. Using this app, you can configure wifi settings send them to the device using a QR code. The credentials are stored in some files in /etc/config (.wifitype, .wifipasswd, .wifissid). By default, the Fang Hacks scripts assume this is the case and leave wifi settings untouched. Since the cloud app manages the wifi connection, the checkbox to disable cloud apps on the status page is greyed out and on the network page the mode is set to "Cloud" (DISABLE_CLOUD=0, NETWORK_MODE=0). Note that changing ssid/passphrase in this mode simply modifies the files in /etc/config mentioned before. Before any other services are started (i.e. RTSP) the cloud apps are stopped by the "stop cloud" script.
It takes quite a while for the cloud apps to start and configure the wifi interface and obviously there's a risk of outgoing cloud connections before the apps are stopped. For most people this is undesirable, but if the cloud apps are not started at all, the wifi interface isn't configured either! Therefore it's required to first configure the wifi: "Wireless client" or "Access-point" mode on the network page (NETWORK_MODE=1|2). Note that you will be locked out of the device if the wifi connection fails after a reboot. In case of wireless-client mode, you must first connect to the network (and re-open the network page in case the device changes IP address) before the settings can be applied. Once applied, the "Disable Cloud" checkbox on the status page will become available. But, please make sure your wifi settings work by rebooting a couple of times! If you run into issues you can simply remove the sdcard and reboot: the cloud apps are still enabled and without sdcard the network script is not present so will not override wifi configuration. Once you're happy, you can check the "Disable cloud" checkbox to prevent cloud apps from starting.
If for some reason things don't work out for you, there's a recovery file in the bootstrap folder: rename fang_hacks_rescue.cfg.tmpl to fang_hacks_rescue.cfg. This file is copied on reboot and restores the default settings. So you need to reboot twice: first to copy the file, then a fresh reboot to use the restored settings.