It used to happen quite a bit with the ML600. I cannot tell you why or what caused it. A firmware upgrade to fix this problem for the most part. It did not happen on all jobs and even on those where it did show it was intermittent. I still see it from time to time on my own system with a ML600. It's rare. It's also impossible to track down and fix.

By the way, G-man, how did you code this logic in SB? If you were to look at the underlying macros you would see that the volume press driving the macro for volume up/down are hidden. Only the analog output is exposed.

In Simpl you can interupt this signal and conditonalize it. But in SB this is impossible or I've not found a way to accomplish it. Assuming you are using the default SB logic where the scrolling text can control any room how are you interupting the logic and generating you receiver ir codes?

I have thought of writing a module to take in the volume analog from the underlying macro and if increasing send the vol+ ir command and if decreasing send the vol- till the value stops changing.

In Simpl it is simple to interupt the button press and conditonalize it. If it's not the receiver's room then let the logic pass to the macro. If it is the receiver's room then let the button press generate volume ir code.

The macro WILL provide an integer value for the room in use. I did try to "and" the logic with the volume press join number but it failed. The only way I can think to do this is to conditionalize volume subpages for receiver and system macro. The problem I found was the value SB was using to determine the room in use was incorrect--at least in the SB file I was using.

Alan