edfinley Posted February 28, 2012 Share Posted February 28, 2012 Hi, I had upgraded to 3.1.17 and my Elk quit controlling a morninglinc. ISY could still control it but not ELK. I downgraded back to an older firmware and it worked. I've now upgraded to 3.1.17 and installed the Elk module and the problem is back. I re-exported an ELk file but still no luck. Elk is controlling the lights fine, just no response from Morninglinc. Any ideas are appreciated. Thanks, Ed Link to comment Share on other sites More sharing options...
Michel Kohanim Posted February 29, 2012 Share Posted February 29, 2012 Hi Ed, Sincere apologies for tardy reply. Please note that there was a bug in 2.8.16 whereby node addresses were moved up by one. This was fixed in 3.1.17. Are you certain that the ELK address for the morninglinc is the same as it used to be? With kind regards, Michel Link to comment Share on other sites More sharing options...
edfinley Posted March 1, 2012 Author Share Posted March 1, 2012 Good point. Both Elk export files have them in the same place, but I noticed a duplicate set in the Elk Remote Programming software, maybe from an earlier export. I"m guessing I should delete these and try upgrading again. Regards, Ed Link to comment Share on other sites More sharing options...
Michel Kohanim Posted March 2, 2012 Share Posted March 2, 2012 Hi Ed, thanks and please do keep us posted. With kind regards, Michel Link to comment Share on other sites More sharing options...
edfinley Posted March 16, 2012 Author Share Posted March 16, 2012 Starting over with a new export and deleting all the old ELK lighting worked. I ended up having to go through over 100 rules and change every Insteon device back to it's new location, but it worked. Regards, Ed Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.