pi@192.168.1.34's password: +--------------------------------------------------------------------+ ¦ • MobaXterm 10.6 • ¦ ¦ (SSH client, X-server and networking tools) ¦ ¦ ¦ ¦ ? SSH session to pi@192.168.1.34 ¦ ¦ • SSH compression : ? ¦ ¦ • SSH-browser : ? ¦ ¦ • X11-forwarding : ? (remote display is forwarded through SSH) ¦ ¦ • DISPLAY : ? (automatically set on remote server) ¦ ¦ ¦ ¦ ? For more info, ctrl+click on help or visit our website ¦ +--------------------------------------------------------------------+ Linux raspberrypi 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Fri Jan 18 23:50:17 2019 from 192.168.1.32 SSH is enabled and the default password for the 'pi' user has not been changed. This is a security risk - please login as the 'pi' user and type 'passwd' to set a new password. pi@raspberrypi:~ $ sudo ./tuyota.pl -ip 192.168.1.36 -s mySSID -p myPassword sudo: ./tuyota.pl: command not found pi@raspberrypi:~ $ ll total 96K drwxr-xr-x 17 pi pi 4.0K Jan 18 23:51 ./ drwxr-xr-x 3 root root 4.0K Nov 13 13:09 ../ -rw------- 1 pi pi 313 Jan 18 23:51 .bash_history -rw-r--r-- 1 pi pi 220 Nov 13 13:09 .bash_logout -rw-r--r-- 1 pi pi 3.5K Nov 13 13:09 .bashrc drwxr-xr-x 5 pi pi 4.0K Nov 13 14:24 .cache/ drwx------ 3 pi pi 4.0K Nov 13 14:24 .config/ drwxr-xr-x 2 pi pi 4.0K Nov 13 14:24 Desktop/ drwxr-xr-x 2 pi pi 4.0K Nov 13 14:24 Documents/ drwxr-xr-x 2 pi pi 4.0K Nov 13 14:24 Downloads/ drwx------ 3 pi pi 4.0K Nov 13 14:24 .gnupg/ drwxr-xr-x 3 pi pi 4.0K Nov 13 13:45 .local/ drwxr-xr-x 2 pi pi 4.0K Nov 13 13:45 MagPi/ drwxr-xr-x 2 pi pi 4.0K Nov 13 14:24 Music/ drwxr-xr-x 2 pi pi 4.0K Jan 18 21:56 .nano/ drwxr-xr-x 2 pi pi 4.0K Nov 13 14:24 Pictures/ -rw-r--r-- 1 pi pi 675 Nov 13 13:09 .profile drwxr-xr-x 2 pi pi 4.0K Nov 13 14:24 Public/ drwxr-xr-x 2 pi pi 4.0K Nov 13 14:24 Templates/ drwxr-xr-x 4 pi pi 4.0K Jan 18 23:05 TuyOTA/ drwxr-xr-x 2 pi pi 4.0K Nov 13 14:24 Videos/ -rw-r--r-- 1 pi pi 215 Jan 18 23:05 .wget-hsts -rw------- 1 pi pi 170 Jan 18 23:51 .Xauthority -rw------- 1 pi pi 3.9K Nov 13 14:24 .xsession-errors pi@raspberrypi:~ $ ll MagPi total 30M drwxr-xr-x 2 pi pi 4.0K Nov 13 13:45 ./ drwxr-xr-x 17 pi pi 4.0K Jan 18 23:51 ../ -rw-r--r-- 1 pi pi 30M Nov 13 13:45 MagPi75.pdf pi@raspberrypi:~ $ cd TuyOTA/ pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.36 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2074 Redirecting device 192.168.1.36 to use Access Point ZAGDU-789 **** Redirect appears successful DHCP Discover e4:f0:42:de:76:ee 10.44.57.120 DHCP Discover 84:0d:8e:53:34:7c Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 10. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 97.80.250.180 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2097 Redirecting device 97.80.250.180 to use Access Point ZAGDU-789 Unable to open socket to 97.80.250.180: Connection refused The device might be at the next stage, ignoring for now DHCP Discover e4:f0:42:de:76:ee 10.44.57.96 DHCP Discover e4:f0:42:de:76:ee 10.44.57.96 Shutting down... Setting up IP Address 192.168.4.2 for Final Stages Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Setting up wifi scan Setting up listener for FinalStage Shutting down... Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Finished Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ ping 192.168.1.36 PING 192.168.1.36 (192.168.1.36) 56(84) bytes of data. From 192.168.1.34 icmp_seq=9 Destination Host Unreachable From 192.168.1.34 icmp_seq=10 Destination Host Unreachable From 192.168.1.34 icmp_seq=11 Destination Host Unreachable From 192.168.1.34 icmp_seq=12 Destination Host Unreachable From 192.168.1.34 icmp_seq=13 Destination Host Unreachable From 192.168.1.34 icmp_seq=14 Destination Host Unreachable From 192.168.1.34 icmp_seq=15 Destination Host Unreachable From 192.168.1.34 icmp_seq=16 Destination Host Unreachable From 192.168.1.34 icmp_seq=17 Destination Host Unreachable ^C --- 192.168.1.36 ping statistics --- 20 packets transmitted, 0 received, +9 errors, 100% packet loss, time 19764ms pipe 4 pi@raspberrypi:~/TuyOTA $ ping 192.168.1.36 PING 192.168.1.36 (192.168.1.36) 56(84) bytes of data. ^C --- 192.168.1.36 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2102ms pi@raspberrypi:~/TuyOTA $ ping 97.80.250.180 PING 97.80.250.180 (97.80.250.180) 56(84) bytes of data. 64 bytes from 97.80.250.180: icmp_seq=1 ttl=64 time=3.55 ms 64 bytes from 97.80.250.180: icmp_seq=2 ttl=64 time=8.24 ms 64 bytes from 97.80.250.180: icmp_seq=3 ttl=64 time=1.95 ms 64 bytes from 97.80.250.180: icmp_seq=4 ttl=64 time=2.22 ms 64 bytes from 97.80.250.180: icmp_seq=5 ttl=64 time=3.03 ms 64 bytes from 97.80.250.180: icmp_seq=6 ttl=64 time=3.30 ms 64 bytes from 97.80.250.180: icmp_seq=7 ttl=64 time=3.62 ms 64 bytes from 97.80.250.180: icmp_seq=8 ttl=64 time=3.47 ms ^C --- 97.80.250.180 ping statistics --- 8 packets transmitted, 8 received, 0% packet loss, time 7010ms rtt min/avg/max/mdev = 1.950/3.677/8.244/1.822 ms pi@raspberrypi:~/TuyOTA $ ping 192.168.1.36 PING 192.168.1.36 (192.168.1.36) 56(84) bytes of data. 64 bytes from 192.168.1.36: icmp_seq=1 ttl=255 time=155 ms 64 bytes from 192.168.1.36: icmp_seq=2 ttl=255 time=108 ms 64 bytes from 192.168.1.36: icmp_seq=3 ttl=255 time=124 ms 64 bytes from 192.168.1.36: icmp_seq=4 ttl=255 time=5.29 ms 64 bytes from 192.168.1.36: icmp_seq=5 ttl=255 time=4.50 ms 64 bytes from 192.168.1.36: icmp_seq=6 ttl=255 time=4.37 ms 64 bytes from 192.168.1.36: icmp_seq=7 ttl=255 time=73.2 ms ^C --- 192.168.1.36 ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6009ms rtt min/avg/max/mdev = 4.372/68.014/155.674/59.239 ms pi@raspberrypi:~/TuyOTA $ man ping pi@raspberrypi:~/TuyOTA $ ping -R 192.168.1.36 PING 192.168.1.36 (192.168.1.36) 56(124) bytes of data. ^C --- 192.168.1.36 ping statistics --- 10 packets transmitted, 0 received, 100% packet loss, time 9363ms pi@raspberrypi:~/TuyOTA $ ping 192.168.1.36 PING 192.168.1.36 (192.168.1.36) 56(84) bytes of data. 64 bytes from 192.168.1.36: icmp_seq=1 ttl=255 time=165 ms 64 bytes from 192.168.1.36: icmp_seq=2 ttl=255 time=32.5 ms 64 bytes from 192.168.1.36: icmp_seq=3 ttl=255 time=10.3 ms 64 bytes from 192.168.1.36: icmp_seq=4 ttl=255 time=30.3 ms ^C --- 192.168.1.36 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 10.302/59.767/165.857/61.862 ms pi@raspberrypi:~/TuyOTA $ ping -R 97.80.250.180 PING 97.80.250.180 (97.80.250.180) 56(124) bytes of data. 64 bytes from 97.80.250.180: icmp_seq=1 ttl=64 time=2.93 ms RR: 192.168.1.34 97.80.250.180 97.80.250.180 192.168.1.34 64 bytes from 97.80.250.180: icmp_seq=2 ttl=64 time=3.49 ms (same route) 64 bytes from 97.80.250.180: icmp_seq=3 ttl=64 time=3.50 ms (same route) 64 bytes from 97.80.250.180: icmp_seq=4 ttl=64 time=3.06 ms (same route) 64 bytes from 97.80.250.180: icmp_seq=5 ttl=64 time=4.37 ms (same route) 64 bytes from 97.80.250.180: icmp_seq=6 ttl=64 time=4.77 ms (same route) 64 bytes from 97.80.250.180: icmp_seq=7 ttl=64 time=2.58 ms (same route) 64 bytes from 97.80.250.180: icmp_seq=8 ttl=64 time=2.12 ms (same route) 64 bytes from 97.80.250.180: icmp_seq=9 ttl=64 time=2.12 ms (same route) ^C --- 97.80.250.180 ping statistics --- 9 packets transmitted, 9 received, 0% packet loss, time 8012ms rtt min/avg/max/mdev = 2.122/3.221/4.777/0.873 ms pi@raspberrypi:~/TuyOTA $ ipconfig -bash: ipconfig: command not found pi@raspberrypi:~/TuyOTA $ ifconfig eth0: flags=4163 mtu 1500 inet 192.168.1.34 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::52f1:223e:bc12:6a3c prefixlen 64 scopeid 0x20 ether b8:27:eb:30:30:59 txqueuelen 1000 (Ethernet) RX packets 68334 bytes 25935455 (24.7 MiB) RX errors 0 dropped 20 overruns 0 frame 0 TX packets 12196 bytes 1175528 (1.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 145 bytes 23917 (23.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 145 bytes 23917 (23.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4099 mtu 1500 ether b8:27:eb:65:65:0c txqueuelen 1000 (Ethernet) RX packets 96 bytes 1774 (1.7 KiB) RX errors 0 dropped 91 overruns 0 frame 0 TX packets 39 bytes 6267 (6.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.36 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2264 Redirecting device 192.168.1.36 to use Access Point ZAGDU-789 **** Redirect appears successful DHCP Discover 84:0d:8e:53:34:7c 10.44.57.81 DHCP Request 84:0d:8e:53:34:7c 10.44.57.81 **** New device detected. ID: 75070011840d8e53347c IP:10.44.57.81 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.81 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response DHCP Discover 84:0d:8e:53:34:7c 10.44.57.81 DHCP Request 84:0d:8e:53:34:7c 10.44.57.81 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 15. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.36 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2282 Redirecting device 192.168.1.36 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.36: No route to host The device might be at the next stage, ignoring for now DHCP Discover 84:0d:8e:53:34:7c 10.44.57.17 DHCP Request 84:0d:8e:53:34:7c 10.44.57.17 Accepting MQTT connection, forwarding to not set **** New device detected. ID: 75070011840d8e53347c IP:10.44.57.17 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.17 to use Access Point ZAGDU-789 **** Redirect appears successful Accepting MQTT connection, forwarding to not set DHCP Discover 84:0d:8e:53:34:7c 10.44.57.17 DHCP Request 84:0d:8e:53:34:7c 10.44.57.17 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547860437,"e":false,"success":true} Receiving www request URL: /gw.json?a=tuya.device.dynamic.config.get Response: HTTP/1.1 200 OK {"result":{"validTime":1800,"time":1547860437,"config":{}},"t":1547860437,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 16. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.36 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2301 Redirecting device 192.168.1.36 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.36: No route to host The device might be at the next stage, ignoring for now DHCP Discover 84:0d:8e:53:34:7c 10.44.57.183 DHCP Request 84:0d:8e:53:34:7c 10.44.57.183 **** New device detected. ID: 75070011840d8e53347c IP:10.44.57.183 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.183 to use Access Point ZAGDU-789 **** Redirect appears successful Accepting MQTT connection, forwarding to not set Receiving www request URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response DHCP Discover 84:0d:8e:53:34:7c 10.44.57.183 DHCP Request 84:0d:8e:53:34:7c 10.44.57.183 DHCP Request f0:1f:af:19:56:20 f0:1f:af:19:56:20: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 16. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.36 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2321 Redirecting device 192.168.1.36 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.36: No route to host The device might be at the next stage, ignoring for now DHCP Discover 84:0d:8e:53:34:7c 10.44.57.167 DHCP Request 84:0d:8e:53:34:7c 10.44.57.167 **** New device detected. ID: 75070011840d8e53347c IP:10.44.57.167 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.167 to use Access Point ZAGDU-789 **** Redirect appears successful DHCP Discover 84:0d:8e:53:34:7c 10.44.57.167 DHCP Request 84:0d:8e:53:34:7c 10.44.57.167 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 16. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ ping 192.168.1.36 PING 192.168.1.36 (192.168.1.36) 56(84) bytes of data. From 192.168.1.34 icmp_seq=1 Destination Host Unreachable From 192.168.1.34 icmp_seq=2 Destination Host Unreachable From 192.168.1.34 icmp_seq=3 Destination Host Unreachable From 192.168.1.34 icmp_seq=4 Destination Host Unreachable From 192.168.1.34 icmp_seq=5 Destination Host Unreachable From 192.168.1.34 icmp_seq=6 Destination Host Unreachable From 192.168.1.34 icmp_seq=7 Destination Host Unreachable From 192.168.1.34 icmp_seq=8 Destination Host Unreachable From 192.168.1.34 icmp_seq=9 Destination Host Unreachable ^C --- 192.168.1.36 ping statistics --- 10 packets transmitted, 0 received, +9 errors, 100% packet loss, time 9346ms pipe 4 pi@raspberrypi:~/TuyOTA $ ping 192.168.1.36 PING 192.168.1.36 (192.168.1.36) 56(84) bytes of data. From 192.168.1.34 icmp_seq=1 Destination Host Unreachable From 192.168.1.34 icmp_seq=2 Destination Host Unreachable From 192.168.1.34 icmp_seq=3 Destination Host Unreachable ^C --- 192.168.1.36 ping statistics --- 6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5167ms pipe 4 pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.36 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2355 Redirecting device 192.168.1.36 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.36: No route to host The device might be at the next stage, ignoring for now DHCP Discover 84:0d:8e:53:34:7c 10.44.57.140 DHCP Discover 84:0d:8e:53:34:7c 10.44.57.140 DHCP Request 84:0d:8e:53:34:7c 10.44.57.140 Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content URL: /gw.json?a=s.gw.upgrade.updatestatus Response: HTTP/1.1 200 OK {"t":1547860649,"e":false,"success":true} **** New device detected. ID: 75070011840d8e53347c IP:10.44.57.140 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.140 to use Access Point ZAGDU-789 **** Redirect appears successful DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 1. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.36 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2373 Redirecting device 192.168.1.36 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.36: No route to host The device might be at the next stage, ignoring for now DHCP Discover 84:0d:8e:53:34:7c 10.44.57.222 DHCP Request 84:0d:8e:53:34:7c 10.44.57.222 **** New device detected. ID: 75070011840d8e53347c IP:10.44.57.222 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.222 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response DHCP Discover 84:0d:8e:53:34:7c 10.44.57.222 DHCP Request 84:0d:8e:53:34:7c 10.44.57.222 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547860680,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 16. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.36 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2391 Redirecting device 192.168.1.36 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.36: No route to host The device might be at the next stage, ignoring for now **** New device detected. ID: 75070011840d8e53347c IP:10.44.57.222 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.222 to use Access Point ZAGDU-789 Unable to open socket to 10.44.57.222: No route to host The device might be at the next stage, ignoring for now DHCP Discover 84:0d:8e:53:34:7c 10.44.57.195 DHCP Discover 84:0d:8e:53:34:7c 10.44.57.195 DHCP Request 84:0d:8e:53:34:7c 10.44.57.195 Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Receiving www request Fetching Request Content URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Accepting MQTT connection, forwarding to not set Receiving www request Fetching Request Content URL: /gw.json?a=s.gw.upgrade.updatestatus Response: HTTP/1.1 200 OK {"t":1547860700,"e":false,"success":true} Accepting MQTT connection, forwarding to not set DHCP Request f0:1f:af:19:56:20 f0:1f:af:19:56:20: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 1. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.36 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2411 Redirecting device 192.168.1.36 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.36: No route to host The device might be at the next stage, ignoring for now **** New device detected. ID: 75070011840d8e53347c IP:10.44.57.195 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.195 to use Access Point ZAGDU-789 Unable to open socket to 10.44.57.195: No route to host The device might be at the next stage, ignoring for now DHCP Discover 84:0d:8e:53:34:7c 10.44.57.172 DHCP Request 84:0d:8e:53:34:7c 10.44.57.172 Received DNS query for fakewebsite. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to not set Receiving www request Sending firmware image_user2-0x81000.bin Receiving www request Sending firmware image_user2-0x81000.bin Sending bytes 239271-478490 from offset 0 Accepting MQTT connection, forwarding to not set DHCP Discover 84:0d:8e:53:34:7c 10.44.57.172 DHCP Request 84:0d:8e:53:34:7c 10.44.57.172 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 26. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.36 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2430 Redirecting device 192.168.1.36 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.36: No route to host The device might be at the next stage, ignoring for now DHCP Discover e4:f0:42:de:76:ee 10.44.57.127 DHCP Discover e4:f0:42:de:76:ee 10.44.57.127 Shutting down... Setting up IP Address 192.168.4.2 for Final Stages Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Setting up wifi scan Setting up listener for FinalStage ***** FinalStage Detected ****** ***** Connected to FinalStage ****** ***** Receiving FinalStage Request **** REQ: Client closed connection while receiving request: ***** Receiving FinalStage Request **** Sending firmware sonoff.bin ***** Tasmota Firmware sent to device ****** ***** FinalStage Detected ****** ***** Connected to FinalStage ****** ***** Found Sonoff AP sonoff-5244 ****** ***** Connected to sonoff-5244 ****** Sending config to sonoff-5244 ***** Config sent ***** ***** Found Sonoff AP sonoff-5244 ****** ***** Connected to sonoff-5244 ****** Failed to connect to device sonoff-5244: No route to host Shutting down... Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Finished Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ pi@raspberrypi:~/TuyOTA $ pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.38 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2562 Redirecting device 192.168.1.38 to use Access Point ZAGDU-789 **** New device detected. ID: 75070011840d8e53e2fb IP:192.168.1.38 Asking device to move networks and upgrade... Redirecting device 192.168.1.38 to use Access Point ZAGDU-789 DHCP Request f0:1f:af:19:56:20 10.44.57.32 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 1. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.38 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2578 Redirecting device 192.168.1.38 to use Access Point ZAGDU-789 DHCP Discover e4:f0:42:de:76:ee 10.44.57.72 DHCP Request f0:1f:af:19:56:20 f0:1f:af:19:56:20: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 1. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.38 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2594 Redirecting device 192.168.1.38 to use Access Point ZAGDU-789 **** New device detected. ID: 75070011840d8e53e2fb IP:192.168.1.38 Asking device to move networks and upgrade... Redirecting device 192.168.1.38 to use Access Point ZAGDU-789 **** Redirect appears successful DHCP Discover 84:0d:8e:53:e2:fb 10.44.57.133 DHCP Request 84:0d:8e:53:e2:fb 10.44.57.133 **** Device 75070011840d8e53e2fb has changed IP from 192.168.1.38 to 10.44.57.133 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547866793,"e":false,"success":true} Receiving www request URL: /gw.json?a=tuya.device.dynamic.config.get Response: HTTP/1.1 200 OK {"result":{"validTime":1800,"time":1547866794,"config":{}},"t":1547866794,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 9. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.38 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2613 Redirecting device 192.168.1.38 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.38: No route to host The device might be at the next stage, ignoring for now DHCP Discover 84:0d:8e:53:e2:fb 10.44.57.188 DHCP Discover 84:0d:8e:53:e2:fb 10.44.57.188 DHCP Discover 84:0d:8e:53:e2:fb 10.44.57.188 DHCP Discover 84:0d:8e:53:e2:fb 10.44.57.188 DHCP Request 84:0d:8e:53:e2:fb 10.44.57.188 **** New device detected. ID: 75070011840d8e53e2fb IP:10.44.57.188 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.188 to use Access Point ZAGDU-789 **** Redirect appears successful Accepting MQTT connection, forwarding to not set Receiving www request URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 1. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.38 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2632 Redirecting device 192.168.1.38 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.38: No route to host The device might be at the next stage, ignoring for now DHCP Discover 84:0d:8e:53:e2:fb 10.44.57.203 DHCP Discover 84:0d:8e:53:e2:fb 10.44.57.203 DHCP Request 84:0d:8e:53:e2:fb 10.44.57.203 **** New device detected. ID: 75070011840d8e53e2fb IP:10.44.57.203 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.203 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response DHCP Discover 84:0d:8e:53:e2:fb 10.44.57.203 DHCP Request 84:0d:8e:53:e2:fb 10.44.57.203 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547866854,"e":false,"success":true} Receiving www request URL: /gw.json?a=tuya.device.dynamic.config.get Response: HTTP/1.1 200 OK {"result":{"validTime":1800,"time":1547866855,"config":{}},"t":1547866855,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 15. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.38 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2651 Redirecting device 192.168.1.38 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.38: No route to host The device might be at the next stage, ignoring for now **** New device detected. ID: 75070011840d8e53e2fb IP:10.44.57.203 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.203 to use Access Point ZAGDU-789 Unable to open socket to 10.44.57.203: No route to host The device might be at the next stage, ignoring for now DHCP Discover 84:0d:8e:53:e2:fb 10.44.57.21 DHCP Request 84:0d:8e:53:e2:fb 10.44.57.21 Receiving www request Fetching Request Content URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content URL: /gw.json?a=s.gw.upgrade.updatestatus Response: HTTP/1.1 200 OK {"t":1547866874,"e":false,"success":true} Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Received DNS query for fakewebsite. Sending 10.44.57.1 as response Receiving www request Sending firmware image_user2-0x81000.bin Receiving www request Sending firmware image_user2-0x81000.bin Sending bytes 239271-478490 from offset 0 Accepting MQTT connection, forwarding to not set DHCP Discover 84:0d:8e:53:e2:fb 10.44.57.21 DHCP Request 84:0d:8e:53:e2:fb 10.44.57.21 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 27. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.38 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2669 Redirecting device 192.168.1.38 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.38: No route to host The device might be at the next stage, ignoring for now DHCP Request f0:1f:af:19:56:20 10.44.57.144 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 1. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.38 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2684 Redirecting device 192.168.1.38 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.38: No route to host The device might be at the next stage, ignoring for now DHCP Discover e4:f0:42:de:76:ee 10.44.57.150 DHCP Discover e4:f0:42:de:76:ee 10.44.57.150 Shutting down... Setting up IP Address 192.168.4.2 for Final Stages Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Setting up wifi scan Setting up listener for FinalStage ***** FinalStage Detected ****** ***** Connected to FinalStage ****** ***** Receiving FinalStage Request **** REQ: Client closed connection while receiving request: ***** Receiving FinalStage Request **** Sending firmware sonoff.bin ***** Tasmota Firmware sent to device ****** ***** FinalStage Detected ****** ***** Connected to FinalStage ****** ***** Found Sonoff AP sonoff-0763 ****** ***** Connected to sonoff-0763 ****** Sending config to sonoff-0763 ***** Config sent ***** ***** Found Sonoff AP sonoff-0763 ****** ***** Connected to sonoff-0763 ****** Failed to connect to device sonoff-0763: No route to host Shutting down... Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Finished Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2794 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 **** Redirect appears successful DHCP Discover dc:4f:22:8b:d5:59 10.44.57.222 DHCP Request dc:4f:22:8b:d5:59 10.44.57.222 **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.222 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.222 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 11. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2810 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.70 DHCP Discover dc:4f:22:8b:d5:59 10.44.57.70 DHCP Discover dc:4f:22:8b:d5:59 10.44.57.70 DHCP Request f0:1f:af:19:56:20 f0:1f:af:19:56:20: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 1. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2829 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.26 DHCP Request dc:4f:22:8b:d5:59 10.44.57.26 **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.26 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.26 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Receiving www request URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content Timed out waiting for content DHCP Discover dc:4f:22:8b:d5:59 10.44.57.26 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 13. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2846 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.253 DHCP Request dc:4f:22:8b:d5:59 10.44.57.253 **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.253 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.253 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response DHCP Discover dc:4f:22:8b:d5:59 10.44.57.253 DHCP Request dc:4f:22:8b:d5:59 10.44.57.253 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 19. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2866 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.253 DHCP Request dc:4f:22:8b:d5:59 10.44.57.253 **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.253 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.253 to use Access Point ZAGDU-789 **** Redirect appears successful Accepting MQTT connection, forwarding to not set DHCP Request f0:1f:af:19:56:20 f0:1f:af:19:56:20: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 13. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2884 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.85 DHCP Request dc:4f:22:8b:d5:59 10.44.57.85 **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.85 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.85 to use Access Point ZAGDU-789 **** Redirect appears successful DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 13. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2900 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.96 DHCP Request dc:4f:22:8b:d5:59 10.44.57.96 **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.96 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.96 to use Access Point ZAGDU-789 Unable to open socket to 10.44.57.96: Connection refused The device might be at the next stage, ignoring for now Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547868290,"e":false,"success":true} Receiving www request URL: /gw.json?a=tuya.device.dynamic.config.get Response: HTTP/1.1 200 OK {"result":{"validTime":1800,"time":1547868291,"config":{}},"t":1547868291,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 10. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2916 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.59 DHCP Request dc:4f:22:8b:d5:59 10.44.57.59 **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.59 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.59 to use Access Point ZAGDU-789 **** Redirect appears successful Accepting MQTT connection, forwarding to not set DHCP Discover dc:4f:22:8b:d5:59 10.44.57.59 DHCP Request dc:4f:22:8b:d5:59 10.44.57.59 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547868329,"e":false,"success":true} Receiving www request URL: /gw.json?a=tuya.device.dynamic.config.get Response: HTTP/1.1 200 OK {"result":{"validTime":1800,"time":1547868331,"config":{}},"t":1547868331,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 16. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2934 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.139 DHCP Request dc:4f:22:8b:d5:59 10.44.57.139 DHCP Request f0:1f:af:19:56:20 f0:1f:af:19:56:20: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 15. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2951 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.120 DHCP Request dc:4f:22:8b:d5:59 10.44.57.120 Accepting MQTT connection, forwarding to not set **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.120 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.120 to use Access Point ZAGDU-789 **** Redirect appears successful Accepting MQTT connection, forwarding to not set Receiving www request URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content URL: /gw.json?a=s.gw.upgrade.updatestatus Response: HTTP/1.1 200 OK {"t":1547868357,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 15. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2967 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.137 DHCP Request dc:4f:22:8b:d5:59 10.44.57.137 **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.137 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.137 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response DHCP Discover dc:4f:22:8b:d5:59 10.44.57.137 DHCP Request dc:4f:22:8b:d5:59 10.44.57.137 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547868386,"e":false,"success":true} Receiving www request URL: /gw.json?a=tuya.device.dynamic.config.get Response: HTTP/1.1 200 OK {"result":{"validTime":1800,"time":1547868387,"config":{}},"t":1547868387,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 20. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 2985 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.157 DHCP Request dc:4f:22:8b:d5:59 10.44.57.157 **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.157 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.157 to use Access Point ZAGDU-789 **** Redirect appears successful Accepting MQTT connection, forwarding to not set Receiving www request URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Accepting MQTT connection, forwarding to not set Receiving www request Fetching Request Content Timed out waiting for content DHCP Discover dc:4f:22:8b:d5:59 10.44.57.157 DHCP Discover dc:4f:22:8b:d5:59 10.44.57.157 DHCP Discover dc:4f:22:8b:d5:59 10.44.57.157 DHCP Request dc:4f:22:8b:d5:59 10.44.57.157 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 12. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3005 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.30 DHCP Request dc:4f:22:8b:d5:59 10.44.57.30 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.30 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.30 to use Access Point ZAGDU-789 **** Redirect appears successful DHCP Request f0:1f:af:19:56:20 f0:1f:af:19:56:20: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 13. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3023 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.38 DHCP Request dc:4f:22:8b:d5:59 10.44.57.38 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 29. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3039 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.51 DHCP Request dc:4f:22:8b:d5:59 10.44.57.51 Accepting MQTT connection, forwarding to not set **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.51 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.51 to use Access Point ZAGDU-789 Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 30. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3056 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.201 DHCP Request dc:4f:22:8b:d5:59 10.44.57.201 **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.201 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.201 to use Access Point ZAGDU-789 Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 29. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3072 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.234 DHCP Request dc:4f:22:8b:d5:59 10.44.57.234 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.234 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.234 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547868535,"e":false,"success":true} DHCP Discover dc:4f:22:8b:d5:59 10.44.57.234 DHCP Request dc:4f:22:8b:d5:59 10.44.57.234 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 46. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3091 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.34 DHCP Request dc:4f:22:8b:d5:59 10.44.57.34 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.34 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.34 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content URL: /gw.json?a=s.gw.upgrade.updatestatus Response: HTTP/1.1 200 OK {"t":1547868563,"e":false,"success":true} DHCP Discover dc:4f:22:8b:d5:59 10.44.57.34 DHCP Request dc:4f:22:8b:d5:59 10.44.57.34 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 35. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3109 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.246 DHCP Request dc:4f:22:8b:d5:59 10.44.57.246 DHCP Request 00:04:f2:a3:4a:76 00:04:f2:a3:4a:76: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 30. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3126 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.164 DHCP Request dc:4f:22:8b:d5:59 10.44.57.164 **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.164 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.164 to use Access Point ZAGDU-789 **** Redirect appears successful DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 30. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3142 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.100 DHCP Request dc:4f:22:8b:d5:59 10.44.57.100 **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.100 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.100 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response DHCP Discover dc:4f:22:8b:d5:59 10.44.57.100 DHCP Request dc:4f:22:8b:d5:59 10.44.57.100 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 34. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3161 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.134 DHCP Request dc:4f:22:8b:d5:59 10.44.57.134 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547868647,"e":false,"success":true} **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.134 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.134 to use Access Point ZAGDU-789 **** Redirect appears successful Receiving www request URL: /gw.json?a=tuya.device.dynamic.config.get Response: HTTP/1.1 200 OK {"result":{"validTime":1800,"time":1547868653,"config":{}},"t":1547868653,"e":false,"success":true} Receiving www request Fetching Request Content URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response DHCP Discover dc:4f:22:8b:d5:59 10.44.57.134 DHCP Request dc:4f:22:8b:d5:59 10.44.57.134 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 36. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3179 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.134 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.134 to use Access Point ZAGDU-789 Unable to open socket to 10.44.57.134: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.140 DHCP Request dc:4f:22:8b:d5:59 10.44.57.140 Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content URL: /gw.json?a=s.gw.upgrade.updatestatus Response: HTTP/1.1 200 OK {"t":1547868683,"e":false,"success":true} Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 30. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3195 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:d5:59 10.44.57.137 DHCP Request dc:4f:22:8b:d5:59 10.44.57.137 Received DNS query for fakewebsite. Sending 10.44.57.1 as response Receiving www request Sending firmware image_user2-0x81000.bin Receiving www request Sending firmware image_user2-0x81000.bin Sending bytes 239271-478490 from offset 0 **** New device detected. ID: 75070011dc4f228bd559 IP:10.44.57.137 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.137 to use Access Point ZAGDU-789 **** Redirect appears successful Accepting MQTT connection, forwarding to not set DHCP Discover dc:4f:22:8b:d5:59 10.44.57.137 DHCP Discover dc:4f:22:8b:d5:59 10.44.57.137 DHCP Request dc:4f:22:8b:d5:59 10.44.57.137 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 47. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.40 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3214 Redirecting device 192.168.1.40 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.40: No route to host The device might be at the next stage, ignoring for now DHCP Discover e4:f0:42:de:76:ee 10.44.57.195 DHCP Discover e4:f0:42:de:76:ee 10.44.57.195 Shutting down... Setting up IP Address 192.168.4.2 for Final Stages Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Setting up wifi scan Setting up listener for FinalStage ***** FinalStage Detected ****** ***** Connected to FinalStage ****** ***** Receiving FinalStage Request **** REQ: Client closed connection while receiving request: ***** Receiving FinalStage Request **** Sending firmware sonoff.bin ***** Tasmota Firmware sent to device ****** ***** FinalStage Detected ****** ***** Connected to FinalStage ****** ***** Found Sonoff AP sonoff-5465 ****** ***** Connected to sonoff-5465 ****** Sending config to sonoff-5465 ***** Config sent ***** Shutting down... Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Finished Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3297 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Request f0:1f:af:19:56:20 10.44.57.218 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 1. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3313 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover e4:f0:42:de:76:ee 10.44.57.166 DHCP Request f0:1f:af:19:56:20 f0:1f:af:19:56:20: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 1. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3330 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 DHCP Discover e4:f0:42:de:76:ee 10.44.57.86 DHCP Discover e4:f0:42:de:76:ee 10.44.57.86 Shutting down... Setting up IP Address 192.168.4.2 for Final Stages Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Setting up wifi scan Setting up listener for FinalStage Shutting down... Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Finished Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3371 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 **** Redirect appears successful DHCP Discover e4:f0:42:de:76:ee 10.44.57.219 DHCP Discover dc:4f:22:8b:a3:36 Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 12. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3386 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Request f0:1f:af:19:56:20 10.44.57.137 DHCP Discover dc:4f:22:8b:a3:36 Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 1. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3401 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.92 DHCP Request dc:4f:22:8b:a3:36 10.44.57.92 Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content URL: /gw.json?a=s.gw.upgrade.updatestatus Response: HTTP/1.1 200 OK {"t":1547869409,"e":false,"success":true} **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.92 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.92 to use Access Point ZAGDU-789 **** Redirect appears successful DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 14. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3417 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.126 DHCP Request dc:4f:22:8b:a3:36 10.44.57.126 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.126 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.126 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response DHCP Discover dc:4f:22:8b:a3:36 10.44.57.126 DHCP Request dc:4f:22:8b:a3:36 10.44.57.126 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 33. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3436 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.31 DHCP Request dc:4f:22:8b:a3:36 10.44.57.31 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.31 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.31 to use Access Point ZAGDU-789 **** Redirect appears successful Accepting MQTT connection, forwarding to not set DHCP Discover dc:4f:22:8b:a3:36 10.44.57.31 DHCP Request dc:4f:22:8b:a3:36 10.44.57.31 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547869470,"e":false,"success":true} Receiving www request URL: /gw.json?a=tuya.device.dynamic.config.get Response: HTTP/1.1 200 OK {"result":{"validTime":1800,"time":1547869471,"config":{}},"t":1547869471,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 35. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3455 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.191 DHCP Request dc:4f:22:8b:a3:36 10.44.57.191 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.191 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.191 to use Access Point ZAGDU-789 **** Redirect appears successful Accepting MQTT connection, forwarding to not set Receiving www request URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content Timed out waiting for content DHCP Request f0:1f:af:19:56:20 f0:1f:af:19:56:20: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 30. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3473 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.241 DHCP Request dc:4f:22:8b:a3:36 10.44.57.241 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.241 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.241 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Receiving www request URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content URL: /gw.json?a=s.gw.upgrade.updatestatus Response: HTTP/1.1 200 OK {"t":1547869526,"e":false,"success":true} DHCP Discover dc:4f:22:8b:a3:36 10.44.57.241 DHCP Request dc:4f:22:8b:a3:36 10.44.57.241 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 35. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3491 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.8 DHCP Request dc:4f:22:8b:a3:36 10.44.57.8 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547869548,"e":false,"success":true} **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.8 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.8 to use Access Point ZAGDU-789 **** Redirect appears successful Receiving www request URL: /gw.json?a=tuya.device.dynamic.config.get Response: HTTP/1.1 200 OK {"result":{"validTime":1800,"time":1547869554,"config":{}},"t":1547869554,"e":false,"success":true} Receiving www request Fetching Request Content URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response DHCP Request f0:1f:af:19:56:20 f0:1f:af:19:56:20: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 30. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3510 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover e4:f0:42:de:76:ee 10.44.57.66 DHCP Discover dc:4f:22:8b:a3:36 Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 30. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3525 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.107 DHCP Request dc:4f:22:8b:a3:36 10.44.57.107 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.107 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.107 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Receiving www request URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content URL: /gw.json?a=s.gw.upgrade.updatestatus Response: HTTP/1.1 200 OK {"t":1547869589,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 30. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3541 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.232 DHCP Request dc:4f:22:8b:a3:36 10.44.57.232 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.232 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.232 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response DHCP Discover dc:4f:22:8b:a3:36 10.44.57.232 DHCP Request dc:4f:22:8b:a3:36 10.44.57.232 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 36. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3559 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Request f0:1f:af:19:56:20 10.44.57.95 DHCP Discover dc:4f:22:8b:a3:36 Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 30. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3574 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.206 DHCP Request dc:4f:22:8b:a3:36 10.44.57.206 Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.206 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.206 to use Access Point ZAGDU-789 **** Redirect appears successful Accepting MQTT connection, forwarding to not set DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 30. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3590 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.193 DHCP Request dc:4f:22:8b:a3:36 10.44.57.193 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.193 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.193 to use Access Point ZAGDU-789 Unable to open socket to 10.44.57.193: Connection refused The device might be at the next stage, ignoring for now Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547869675,"e":false,"success":true} Receiving www request URL: /gw.json?a=tuya.device.dynamic.config.get Response: HTTP/1.1 200 OK {"result":{"validTime":1800,"time":1547869677,"config":{}},"t":1547869677,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 29. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3606 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.35 DHCP Request dc:4f:22:8b:a3:36 10.44.57.35 DHCP Request f0:1f:af:19:56:20 f0:1f:af:19:56:20: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 29. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3623 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.196 DHCP Request dc:4f:22:8b:a3:36 10.44.57.196 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.196 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.196 to use Access Point ZAGDU-789 **** Redirect appears successful DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 31. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3639 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.74 DHCP Request dc:4f:22:8b:a3:36 10.44.57.74 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.74 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.74 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response DHCP Discover dc:4f:22:8b:a3:36 10.44.57.74 DHCP Request dc:4f:22:8b:a3:36 10.44.57.74 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 34. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3657 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.139 DHCP Request dc:4f:22:8b:a3:36 10.44.57.139 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.139 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.139 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to not set Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content URL: /gw.json?a=s.gw.upgrade.updatestatus Response: HTTP/1.1 200 OK {"t":1547869765,"e":false,"success":true} DHCP Discover dc:4f:22:8b:a3:36 10.44.57.139 DHCP Request dc:4f:22:8b:a3:36 10.44.57.139 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 37. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3675 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.211 DHCP Request dc:4f:22:8b:a3:36 10.44.57.211 DHCP Request f0:1f:af:19:56:20 f0:1f:af:19:56:20: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 29. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3693 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.211 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.211 to use Access Point ZAGDU-789 Unable to open socket to 10.44.57.211: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.39 DHCP Request dc:4f:22:8b:a3:36 10.44.57.39 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 30. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3709 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.39 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.39 to use Access Point ZAGDU-789 Unable to open socket to 10.44.57.39: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.105 DHCP Request dc:4f:22:8b:a3:36 10.44.57.105 Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set Accepting MQTT connection, forwarding to not set DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 30. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3726 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.93 DHCP Request dc:4f:22:8b:a3:36 10.44.57.93 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.93 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.93 to use Access Point ZAGDU-789 **** Redirect appears successful Accepting MQTT connection, forwarding to not set DHCP Discover dc:4f:22:8b:a3:36 10.44.57.93 DHCP Request dc:4f:22:8b:a3:36 10.44.57.93 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547869861,"e":false,"success":true} Receiving www request URL: /gw.json?a=tuya.device.dynamic.config.get Response: HTTP/1.1 200 OK {"result":{"validTime":1800,"time":1547869862,"config":{}},"t":1547869862,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 34. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3744 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.94 DHCP Request dc:4f:22:8b:a3:36 10.44.57.94 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.94 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.94 to use Access Point ZAGDU-789 **** Redirect appears successful Accepting MQTT connection, forwarding to not set Receiving www request URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content URL: /gw.json?a=s.gw.upgrade.updatestatus Response: HTTP/1.1 200 OK {"t":1547869883,"e":false,"success":true} DHCP Discover dc:4f:22:8b:a3:36 10.44.57.94 DHCP Request dc:4f:22:8b:a3:36 10.44.57.94 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 36. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3764 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.213 DHCP Request dc:4f:22:8b:a3:36 10.44.57.213 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.213 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.213 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to not set Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Accepting MQTT connection, forwarding to not set DHCP Discover dc:4f:22:8b:a3:36 10.44.57.213 DHCP Request dc:4f:22:8b:a3:36 10.44.57.213 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 34. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3782 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.213 DHCP Request dc:4f:22:8b:a3:36 10.44.57.213 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.213 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.213 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to not set Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content Timed out waiting for content DHCP Discover dc:4f:22:8b:a3:36 10.44.57.213 DHCP Discover dc:4f:22:8b:a3:36 10.44.57.213 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 31. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3800 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.240 DHCP Request dc:4f:22:8b:a3:36 10.44.57.240 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.240 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.240 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Receiving www request URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response DHCP Discover dc:4f:22:8b:a3:36 10.44.57.240 DHCP Request dc:4f:22:8b:a3:36 10.44.57.240 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 34. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3819 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Request f0:1f:af:19:56:20 10.44.57.231 DHCP Discover dc:4f:22:8b:a3:36 Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 32. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3834 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.25 DHCP Request dc:4f:22:8b:a3:36 10.44.57.25 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 30. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3850 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.25 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.25 to use Access Point ZAGDU-789 Unable to open socket to 10.44.57.25: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.114 DHCP Request dc:4f:22:8b:a3:36 10.44.57.114 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547870027,"e":false,"success":true} Receiving www request URL: /gw.json?a=tuya.device.dynamic.config.get Response: HTTP/1.1 200 OK {"result":{"validTime":1800,"time":1547870027,"config":{}},"t":1547870027,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 32. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3867 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.65 DHCP Request dc:4f:22:8b:a3:36 10.44.57.65 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.65 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.65 to use Access Point ZAGDU-789 **** Redirect appears successful Accepting MQTT connection, forwarding to not set DHCP Request f0:1f:af:19:56:20 f0:1f:af:19:56:20: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 31. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3884 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover e4:f0:42:de:76:ee 10.44.57.181 DHCP Discover dc:4f:22:8b:a3:36 Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 30. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3899 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.201 DHCP Request dc:4f:22:8b:a3:36 10.44.57.201 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.201 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.201 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Receiving www request URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content URL: /gw.json?a=s.gw.upgrade.updatestatus Response: HTTP/1.1 200 OK {"t":1547870096,"e":false,"success":true} DHCP Discover dc:4f:22:8b:a3:36 10.44.57.201 DHCP Request dc:4f:22:8b:a3:36 10.44.57.201 DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 36. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3919 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.143 DHCP Request dc:4f:22:8b:a3:36 10.44.57.143 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547870119,"e":false,"success":true} **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.143 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.143 to use Access Point ZAGDU-789 **** Redirect appears successful Receiving www request URL: /gw.json?a=tuya.device.dynamic.config.get Response: HTTP/1.1 200 OK {"result":{"validTime":1800,"time":1547870125,"config":{}},"t":1547870125,"e":false,"success":true} Receiving www request Fetching Request Content URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response DHCP Request f0:1f:af:19:56:20 f0:1f:af:19:56:20: Unknown host Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 31. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3936 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.187 DHCP Request dc:4f:22:8b:a3:36 10.44.57.187 **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.187 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.187 to use Access Point ZAGDU-789 **** Redirect appears successful Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response DHCP Discover dc:4f:22:8b:a3:36 10.44.57.187 DHCP Request dc:4f:22:8b:a3:36 10.44.57.187 Received DNS query for mq.gw.tuyaus.com. Sending 10.44.57.1 as response Accepting MQTT connection, forwarding to mq.gw.tuyaus.com. Received DNS query for a.tuyaus.com. Sending 10.44.57.1 as response Receiving www request Fetching Request Content URL: /gw.json?a=atop.online.debug.log Response: HTTP/1.1 200 OK {"result":true,"t":1547870158,"e":false,"success":true} Receiving www request URL: /gw.json?a=tuya.device.dynamic.config.get Response: HTTP/1.1 200 OK {"result":{"validTime":1800,"time":1547870159,"config":{}},"t":1547870159,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 35. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3954 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.187 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.187 to use Access Point ZAGDU-789 Unable to open socket to 10.44.57.187: No route to host The device might be at the next stage, ignoring for now DHCP Discover a4:77:33:92:5b:0a 10.44.57.233 DHCP Request a4:77:33:92:5b:0a 10.44.57.233 DHCP Discover dc:4f:22:8b:a3:36 Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 28. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3970 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.11 DHCP Request dc:4f:22:8b:a3:36 10.44.57.11 Receiving www request Fetching Request Content URL: /gw.json?a=tuya.device.upgrade.silent.get Sent upgrade response Receiving www request Fetching Request Content URL: /gw.json?a=s.gw.upgrade.updatestatus Response: HTTP/1.1 200 OK {"t":1547870192,"e":false,"success":true} DHCP Discover e4:f0:42:de:76:ee Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 43. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 3987 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now **** New device detected. ID: 75070011dc4f228ba336 IP:10.44.57.11 **** New device looks to be part way through upgrading **** Forcing it to retry the upgrade Redirecting device 10.44.57.11 to use Access Point ZAGDU-789 Unable to open socket to 10.44.57.11: No route to host The device might be at the next stage, ignoring for now DHCP Discover dc:4f:22:8b:a3:36 10.44.57.123 DHCP Request dc:4f:22:8b:a3:36 10.44.57.123 Received DNS query for fakewebsite. Sending 10.44.57.1 as response Receiving www request Sending firmware image_user2-0x81000.bin Receiving www request Sending firmware image_user2-0x81000.bin Sending bytes 239271-478490 from offset 0 DHCP Discover dc:4f:22:8b:a3:36 10.44.57.123 DHCP Request dc:4f:22:8b:a3:36 10.44.57.123 DHCP Discover c4:1c:ff:93:89:c1 Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 46. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 4006 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Request f0:1f:af:19:56:20 10.44.57.42 DHCP Discover a4:77:33:92:5b:0a Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/arm-linux-gnueabihf/perl/5.24/Socket.pm line 157, <$fh> line 1. Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $ sudo ./tuyota.pl -ip 192.168.1.41 -s mySSID -p myPassword Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Using WiFi device wlan0 for Access Point Starting Access Point with SSID ZAGDU-789 Giving Access Point IP address 10.44.57.1, pid is 4021 Redirecting device 192.168.1.41 to use Access Point ZAGDU-789 Unable to open socket to 192.168.1.41: No route to host The device might be at the next stage, ignoring for now DHCP Discover e4:f0:42:de:76:ee 10.44.57.20 DHCP Discover e4:f0:42:de:76:ee 10.44.57.20 Shutting down... Setting up IP Address 192.168.4.2 for Final Stages Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Setting up wifi scan Setting up listener for FinalStage ***** FinalStage Detected ****** ***** Connected to FinalStage ****** ***** Receiving FinalStage Request **** REQ: Client closed connection while receiving request: ***** Receiving FinalStage Request **** Sending firmware sonoff.bin ***** Tasmota Firmware sent to device ****** ***** FinalStage Detected ****** ***** Connected to FinalStage ****** ***** Found Sonoff AP sonoff-0822 ****** ***** Connected to sonoff-0822 ****** Sending config to sonoff-0822 ***** Config sent ***** ***** Found Sonoff AP sonoff-0822 ****** ***** Connected to sonoff-0822 ****** Failed to connect to device sonoff-0822: No route to host Shutting down... Getting interface into stable state RTNETLINK answers: Cannot assign requested address Done Finished Exiting.... Shutting down... pi@raspberrypi:~/TuyOTA $