mattavila

I just had an "ID 10 T" error.... I created two programs that are in a constant loop. Now I cannot login to the admin portal. Any suggestions on how I might disable programs from running on a boot of the ISY so I can possibly get logged back into the console to correct the error? Thanks

Kevin - I believe that I was running without a confi.txt file previously, then again as I re-installed its difficult to verify. One note that I haven't re-tried... my ISY password used to contain a special character - a comma. Ive actually found a couple of instances where that has been problematic (one being my trading account password) so I decided to change it while I was re-imaging the raspberry pi.... short answer is Im not 100% sure as I made two changes simultaneously. I did verify the password issue however - you cannot have a comma in your ISY password with THIS project, it behaves badly! Appreciate the tip on using multiple configuration files from the CLI. I was just able to show this to my wife and her response was "WOW.... that's fantastic!" We can actually see this without our glasses and that's huge for the "over 50 crowd" In other words I just got a shopping pass to buy some more raspberry pi kit and work with your code a bit more. My only real issue is I still have a day job. At any rate, now its time to dig in, read your documentation, read more on python... then start having a bit of fun. Appreciate the opportunity to learn, create , and contribute. Cheers! Matt

Kevin Appreciate your willingness to dig deeper. I did change my password as it contained special characters, also for "good measure" did a full reinstall on the Raspberry Pi from your script. So I found a "rookie" mistake I was making... the config file! While I did have stuff in there that WAS valid (being my ISY address & password), I had the file NAMED..... (can you guess..... "exampleconfig.txt" - DOH). At this point I have it working, albeit just your example. Im re-working that now and re-thinking MY naming convention on the ISY as well. Going to play the next couple evenings and help a couple new users out that just got their ISY's today. Next purchase is a book on python - then again I do have a subscription to Safari online through my company... now only to save them as PFD's Thanks again for the assist - appreciated Matt

After reading some of your earlier responses I kind of figured there may be a version issue - and continued to poke around your documentation. Im running the "wget https://raw.githubusercontent.com/kevinkahn/softconsole/master/docs/consoleprep.sh" command and executing the script from there. I DID happen to see the install script appears to be calling for v1.1.tar.gz - what I cant figure out is where to point it for current release of code (not sure what the directory structure is for your releases. That may be some of the issue? Ill jump into it later this evening... wife want to go out for dinner so Im offline for awhile - Thanks for the assist Matt

Kevin, THis one really caught my attention so I gathered the remaining parts I needed over the weekend. I'm NOT a coder, but can follow along to a limited extent. What I keep getting is similar to what was posted earlier; pi@localhost ~/consolestable $ sudo python -u console.py CSignal: 17 Screensize: 320 480 CSignal: 17 /usr/lib/python2.7/dist-packages/urllib3/connectionpool.py:732: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.org/en/latest/security.html (This warning will only appear once by default.) InsecureRequestWarning) Traceback (most recent call last): File "console.py", line 83, in <module> config.ISY = isy.ISY(config.ISYrequestsession) File "/home/pi/consolestable/isy.py", line 206, in __init__ configdict = xmltodict.parse(r.text)['nodes'] File "/usr/local/lib/python2.7/dist-packages/xmltodict.py", line 311, in parse parser.Parse(xml_input, True) xml.parsers.expat.ExpatError: no element found: line 1, column 0 Any idea what this may be? Ive grabbed the release as of today, reinstalled and this keeps popping up. the config file has been slimmed WAY back, hopefully enough to get started with rudimentary communication (pasted below). I tried with YOUR config example and same results. Putting in IP of my ISY obviously helped - also had my ISY on different ports, so I changed them to defaults of 80 & 443 (seemed to eliminate more errors) pi@localhost ~/consolestable $ cat config.txt ISYaddr = "10.10.1.124" ISYuser = admin ISYpassword = password HomeScreenName = BR HomeScreenTO = 90 DimLevel = 5 DimTO =25 DimHomeScreenCoverName = MyClock MainChain = "Office", Local, "Main", MyClock .... (few trivial (i think) things afterwards Appreciate any assistance Matt

Well, as I said, Im not "new" to using these products - however Id chalk this up to an ID-10-T error.... Digging into the links table showed some major inconsistencies (especially that I had just added it as a new device and only linked a few programs to it). At any rate, a complete "device resort" seems to have fixed ALL the issues - at least from a status indication perspective. Now responds to all status from programs and other keypads. The behavior of the "turn on to 100%" is a scene is say dimmed to 50% is still annoying, but Ill fight that another day.

I recently swapped a dead 2486D 8 button keypad with a "new" dual-band 5 button keypad (didn’t need the extra buttons) and for whatever reason the newer model seems to behave differently. I now have three of these "new" devices in my system, and they seem "different". the latest swap had indicators for my garage door status and one button set for NON-TOGGLE OFF mode (this would then only CLOSE the open door). so far this seems to work okay. The button is a RESPONSER to the door status program, although I cannot get it to light when the door program is true (all other keypads work fine - two "old" and one other "new"). In fact NONE of the "other" buttons, A,B,or C seem to respond and indicate status, just the "main ON or OFF button", and D button (D is a responder to an IOlinc connected to a freeze alarm)....This is particularly frustrating! I have changed that garage status to respond to ONLY the IOLinc and it still doesnt work either. I also have another "new" that’s part of lighting scenes and when the load dimmer (a single 2476D) is say 50% on, pressing the keypad button doesn’t turn the lights off, but rather UP to 100%... it then takes a second press to turn them off (still annoying, but not as much as the above status) Not sure what anyone would need to see although I can post most anything form the ISY setup necessary. Im not new to using this - but one would THINK its somewhat simple. All suggestions would be appreciated. Thx

I don't have any X10 in my system, but I did see that as well. I'm not sure where its coming from however. According to the log X10 is getting a control of "P13", value "Off (11)", but no idea whats generating this. I'm guessing that translates loosely to housecode "P", device "13", and an off signal to device "11"? No idea whats generating that, but more importantly why its affecting insteon devices that aren't even showing in the log?

I have a 994 running 4.0.5 firmware and have been noticing some random lights being on in the morning. I've pulled logs a couple times now and don't see anything out of the ordinary, however with a case of insomnia I witnessed an "event" happen this morning where an alarm (IOLinc) appears to have triggered and the family room lights went to full bright. The log output is below. Interior / OffKeypad Status 50.00% 05/01/14 02:43 AM System Log Interior / OffKeypad Status 0.00% 05/01/14 02:44 AM System Log X10 P13 Off (11) 05/01/14 02:44 AM System Log Interior / Christmas / FamilyRoomTable Status 0.00% 05/01/14 03:30 AM System Log Interior / FamRoomKpd / Freezer Alert Status 100.00% 05/01/14 04:01 AM System Log Special / Freezer / freezer alarm-Sensor Status 100.00% 05/01/14 04:01 AM System Log Interior / Kitchen / kitchen sink / Freezer_Alarm Status 100.00% 05/01/14 04:01 AM System Log Scene:Scenes / all interior Beep 05/01/14 04:01 AM Program Log Scene:Scenes / all interior Beep 05/01/14 04:01 AM Program Log Interior / Family Room - Fireplace Spots Status 0.00% 05/01/14 04:01 AM System Log Interior / dining room / DinKey / DinKey-FireSpots Status 0.00% 05/01/14 04:01 AM System Log Interior / Kitchen / kitchen sink / Freezer_Alarm Status 0.00% 05/01/14 04:03 AM System Log Interior / FamRoomKpd / Freezer Alert Status 0.00% 05/01/14 04:03 AM System Log Interior / OffKeypad Status 50.00% 05/01/14 04:04 AM System Log Special / Freezer / freezer alarm-Sensor Status 0.00% 05/01/14 04:05 AM System Log What is REALLY strange is the fireplace spots went on to 100% brightness, but are NOT reflected in the log! My daughter tells me that "something" is on almost daily in the morning when she gets out of bed, however I still don't see it. The error log isn't showing any activity at this time - however I have no idea what this stuff is either 04/30/14 08:25 PM System -100 [DHCP] state=RENEW 05/01/14 03:08 AM System -170001 [TCP-Conn] -1/-140002 FYP 05/01/14 03:09 AM System -170001 [TCP-Conn] -1/-140002 Portal-Dispatch 05/01/14 03:09 AM System -170001 [TCP-Conn] -1/-140002 FYP 05/01/14 03:10 AM System -170001 [TCP-Conn] -1/-140002 Portal-Dispatch 05/01/14 03:10 AM System -170001 [TCP-Conn] -1/-140002 Portal-Dispatch Only ONE change, a switch replacement late last week - and I did a swap with the ISY. This seems to have been happening for about a month now, and I hadn't given it too much thought till now. I haven't done anything to the system, programs, or otherwise until a switch crapped out last week (hence the swap-out). Any ideas would be appreciated.

Bingo! Exactly what I was looking for. Thanks a bunch io_guy... this REALLY helps me out.

Thats why I was asking. I havent put a meter on the line, although interconnecting all the detectors (and the AC line that runs between them all) has a 4th wire for common trigger. Being that the 4th wire is in with 120VAC I would assume that this too is 120, but who knows. My thought was to attach the sense to that line if the things were to trigger, but Im not familiar with the characteristics of it (meaning does it go high and stay there, momentarily go high (or low)....) Appreciate the feedback though

Has anybody had any experience connecting smoke alarms to an in-linelinc? My thoughts are to use the "trigger" wire (that runs common to all the smokes in my home) and attach this to the sense. One (or two for redundancy) in-linelinc's should then be able to trigger the ISY to run scenes (flash all exteriors for example - makes spotting the house for the FD easier). Wondering if anyone has tried this Thanks

I agree that in a SCENE there isnt a way to necessarily add a wait - but you could do it in a PROGRAM. Try creating a program that activates a couple scenes - pretty simple to add a wait in either an "if or then" and achieve the same effect. I use them in vacation programs (waits) with a "random" variable to simulate differences in scene activation (it helps give the appearance of home occupancy). Give that a try and see how it works for you

I installed 3.3.1 a couple days ago. The only thing I see broken at the moment is my evening and morning programs to adjust the ramp rate and on levels dont seem to run - either as they did under stable code, or trying to run the "else" manually. As they are in a deferent room from my systems, Im not sure if the beep is working either (Ive been too tired to hear it at sunrise - when they are set to beep a couple times.... working for my in-laws for free this last week) The switches are 2476D's v 37 & 38 firmware.

One 'issue' that I was having with following this logic, the switch itself MUST be a controller to the scene for this to work. Meaning when you build the SCENE, be sure to add the switch you want to set the ramp. rates and brightness levels as CONTROLLERS, not responders (otherwise they don't show up this way in the ISY program this way). I fought with this for the better part of an evening till I figured out that little nugget. Otherwise, Ive got a few nifty dimmer changes myself that are time based - and the kids are none the wiser why the hall light isnt shining at a megawatt every night