R4 hard button issue
Joe Hebert
Posts: 2,159
in AMX Hardware
Has anyone had any type of issues with the hard buttons with the R4?
Here’s my problem:
I have a channel code assigned to the power button.
There is also a page flip assigned to that button.
When the button is pushed the page flip happens and the push shows up in the push message status bar display, however, nothing shows up in the Notifications window and my code doesn’t run.
How is it possible for the push message status bar to show the push but not show up in the the notifications window?
Other hard buttons show up fine in both spots but not the power button. If the channel up button is pushed the push message status bar shows the push and the push shows up in notifications so I know it’s not my notification settings (which is setup to show everything.)
The only thing I can tell that is different with the hard power button is that there is a page flip assigned to it aside from the channel code. The other hard buttons for that page just spit out channel codes and they seem to work fine.
The Zigbee gateway was rebooted and the first time the power button was pushed after the reboot the push shows up and code runs as it should. But that’s it, after that no notifications and code doesn’t run.
The Zigbee gateway, the R4remotes, and the NI-3100 all have the latest firmware
Has anyone experienced this before? Any ideas on what is going on?
TIA
Here’s my problem:
I have a channel code assigned to the power button.
There is also a page flip assigned to that button.
When the button is pushed the page flip happens and the push shows up in the push message status bar display, however, nothing shows up in the Notifications window and my code doesn’t run.
How is it possible for the push message status bar to show the push but not show up in the the notifications window?
Other hard buttons show up fine in both spots but not the power button. If the channel up button is pushed the push message status bar shows the push and the push shows up in notifications so I know it’s not my notification settings (which is setup to show everything.)
The only thing I can tell that is different with the hard power button is that there is a page flip assigned to it aside from the channel code. The other hard buttons for that page just spit out channel codes and they seem to work fine.
The Zigbee gateway was rebooted and the first time the power button was pushed after the reboot the push shows up and code runs as it should. But that’s it, after that no notifications and code doesn’t run.
The Zigbee gateway, the R4remotes, and the NI-3100 all have the latest firmware
Has anyone experienced this before? Any ideas on what is going on?
TIA
0
Comments
Here's my post about it.
http://www.amxforums.com/showthread.php?3495-Odd-R4-code-problem
AMX ended up replacing the R4 but the problem still remained. I believe it to be a bug in the firmware.
The solution for me was to put a DO_RELEASE() in the buttons PUSH: event. The R4 for some reason never sends the release when the button is pressed then released.
Edited to add: The Push notifications "sees" the button push as does the master but if there was a previous PUSH and no RELEASE it handles the PUSH differently. For example it is probably testing to see if it should fire a HOLD event but doesn't do the PUSH event because that already happened and was never cleared by a RELEASE due to the R4 firmware bug.
I’m seeing the same exact problem that you reported over 3 years ago.
The hard power button works once after a Zigbee gateway reboot or after the R4 is rebooted. After that the push shows up in the push message status bar display but not in the notifications window which really has me scratching my head.
If I put the same channel code and page flip on a soft button on the same page then it works every time without issue.
Smells like a firmware bug to me. Ugh.
Did you have a page flip on the button too? We don't and it works as it should.
An old commonly warned item about presses/releases on popups may apply here for some reason:
If you put a page flip on a button such that the page with the button is removed before you release the button, the system is never informed that the button is released. It's not there when you take your finger off, so THAT button is still "pushed" per the system. It can see more pushes, but until released, which it never can do, it can't be processed by other routines... It can work occasionally, pending the hardware and communication timing, as in if you get your finger off before the panel gets around to flipping itself, you win.
This was apparently fixed some years back in G4 firmware. It persists in G3, and may be in R4 now.
Don't link a flip to this button and it may be fine. Have your code do the flip or, yes, use the forced release in your code. Oh the fun of corner cases.
The destination page did not have a channel code assigned to it so the channel wasn’t getting released.
I wonder if AMX is considering this a bug or if this is just going to be the way it is?
Thanks for the feedback everyone. Problem solved.
I can't imagine how many ghost problems this is causing by pushed channels not being released and subsequently not working.
Just another reason to avoid using R4's.
That might simply be an RF issue. You tend not to notice flaky RF on a push, because you just push the button again, but release is another story because it often signals a stop-action of some sort, and when stuff starts but doesn't stop, you tend to notice. That's why they recommend a timeout on HOLDs for R4s.