Closed sambeetm closed 9 months ago
Do you not have fragrances in your car diffusers at the moment? It looks like that's where it is causing the error. Because the data is pulled via a single endpoint for all devices, it's causing the error to show up on every interaction.
I have one Car diffuser with 26% fragrance and is working. This was the warranty replacement. The initial faulty one which I sent them back, does not show in my account(app). But, somehow being pulled by the API. May be I had not or could not remove from the app before sending them back.
Ahh, interesting, ok. I'll have to look through your data a little more and see if there is anything I can use to distinguish and exclude that.
Release 0.1.18 should resolve the errors you are seeing with every call
Thank you for the great integration and prompt support. Now I can use these devices to the fullest. One observation though..the status update for any actions taken from HA (like select off/slot1/slot2, RGB etc) takes almost 30 sec to update the status back. I see the actual actions are instant including the status in the app. Just the HA status is delayed. Is it related to this issue ?
Updated to 0.1.18. Confirmed that error is gone. But, I still have the 30 sec delay.
The 30 second delay is unrelated. This integration uses polling to get the data from Pura APIs which is defaulted to 30 seconds. After making a change, it tries to refresh data pretty quickly, but if the new state isn't available yet, then it waits 30 seconds for the next refresh. You can follow this discussion for updates: https://github.com/natekspencer/hacs-pura/discussions/24
The problem
I am getting below banner in the left lower every time select Off/Slot 1/Slot 2 or Turn On or Off the light. But, all seems to be working normally. More info is in the log.
What version of Home Assistant Core are you running?
core-2023.11.3
What was the last working version of Home Assistant Core?
No response
Diagnostics information
config_entry-pura-1f647cfabee36f754ac72049e4ae95dc.json.txt
Anything in the logs that might be useful?
Additional information
Integration ver. Release 0.1.17