both my sp20's rolled over. I will look for roll back. as of now they should roll back since they are set for 0.0121
and the lowest pool is 0.0135 but if some one is renting at 0.0120 they will stay ahead of me.
this may be the issue you are having. I will keep checking back.
Forgive me if this has been asked earlier. Unfortunately searching on the forum at large seems to be broken.
Like you I'm using NiceHash (or rather WestHash) as the primary with a profitability value set to flat BTC/THs/Day. I'm not having any problems with the miner switching. I've got 2.5.52 firmware.
My concern is that switches happen fairly frequently. That means that my miner sporadically points at WestHash and the secondary throughout the day, which results in automated pool-hopping.
While it's nice to take advantage of NiceHash's profitability, I'm concerned that the sporadic hash rate pointed at my secondary pool results in an effective penalty while it charges up. Since it's hard to track this split profitability, I'm not sure if I'm actually ahead, or if I'd be better off just pointing at a non-rental pool and be done with it.
I noticed that you're using Kano.is as the failover pool. I currently have BTCGuild as my secondary. I switched from Slush because from what I gather, the score method used by that pool penalizes pool hopping.
Any particular reason why you chose Kano as the secondary to WestHash?
On a related note, I wish that NiceHash would let us specify profitability as a percentage instead of a constant. That way we wouldn't have to keep changing the value after each difficulty change. I posted this as a request on the the NiceHash forum thread a while back, but got no reply from them.