Skip to content
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

Device hangs with 1.05 #227

Open
SylvainGa opened this issue Feb 28, 2023 · 6 comments
Open

Device hangs with 1.05 #227

SylvainGa opened this issue Feb 28, 2023 · 6 comments

Comments

@SylvainGa
Copy link

When my devices were using HASP 0.40 for over a year, they were rock solid. Never had a device hang. Now that I've upgraded to 1.05, all of them (I have four) have at least hung once and that is just in a few months. The screen is unresponsive (well, it register the press but that's it) and its web interface isn't working either. It takes a breaker reset to bring them back. What should I try to try to troubleshoot what's going on? Thanks.

@aderusha
Copy link
Collaborator

Without logs we're kind of shooting blindly for a solution. That is an annoying answer, because that means running the device for months on USB to see what the log output looks like when an event happens, but without some sense of what is actually happening on the device, we don't really have anything to go on.

The only other external factors you might be able to play with when the device is in a hung state:

  • Disable your WiFi to force HASP into attempting a reconnection
  • Try sending MQTT commands to see if it's still reacting (I'd guess not but maybe?)

Any chance you can let one run on USB for a spell to help track this down?

@SylvainGa
Copy link
Author

Thanks for the reply. Since that message, one of the frozen screen changed from frozen at the 'Scenes' page to frozen at "Connected to MQTT / Connected to Wifi" for a few days and yesterday, it's responsive again. That's the device I wanted to disconnect and plug it through USB.

One question, on Windows, I can't get the logs at boot since when I connect the USB cable, the serial terminal I'm using (Termite) do not know about the virtual serial port until it's connected and by the time I activate it, the boot data is long gone. Do you know of a serial terminal program that doesn't have that limitation or a way to hard reboot a hung Wemos D1 while maintaining its serial port connection?

@aderusha
Copy link
Collaborator

aderusha commented Mar 7, 2023

I do! I've been using SimplySerial which is a window terminal app that will handle disconnect/reconnect and can usually pick up boot messages.

@jwhamlin244
Copy link

Hello. recently purchased a preassembled unit and about once ever few days I think I'm having this same issue.
The device itself responds to my touch. I can move sliders, and I can see the button text color change when I touch it. However, nothing ultimately happens. Screens do not change, control of my devices is nonexistent.

Only way I can get it to resolve is by turning my breaker off and on to reboot the entire device.
Is it an issue with MQTT? I have attempted to stop my broker entirely to see if the device reverts to the 'connecting' screen, but it does not..

@aderusha
Copy link
Collaborator

aderusha commented Oct 3, 2023

One common situation we've encountered are problems with the WiFi. @jwhamlin244 would it be possible to try and reboot the WiFi AP that your HASPone is attached to and see how it responds?

@jwhamlin244
Copy link

@aderusha I have turned off my router -> no change on haspOne -> restarted router -> still no change on haspOne.
I have not noticed any internet issues, although i can't rule out that it has never blipped out without me noticing at some point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants