Currently on my fab4 back hold causes the error shown below(tries to disconnect player but fails)
 
Ignoring that error for the moment, my understanding of the back design is to be more like ip3k devices rather than be like jive:
for fab4 and controller, back "regular hold" will be go_home. back "long_hold" will be disconnect_player.

Dean, can you confirm that this design is correct?

We will need to add "long hold" support to make this work, which should be pretty straightforward... just pointing out that we don't currently have it..


114137:75918 INFO (NetworkThread.lua:256) - NOTIFY: playerCurrent(nil)
error in event function:
        ...ts/SetupFirmwareUpgrade/SetupFirmwareUpgradeMeta.lua:41: attempt to index local 'player' (a nil value)
stack traceback:
        ...ts/SetupFirmwareUpgrade/SetupFirmwareUpgradeMeta.lua:41: in function '?'
        /usr/share/jive/jive/net/NetworkThread.lua:262: in function 'notify'
        /usr/share/jive/jive/slim/Player.lua:159: in function 'setCurrentPlayer'
        ...e/jive/applets/SlimDiscovery/SlimDiscoveryApplet.lua:526: in function <...e/jive/applets/SlimDiscovery/SlimDiscoveryApplet.lua:525>
        (tail call): ?
        /usr/share/jive/jive/JiveMain.lua:146: in function 'listener'
        /usr/share/jive/jive/ui/Framework.lua:766: in function </usr/share/jive/jive/ui/Framework.lua:759>
        [C 0x23418]: ?
        [C 0x236e4]: ?
        [C 0x23c8c]: in function 'processEvents'
        /usr/share/jive/jive/ui/Framework.lua:264: in function </usr/share/jive/jive/ui/Framework.lua:262>