bsobel

Michel if the ISY gets a comm error during the query does it change the current state to a default value or just leave it unmodified? To the poster if you can't restore the device you have com issues. This is going to continue until you tackle them.

If one of your programs gets into a tight loop generating insteon traffic (eg event causes traffic something in that traffic causes the program to refire) all kind of bad happens. This may be what you were seeing.

The switch is somehow in 8 button mode not 6 button mode. The docs show how to switch it off. The top bottom will then turn the load on and the bottom off. Bill

You might want to consider using state variable instead.

Has the temp changed by more than 2degrees while you were testing it? You can force it by putting a hair dryer 'near' it and let the temp fluctuate, you should see ISY receive the current temp.

Can I suggest changing the data cable. I'm wondering if a bad one could cause corruption that winds up manifesting this way. Long shot but cheap test.

Oops, concentrated on the then logic and didn't consider the if correctly...

Repeat 2 times Set Scene 'Housewide Scenes / Nightlights' On Wait 5 seconds You turn off the lights and while you wait 5 seconds you turn the shade back on. Then this wait finishes and you turn it back off. You shouldn't need the repeat 2 times but if you think you do lower the wait a bit and raise the wait in the other program so they no longer overlap.\ edit: Easier fix may be to move the setting of your flag down to after the repeat loop. Timing will still take 10 seconds tho....

Lee you are correct. I still have a couple of these and you must physically set them on or off before the ISY 'locks' the setting as the non-toggle command.

Wondering if there was any update to this, I'm seeing the same thing here as well. Bill

I think I'm seeing this too on a 6 button. I can not set the D button to always off. I think the issue was found in another thread, putting the button into a scene as a responder and setting its On level to 0 (it was for a fanlinc scene) seems to have caused it. It says is ISY always off but instead is always lit up and always generates an ON.

I create a scene for all the devices I want off, make the keypad button a controller and set it to always off mode. Works great.

More data. I have a brand new 6 button v.41 switch that I just installed and i'm seeing the same behavior when programmed through the current release. The button says it is programmed non-toggle off via the admin console but it is in non-toggle on mode when used (and ISY sees an ON not an OFF). I've reset it quite a few times now with the same results. So suspect either a firmware change or a bug in the release effecting this. If there are tests I can run, happy to do so. Bill

I had horrible problems with my iSY's not rebooting but coming up properly when I reset the power. Same symptom only the one blue light was on. UDI had me turn off Internet Access (that sets the UPnP in the router) and the ISY's that were troublesome are working fine now. I suspect you are hitting the same bug. If it comes right up after a power cycle I'd be almost positive. This happened to me quite a bit lately. You can still have internet access to the unit, just manually setup forwarding rules in your router.

Im in the middle of a project to do just this and plan to make what I'm working on available in one form or another (software only or maybe a full device). I'm do this on the Raspberry Pi platform. I currently configure the system with the either/or the bluetooth and wifi MAC of the devices I want to track. It does both bluetooth queries as well as arp queries to determine when someone is around. I tie that to the ISY via variables (e.g. I can say if this device is found via either arp or bluetooth then set an ISY variable to X) or I can count the number of 'unknown' bluetooth devices and set another variable (I use that so the house knows if I likely have company or not). I'm hoping to play more with Bluetooth and get range information, I'm thinking of a model where I'll have 4 of these in 'areas' of the house and I can get an idea of not only who is home but what zone they are likely in. If you don't want to wait for what I'm cooking up, I'd suggest getting a Raspberry pi youself to play with, great little addon for the ISY if you think of it as a slave device to the ISY.

If this is verbatim they are reversed, swapping them should resolve it.

Oops, my advice was for the motion sensor flood light kit SH sells, not the 2420m units you have...

Change the programs to issue fastON's and fastOFF's. The fastON with the inline linc turns off the sense until you send the fastOFF as I recall. This way the switch will disable the sense feature and be the master until turned off...

Depending on the size of the lamp you may be able to shove a microdimmer and a touch sensor tied to its sense wire...

I've seen this numerous times with my new 994iz units. My older 99i's never did this. Perchance are you on the newer hardware as well?

Lee, thanks that is what I thought would happen. I also considered the massive 'other' scene to query but it felt pretty ugly to maintain. I guess I'll have to beg UDI for a UI option to ignore errors from a device at some point. And thanks for the hint on clearing the error, I'll add that to the home 'wakeup' program so query all the syncrolincs I add.

a) Using an appliance linc would have the exact same issue with communications, so really hoping UDI can comment on options here (the base issue remains can you ignore a device on query failures or not) An appliance linc would not be able to determine between the low power 'standby' mode and 'on' vs true off vs 'on'. In addition with the appliance link in off state you couldn't turn the TV on with a remote (since it would have no power and not be in standbymode) Cheers, Bill

Ok I have a situation where I have an Outletlinc that turns off power to my TV when I am not at the house. In addition I want to put a SynchroLinc into the mix (TV into SyncroLinc and Syncrolinc into controlled outlet of the Outletlinc). The goal is to save power when I am not there but still get SyncroLinc events when I am there. My concern is that while I am gone the SyncroLinc will cause 'can not communicate' errors in the console when the startup or nightly query runs. Is there a way to tag a device as 'dont warn on this' since I know failure to communicate here will be common when I am not home. If I disable a device I presumed I couldn't query it, but would ISY still accept events from it? Any other ideas of how to do this in a way that will work?

I only have java 7 as well. No issues.

When a device can not be found the system often reports the 'can not determine engine' (wish it would report 'unit not found'). So it sounds like it can't talk to it at all, possibly dead?