Hi, I’m trying to edit my Mi Home V3 gateway.
I have the token, have managed to enable telnet (php miio-cli.php --ip 192.168.10.195 --token **** --sendcmd ‘{“id”:0,“method”:“enable_telnet_service”, “params”:}’)
Then i telnet 192.168.10.195
Trying 192.168.10.195...
Connected to 192.168.10.195.
Escape character is '^]'.
rlxlinux login: admin
Lumi Linux version 3.0
_ _ _ _
| | |_| | ||_|
| | _ _ _____ _ | | _ ____ _ _ _ _
| || || || \| | | || | _ \| | | |\ \/ /
| || || || | | || | | || | | | | |_| |/ \
|_|\____||_|_|_||_| |_||_|_| |_|\____|\_/\_/
For further information check:
https://www.aqara.com
BusyBox v1.22.1 (2020-03-19 12:38:22 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
I am trying to test your OTA trick with my lumi gateway lmuk01. I had it all working before but had to do a reset, and this caused me to lose ssh. I burnt off my soldering connection point on the board, so would like to try your OTA method. Any help on the steps would be great! I downloaded both miio software and the python-miio software. with miiocli I can see the info of the device. I also have the token (which I got from the hacked android app).
You can most likely also do this from within openHAB miio binding.
While miio binding has nothing specific to the lumi gateway, it should be possible to send commands to it and get the token from the Xiaomi cloud.
The lumi would show as unsupported device, but will have a command channel There you can send the command like: enable_telnet_service. The miio binding will then indeed send ‘{“id”:0,“method”:“enable_telnet_service”, “params”:}’ to the lumi device.
After that, you don’t need the miio binding anymore to control the lumi.
I don’t have a lumi device to test this, but would be surprised if it would be so different to other devices that it wont work
hi guys, can you help me please, i have a hub Aqara but the rx and tx is not the same pins that the xiaomi gateway, do you know the rx and tx pins for aqara hub? and do you know if this hub also has programming mode?
I have received a new v2 gateway (I already have one which works). This came with port 9898 closed. I managed to get the device connected to the PC and can type in commands. I typed in psm-set network.open_pf 3 a couple of times, verified with psm-get network.open_pf and it replies
network.open_pf = 3 (1 bytes)
so this seems good. However if I unplug it, wait and put it back in the socket (without the UART attached) and try the nmap, port 9898 is still closed. What am I doing wrong?
(don’t know if it matters but I upgraded to the newest firmware. Don’t recall if I turned on the LAN support before doing so. Did I mess that up?)
a week ago as i was reorganizing cables, i accidentally pressed the button on the gateway for a few seconds, the gateway was reset.
Does a reset like this also disable the LAN-Mode/Developer mode?
since then i haven’t been able to communicate with the gateway for more than a few minutes. the psm-set network.open_pf 3 command doesn’t help either.
Sorry to reply on such an old thread, but I need help I’ve followed the steps exactly as @cadavre stated but can’t seem to get it work.When I call “boot” after setting bootargs process moves until starting Kernel then it’s all hieroglyphics. I get no prompt, interface halts. When I try to boot it into login -without setting args- I get:
====================================
========== start mi=================
====================================
.
umount: /mnt/.psplash: not mounted
INIT: no more processes left in this runlevel
and it halts again, I get no prompt. Any help is appreciated.
If you have the 2 pin version without the ground pin, soldering the earth pin to a plug with an earth lead, and then inserting that plug into the same power strip that your FTDI UART PC uses will prevent ground loops and (induced?) voltages on the GND of the UART (which is connected to AC socket GND).
I’ve followed the steps exactly as