larryllix

If you can access your router see if you can locate your ISY IP address in the "attached device" table. That should give you some IP addresses to try in your browser as a URL.

OK read all instructions before starting Your ISY probably needs to have a new eprom installed. Here's how Open the case and ....j/k Try clicking this link. http://isy

Off topic somewhat: I am just starting to trust ISY more for state variable triggering programs. I spent a lot of time writing industrial control stuff on real time systems like ISY (but bigger) and I am just beginning to realise the power of letting the ISY engine do the dirty work for me. The only trouble is that all the programs involved can be obscure to find when you make function changes. It does simplify programming a lot. Not so many subroutine calls. ahhhh! *** Feature request for Admin Console to make a list on command of all programs that use a given variable. Not a search with one on each result but rather a list of all programs using it. *** Maybe right click on a variable in the variable page and a menu to select, or just a list of programs pops up???

I don't think that is going to do what you want. There is no trigger that can turn your lights off. You need an Else clause in the first program to trigger on the end nodes of the time frames. ie. 2:00 AM and Sunrise. And be aware that your lights will turn off every day whether away or not at the same times. That may not be a bad thing but may bite you down the road when other programs are written and you wonder why. ------------ RUN_AWAY_LIGHTING If From Sunset To 2:00:00AM (next day) Or From 5:00:00AM To Sunrise (same day) Then Run Program 'AWAY_LIGHTING' (If) Else Run Program 'AWAY_LIGHTING' (Else) <---no condition needed. You just want them off no matter what. --------------- I like timers better but you are dealing with external events (like sunrise)

Very interesting. I don't know why they wouldn't have gone full protocol on the open or closed node and copy the style what other protocols have done. One signal that is updated on status change but a resend every x hour/minutes as a heartbeat. Wait! I think I just figured out why not. Simple HA would get triggered and not be able to sort out whether the status changed. ...Of course, ISY could do it because it has variables that could remember the last known status and react accordingly sorting out whether the door was just operated or it was just a heartbeat.

I was thinking the same thing. GFI's are not used in the Canadian Electrical Code but I thought perhaps in the US NEC they might be. I have been told these AFCI breakers are really bad for passing Insteon signals. I did have some trouble with my MBR reliability using an AFCI but after enough dual-band devices were installed it seems reliable now, especially at nights when I rely on them, and my PV system inverters are shut down.

We are just trying to BoyScout the little old lady across the street but she didn't want to go!

I wish SH would not have discontinued their power supply adapter that would connect into MS units without having to fudge wiring to connectors or use cable adapters adding up to as much as the MSes.

It still appears that the HUB's only HA is some timers. That makes it mostly Home Control, not automation. ISY does complex logic. They mention coloured lighting, the new HA fad, but not what.

Your ISY heartbeat monitoring program will send you a notification. The heartbeat is a spare node transmitted to your ISY and not dependant on the door sensor operating. When the heartbeat stops the timer in the program times out and notifies you.

This is the usual style heartbeat used elsewhere. Think of the heartbeat this way. "I'm alive".... "I'm alive".... "I'm alive".... "I'm alive".... I just hope my heartbeat never goes off but just beats, beats, beats, also. To monitor the health your heartbeat program (ISY already does it) but... OK lesson in most database programme basics - In the Admin Console - select Program tab - select the sub-Tab "summary" or right click on the very top "My programs" and select "status" - in the database chart of your programs click on the title "Last Run" You will probably see a chunk of blank entries at the top of this column - click the "Last Run" title gain to re-sort the column in descending order - find your heartbeat program in the left and second columns and view the last time ISY received a heartbeat from your device. - also if it shows true and running then... your ISY is again watching out for you and making your life easier!

On and Off are not required with ISY. One signal, On or Off should suffice. This is how most heartbeats are done. I haven't experienced a bi-polar heartbeat out of the dozens I have experienced before. Insteon units are a new style for me. LeeG's program, demonstrated, should work with either style just fine. ISY can detect a repeated initiator with it's "control" trigger.

I guess the folder condition only turns off initiating triggers. and a time frame end node is a trigger. Violating that same line of logic is the folder state changing state to False also stops the running program also. This also happens with programs when you disable them. - If the program is already running. It stops executing. - If the same program is already disabled and another program runs it (if, then or else) like a subroutine it still runs to completion if allowed by all other influences.

Maybe you stated your conditions backwards?

If you cannot access it remotely how can you update ISY firmware? The other thing that happens to some running multiple firmware versions is Java applet access to the ISY version doesn't match.

Sorry. I know very little of the Mac apps or operations. Have you installed certificate(s) allowing remote access?

Isn't MobiLinc remote access? Your text is not detailed enough. What are you using to attempt remote access that is not working? Was remote access working before?

As you add dual band Insteon devices the signal usually gets more reliable also.

You can also watch your program status list and see if "Last run" is updating a lot for some programs.

Or....You could just use an everyday SwitchLinc Dimmer to control everything. Off and On, dim and brighten for lights. Double tap On for Fan Low and then again for Med and then again for High Fan. Double tap Off turns fan Off. Lights will be a natural Off being connected to the switch. If lights are connected to the FanLinc, anything can be done. The SwitchLinc dimmer looks like a regular Decora wall switch but will take some wife training but won't freak out visitors or be so décor rude. Other SwitchLinc dimmer switches in the room can duplicate the commands and styles so that your fan can be operated from other angles too. Just some thoughts. I don't like the KPL for everyday switches.

My newly acquired KPL can trigger events in my ISY and my ISY can do anything!

Basically ditto the above. I installed a double breaker 3 wire circuit into the first box, as close to the distribution panel as possible, containing an old X10 phase coupler bridge that is supposed to handle Insteon signals also. From there I ran one phase to three more surface mount receptacles, creating a power bar arrangement, where my PLM, ISY and my older alternative energy system monitoring computer and monitor is plugged-in. My ISY is perched atop one surface mount receptacle facing semi-upwards. I have another panel run by a UPS system with two 120 Volt phases that are all Insteon device signal repeated to. No signal bridges connect these to the main panel other than Insteon plug-in devices. When the power is out ISY is dead anyway so I have never tested if the signal transfer is successful when on UPS. Any backed up lights are all manually switched on.

If one doesn't use a browser how else would we access our ISYs to programme them?

My last Tasker update cleaned out all my programs and I haven't had the energy to recreate them since. Going away seemed to be hardest to make reliably and responsive. I used Tasker to turn on and off my WiFi etc., but it turned out the built in Samsung algorithm saved more battery energy than Tasker did dong it less smartly than the built-in Android algorithms. There are other cooler things I want to do once I get back to it.

Those are not even legal for usage in my electrical utility world.