-
-
Notifications
You must be signed in to change notification settings - Fork 507
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to connect to vtrust-flash #551
Comments
Hi Jay, Can you check your |
Hi Colin,
Thanks for a quick turnaround on this. I'm attaching those logs.
Jay
…On Sat, Feb 22, 2020 at 5:13 PM Colin Kuebler ***@***.***> wrote:
Hi Jay,
Can you check your /scripts and /backup directories to see if you have
any *.log files?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#551?email_source=notifications&email_token=AEA3FGWPQ4I2AI45XXRPCUTREGPPJA5CNFSM4KZUPFEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMVLZIA#issuecomment-590003360>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEA3FGTTZEFFNZKMJORVVCLREGPPJANCNFSM4KZUPFEA>
.
|
i have the same problem. tried with 2 different devices. using debian stretch with wifi adaptor. smarthack-mqtt.log |
Are you able to successfully use the hotspot feature of the OS? |
If you have
|
Was that question for me? I haven't used it |
@kueblc: I just bought a raspberry pi 4b and installed Raspbian Buster Lite on it and ran the start_flash but this time I don't even see the vtrust_flash ssid. Please see the log attached. Am I missing wifi drivers? |
It's fixed and I was able to successfully flash one of the tuya switches I had. Not sure exactly what I did to fix it but couple of reboots and setting up wifi network through raspi-config fixed it for me. I will attempt to flash it on the VM again just to see if it works and post my update just so it helps others who are having the same issue |
Still unable to connect to vtrust-flash. What am I missing? |
I did note this in your log:
Which you can address with |
Hello, I seem to have the same problem, i've attached my file - although it seems related to "wlan0 could not connect to kernel driver" error instead, any idea how to fix that mr wise kueblc :) I tried your command with "rfkill unblock wifi" which seems to have removed that block, now i have the issue with the kernel... |
Don't worry about:
This is not a problem unto itself. Do you see |
Ok cool. It should just appear as a standard WiFi network right? |
Yeah now i see it, seems like your command worked after a bit of patience :) |
@kueblc I noticed that if I remove the setting --redirect-to-localhost setting in the line 20 of start_flash.sh. I'm able to connect to vtrust-flash with the VM approach but I'm still unable to flash. Does this help to understand what could be causing the issue? |
This could mean that the device you are connecting with expects an internet connection, and disconnects when it realizes there is none. However this is intended, we do not want a connection to the outside internet, so you must force the device to stay connected anyway. With my Android device, it might say something like "No internet connection, won't automatically reconnect", but if I manually reconnect after that it will stay. Do any other logs show activity? |
i'm using an iPhone to connect to the AP and it does allow to connect to networks which doesn't have internet connections. I have tried to connect to vtrust-flash from my windows laptop and it says unable to connect too. I know that the usb wifi adapter is capable of hosting an AP. I have tried following create_ap examples and I'm able to connect to the ap i made up. Also if I comment the below line it aloows me to connect to vtrust-flash. My guess is there is something happening in redirecting to the fake webserver created at 10.42.42.1 $screen_with_log smarthack-web.log -S smarthack-web -m -d ./fake-registration-server.py I will attach the logs in the next reply. wifi adapter that I am using |
Windows events: Interface name: Intel(R) Dual Band Wireless-AC 8265 Result of diagnosis: Problem found Root cause: Detailed root cause: Repair option: Root Cause: Wireless association to "vtrust-flash" failed for an unknown reason Root Cause Guid: {5c92e4e9-4699-418c-9db6-82d57dcbf59f} Repair option: Try connecting to "vtrust-flash" again |
For me the whole procedure is not working and I've debugged it down to the vtrust-flash SSID I understand that its using hostapd to create the SSID and dnsmasq to provide the dhcp addresses. What happens for me is that when I first try to connect my smartphone to the vtrust-flash network I don't get a sustained connection under Android 10. Andoid 10 keeps trying and failing. I tired an iOS smartphone, but it too is having difficulty. I am using a Pi 3B+ with Buster and all fixes applied Presumably if the smartphone (first device) can get a WiFo connection with valid 10.42.42..x address then it is pointless going to the next step where you try to talk to the power switch (in my case) --- log of session --- ./start_flash.shtuya-convert v2.4.3
|
I ran into the same issue and this fixed it for me! Just wanted to let you know. |
I've got an RPi4, I seem to have similar issues as above, no vtrust-flash network appearing. And the same start_flash log: Apologies as I'm really new to this, but I cannot seem to figure out how to obtain the log files. |
@dcolling check inside your |
running 'sudo rfkill unblock all' fixed this issue for me |
I have the same issue on RPi 4. I have flashed many devices with no problem using Ubuntu running on an old MacBook Pro, but I cannot connect to vtrust-flash with the Pi. I can see vtrust-flash but a connection is never established. I have tried with iPhone and also with a script running on another ESP8266. Configuring AP interface... |
I managed to get it working, I confirmed hostapd was working ok by doing this. It seemed to take a lot longer to connect to vtrust-flash than it does with my Ubuntu box, so I am not sure if I was just being impatient. |
I had kind of the same problem. I could (sometimes) see the SSID of the vtrust-flash. What worked for me (after many hours of not finding the bug whatsoever) was changing the Wifi channel of the network. You can do this by changing the value of "channel" in the file "scripts/hostapd.conf" to a value between 1 and 14 that fits best for your environment/neighborhood. I used the Wifi Analyzer app for finding empty channels. (https://play.google.com/store/apps/details?id=com.farproc.wifi.analyzer&hl=en) I live in a house with some shitty routers that wont search for empty channels but just use channel 1. So 3 other routers where simply just "louder" than the little wifi dongle I bought. Thought i'd share it in case someone runs into the same issue. |
I've tried all of the suggestions except for the create-ap. None of my devices will connect to the vtrust-flash AP. Running tuya-convert on a fresh Debian Buster with the Ralink RT5370 usb2.0 wifi adapter. smarthack-mqtt.log smarthack-psk.log smarthack-udp.log smarthack-web.log smarthack-wifi.log
|
Dear all, @RaumZeit shared following information, which has resolved my connection issue with vtrust-flash: |
Hey @kueblc!
Thanks for the amazing work you have done on this project and your continued support.
I'm having issues connecting to the SSID vtrust-flash which is being broadcasted, my phone says unable to connect.
I've tried with both Ubuntu 18.04 and Raspberry Pi desktop running on Oracle VM VirtualBox. For the wifi adapter I'm using Ralink RT5370. I've tried both docker image and regular start_flash.sh method and got stuck at the same step where I'm supposed to connect to vtrust-flash on my phone.
Let me know if you need more information. Appreciate your help and support.
Thanks
Jay
Checking for network interface wlan0... Found.
Checking UDP port 53... Occupied by dnsmasq with PID 2227.
Port 53 is needed to resolve DNS queries
Do you wish to terminate dnsmasq? [y/N] y
Attempting to stop dnsmasq.service
Checking UDP port 67... Available.
Checking TCP port 80... Available.
Checking TCP port 443... Available.
Checking UDP port 6666... Available.
Checking UDP port 6667... Available.
Checking TCP port 1883... Occupied by mosquitto with PID 2484.
Port 1883 is needed to run MQTT
Do you wish to terminate mosquitto? [y/N] y
Attempting to stop mosquitto.service
Checking TCP port 8886... Available.
sudo: ufw: command not found
Starting AP in a screen...
Starting web server in a screen
Starting Mosquitto in a screen
Starting PSK frontend in a screen
Starting Tuya Discovery in a screen
======================================================
IMPORTANT
This step is IMPORTANT otherwise the smartconfig may not work!
Make sure nothing else is plugged into your IoT device while attempting to flash.
^C======================================================
The text was updated successfully, but these errors were encountered: