MWareman

No, does not run on Android tablets, IOS devices or Windows Phone. It needs either Windows, OSX or Linux and a full Java runtime environment.

We have one of the HP streams (well, its my daughters!). The console runs fine once you install Java. I have a Surface 3 at work - again also works fine once you install Java.

Using an app password that's unique to the ISY and not used for anything else prevents that password from being phished. The longer, random nature makes it infeasible to brute force. This allows you to use a weaker main password with two step auth to protect you day to day, yet remain useless to an attacker if you are phished. You can also use an app to generate codes for you, eliminating the need to receive SMS messages. Much more convenient IMO.

@Teken, the Google help and info page on this is here: https://support.google.com/accounts/answer/185833?hl=en Michael.

As I mentioned, you'll need the network resource... 'http' 'GET' 'Host' [iP of ISY] Port [80 or non-ssl port of ISY] Path Example: /rest/vars/set/2/128/${sys.node.27 FA 4D 1.ST.raw} Encode URL: Unchecked Timeout: 500ms In the Headers, add: Authorization Set the username and password to your ISY username and password Save it, and test. Details of the Path: /rest/vars/set/ tells ISY 'I want to set a variable' 2 tells ISY 'set a state variable' (use 1 for an integer) 128 is the variable number (look this up on your ISY admin console variables tab) ${sys.node.27 FA 4D 1.ST.raw} is the substitution variable for the device. Watch out - this needs to be an integer - Insteon devices are normally ranged 0-255. The .raw means 'an unformatted raw value'. Note: Do *not* use 127.0.0.1 for the IP address! There is a limitation in the networking stack of ISY that means this will not only not work - it can actually hang the ISY. Michael.

Who said SMS? I agree, SMS is sometimes delayed. I use a combination of Pushover and Tasker/Autoremote and both are virtually instant.

If you have 4.3.10 and the network module, you can have anything that's substitutable in email set as a variable by using a network resource and variable substitution calling the rest interface directly on the ISY to set the variable.

I thought about doing this as well, but decided against it. How would a visitor know that the doorbell was working? Most people I know would, upon pressing the button and not hearing the chime start pounding on the door. Thus negating the whole reason! I have a motion sensor on my porch that pings my phone and flashes a light. This usually means I can get to the door before the visitor needs to push the Bell.

IP20 is not protected against liquids at all. I wouldn't use it outdoors at all.... http://www.dsmt.com/resources/ip-rating-chart

ISY programs have one (or more) triggering events that cause a program to evaluate the IF condition. Based on that evaluation - either 'Then' or 'Else' is run. For example: If From Sunset + 15 minutes To 11:17:00PM (same day) And $i_vacation_mode is not 0 Then Wait 5 minutes (Random) Set 'Outside / Outside - Rear' On Else Set 'Outside / Outside - Rear' Off $i_vacation_mode is an integer (does not trigger evaluation). The 'From' and 'To' create two separate triggering events - one at Sunset+15mins (will evaluate 'True' when it occurs) and one at 11:17PM (same day - but will evaluate 'False' when it triggers). So - when the two events occur from the 'From' and 'True' - the non-triggering conditions are evaluated to see their state. If all events evaluate 'True' then 'Then' is run. Otherwise 'Else' is run. Changing this (subtlety). If From Sunset + 15 minutes To 11:17:00PM (same day) And $s_vacation_mode is not 0 Then Wait 5 minutes (Random) Set 'Outside / Outside - Rear' On Else Set 'Outside / Outside - Rear' Off This time, the $s_vacation_mode is a 'state' variable. State variables cause evaluation of the condition every time they change. So - the same happens at 'Sunset + 15' and 11:17pm (same day) - but if $s_vacation_mode changes at all an evaluation occurs then as well. So - setting $s_vacation_mode to '1' between the two times will cause 'Then' to run. Setting it to '0' will terminate 'Then' and start running 'Else'. Critically - if you change $s_vacation_mode back to '0' within the (up to) 5 minutes wait in 'Then' of changing it to '1' - the still running 'Wait' will terminate - and 'Else' will immediately start. It's driven by the triggering events. You should do some research on what are triggering events to ISY. For example, Device 'status' triggers on any change of status (either locally, by scene or thru the API or product like Mobilinc). Device 'Control' triggers ONLY when the device is locally controlled. It's important to get to know what causes triggering when in the IF block to help understand the logic. Flow based (or traditional) if-then-else does not have the notion of retriggering and reevaluation during the execution of the 'Then' or 'Else' code blocks. With traditional logic - after evaluation the 'Then' or 'Else' will generally always complete - often using 'Else If' and/or ending with a 'End If' - neither of which have a place in the event driven method. With event based - if the triggering events change it will cause the 'Then' or 'Else' to terminate at the next 'Wait' or 'Repeat', the 'If' will be reevaluated and the 'Then' or 'Else will start from the top again. Michael.

I agree, its easy enough to work around. It's just the 404 is syntactically correct for devices that don't exist, not so much for a /notes request for a device that does exist.

I have notices that if I request /notes from a device where there are no notes, no 'Is Load' and no 'Location' - you get an error indicating that the /CONF/xx.PRP file was not found. It's a 404 satus - but the html in the response messed with the xml parser (which is expecting xml). Any chance the behaviour could be changed to send proper XML with empty fields rather than sending a 404 and error when there is no properties file for the device? Michael.

As I think my PLM is dying, I received a new one from Amazon as well (this morning on Prime). Mine is hardware rev V2.1, but the date code is later at 1514. I assume the date code is YYWW.... Michael.

ISY does not use flow based if-then-else logic. It's event based. So, you need multiple programs each implementing if-then for your two conditions.

I use a 6 button KPL - top and bottom are the light on/off and the middle 4 represent fan speeds off, low, medium and high.

Away for the computer right now, but I thought programs did already have a 'Comments' section....?

Indeed thanks everyone. My main PLM lost some links this weekend - no other symptoms. It's about 3 years old - so I've preemptively ordered a replacement. Nice to save some $$ and still get the latest and greatest. It just sucks that I'll have to get up a ladder for my motion sensors for the PLM switch.

Thanks @LeeG! I missed that one... Michael.

Cool! When did /notes get added to the REST interface? I have a .php script that does most thing via REST, but notes I've been getting via SOAP.

Communications don't need to be scrambled (encrypted) to solve this, but they do need signing to ensure authenticity, so messages cannot be faked. This can be done without a button - each device needs to contain a unique private and public key pair. The public key is sent to a device during initial linking (stored with the link record) and then the sending device of any message signs all messages with the private key. Devices can then verify and reject messages with an invalid or no signature. Yes, I'm aware that the same algorithms are used for signing and encryption, but only message signing is needed to solve this. Encryption is possible with this as well - the sending device simply signs the outgoing message using its private key, then encrypts using the public key of the expected receiving device (from the original link record). Easy enough. However broadcast and group messages still need to be supported, and this is not trivial with an encrypted payload. On the 60Hz thing - this is a wireless vector, using your dual band devices to do the sync work for the attacker.

To me its easy to fix the main issue - require the user to hit a button on the device before it will accept a link request.... Like zwave. However, is there any protection from discovering the current PLM ID and a device ID and sending commands 'from' the PLM that the device would accept? How do you protect against this method being used to add new links? I can't see any way around some form of cryptographic message authentication with a key exchange during initial linking so that devices could ignore invalid messages.

I disagree that it makes no sense. To answer the questions posed: 1) 50%, obviously (to me at least!). This is how devices respond, why shouldn't scenes? 2) Still off, since 50% of zero is still zero. Setting a scene to 50% should set all constituent members to 50% of their configured values. This is entirely consistent with the view that sending a 'scene on' sets all constituent members to 100% of their configured values (rather than 100% of their current setting - which wouldn't make sense IMO).

For controller shift, my stick needs to be 2-3' from ISY to work.

Agreed! I do agree with your direction - an HTML5 admin UI is *definitely* the way to go!

For the SOAP ones, its because the ISY opens a socket back to the caller - and when you come thru a proxy the caller appears to be the proxy itself. So the callback never makes it to the client. Even if it did work - it would make the point of an SSL proxy somewhat redundant. For webservices, there is a proxy module I need to install to handle webservices. I just have not installed and configured it (yet). I know io_guy has now converted all of his apps over to the websocket interface. Has the admin console moved yet? Or is this still using the older subscription method? If the latter - are there plans to change - or are you still waiting for a half decent websocket library for Java that supports basic authentication?