TMC is an independent, primarily volunteer organization that relies on ad revenue to cover its operating costs. Please consider whitelisting TMC on your ad blocker and becoming a Supporting Member. For more info: Support TMC

Tesla Energy says there are no "Tesla Powerwall Certified Installer" licensed in the State of Nevada

Discussion in 'Tesla Energy' started by M Mode, Mar 29, 2018.

  1. M Mode

    M Mode New Member

    Joined:
    Mar 24, 2018
    Messages:
    3
    Location:
    Crystal Bay, NV
    I have been planning to install a Powerwall system in our new house under construction in North Lake Tahoe (Nevada side) and was initially directed to an "Inside Energy Advisor" based in Las Vegas who I communicated with for a few months starting 6/1/17 before he disappeared. After learning the advisor was gone, I made a Powerwall Reservation after consulting the electricians on our new house build (12/1/17). I called Tesla explaining our timing was approaching and they told me someone would be contacting me within 30 days. I called them again and they professed that they have no "Tesla Powerwall Certified Installer" licensed in the state of Nevada, and they don't know when they will. Being proactive, I convinced our electrical contractor to apply to TE to become a certified installer. The application was lengthy. That was a couple months ago and my contractor has as yet to hear back from Tesla Energy.

    I am curious to know what anyone else in Nevada has experienced with Powerwall reservations.
     
  2. FlyF4

    FlyF4 Son of a MX

    Joined:
    Mar 21, 2017
    Messages:
    822
    Location:
    moved to San Diego
    Hey, but we have plenty of desert in Nevada !!!

    On a more serious note, I'm waiting for the same thing up here.
     
  3. Shygar

    Shygar Member

    Joined:
    Aug 7, 2017
    Messages:
    924
    Location:
    Pleasant Hill, CA
    Guess you can build them in NV but not install them?
     
    • Funny x 3
  4. Michael_R

    Michael_R Member

    Joined:
    Mar 31, 2018
    Messages:
    6
    Location:
    Las Vegas, NV
    Not Sure who you were speaking with, But we just had our system installed Feb 21 2018, with a 5 kwh Solar array and 1 powerwall2. Another was installed the week before. We were the first one to pass the city inspection and was able to turn on Wed March 28th. So they have a least one installer here in vegas. Our Powerwall is only being able to charge to 57%. Have seen that has been an issue. Waiting for a response from Tesla. Sent Email and Called, waiting on response. But it seems from this is maybe a sensor issue.
     
  5. M Mode

    M Mode New Member

    Joined:
    Mar 24, 2018
    Messages:
    3
    Location:
    Crystal Bay, NV
    Michael_R, Can you tell me who the installer is?
     
  6. Michael_R

    Michael_R Member

    Joined:
    Mar 31, 2018
    Messages:
    6
    Location:
    Las Vegas, NV
    tesla solar city. The battery was finally replaced on May 31st, and is now working like it is supposed to. Which is great, but I have seen no reason to not be wary of the bad Customer service. I really wanted to support tesla. I do believe solar is the way. The installers were great, i just have no faith in the warrenty or reponse from tesla. SO do so at your own risk. (they did replace, the battery, so mixed feelings)
     
  7. Lloyd

    Lloyd Well-Known Member

    Joined:
    Jan 12, 2011
    Messages:
    6,187
    Location:
    San Luis Obispo, CA
    So I have an installation date for my Tesla Solar roof in October 2019 in the slate configuration. Recently News appeared that the Slate configurations was sent back to design due to obvious differences between the active and non-active slates. We have been planning construction as a new home for some time and reserved this roof after the initial release. I have made no less than 6 calls to tesla energy requesting assistance with conduit placement and design with no return of calls or emails.

    Today I got a call from a Tesla representative trying to sell me solar. Well my current home is Net Zero, so I don't need any. I vented and requested a call from someone knowledgeable and able to provide assistance with our new construction. I spent an hour describing what we need and was advised to send copies of plans to "[email protected].

    Hi Lloyd,



    Thank you for your time on the phone today, as mentioned please email [email protected]

    Describe what your plans are subject to be and all of the concerns with our solution being available for you at your time of construction.



    We are currently only doing smooth and textured style roof shingles projects for selective customers.



    Attached is some examples of what is considered in the overview aspects of our solar roof tiles and what a design layout looks like.

    Please keep in mind that a real and or virtual site survey of your home is required since there are many variables to be discussed before getting into design(s) review.



    As I mentioned, we will be looking at more details as certain type of Tesla solar roof tiles/shingles becomes available later this year and next.

    All information supplied is subject to change, thank you in your consideration for our solar roof tiles as a clean energy solution.



    Solar Roof has a 30-year solar module and weatherization warranty and an infinite glass warranty.

    We are here to support you with any questions during that time. You can reach us at 1.877.798.3752



    Here is a quick video to see the Tesla Solar Roof Tiles up close

    https://youtu.be/BhDrazgGswk



    You can get a solar roof estimate per our website here, also place your reservation order today, and don’t worry your deposit is refundable.

    Tesla Solar Roof



    Again, thank you for patience as we will ramping up to complete more solar roof projects.



    Regards,



    Tony Pace | Advisor

    367 Newport Center Drive, Newport Beach, CA 92660

    C: 949.357.3857 | [email protected]


    Per their recommendation I sent the following:

    Dear Tesla,

    I was advised to write to you after many attempts to get a call back from the Tesla energy department.

    We have schedule construction to begin in the spring for the attached house which we have had a solar roof in the slate configuration reserved for some time. Our install still shows Sept to Oct, 2019. I understand that the slate configuration has gone back to the drawing board to be less visible to the active shingles.

    We are committed to wait until your product is available. In the meantime, we need some direction to essential and non-essential loads. Conduits to the roof area to avoid external conduits on the new construction as well as connections to our generator for secondary backup. Partial install with the powerwalls should be available prior to our completion of construction.

    In the event that your roof is not available for install. What specific measures should we provide for temporization and occupancy of the roof until your roof is available. Understand that our HOA provides penalties for incomplete construction monthly following one year from beginning. Additionally the HOA has allowed ONLY the slate configuration of your tiles.


    I received the following response from Tesla:


    [​IMG]
    Your message to [email protected] couldn't be delivered.
    The group newhomes only accepts messages from people in its organization or on its allowed senders list, and your email address isn't on the list.
    marcair1tc Office 365 newhomes
    Sender Action Required

    Sender not allowed

    How to Fix It
    It appears you aren't in the same organization as the group (or a sub-group) you're sending to or your email address isn't on the group's allowed senders list. Ask the owner of the group to grant you permission to send to it, and then try again. If the group belongs to a different organization than yours, contact the organization's customer service department for assistance. If the group is in your organization and you don't know who the group owner is, you can find it by doing the following in either Outlook on the web or Outlook:
    • Open your Sent folder and select the original message.
    • If you're using Outlook on the web, select the group name located on the To or CC line. If you're using Outlook, double-click the group name located on the To or CC line.
    • In Outlook on the web, from the pop-up dialog box, choose Owner. In Outlook, choose Contact. The owner's name is listed under Owner.
    The owner of the group may have intentionally chosen to restrict who can send messages to it, and they may not want to adjust the existing restriction. In this case, you'll have to contact the group members by some other means, such as sending an email message to their individual email addresses or contacting them by phone.

    Was this helpful? Send feedback to Microsoft.

    More Info for Email Admins
    Status code: 550 5.7.133

    This error occurs when the distribution group, security group, or Office 365 group is configured to accept messages only from authenticated senders (senders in the same organization or those added to the group's allowed senders list).

    To fix the issue, the recipient's email admin or the group owner must add the sender's email address to the group's allowed senders list or change the group's delivery management setting to accept messages from senders inside and outside of the organization.

    Usually this issue can only be fixed by the recipient's email admin or the group owner.

    For more information and steps to fix this error, see Fix email delivery issues for error code 5.7.133 in Office 365.

    Original Message Details
    Created Date: 2/16/2019 2:52:12 AM
    Sender Address: [email protected]
    Recipient Address: [email protected]
    Subject: New Construction Scheduled

    Error Details
    Reported error: 550 5.7.133 RESOLVER.RST.SenderNotAuthenticatedForGroup; authentication required; Delivery restriction check failed because the sender was not authenticated when sending to this group
    DSN generated by: BLUPR16MB0355.namprd16.prod.outlook.com

    Message Hops
    HOP TIME (UTC) FROM TO WITH RELAY TIME
    1 2/16/2019
    2:52:17 AM sonic.gate.mail.ne1.yahoo.com sonic310.consmr.mail.ne1.yahoo.com HTTP 5 sec
    2 2/16/2019
    2:52:18 AM sonic310-23.consmr.mail.ne1.yahoo.com mx0a-0019bd01.pphosted.com ESMTP 1 sec
    3 2/16/2019
    2:52:21 AM pps.filterd mx0a-0019bd01.pphosted.com SMTP 3 sec
    4 2/16/2019
    2:52:21 AM mx0b-0019bd01.pphosted.com BY2NAM03FT005.mail.protection.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) *
    5 2/16/2019
    2:52:22 AM BY2NAM03FT005.eop-NAM03.prod.protection.outlook.com MW2PR16CA0010.outlook.office365.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 1 sec
    6 2/16/2019
    2:52:22 AM MW2PR16CA0010.namprd16.prod.outlook.com BLUPR16MB0355.namprd16.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *

    Original Message Headers

    Received: from MW2PR16CA0010.namprd16.prod.outlook.com (2603:10b6:907::23) by
    BLUPR16MB0355.namprd16.prod.outlook.com (2a01:111:e400:c468::13) with
    Microsoft SMTP Server (version=TLS1_2,
    cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1622.16; Sat, 16 Feb
    2019 02:52:22 +0000
    Received: from BY2NAM03FT005.eop-NAM03.prod.protection.outlook.com
    (2a01:111:f400:7e4a::207) by MW2PR16CA0010.outlook.office365.com
    (2603:10b6:907::23) with Microsoft SMTP Server (version=TLS1_2,
    cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1622.16 via Frontend
    Transport; Sat, 16 Feb 2019 02:52:22 +0000
    Authentication-Results: spf=softfail (sender IP is 148.163.155.1)
    smtp.mailfrom=aol.com; tesla.com; dkim=fail (body hash did not verify)
    header.d=aol.com;tesla.com; dmarc=fail action=oreject header.from=aol.com;
    Received-SPF: SoftFail (protection.outlook.com: domain of transitioning
    aol.com discourages use of 148.163.155.1 as permitted sender)
    Received: from mx0b-0019bd01.pphosted.com (148.163.155.1) by
    BY2NAM03FT005.mail.protection.outlook.com (10.152.84.94) with Microsoft SMTP
    Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id
    15.20.1580.10 via Frontend Transport; Sat, 16 Feb 2019 02:52:21 +0000
    Received: from pps.filterd (m0127436.ppops.net [127.0.0.1])
    by mx0a-0019bd01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x1G2m57Q027299
    for <[email protected]>; Fri, 15 Feb 2019 18:52:21 -0800
    Authentication-Results-Original: ppops.net; spf=pass
    [email protected]; dkim=pass header.d=aol.com header.s=a2048;
    dmarc=pass header.from=aol.com
    Received: from sonic310-23.consmr.mail.ne1.yahoo.com (sonic310-23.consmr.mail.ne1.yahoo.com [66.163.186.204])
    by mx0a-0019bd01.pphosted.com with ESMTP id 2qp94ag463-1
    (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT)
    for <[email protected]>; Fri, 15 Feb 2019 18:52:18 -0800
    DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aol.com; s=a2048; t=1550285537; bh=uby1HjNKOD7zegm4sJjqV/tgyVhvFZZy4avlyKC1ke8=; h=Date:From:To:Cc:Subject:References:From:Subject; b=DrbjkC/WtP1MleYOqu+aqWv9oSrNZOxKXckwsn4FstjwNJhJsW+NRkSpehtiQwv4NsA+sIFHjB8UnyeIlkvEX1c0nNzR9u0sPeua2StIEKlQlQ1m85avBt8qCETNyaQA9smWy/8StApKhezJ2LmGbeycbxHhWVvcbvPpzLTQlgCZ54WJ+W/CogNfHML5Wf7pNsau8v6idIggpHsEa/+0Fqma7rVkU0p5WFSg+2p/OTzPvHJl1ZY2o35I9Wwl7ZybIVziw9fqJRIQmcuI+S+XOvIzwNZAr4zMkXR+OE0K126uPxcqnG/agYsGJYgHakr4AICnbzBf6mhSOTkDTJRsHA==
    X-YMail-OSG: pSNMsfYVM1k4IOFdMdkHW92f7i3r3eRhWRsJudH9FxQh.SwTse19770E49P4zvn
    wIOWDZbkoF8VBNmYMxcw9jE6PwB3YakVnocqYuy6PB0xDhw8QFJ8jc97pzxCHMdffZHzXnRNW.Ri
    m6t24lAit0iLrY0jn5JfzwNiGSqehh6Tve_oNhWz05J0ZNjAmYNC.r3KGwyhRz_I964TnLtYeKiD
    ..7Bli8O9KWxnxwe4GEDWM8J1W0rWMoRhDKytp.EpvBx63zCZgJO3JlF57SG8Z.PKLjUPTEivvG.
    S_d4akWv_4CUYlSq6389rEnBGn35FKdGlUsv2W_ufCn8dc24Du8O1nMrZ6.PCNdWkBs4XcxDy0Rr
    pai1Ijf9HzAdrDvcwJSHBmi0Iu2HS5TOEbBEYjLyaY0gZxQFuA5hoYu6AE1ojvtoC.HK0oc1GCD6
    Peve5SyZtVxY90jzeMSZwr2HEJgZOAP.B41r9qtZAqCvsnA7htzveEl0x55.TYqHDzrRIKuTW5mg
    qqYjDJRlmQt3qFZH23h2Ihe0H8U0mKS9O6.jKmisPdysfFdM5D60OvAq_UGo86BVOqvJkgeFY0hF
    4Q1lMVk04ZpGQHRdsmmwQ5hFizuhaO8BLmo4SNKz7NTzDJysErd8b7Spzag76e_nIxH2ZW3miHrp
    rzAJGCtP8Q4Pe9LsXmocFe5TqwXJHlMdnVkdWWA8Ut6sHwc1gXrQCtDkILTtp0kBtgm6TCfsxCDr
    YA4BJ4m_kJpzpUDpDBhtsnkgP6JlrQ3PRjoQL2kItxPDdw5rUWQvuAW9XwDt_T8hztFg9C6RWqAg
    h9KijvwPqA6.qhg5.XonrN_WC_MDebVZowVrPhrSvTnwDfEEJOoEeyjBS2arK7g.h1Nk2XdaGPzD
    vdAv5wCT0uccWSLN4CD8RntQDBiYkTmAR3qlsIUFHoLlH1.uuXamYowCVPqtnU74NunVBvIoRwLu
    el9OTDyMwixy9McLKsA6kT21dJD30qgUpG0lEzxNFNbhT9YaymHU.6IGvbal9ml_g8f9Ii_JpGPM
    5fwhnzOAHs3qH1tKZvk7b
    Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.ne1.yahoo.com with HTTP; Sat, 16 Feb 2019 02:52:17 +0000
    Date: Sat, 16 Feb 2019 02:52:12 +0000 (UTC)
    From: "Lloyd Marcum, Pres. Marc Air" <[email protected]>
    To: [email protected]
    CC: [email protected], [email protected]
    Message-ID: <[email protected]>
    Subject: New Construction Scheduled
    Content-Type: multipart/mixed;
    boundary="----=_Part_115343_1096795609.1550285532929"
    References: <[email protected]>
    X-Mailer: WebService/1.1.13123 aolloki Apache-HttpClient/4.5 (Java/1.8.0_144)
    X-CLX-Shades: MLX
    X-CLX-Response: 1TFkXGB4bEQpMehcYGRsRCllEF2dgXGd4YkRQRFhZEQpYWBdte0RlBWEZfhJ NExEKeE4XaHhpQE9BeUUTf1kRCnlMF2Z/c119YW9GQFJfEQp5QxdkHnJbcxhLRRx8aREKWU0XZ2 ZyEQpZSRcacRoQGncGGBgbcRscGBAadwYYGgYaEQpZXhdsbHkRCklGF15PWUZLR0VeRVhZdUJFW
    V5PThEKQ04XW2tjY2htH2xieGB8U0tnf0lAG2tQaXt7GhNTTRpwY1IRClhcFx8EGgQbHBkHThtO GxJISRMFGxoEGxsaBB4SBBsQGx4aHxoRCl5ZF35EeBMFEQpNXBcbHR0RCkxaF2loaU1NaxEKTEY Xb2trb2trEQpCTxdrTG5EU15pWHlCaBEKQ1oXHBwEGxwZBBsSHAQYGh4RCkJeFxsRCkRJFxgRCk
    JcFxsRCl5OFxsRCkJLF2h4aUBPQXlFE39ZEQpCSRdoeGlAT0F5RRN/WREKQkUXbGtSZHtSAWxmc 0wRCkJOF2h4aUBPQXlFE39ZEQpCTBdte0RlBWEZfhJNExEKQmwXaW9HQktheXp/GRoRCkJAF2xz X0Nze1l+aHppEQpCWBduR0NSYn9hTwESWxEKTV4XGxEKWlgXGREKcGgXemtNR3plHVNfTk0QGhE
    KcGgXY0Vuel15ZX9nbWEQGhEKcGgXYUkaXE9tRxoda0UQGhEKcGgXYVlQXURvTn1lTVgQGhEKcG gXbF1hYmteGVAeaG0QGhEKcH8XY1hJZ0ZEXQV8SGgQGhEKcF8XYkNLZWYBf0ldcEcQGhEKcH0XY kNLZWYBf0ldcEcQGhEKcGsXenMSWBxkWHx4YEQQGhEKcEsXYxgYZX5LfkJyfQUQExMRCnBsF2t8
    YhtCHBx6bWluEBkaEQptfhcbEQpYTRdLESA=
    MIME-Version: 1.0
    x-proofpointheader: true
    X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-02-16_02:,,
    signatures=0
    X-Proofpoint-Spam-Details: rule=inbound_notspam policy=inbound score=0 priorityscore=231
    malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0
    clxscore=241 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=606
    adultscore=0 classifier=scan_limit adjust=0 reason=mlx scancount=1
    engine=8.0.1-1810050000 definitions=main-1902160017
    Return-Path: [email protected]
    X-EOPAttributedMessage: 0
    X-EOPTenantAttributedMessage: 9026c5f4-86d0-4b9f-bd39-b7d4d0fb4674:0
    X-Forefront-Antispam-Report: CIP:148.163.155.1;IPV:NLI;CTRY:US;EFV:NLI;
    X-MS-PublicTrafficType: Email
    X-MS-Office365-Filtering-Correlation-Id: 1e0866b3-63eb-4364-c59f-08d693b9c603
    X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:(2390118)(7020095)(4652040)(5600110)(711020)(4605098)(4710089)(4711035)(49563074)(1401299)(1421009)(1415048)(71702078);SRVR:BLUPR16MB0355;
    X-MS-TrafficTypeDiagnostic: BLUPR16MB0355:
    X-MS-Exchange-PUrlCount: 1

    I tried to call Tony back, but got nothing but voicemail and no call back.

    So, I'm back to where I started. New construction started. No communication with Tesla. Incorrect information from representatives. No resolution after MANY attempts.

    Anyone else had the same experience?
     
  8. Barklikeadog

    Barklikeadog Active Member

    Joined:
    Jul 13, 2016
    Messages:
    1,737
    Location:
    PA
    egads, sorry to hear about this. you're stuck between an evil organization and an incompetent one.
    hope they give you some answers
     
  9. boaterva

    boaterva Supporting Member

    Joined:
    Apr 2, 2016
    Messages:
    7,465
    Location:
    Northern Virginia, USA
    Good grief. Assume you’ve tried this, but what do you get calling TE at the main Tesla number, TE submenu? Is that where you got the newhomes internal mail group from? And that sort of error is common for rarely used email addresses (Office 365 admin here...). Just means the idiot admin didn’t actually test it from an external source. :facepalm:

    I’m wondering how far TE can go with all these cutbacks. Just read the other cringe-inducing install thread for the PWs and it’s like no one knows anything.
     
  10. Barklikeadog

    Barklikeadog Active Member

    Joined:
    Jul 13, 2016
    Messages:
    1,737
    Location:
    PA
    updates?
     
  11. Lloyd

    Lloyd Well-Known Member

    Joined:
    Jan 12, 2011
    Messages:
    6,187
    Location:
    San Luis Obispo, CA
    None. Energy people have no idea when this product will be back on the market.
     
  12. mspohr

    mspohr Well-Known Member

    Joined:
    Jul 27, 2014
    Messages:
    8,092
    Location:
    California
    I'm in the same situation.
    I live on the California side of the Lake (near Tahoe City) and ordered Powerwall last October.
    I've called them several times and each time they tell me to call back in a few months.
    When I ask them if they have an installer for this area, they waffle. I don't think they have anyone.
    Still waiting.
     

Share This Page

  • About Us

    Formed in 2006, Tesla Motors Club (TMC) was the first independent online Tesla community. Today it remains the largest and most dynamic community of Tesla enthusiasts. Learn more.
  • Do you value your experience at TMC? Consider becoming a Supporting Member of Tesla Motors Club. As a thank you for your contribution, you'll get nearly no ads in the Community and Groups sections. Additional perks are available depending on the level of contribution. Please visit the Account Upgrades page for more details.


    SUPPORT TMC