You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
@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.
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
The text was updated successfully, but these errors were encountered: