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.

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

Calling service on device picks up the wrong device ID #681

Closed
TheSimpleZ opened this issue Jan 14, 2025 · 1 comment
Closed

Calling service on device picks up the wrong device ID #681

TheSimpleZ opened this issue Jan 14, 2025 · 1 comment

Comments

@TheSimpleZ
Copy link

TheSimpleZ commented Jan 14, 2025

I am trying to call a service to start my dishwasher.

The service YAML that works:

action: connectlife.set_action
target:
  device_id: f843d2956a8f5543756e46bfbacd84e7
data:
  action: "2"

This is what I write in pyscript:

connectlife.set_action(device_id="f843d2956a8f5543756e46bfbacd84e7", action="2")

But for some reason, this fails. In the logs I see:

2025-01-14 02:18:02.148 DEBUG (MainThread) [custom_components.connectlife.services] device_id: 0000000000007395170001202200024030030
2025-01-14 02:18:02.148 DEBUG (MainThread) [custom_components.connectlife.services] Setting Actions to 2 on 0000000000007395170001202200024030030

I have no idea where that device ID in the logs comes from. What am I missing here?

@TheSimpleZ
Copy link
Author

nvm, this was an error in the connectlife integration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant