Mark Sanctuary

Yes it is. Also remember that if you decide to try connecting to it from the internet outside world all you do is change the "p" to an "x" like in this example here. External: http:/192.169.x.y:z/0/x Internal: http:/192.169.x.y:z/0/p

I don't think they have made any changes. Gosh I don't know any more; I try to call it like I see it and I am scoring correct only half the time these days.

You know the resources might be small if it was implemented with only trying to return device levels as there where before. The scene provided in the "Save Snapshot" would be the device list to key off of and you could create an indexable lookup list. Then the scene device list could be gotten again in "Restore Snapshot" used again to go thru the list to return levels. Save Snapshot Retreave the Scene device list: Light1:Light2:Light3:Switch1:Light4:Light5:Light6 Store level data in same order as scene list so indexing would match: 30:30:60:ON:OFF:100:0 Restore Snapshot Retreave the Scene device list again for indexing the data list: Light1:Light2:Light3:Switch1:Light4:Light5:Light6 Look up the data by index with the scene list: 30:30:60:ON:OFF:100:0 This is a high level concept so I am guessing there is some low level stuff I am not accounting for. I think the only stored data would be the levels. If wanted it could be done with a normal hash table too then the indexing would be automatic but would use a bit more memory to store the names in the array too.

You could have a command that snapshots the current state of any scene device list; in this case My Network. Then run the security scene. Finally use a Restore state command and all is back to the way it was. This would be a very cool feature. Save Snapshot 'My Lighting' Run Program 'Security Scene' Restore Snapshot 'My Lighting'

See told you I have not telneted yet, cool over network is very nice.

Thanks for the heads up. Good catch.

Doesn’t sound like the login route issue it sounds like a install issue/bug. I don't really have much of an idea for this one.

I have never used the telnet yet, I guess I will have to fire up the laptop and hall it out to the structured media panel and connect up to the ISY.

Maybe the instructions part could be removed, but other than that sounds fine. Add conditions to limit when programs in this folder are allowed to run.

You can also use the IP address but if you’re using DHCP you will have to figure out what that might be. I think the port number (example: 16142) can be different from ISY to ISY. You can also telnet into the box and get its address, but the easiest would to turn on UPnP. If the guys update the weblink when they release the beta you can use the weblink then. I recommend though that you turn on UPnP or look up your IP and port address because that URL approach is dependent on the link working. http://your.internal.ip.address:16142/0/p

You have to use the My Lighting icon from the windows "My Network Places" area to login to the beta. If you using a icon shortcut that uses the http://www.universal-devices.com/my_inst_isy/myisy.htm to log in it will not get the beta software and you will get weirdness just as you described.

PLM 4a came with mine; the funny thing was they sent me two for no reason other than my shipment got split so I ended up with two 4a modems when I got the ISY. I called them up and they told me just to keep the extra one. So long story short, the ISY did come with 4a modems.

Your right it is not preserving the choice if it’s on both status and control combo box lists.

Updating status on this topic; still in 2.4.10 beta drop.

Updating status on this topic; still in 2.4.10 beta drop.

Updating status on this topic; still in 2.4.10 beta drop.

Not sure if this was fixed but I rebooted this morning and it only asked for the password one time. Did you guys fix this?

Confirmed it's in 2.4.10 - Newlines preserved in Program Comment field - 'Finally' replaced by 'Else'; semantic difference is 'Else' runs independent of whether 'Then' ran - Fixed program true/false status, and various logic bugs in programs. - Added 'is not received' to X10 conditions - Keypad buttons available in Status conditions Not sure about - Keypad buttons available in actions (not sure if this was a typo in the beta notes but I did not see KPL buttons in the actions combo box) Not tested - Log key presses/X10 messages received to the java console (turned on/off in the shell)

Tested and confirmed this bug is resolved.

Tested and confirmed this bug is resolved.

Tested and confirmed this bug is resolved.

ISY Controller tree example: ISY Controller scene example:

ISY Local tree example: ISY Local scene example:

Don't really know what "scene" is for I just brought it down from one of your earlier posts. It hit me while we where out of town this weekend; ISY local is the keypadlinc load that also has a same keypadlinc non-load button in a mutual scene. This is the device(s) that will always need to be run from the ISY by user or ISY program in order to see the ISY local level otherwise the keypadlinc default level is used when the keypadlinc non-load button is pressed. Updated color labels Controller Controlsponder Responder Responder ISY Local (Is KPL load only when included with mutual KPL non-load) Scene Name Also I am wondering if the sliders don't really need more words just the device names need the “Controllerâ€, “Responder â€, and “Responder ISY Local†colorization instead in the scene sub window which would then match the tree.

Chris you might want to check with Smarthome on the PLM, because I just had them trade mine out for new firmware and they said there was a known X10 issue with PLM version 4a that was fixed with the 5.(something) release of the PLM. I am waiting for my new one to arrive so I can get it swapped out and find out if that is my X10 issue.