<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I have been looking deeper in the implementation of the User defined Actions add-on to try to understand why scenes 11 and 12 were never presented in the UI.<div><br></div><div>If I understand correctly (not 100% sure), the list of scenes to present in the UI comes from the getScenes function implemented in the dss-datamodel.js file.</div><div><br></div><div>The definition of the function starts like this:</div><div><br></div><div><div><font face="Courier New">dss.staticDataModel.getScenes = function(zoneId, groupId) {</font></div><div><font face="Courier New"><span class="Apple-tab-span" style="white-space:pre"> </span>if (dss.staticDataModel.nameCache == null)</font></div><div><font face="Courier New"><span class="Apple-tab-span" style="white-space:pre"> </span>dss.staticDataModel.initCaches();</font></div><div><font face="Courier New"><span class="Apple-tab-span" style="white-space:pre"> </span>var oDeviceArray = dss.staticDataModel.getDevicesForZone(zoneId, groupId);</font></div><div><font face="Courier New"><br></font></div><div><font face="Courier New"> var oRetArray = [];</font></div><div><font face="Courier New"> var sceneArray = [ 0, 5, 17, 18, 19, 1, 6, 2, 7, 3, 8, 4, 9, 32, 33, 20, 21, 22, 34, 35, 23, 24, 25, 36, 37, 26, 27, 28, 38, 39, 29, 30, 31, 67,</font></div><div><font face="Courier New"> 64, 68, 69, 70, 72, 71, 73, 65, 76, 74, 83, 84, 85, 88, 89];</font></div><div><font face="Courier New"> if (groupId==1)</font></div><div><font face="Courier New"> <span class="Apple-tab-span" style="white-space:pre"> </span>sceneArray = [ 0, 40, 5, 17, 18, 19, 1, 6, 2, 7, 3, 8, 4, 9, 32, 33, 20, 21, 22, 34, 35, 23, 24, 25, 36, 37, 26, 27, 28, 38, 39, 29, 30, 31, 67,</font></div><div><font face="Courier New"> 64, 68, 69, 70, 72, 71, 73, 65, 76, 74, 83, 84, 85, 88, 89];</font></div><div><font face="Courier New"> if (zoneId==0)</font></div><div><font face="Courier New"> <span class="Apple-tab-span" style="white-space:pre"> </span>if (groupId==0) {</font></div><div><font face="Courier New"> <span class="Apple-tab-span" style="white-space:pre"> </span>sceneArray.push(90);</font></div><div><font face="Courier New"> <span class="Apple-tab-span" style="white-space:pre"> </span>sceneArray.push(91);</font></div><div><font face="Courier New"> <span class="Apple-tab-span" style="white-space:pre"> </span>}</font></div><div><font face="Courier New"> if (groupId == 2)</font></div><div><font face="Courier New"> {</font></div><div><font face="Courier New"> sceneArray.splice(5,0,56);</font></div><div><font face="Courier New"> sceneArray.splice(34,0,15);</font></div><div><font face="Courier New"> }</font></div><div><font face="Courier New">...</font></div><div><br></div></div><div><br></div><div>The scenes 11 and 12 are never listed in the sceneArray. So even if they are actually defined in the system, they never get presented as an option for the actions.</div><div><br></div><div>I understand I can probably code myself a dss-addon to enable triggers to call those scenes. But it seems like an overkill and I think it would be better for user experience if those scenes were presented as options for user defined actions and event responders.</div><div><br></div><div><br></div><div>jmt</div><div><br></div></body></html>