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

False Positive TOP position recognition, half the way down #19

Open
popy2k14 opened this issue Jun 27, 2022 · 2 comments
Open

False Positive TOP position recognition, half the way down #19

popy2k14 opened this issue Jun 27, 2022 · 2 comments

Comments

@popy2k14
Copy link

Dear @mjuhanne

Using your new 0.87 builds with original ZigBee Module. A huge thanks for this!!!!!! It's running way smoother than before (0.82).

Flexi speed was triggered two times wrong. I think it has Todo with ZigBee retrys. Is that possible?
Always using bri values to set the position.
Anyway, i am now using the 5 rpm and so don't have this issue.

But sadly, it triggered the TOP position reset once.
In the morning my smarthome sends 60% to the blind. This was executed as it should. After waking up i was sending 0% with Hue Essentials over deconz+conbee II.

Then it moved down!? Instead of up.
After recognizing this i pressed up on my hue dimmer, which sends bri 0% again and this time it moved to the Top and it's working.

Any hints what could have caused this and how to prevent it.

Thx

@simlu
Copy link

simlu commented Jun 28, 2022

@popy2k14 I had something similar happening. It's really unfortunate that this firmware is so buggy. I currently still have one prototype blind up, but plan to install at least seven more - so re-flashing becomes a real pain in the butt.

Meanwhile, until we can figure out the bugs with this firmware, I've decided to go a different approach and edit the original firmware instead. This is work in progress, but if you're curious this is where I'm currently at: https://reverseengineering.stackexchange.com/questions/30565/stm32-disable-voltage-check

@popy2k14
Copy link
Author

Thanks for confirming the issue.
Good idea to reverse engineer it, i have posted on stackexchange where we should discuss this further.

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

No branches or pull requests

2 participants