-
-
Save zvldz/b40b4873e3c4c1a64ac536e8ce5dbdad to your computer and use it in GitHub Desktop.
Yes, you need reset. Format some db has changed.
Does the ble firmware update fail?
Sometimes it takes about 5 minutes.
The gateway does a firmware check at startup.
You can also try rebooting it.
There were times when firmware 1.4.6_0012 did not update.
I'll recheck if there's different path.
hi zvldz,
Yes, I flash the firmware 1.4.6_0012..
I flash the firmware 1.4.6_0012..
In fw 1.4.6_0012 full.gbl must be moved to /data and reboot gw.
I try to manual reboot the gw after 5 minutes, but /data/firmware/full.gbl file, still exist.
path to full.gbl on fw 1.4.6_0012
/data/full.gbl
I try to mv full.gbl from /data/firmware/ to /data then reboot gw (on fw 1.4.6_0012), after reboot the /data/full.gbl not exist.
/data/full.gbl not exist
so firmware has been updated
Oh yes, it may be more perfect to add BLE firmware path in firmware 1.4.6_0012 to mgl03_update.sh.
Thank you very much zvldz!
Trying
wget -O /tmp/wget http://pkg.musl.cc/wget/mipsel-linux-musln32/bin/wget && chmod +x /tmp/wget
But get
Resolving pkg.musl.cc (pkg.musl.cc)... 104.232.42.245
Connecting to pkg.musl.cc (pkg.musl.cc)|104.232.42.245|:80... failed: Connection refused.
Trying
wget -O /tmp/wget http://pkg.musl.cc/wget/mipsel-linux-musln32/bin/wget && chmod +x /tmp/wget
But get
Resolving pkg.musl.cc (pkg.musl.cc)... 104.232.42.245
Connecting to pkg.musl.cc (pkg.musl.cc)|104.232.42.245|:80... failed: Connection refused.
similar error
Yes, the site is down.
I'll update the link later
similar error
In this case, try command:
printf 'GET /files/curl HTTP/1.1\r\nHost: mipsel-ssl.vacuumz.info\r\nUser-Agent: Wget/1.20.3\r\nConnection: close\r\n\r\n' | openssl s_client -quiet -tls1_1 -connect mipsel-ssl.vacuumz.info:443 -servername mipsel-ssl.vacuumz.info | sed '/alt-svc.*/d' | tail -n +19 > /tmp/curl && chmod +x /tmp/curl
export PATH="$PATH:/tmp"
Then run first command again.
Then run first command again.
curl -s -k -L -o /tmp/update.sh https://gist.github.com/zvldz/b40b4873e3c4c1a64ac536e8ce5dbdad/raw/mgl03_update.sh && sh /tmp/update.sh
run this command
wget -O /tmp/wget http://pkg.musl.cc/wget/mipsel-linux-musln32/bin/wget && chmod +x /tmp/wget
and got the error as below
Connecting to pkg.musl.cc (104.232.42.245:80)
wget: server returned error: HTTP/1.1 404 Not Found
Manual has moved to https://github.com/zvldz/mgl03_fw/tree/main/firmware
Can someone help me, whats wrong there?
miiocli device --ip 192.168.188.43 --token hereismytoken raw_command set_ip_info '{"ssid":"\"\"","pswd":"123123 ; passwd -d admin ; echo enable > /sys/class/tty/tty/enable; telnetd"}'
I always get
Traceback (most recent call last):
File "C:\Program Files\Python310\lib\runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "C:\Program Files\Python310\lib\runpy.py", line 86, in _run_code
exec(code, run_globals)
File "C:\Users\Nico\AppData\Roaming\Python\Python310\Scripts\miiocli.exe\__main__.py", line 7, in <module>
File "C:\Users\Nico\AppData\Roaming\Python\Python310\site-packages\miio\cli.py", line 66, in create_cli
return cli(auto_envvar_prefix="MIIO")
File "C:\Users\Nico\AppData\Roaming\Python\Python310\site-packages\miio\click_common.py", line 51, in __call__
return self.main(*args, **kwargs)
File "C:\Users\Nico\AppData\Roaming\Python\Python310\site-packages\click\core.py", line 1055, in main
rv = self.invoke(ctx)
File "C:\Users\Nico\AppData\Roaming\Python\Python310\site-packages\click\core.py", line 1657, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "C:\Users\Nico\AppData\Roaming\Python\Python310\site-packages\click\core.py", line 1655, in invoke
sub_ctx = cmd.make_context(cmd_name, args, parent=ctx)
File "C:\Users\Nico\AppData\Roaming\Python\Python310\site-packages\click\core.py", line 920, in make_context
self.parse_args(ctx, args)
File "C:\Users\Nico\AppData\Roaming\Python\Python310\site-packages\click\core.py", line 1378, in parse_args
value, args = param.handle_parse_result(ctx, opts, args)
Great job!
If I use telnet update from mgl03_1.4.7_0065_mod20201211 to mgl03_1.4.7_0115_mod20201222, do I need to do factory reset after the update?
reconnect all the iot is a hard job...