Replies: 7 comments 16 replies
-
|
Well that's no good. Are these in the wall? Do you have any way to hook them up to USB and watch serial debug messages? |
Beta Was this translation helpful? Give feedback.
-
|
I'm not getting a COM port at all. Tried different USB ports and another cable. |
Beta Was this translation helpful? Give feedback.
-
|
That's pretty odd :| When plugging in both devices, you don't see a COM port being created? Do you get the device insert notification sound from Windows (presuming here you're running Windows)? Did you purchase these assembled from me or was this your own build? |
Beta Was this translation helpful? Give feedback.
-
|
Yeah bought pre-assembled and there is no activity on the pc side. No bonk usb plugged in or unplugged noises, no movement in device manager. Pulled the other unit from the wall last night and same behavior, blue light sometimes flashes once when plugged in, other times flashes constantly, and sometimes the screen flashes initializing. I tried all the ports on my laptop, I didn't try another pc but I can later. It's acting like it was bricked from the fw update but it was up for a little bit after it took it. But this happened the next reboot after the update, maybe the bug took after a reboot. |
Beta Was this translation helpful? Give feedback.
-
|
In that case, I think the best solution will be for me to send you out a couple of replacements, along with a return label to send these two units back. No idea what's happened here and your experience isn't typical. I don't want to waste more of your time trying to troubleshoot something that should have arrived in working order! If you can give me your order number I can get this sent out by tomorrow at the latest. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, thank you for all your help. It was purchased a while ago but we were doing a remodel so it was just now implemented. My order is #193470. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Allen, I apologize for not getting back to you sooner. I received the
replacement parts and put them together, they worked right away then I got
busy with selling my house and my server needed to be redone. When I
finally got to mess with these I connected one of them to my wifi and mqtt
and it went to reboot and never came back on. It did the same damn thing. I
didn't want to even think about these stupid things for a bit so I left the
second one alone.
So #2 has only had the new board connected physically with no configuration
done. I would like to coordinate with you on how to proceed. I can't
imagine I'm doing anything wrong here in that the only thing I'm doing is
entering my wifi and mqtt information but I don't want you to think I'm
trying something funny here.
I don't know if you want to do something over video chat or just send these
old ones back so you can test them out. Again, I'm sorry for the delay.
Please let me know what we should do here, you have my full cooperation
with however you want to proceed.
…On Thu, Apr 15, 2021, 8:00 AM Allen Derusha ***@***.***> wrote:
In that case, I think the best solution will be for me to send you out a
couple of replacements, along with a return label to send these two units
back. No idea what's happened here and your experience isn't typical. I
don't want to waste more of your time trying to troubleshoot something that
should have arrived in working order!
If you can give me your order number I can get this sent out by tomorrow
at the latest.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#78 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATUJXQ3FW77MT2GAW2B3PYDTI3POJANCNFSM422O6X7A>
.
|
Beta Was this translation helpful? Give feedback.
-
|
Let's start with #1 just because it's in a known problem state and figuring out what is happening there is likely to be step 1 in figuring out what's going on overall. So, back to getting that plugged into a PC and getting debug logs. If you aren't seeing a COM port, I think I can now safely say that something is going wrong on either the PC end or the USB cable you are using. What OS are you running on your PC? Also, did you get a chance to return the existing unit? The tracking on the RMA label I sent you suggests it never hit the mail. |
Beta Was this translation helpful? Give feedback.
-
|
So I'm not sure how much this makes a difference, but I am unable to get
into the web config to enable USB debugging. But still trying to connect it
to my Windows PC, I get "USB serial" in device manager with no driver
isntalled and the yellow exclamation point icon. Does it typically install
the driver automatically
If I manually install it with Microsoft USB serial driver I get com3 but
when I try to putty with the settings in the guide you linked before but it
is unable to connect.
I tried multiple USB cables and ports, I don't know what PC issue it could
be, but I am not ruling out pebkac error cause I haven't used Putty often
and I'm not sure if I used the right driver.
I have not shipped the old devices back yet, but I have a long weekend so I
can get it done asap.
[image: image.png]
[image: image.png]
[image: image.png]
…On Thu, Jul 1, 2021 at 9:20 AM Allen Derusha ***@***.***> wrote:
Let's start with #1 just because it's in a known problem state and
figuring out what is happening there is likely to be step 1 in figuring out
what's going on overall.
So, back to getting that plugged into a PC and getting debug logs. If you
aren't seeing a COM port, I think I can now safely say that something is
going wrong on either the PC end or the USB cable you are using. What OS
are you running on your PC?
Also, did you get a chance to return the existing unit? The tracking on
the RMA label I sent you suggests it never hit the mail.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#78 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATUJXQZCH4FVF6SSWFPERNDTVR2SPANCNFSM422O6X7A>
.
|
Beta Was this translation helpful? Give feedback.
-
|
Allright so first thing we need to do is to get your system talking to the serial device. Take a look at this guide for what's going on and some links to suitable drivers for the CH340 USB-to-serial bridge used on the Wemos boards. Windows should have this cooked in, but if for whatever reason it's not deploying the right driver (MS serial driver is for sure not going to work). Once you have that driver installed you should be able to see serial messages, which are enabled by default in the HASPone firmware. This should help you out a bit, the serial debug messages will tell us exactly what's going on with your setup and probably give us enough info to get you up and running! |
Beta Was this translation helpful? Give feedback.
-
|
Ok, the driver installed fine and initially I was just getting a blank
screen in Putty. After some messing with it and testing with the working
unit. I get a very rapid loop of this. I can't tell what all info is in
here, I tried to grab different screenshots to hopefully get all the info
it's providing.
[image: image.png]
[image: image.png]
[image: image.png]
[image: image.png]
…On Fri, Jul 2, 2021 at 7:52 AM Allen Derusha ***@***.***> wrote:
Allright so first thing we need to do is to get your system talking to the
serial device. Take a look at this guide
<https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all#drivers-if-you-need-them>
for what's going on and some links to suitable drivers for the CH340
USB-to-serial bridge used on the Wemos boards. Windows should have this
cooked in, but if for whatever reason it's not deploying the right driver
(MS serial driver is for sure not going to work). Once you have that driver
installed you should be able to see serial messages, which are enabled by
default in the HASPone firmware.
This should help you out a bit, the serial debug messages will tell us
exactly what's going on with your setup and probably give us enough info to
get you up and running!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#78 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATUJXQYRHWE4XE3IMMRIA4DTVWZADANCNFSM422O6X7A>
.
|
Beta Was this translation helpful? Give feedback.
-
|
Any chance you can post those screenshots somewhere where we can take a look? Copy+pasting the text should work too. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, here you go. |
Beta Was this translation helpful? Give feedback.
-
|
Based on that, either you have a bad flash or the USB port you are plugged into isn't providing enough voltage to run the board. You can try re-flashing, or maybe try another port, USB cable, or a different computer. |
Beta Was this translation helpful? Give feedback.
-
|
I've received the returned PCBs (thanks!) which are both behaving as you've shown above, where the device is stuck in a boot loop due to what appears to be a bad firmware flash. Here's the good news - following this guide restored both devices to service and both are now working as expected. Can you give that a shot and see if it helps you at all? |
Beta Was this translation helpful? Give feedback.
-
|
Hey Allen, yeah I was able to flash it and it did come back. So I have 2
ready to be connected but I haven't had time to mess with it more. I'll let
you know when I get those connected to my server. I appreciate the help.
…On Thu, Jul 1, 2021, 9:20 AM Allen Derusha ***@***.***> wrote:
Let's start with #1 just because it's in a known problem state and
figuring out what is happening there is likely to be step 1 in figuring out
what's going on overall.
So, back to getting that plugged into a PC and getting debug logs. If you
aren't seeing a COM port, I think I can now safely say that something is
going wrong on either the PC end or the USB cable you are using. What OS
are you running on your PC?
Also, did you get a chance to return the existing unit? The tracking on
the RMA label I sent you suggests it never hit the mail.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#78 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATUJXQZCH4FVF6SSWFPERNDTVR2SPANCNFSM422O6X7A>
.
|
Beta Was this translation helpful? Give feedback.
-
|
Just as a +1 here... I had the same thing happen to a device I just received yesterday, but following these flashing instructions got it back on track! It'd be great if the USB port were accessible from the side of the box, but I totally understand why it was not. Overall, 20 minutes and I'm back. |
Beta Was this translation helpful? Give feedback.
-
|
NEC doesn’t allow for any ingress into the enclosure so that port has to stay covered. Annoying that the FW upgrade didn’t work but glad to hear you’re sorted! |
Beta Was this translation helpful? Give feedback.
-
I just setup 2 haswitchplates. I got them connected to wifi and I'm pretty noob to home assistant but I managed my way through getting them detected by MQTT in my HA. I updated the firmware on them patiently one at a time. Then decided I didn't like how I named them and impatiently changed the name, saved, and rebooted them one right after another; I don't think doing that so close would matter, but that's what happened.
Now they both are just black. No detection in HA or MQTT, no ping response. It's pretty weird both went down at the same time. I hope someone has an idea of what to do, I felt like I was finally getting some progress then 💩 .
Beta Was this translation helpful? Give feedback.
All reactions