accessha Posted November 18, 2008 Share Posted November 18, 2008 Not yet but I will give it a try. Link to comment Share on other sites More sharing options...
accessha Posted November 26, 2008 Share Posted November 26, 2008 accessha. Do you know if this issue goes away if you downgrade to 5.1.4? snhroc, I downgraded to 5.1.4 on the Elk but now my ISY will not connect. Running 2.6.8 on the ISY. Link to comment Share on other sites More sharing options...
Michel Kohanim Posted November 26, 2008 Share Posted November 26, 2008 accessha, ELK actually found a bug in 5.1.8 which caused the issues you were experiencing. Here's the excerpt: I have found the bug and it did pop up between v5.1.4 and v5.1.8. Let me try to explain what is happening: When a M1 lighting rule triggers, the lighting commands are buffered. We have a buffer that can hold up to 32 pending lighting devices at a time. The light's timer value is an element of this buffer. When the M1 receives a lighting update from the ISY it uses the same buffer, but the problem is that the M1 didn't clear the buffered timer value. So, if the ISY sends the M1 a lighting update, the M1 might store that update to a buffer position that previously held a timer value. When the M1 acts on that buffered light update it will see a timer value and associate the timer to the light that the M1 received from the ISY. The good news is that I have tested the change to the rules that I suggested below and they are a good work-around and allows you to continue to use firmware version 5.1.8. Because in the new rules the timers are based off the phantom output instead of the light's timer, no timer value is stored in the lighting buffer. I do suggest that you power down the M1 to clear any lighting timer values that might be stored from before you changed the rules. After that no lighting timer values will be in play from the M1. I've made the correction to the M1 code to fix this issue and it will be in the next release of the firmware. Sorry for any inconvenience and thank you again for your help and time in this matter. Please let me know if you have any questions. With kind regards, Michel accessha. Do you know if this issue goes away if you downgrade to 5.1.4? snhroc, I downgraded to 5.1.4 on the Elk but now my ISY will not connect. Running 2.6.8 on the ISY. Link to comment Share on other sites More sharing options...
accessha Posted November 26, 2008 Share Posted November 26, 2008 Excellent... thanks Michel. Link to comment Share on other sites More sharing options...
accessha Posted December 28, 2008 Share Posted December 28, 2008 Hi Michel, Any updates from Elk on this issue? Link to comment Share on other sites More sharing options...
Michel Kohanim Posted December 29, 2008 Share Posted December 29, 2008 Hello accessha, No! We do not actively follow ELK progress on their own bugs. I assume since there's a workaround, it might not have the highest priority. With kind regards, Michel Hi Michel, Any updates from Elk on this issue? Link to comment Share on other sites More sharing options...
accessha Posted January 17, 2009 Share Posted January 17, 2009 Hi Michel, I read back through the entire thread and didn't find a 'work around' for this issue. Was it downgrading the Elk firmware? Link to comment Share on other sites More sharing options...
Michel Kohanim Posted January 18, 2009 Share Posted January 18, 2009 Hi accessha, I don't think you read the excerpt that I had posted: .... Because in the new rules the timers are based off the phantom output instead of the light's timer, no timer value is stored in the lighting buffer. I do suggest that you power down the M1 to clear any lighting timer values that might be stored from before you changed the rules. After that no lighting timer values will be in play from the M1. With kind regards, Michel Hi Michel, I read back through the entire thread and didn't find a 'work around' for this issue. Was it downgrading the Elk firmware? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.