8000 0.56 - Nest shows as climate.unnamed_device · Issue #10047 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

0.56 - Nest shows as climate.unnamed_device #10047

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.

Sign up for GitHub

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

Jump to bottom
Closed
borisfeldman opened this issue Oct 22, 2017 · 1 comment
Closed

0.56 - Nest shows as climate.unnamed_device #10047

borisfeldman opened this issue Oct 22, 2017 · 1 comment

Comments

@borisfeldman
Copy link
borisfeldman commented Oct 22, 2017 •
edited
Loading

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version):
0.56.0

Python release (python3 --version):
3.5.3

Component/platform:
Nest

Description of problem:
Nest is named “Dining Room” and the device name in Home Assistant used to pull from that to be climate.dining_room. But now showing as climate.unnamed_device in 0.56

Not possible to override in YAML config.

Expected:

Problem-relevant configuration.yaml entries and steps to reproduce:

nest:
  client_id: !secret nest_client_id
  client_secret: !secret nest_client_secret

Traceback (if applicable):



Additional info:

      		
    

      
  





        



            
            

              
            

        

      


      
    








      

    



      

  
      



  

  @amelchio





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      

  
    Contributor


      

  


  
    

  




      


        


  
    

      
          
This is a duplicate of #10018 and fixed in 0.56.1.

      		
    

  





        


            

            
            

              
            

        

      


      

            
  
  

    
  
    
    

  

  

  


    












      

  
            

    


    

    

      
    

    


      

          @home-assistant
home-assistant




        locked and limited conversation to collaborators


      Mar 2, 2018

    

  












  
  

    

      

  





  




  
  

             

  
      Sign up for free
      to subscribe to this conversation on GitHub.
      Already have an account?
      Sign in.


  


  






  
                  




    

  


      
  

    Assignees
  



        

    No one assigned







      


  


  

    Labels
  



    

    None yet







      

  

    

        

    Projects
  


        




    None yet




  



      


  

    
  

    Milestone
  


      No milestone





    
      
          


  

    

      
        

          
    

    Development
  




            
    
No branches or pull requests







      
    

  




      

    

  
      

  

    

      2 participants
    

    

        
          @borisfeldman 
        
          @amelchio 
    

  






    

    




    






  

          

        



    



  





    

  


  


          



    



  

    

    

    





    


    

    

  



0