-
Notifications
You must be signed in to change notification settings - Fork 52
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
MSG100 needs to be adjusted #29
Comments
Hello @scannifn Thank you anyway in showing this since another post was stating the 'msg100' was working ok but it was probably too optimistic! |
Hi, please could you help me to collect log info for you?
If it's correct... how can I export the log? |
I hope it's enough for debugging. I f you needs more I'm here ;-)
|
Hey..very fast! |
I've published what could be a good candidate to work on the 'dev' branch. I'll wait a bit before officially releasing since I don't want to overwhelm the users with lot of mid-term releases and non-critical bug-fixes. If you want to give it a try, that could help a lot so I could safely release a 'good' version. If not, don't worry, I'll just take a deep breath and publish in very few days |
Hi @krahabb, sorry for my late answer... for me it's a plasiure to help you. I'm available to do any test that you like. |
Hey @scannifn Ciao! |
Hi @krahabb I send you a small update regarding entity registry and debug log. This is registry screenshot made during my test: This is the log:
|
Closing since it was fixed |
Thank you very much for all! |
I added 2 devices in my envirorment but the state is set as off or on and not as close or open.
I think that for this kind of device should be correct to have a different state compared to a switch or light devices.
Status Open (or on) never appears. When I open the cover I can see Opening state... but not Open (or Opened)
Another point is that I'm syncing these devices with HomeKit integration and they report a state opposite to the correct one.
When cover is off (closed) I get state Open in HomeKit.
The text was updated successfully, but these errors were encountered: