From: Marc M. <ma...@me...> - 2009-03-15 05:49:06
|
So, for my understanding, and to mention this in the new docs: I'm still not super sure what this message is supposed to say exactly. Is it a failure of a message that just wans't delivered due to some mh bus problem? So, a command was send and retried twice as part of the first send, and no ack was received then, mh noticed that and tried to send the command again (x3 with insteon protocol) after that, I'm not too sure what happens exactly, how long/how many times mh tries to resend that unacked command before giving up, and how this is involved: @ In addition, you can adjust the duration before mh will requeue a @ transmitted message when it has not recevied an ack. The default is 15 @ seconds and is likely sufficient for most cases. To adjust: Insteon_PLM_max_queue_time=5 Is the text I have correct? I.e. does it mean mh tries resending an unacked command every 5 seconds forever? If not, what actually happens? More importantly, is it an error that means that the command was lost and mh gave up sending it, potentially leaving my outside light on? For now, I unset those two, just in case: #Insteon_PLM_disable_throttling=1 #Insteon_PLM_xmit_delay=0.15 Thanks :) Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ |