-
Notifications
You must be signed in to change notification settings - Fork 255
Preparations on the Vacuum Robots
Achilleas Pipinellis edited this page Jan 16, 2020
·
5 revisions
The Dustcloud IP must be a public IP address and not from your locale LAN!
You don't need to host the dustcloud on a public IP though, you can just use any public address and then redirect the traffic on your vacuum robot.
-
Point your vacuum via
/etc/hosts
to your<my_cloudserver_ip>
.<my_cloudserver_ip>
can be130.83.47.181
(this is a Server of the TU Darmstadt, content does not matter):0.0.0.0 awsbj0-files.fds.api.xiaomi.com 0.0.0.0 awsbj0.fds.api.xiaomi.com 130.83.47.181 ott.io.mi.com 130.83.47.181 ot.io.mi.com
-
Execute on vacuum:
iptables -t nat -A OUTPUT -p tcp --dport 80 -d 130.83.47.181 -j DNAT --to-destination 192.168.42.42:80 iptables -t nat -A OUTPUT -p udp --dport 8053 -d 130.83.47.181 -j DNAT --to-destination 192.168.42.42:8053
where
192.168.42.42
is the IP of your local instance and the port number on whichserver.py
runs (can technically run on a Raspberry pi).
Navigation
- Home
- Vacuum Robots
- Lumi Aqara Camera (experimental)
- Lumi Aqara Gateway (new Version, without Homekit)
- Documentation
- Dustcloud