siegeld

I'm surprised that you mention a 2500 sq feet limit. I thought zwave would scale well to a larger sized installation, given its mesh design. Do you have experiences that should make me worry? I am thinking of deploying zwave with your new controller in a large home.

I've had an ISY for a few years now, and I am entirely happy with the product. The staff are reliable and have created a product that is rock solid. It just works. I highly recommend this device.

I upgraded to this new release, hoping that this would fix the problem of adding my new V.35 devices to a scene. No luck. I still get the same problem as before - when I add the device to a scene it programs away for a little while, then a request times out.

Would you be so kind as to post an example of Java code that prints out the insteon address of devices that are double clicked? I'm not sure how the args to onTriggerStatus are used. Thanks!

Any advice how I can get notified of a Fast On or Fast Off event from the JDK?

Ah, so to be clear, it worked for you? I'll delete and recreate the program tomorrow to test again.

Actually, it is working after all! Here is the program, for the record: If Status 'Master Bath - Toilet' < 30% And Status 'Master Bedroom Dressing' < 30% And Control 'Master Bedroom Dressing' is switched Off Then Set 'Master Bath - Toilet' Off Set 'Master Bath - Overhead' Off Set 'Master Bath - Vanity' Off Else - No Actions - (To add one, press 'Action')

Yes, what you describe is what I'm looking for.

If Status 'Foo' < 30% AND Status 'Bar' < 30% AND Status 'Baz' < 30% AND Control 'XYZ' is switched Off Then ... It seems that the < tests are not working correctly...

I have the following IF statement: If Control 'Foo' is switched On Or ( Status 'Bar' is Off And Control 'Bar' is switched Off ) Then ... The then does not seem to get executed in either case - be it Foo getting switched on or Bar being switched off. If I delete the entire Or part, the Foo switch does work.

Fixed. I upgraded to the latest beta. Thanks.

I'd like to have ISY respond to, say, a "fast-off" action on a switch even if the switch was already off. Is there a way to do this? The reason for this, and I think this might be a common request, is that sometimes I bind fast-off to turn all lights off in the room. The switch that you are issuing the fast-off on may already be off for some reason. It is not user-friendly to have to first turn the switch on, and then fast-off, to get the fast-off action to trigger.

Are there any plans for a Z-Wave version of ISY?

Oh, the other related request which I have was as follows: I want to define a scene, say Night Lights ON, that is enables certain lights, but is not linked to any particular "controller" button. I would like to be able to have ISY run a program when this scene is turned ON or OFF. This would allow, for example, triggering Night Lights On from the JDK, which would turn on the scene, and also, if one was defined, run a program on that event.

MikeB and Michel: That's fine if MikeB would like to send his. I also have an ICON dimmer that is no longer installed that I could send. Either way is fine with me. Michel - my guess is that the bug has something to do with how the Insteon address is parsed or reformatted by ISY. I've noticed an issue with leading zeros in the first two bytes of the address. There appears to be some inconsistent behavior in the JDK with regard to addresses that start with a 0X.YY.ZZ. I can examine this more, but if I recall correctly I think that I need to omit the leading 0 when sending addresses via the JDK. Perhaps the bug concerns how ISY formats an address with two fully zero bytes?

Did some more testing. It really appears to only be an issue with XX.00.YY addresses, and only when I send a command from the ISY. When I toggle the switch itself status is reported back to ISY.

Yes, that's exactly the problem I am having. When I toggle the switch itself, I do get the status update. The problem occurs when from ISY I send an ON. Like you, I do not get the status update back. This is why I'm pretty sure it is an ISY bug.

I've done this. No luck. I've done a bit of experimenting, and, as odd as it seems, the 00 in the middle of the address does seem to be the problem!

After much poking around, it appears that ISY does not get status responses from Insteon devices with 00 in the middle two bytes of its address. That is, addresses of the form XX.00.YY. ISY will control such devices, but it does not get status updates back. If I query the device, I do get the proper status. I'm pretty sure this is the case because two devices where I have not been getting back the status updates both have 00 in the middle of the address. Could you check the code to see if this could be possible?

Perfect, thank you.

Thanks. What I mean about the scene feature request is this. Let me use an example: I have a program that runs at sunset that enables the "Nightime Scene". I'd like to get a JDK event that says, basically, "Nightime Scene - ON".

As an example of the final request, you already have a NOTIFY function, that sends out email. I'd like the have a version of this NOTIFY that triggers a method in the Java JDK.

Let me be more specific. First, I am interested, from an ISY program or from the JDK, to be able to trigger an action based on a scene being turned on or off, WITHOUT THE SCENE BEING LINKED TO A KPL BUTTON. I do not see a way to do this. I would think this should be possible because the ISY is made a member of each scene (group), so it is aware of when a scene is turned on or off. Second, I would like to be able to, from the JDK, trigger some sort of psudo event in the ISY that runs a program. In other words, I want the JDK to be able to enable a condition that will cause the ISY to run a program. Again, no KPL buttons or other switches involved. Purely from the software. Finally, I would like an ISY program to invoke some method in the JDK as an action from a program. Again, this should not be linked to something actually going on with Insteon hardware. Thanks!

It would be great if you could have some way for a program to generate an SDK event, and nothing more. That way, you could for example trigger something in java when certain conditions have been met.