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.

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

Kelvin Argument has a strange behavior #139604

Closed
bernardesarthur opened this issue Mar 1, 2025 · 10 comments · Fixed by #142456
Closed

Kelvin Argument has a strange behavior #139604

bernardesarthur opened this issue Mar 1, 2025 · 10 comments · Fixed by #142456
Labels
integration: light

Comments

@bernardesarthur
Copy link

The problem

I have this warning in my logs: Got kelvinargument inturn_onservice, which is deprecated and will break in Home Assistant 2026.1, please usecolor_temp_kelvin argument

Until then ok, but I call this service directly on Developer Tools -> Actions that way:

Image

And if a see the YAML option I see that: action:

light.turn_on
target:
  entity_id: light.lampada_do_setup_home_office
data:
  kelvin: 2000

The only way I can use color_temp_kelvin is editing the YAML mode, shouldn't update the web interface for this? Thank's a lot!

What version of Home Assistant Core has the issue?

core-2025.2.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

14.2

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet



Anything in the logs that might be useful for us?




Additional information


No response

      		
    

      
  





        

            


            

              
            

        

      


      
    








      

    



      

  
            







      

  
      



  

  @home-assistant





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      



      

  


  

    

      

      
            home-assistant
  bot

      

      

      commented


        Mar 2, 2025


      
    


  





      


        


  
    

      
          
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (light) you are listed as a code owner for? Thanks!



Code owner commands

Code owners of light can trigger bot actions by commenting:


    

  • @home-assistant close Closes the issue.
    • 

  • @home-assistant rename Awesome new title Renames the issue.
    • 

  • @home-assistant reopen Reopen the issue.
    • 

  • @home-assistant unassign light Removes the current integration label and assignees on the issue, add the integration domain after the command.
    • 

  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
    • 

  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
    • 





(message by CodeOwnersMention)




light documentation

light source

(message by IssueLinks)

      		
    

  





        


            

            

              
            

        

      


      

            
  

    
  
    
    

  

  



    












      

  
      



  

  @Chaoscontrol





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      



      

  


  

    

  





      


        


  
    

      
          
Same here. It's been like this for a couple months now. It's funny and strange they launched the warning but the UI generated code wasn't updated to match. :S

      		
    

  





        


            

            

              
            

        

      


      

            
  

    
  
    
    

  

  



    












      

  
      



  

  @rinyheuvelman





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      



      

  


  

    

  





      


        


  
    

      
          
Have same issue

      		
    

  





        


            

            

              
            

        

      


      

            
  

    
  
    
    

  

  



    












      

  
      



  

  @bernardesarthur





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      



      

  Author


  


  

    

  





      


        


  
    

      
          
Anyone can help us with this issue?

      		
    

  





        


            

            

              
            

        

      


      

            
  

    
  
    
    

  

  



    












      

  
      



  

  @endyb66





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      



      

  


  

    

      

      
            endyb66
  

      

      

      commented


        Apr 3, 2025


      
    


  





      


        


  
    

      
          
Same here. Is there a workaround in the meantime?

      		
    

  





        


            

            

              
            

        

      


      

            
  

    
  
    
    

  

  



    












      

  
      



  

  @bernardesarthur





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      



      

  Author


  


  

    

      

      
            bernardesarthur
  

      

      

      commented


        Apr 5, 2025


      
  •

  

    
      

        
          edited
          
        
        
      

    
    
      
        
      Loading

      
    
  



    


  





      


        


  
    

      
          
I'll open a issue on frontend repo. I think there we gonna receive a answer.


Edit: I opened there home-assistant/frontend#24932

      		
    

  





        


            

            

              
            

        

      


      

            
  

    
  
    
    

  

  



    












      

  
          

  

    
  


  

      

  This was referenced Apr 6, 2025





  


  

      
  
  Closed

  






      






  


  

      
  
  Closed

  






  









      

  
      



  

  @bernardesarthur





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      



      

  Author


  


  

    

  





      


        


  
    

      
          
@home-assistant/core can you take a look?

      		
    

  





        


            

            

              
            

        

      


      

            
  

    
  
    
    

  

  



    












      

  
      



  

  @k8gg





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      



      

  


  

    

      

      
            k8gg
  

      

      

      commented


        Apr 6, 2025


      
    


  





      


        


  
    

      
          
Wait I'm confused. So is the issue being that we should all using kelvin instead of color_temp_kelvin? Or is the issue being the frontend not handling the color_temp_kelvin properly, but the solution for frontend would have to come from core...?

      		
    

  





        


            

            

              
            

        

      


      

            
  

    
  
    
    

  

  



    












      

  
      



  

  @bernardesarthur





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      



      

  Author


  


  

    

      

      
            bernardesarthur
  

      

      

      commented


        Apr 6, 2025


      
  •

  

    
      

        
          edited
          
        
        
      

    
    
      
        
      Loading

      
    
  



    


  





      


        


  
    

      
          
We should to use color_temp_kelvin instead to use kelvin, until then ok. But the frontend is incorrect, the frontend use kelvin instead color_temp_kelvin. I opened a issue on the frontend repo but they closed saying that problem is from core.


If you use kelvin or you use the frontend (without a edition on YAML as I said on top) you're gonna receive that message:


Got kelvin argument in turn_on service, which is deprecated and will break in Home Assistant 2026.1, please use color_temp_kelvin argument


Now think: what's is gonna happen in 2026.1 if the frontend is wrong? Doesn't work? The service doesn't work if you make your automations and scripts via frontend instead the YAML? That's my point.

      		
    

  





        


            

            

              
            

        

      


      

            
  

    
  
    
    

  

  



    












      

  
          

  

    
  


  

      

    @epenet
epenet



    mentioned this issue
    
      Apr 7, 2025
    





  


  

      
   Merged

  





  
  

      
        
      
      

  
    
    
  


    19 tasks
  





  









      

  
      



  

  @epenet





  


    

      

  

    

        
    
    

  


      
          
  
      
            Copy link

  

      
    

  


  

      

  
    Contributor


      

  


  

    

      

      
            epenet
  

      

      

      commented


        Apr 7, 2025


      
    


  





      


        


  
    

      
          
PR #142456 should solve this

Feel free to test

      		
    

  





        


            

            

              
            

        

      


      

            
  

    
  
    
    

  

  



    












      

  
            

    











  
  

    

      

  





  




  
  

              

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


  



  






  
                  




    

  


      
  

    Assignees
  



        

    No one assigned







      


  


  

    Labels
  



    

      

    integration: light









      

  

    

        

    Projects
  


        




    None yet




  



      


  

    
  

    Milestone
  


      No milestone





    
      
          


  

    

      
        

          
    

    Development
  




            
  
Successfully merging a pull request may close this issue.





    


  
          
      Fix kelvin parameter in light action specifications

    
      epenet/home-assistant-core
    





      
    

  




      

    

  
      

  

    

      7 participants
    

    

        
          @bernardesarthur 
        
          @Chaoscontrol 
        
          @epenet 
        
          @k8gg 
        
          @rinyheuvelman 
        
          @mib1185 
        
          @endyb66