-
Notifications
You must be signed in to change notification settings - Fork 2
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
Fix UI issue #88
Fix UI issue #88
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #88 +/- ##
==========================================
- Coverage 89.90% 89.82% -0.08%
==========================================
Files 19 19
Lines 1208 1209 +1
==========================================
Hits 1086 1086
- Misses 122 123 +1
|
@tykeal do you mind testing this PR? Trying to figure out where the issue is, and as far as I can tell it's a timing issue but I can't quite be sure |
I'll give it a try in the morning. I'm nowhere near my test system right now |
@raman325 Well, it loads, unlike what I was seeing with 0.4.0. Everything is showing as unavailable though. I removed the configuration, added it back in and then when to look at the dashboard and everything was showing as available when I first got to it but shortly after it showed everything as unavailable again. |
I enabled debug for the component and here's all the spew for my test system related to LCM
|
I then see a few more updates after I captured that with the following:
Which looks pretty standard but the entities all remain unavailable to me. |
:-/ ok, looks like my zwave lock is showing up as unavailable in HA for some reason even though ZWave-JS is showing it as active. So that will probably explain my unavailable entities. Let me figure out my test bed problem |
Right.... that's great. I knew this lock was having issues which is why I removed it from active service. Now the Zwave has gone flaky on me 😆 I've got a spare lock for use on my properties if one of the locks fails suddenly. I guess I'll hook that up to my test instance. |
Given what I'm seeing I believe this will fix #98 |
Breaking change
Proposed change
Type of change
Additional information