Disappearing TeslaPW_xxxxxx AP #669
-
|
TeslaPW_xxxxxx AP was working at approx 3pm then just disappeared. It had re-appeared however when attempting to join via iphone it was saying either incorrect password or unable to join. Try to connect via wifi on Powerwall Dashboard host getting auth_failures=1 duration=10 reason=CONN_FAILED followed soon after with CTRL-EVENT-ASSOC-REJECT status_code=1 . I know 100% that the password is correct. Ihave shutdown the dashboard host to stop any further connection attempts until such time as I am able to successfully connect via iphone. As I am drafting this I am unable to see the AP via a SSID scan from any host, although I could approx 30 minutes ago. The PW3 is on firmware 25.18.1 which was updated a few weeks ago. I have powered off via the side switch and was about to do a full power down until I stumbled across a reddit thread where a user had the same issue but had no luck when the system came back up. https://www.reddit.com/r/Powerwall/comments/1lu2u9s/pw3_local_wifi_no_longer_accessible/ The PW3 is connected to my home network via wifi and ethernet. It has been like this since day 1. I can ping both addresses without issue. Another observation is that if I re-establish the static route for 192.168.91.0/24 via ethernet i can ping 192.168.91.1 and open a port to 443. Obviously post 25.10.x firmware I can not get any data this way. I am at a loss to understand WTH is going on. I don't believe that the issue lies with my infra as multiple clients exhibit the same symptom. I'm over this crap with Tesla and the constant game of "whackamole". This is our kit, not theirs! If anyone who comes across this has any tips as to how to re-connect to the TeslaPW_xxxxxx I'm all ears. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
|
I saw your update in #651 (comment) - I know this whackamole game is difficult with the PW AP. Besides trying to keep using it less (some of the recent pypowerwall updates), it's not clear to me what we can do to make it better. Let me know if you have any suggestions. |
Beta Was this translation helpful? Give feedback.
-
|
I don't kow, I think that whats happening is like trying to put a bandaid on an axe wound, the axe wound of course is the unreliable Tesla AP. This is how I have pypowerwall configured: PW_EMAIL= I would like to know what the trigger is, there must be one. Are we submitting too many API requests, is there a finite number of clients that can be simultaeniously connected (previously I had 2, 1 via a router running OpenWrt that is configured to use wifi as a client for wwan with a static IP, ethernet as LAN on my subnet & also a NUC that had a direct wifi connection, also with a static IP to avoid the hourly disconnects when the DHCP lease would get renewed). Both exhibited similar symptoms. These are rhetorical questions of course. Any other oprational considerations that may induce this behaviour, I just don't know. The AP should be robust enough to not have to think about these things. Also, if it fell into the category of "it just works", there would be no need for multiple clients (as a backup & also diagnostics to see if there are similarities with the erratic behaviour). Just wish that Tesla could get their ducks in a row. |
Beta Was this translation helpful? Give feedback.
-
|
I have multiple systems connecting to my PW2 systems via WiFi without problems. Other PW2 owners report similar robust access, others report very flakey WiFi. I originally attributed that to either distance to AP or some WiFi channel congestion (which is still very possible) but I'm also going to add that I think Tesla frequently changes hardware even in the same models (you never know what you get). And it does seem that PW3 owners have a much more difficult time. That seems plausible as Tesla's general first principles approach would mean to use cheaper components that work good enough, so more recent versions may be lower quality as long as they meet designed goals (e.g. WiFi only needed for installation). In any case, reducing the frequency of pings (increase cache time PW_CACHE_EXPIRE for example) could help as it reduces load and traffic on the AP. |
Beta Was this translation helpful? Give feedback.
-
|
UPDATE: Almost a week now without issue. Got this thing bending to my will. |
Beta Was this translation helpful? Give feedback.
UPDATE:
Almost a week now without issue. Got this thing bending to my will.
#651 (comment)