-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Always error on first execution, after that it works perfectly #47
Comments
@epicbenz thanks for reporting this issue. I have experienced the same issue and it is because Wi-Fi connected Spotify devices go to sleep after a short period of time. I will investigate a possible workaround for this. |
@joeyhage I don't know if this helps you, but the 2nd time you trigger the plugin/automation always works. |
@epicbenz that's my understanding as well. I made a few changes that I am going to test for the next day or so. I will provide an update tomorrow. |
Thank you! |
That’s not something I had noticed before but that happens for me as well. I will see if that is a behavior I can change. |
I still need to do more testing on the sleeping Amazon devices issue. Hopefully will be close to a reliable solution by next week. |
You Sir are a genius. Thanks a lot. Do you know why the Shuffle function don't work at the beginning? Or should i open a new Issue for this? |
You're welcome! If you could open a separate issue that would be great! I am going to start looking into it as well. |
The plugin works by itself, all steps worked when setting it up.
However, the first time I run it (always after a long time) I get the error message below. If I then trigger the automation again, it works as it should.
My automation looks like this: Aqara window contact closed -> Start "Lamp".
If I start the automation after e.g. 30 min break, then nothing happens and I get the error message. If I open the contact and close it directly, everything is executed as intended.
I have tried to restart the Homebridge a few times and the Echo Dot also. But the problem still remains.
Logs:
Plugin Config:
Screenshots:
Environment:
The text was updated successfully, but these errors were encountered: