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

Shadow component blocks after changing which subcomponents are enabled from a sensor #701

Open
tyeth opened this issue Feb 22, 2025 · 2 comments

Comments

@tyeth
Copy link
Contributor

tyeth commented Feb 22, 2025

Connect new sensor with multiple subcomponents, only enable one of them.
wait for reading.
Update sensor to have all subcomponents (I also turned off the first enabled one).
Data arrives for new options like expected, but sensor data/component blocks remain shadow blocks

Image

@brentru
Copy link
Member

brentru commented Mar 3, 2025

This seems like an issue on IO, rather than in WipperSnapper. Is that the case?

@tyeth
Copy link
Contributor Author

tyeth commented Mar 7, 2025

I need more info on it. Seemingly worse on staging although the same in theory in prod. I had to delete a device to clear up the situation at one point again recently.
I think the situation may be two-fold, we are not responding to a message correctly (publish response failure), and then io-rails stalls the subcomponent (or sometimes seemingly all further broker to device UI initiated messages - maybe i2c only) without that failed message response.
I've yet to properly investigate, but that was one reason that contributed to my publish retry work that stalled in virtual networkStatus issues.

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

No branches or pull requests

2 participants