EVictory

I have recently installed a Generac 22KW generator. I built GenMon on a RPi to monitor the generator per the https://github.com/jgyates/genmon/wiki site. GenMon is working correctly and is on IP xxx.xxx.xxx.29. I then added the 'genmon' device to my NodeLink and called it Generac. I am running version 0.9.27 of NodeLink on IP xxx.xxx.xxx.26. I have changed the IP address on the Generac tab of NodeLink to the IP address of my GenMon RPi which is xxx.xxx.xxx.29. I left the port at the default 9082, which is what GenMon expects. I have restarted NodeLink a few times but keep getting repeated rows of the following on the NodeLink main page. By repeated, I mean a new row is added every second or two. 2019-01-20 15:51:17 - GenMon: Data Error: Object reference not set to an instance of an object. [genmon1] As a troubleshooting step, I copied the ClientInterface.pf file and its required library files to the NodeLink RPi. Using Putty, from the NodeLink RPi I am able to use the ClientInterfcae program to communicate with GenMon and am able to display my generator's status data. This indicates that the NodeLink RPi can communicate with the GenMon RPi. I am running v5.0.13A on my ISY. IO_Guy, can you offer any suggestions? -Emile ClientInterface Success.pdf

I have corrected the miss-spelled SceneProxy and the DimTO statements. Thanks for the heads up. I moved into this relatively new home last year. I am experiencing a lot of communication errors between my ISY and various devices. The home has many arc-fault breakers as well as many ground-fault outlets. These are causing a lot of the comm problems. Ground-Fault Outlets - The electrician who wired my house took a lot of shortcuts. Many of the SwitcheLinc devices are wired 'downstream' of ground-fault outlets. I have been slowly working on either replacing the ground-fault outlets or rewiring them so that the SwitchLincs are not downstream. The latter means adding additional ground-fault outlets on downstream outlets to meet code. Arc-Fault Breakers - I have some SwitchLincs that give comm errors when installed on a particular circuit protected by an arc-fault breaker. Yet if I move the SwitchLincs to another circuit, they work fine with no comm errors. The loads are simple lights. It appears that the arc-fault breakers are causing comm errors, especially on circuits that are furthest from the breaker panel. About half of my devices are dual-band. I have tried to ensure I have a dual-band device in every multi-gang box. Anyone had any experience with arc-fault breakers causing comm problems? -Emile

Kevin, My weather pages now respond to the LocationSize = 0 commands. Thank you. Per your request, I have attached some sample Console.log files representing log levels 0, 1, 2, & 3. Thanks, -Emile Console-Level-2.log Console-Level-3.log Console-Level-0.log Console-Level-1.log

Is there a way to suppress the location information obtained from APIXU for a weather location? For example, I have longitude and latitude defined for my location of Folsom LA. However, the APIXU is displaying this as MARTINVILLE on the weather screen. I know of no town named Martinville near here. Below is my w-fols.cfg file. [w-FOLS] type = Weather label = Folsom Weather, location = Folsom-LA BackgroundColor = black CharColor = lightgreen DinTo = 5 The MARTINVILLE is showing up on the line below the label (Folsom Weather). By the way, thank you for such a great program! -Emile

The detailed logs were a big help. It showed the last three lines as below. 12-29-18 23:15:08 Sev: 0 Screen-> New TimeTempDesc tt-Sensors 12-29-18 23:15:09 Sev: 5 Error accessing ScreenParams:store['store']KeyError('store',) 12-29-18 23:15:09 Sev: 3 Exiting with history trace (None) This led me to look at the tt-Sensors.cfg file. This file defines a screen that displays the temperature and humidity from some local 1-wire sensors I have setup with NodeServer. Technically, it is displaying ISY variables that are set with the values. What was causing the errors is I had a Location = command that still had the WU location in it. location = pws:KLAFOLSO4 Once I fixed this to use the new location, SoftConsole loaded.

Kevin, I have been working on converting my consoles to v3.2 and have setup an APIXU weather account. As you know, WU service is ending 12/31/2018 and I wanted to switch over. I have three consoles and have been working on converting just one first. I managed to figure a good bit of it out but have run into an error that has stumped me. The last three entries in the Console.log are as follows: 12-29-18 22:17:54 Sev: 3 Default hub is: ISY 12-29-18 22:17:57 Sev: 5 Error accessing ScreenParams:store['store']KeyError('store',) 12-29-18 22:17:57 Sev: 3 Exiting with history trace (None) Right after these entries, the console fails to start. A minute or two later, it will try again with same results. I have attached the Console.log file. To upgrade, I went into maintenance mode (tapped screen five times), selected Select Version, then Download Release. After this finished, I went back and selected Use Stable Release. Then I restarted the console. It failed to start. I then started modifying my cfg files, copying the upgraded files to the RPi using WinSCP and watched the Console.log file to see the affect. I managed to get my APIXU key setup in the auth.cfg file and created a weathersources.cfg file. PS: The 'Problem with processing node:' lines have been there sense v3.0. I think they are caused by my PolyGlot and NodeServer ISY devices. With v3.0, the console still worked even with these errors. Console.log

PS: I upgraded from v2.8 to v3.0 with no issues.

Keven, It has been a while since I last posted on this thread and a lot has happened since then. I have moved to a new home in the last year. When setting up the ISY in our new house, I went with ISY firmware v5.x instead of v4.x. I have rebuilt my two 3.5" screen SoftConsoles from scratch and created a third unit using a 7" display. The 7" version is really nice. In the process of rebuilding the SoftConsoles, I came across an issue you may want to know about. I also have a question. These are listed below. Issue: I attempted to run the pisetup.sh per your instructions when rebuilding the 3.5" SoftConsles. I used the latest version of Stretch and put the pisetup in the boot directory. When running it, I told it to auto-reboot. I could not get the script to to run all the way through. It would fail at or before running the adafruit-pitft.sh script. To get the SoftConsole working I manually ran adafruit-pitft.sh and then manually ran installconsole.sh. I was installing SoftConsole v2.8. Incidentally, the pisetup.sh of v2.8 worked flawlessly when setting up the 7" display where I did not see this problem. Question: In my system I also have io_guy's NodeLink (OWLink) for 1Wire temperature and humidity sensors. This system uses a Raspberry pi with a 1Wire HAT board to turn the Pi into a sensor controller that makes the sensor readings available in the ISY. The v5.x NodeLink version makes each temperature and humidity sensor available as a read-only device in the ISY that can be used in programs. I have also copied the sensors values into variables for compatibility with the original OWLink. My question is, how can I display the temperatures in the SoftConsole? I would like to be able to have a page that displays the various temperature and humidity values on a SoftConsole screen similar to the Weather or TimeTemp type pages. For example, I would like to have a page that show the temperature and humidity from outside on the rear patio or in the garage/workshop. Since I place the temperature values in ISY variables, is there a way to display the value of an ISY variable. Another way to do this might be to query the OWFS on the NodeLink RPi directly. You have created an assume system with SoftConsole! The addition of the icons in the weather and timetemp screens looks great. Thanks ahead of time for any help you may provide. -Emile

Kevin, I obtained your 3D case from Thingiverse and printed it. The glass screen of my 3.5" PiTFT display board became separated from the PC board and would fall forward out of the printed case if I tilted the Soft-Console. (The double sided tape came loose.) Also, I noticed a lot of light escaping from the edges of the display which was bothering me at night. Therefore, I modified the top cover of your case to include a lip (or bezel) that holds the glass of the display under the case. The edge of the glass display is now covered so no light can be seen around the edges. I used metal threaded inserts (instead of nuts) that I melted into the ABS screw holes to hold the case together. Inserts were used for the 4 mounting holes of the Pi board, the two holes of the display board and for the screws holding the top case to the bottom case. I also added a third screw to the top of the case. Last, I enlarged some of the screw holes so the inserts could be installed with less drilling. Below is a link to the threaded inserts I used. Insert P/N" 1GNL7 https://www.zoro.com/value-brand-ultrasonic-insert-m25x045mm-pk100-1gnl7/i/G2398496/?q=1GNL7 I have attached a picture of the assembled case with the modified top. I also included a picture of the modified case top showing what the metal threaded inserts look like installed. You install them with a soldering iron. I have attached a zip file containing the modified top and bottom case STL files in case you are interested. -Emile caseV3.zip

Kevin, I removed the homesystem file and upgraded to v2.11. I have set the two Daemon flags you mentioned. With the X10 module, you cannot add an X10 device to a scene, so none of the empty scenes were for X10 devices. I no longer have any X10 light switches or appliance modules as all have been upgraded to insteon. I still have some X10 motion sensors, a few X10 RF remotes, an X10 V572RF32 Receiver, and an X10 XTB-IIR X10 Transmit Booster. I deleted all empty scenes - I did not realize they would cause problems. Some of the empty scenes were left over after some experimenting. Others were left over from a garage that has been removed. It may very well be a problem with the communications between the Pi and the ISY. I have noticed the Soft-Console sometimes seems to take a while when loading at the point it reads the ISY. The Pi running Soft-Console is a Pi model 2B with a USB wireless adapter. Also, I have a Pi running OWLink that also reports ISY timeouts from time to time. The OWLink Pi is using the wired NIC. I am not sure what could be causing this. Any thoughts on how to troubleshoot something like this? -Emile

Kevin, I meant to say config, not catch.txt. Attached is a screen shot from the second attempt to install the console files. Looks like it could not locate a module called config. The log.txt file I sent earlier shows a lot of tweaking I was doing on Sunday to the config.txt and its associated x.cfg files. I was making adjustments to the Soft-Console screens then trying them out. At times I had bad configs that I then corrected. I have not made changes since Sunday so any failures after that represent the issue. I have attached the log.txt from today. I actually have configured the yaml file for watchdog by adding my router IP and am interested in this program. I have another Raspberry Pi running OWLink from Automation Shack. That Pi goes unresponsive about once every few weeks. Something like watchdog would help. Just to be clear, I am NOT seeing the entire Pi reboot. I am seeing Soft-Console crash and reload. The homerelease was not intentional. Is there a way to turn it off? -Emile log.txt

Kevin, The last couple of weeks have been busy so I have had little time to work with Soft-Console until this past weekend. I ended up building another SD card from the ground up so I could leave off TightVNC and use the realVNC built into Jessie. That makes two times I have built Soft-Console. I could not get the scripts to install the Soft-Console files either time. The script installs all of the libraries just fine but it fails with the setupconsole.py and githubutil.py scripts saying it could not find the catch.txt file. It is not a problem for me as I manually copied the files over to the home/pi directory using WinSCP but I wonder if others had the same problem. I did some testing with the X10 devices (from the X10 module). The Soft-Console ONOFF type works just fine with the X10 device. When I press the device button in Soft-Console, the ISY sends an X10 ON command. When I press the device button again, the ISY sends an X10 OFF command. In my case, I had programs detect the X10 commands and take actions by setting a variable to 0 or 1. I think I could have done this in Soft-Console using the SetVar type but I wanted to test the X10 device. I am having a Soft-Console reboot problem. Even while leaving the Soft-Console unattended, I have noticed it spontaneously crashes and reloads the Soft-Console. When I look in the log.txt file, I see this sequence. Consoleexit script: restart - /home/pi/Console/config.txt - codeerror I have attached all of my log and config files. My Data.zip

Kevin, The code changes worked! (See below.) The Select Version buttons on the Maintenance screens also worked. They make upgrading rather simple. That's kind of neat. The Set Flags screen now appears to work as well. Perhaps this weekend I will try setting up some buttons to link to an X10 devices to see if they will work. I also need to implement some alerts. I have a few questions: 1. I noticed Rasbian Jessie installs VNC. But I noticed your installer installs tightVNC. Is there a reason you prefer tightVNC over the native VNC that comes with Jessie? 2. I notice you install OpenVPN. What is this used for? Thanks for a great program! -Emile

Kevin, I deleted and reinstalled one of my thermostats. As I thought might happen, when I added it back, it looks different. Now I have three nodes instead of one. Now the thermostat shows as firmware v.0B in the ISY. I also opened up the physical thermostat and it is stamped with physical v1.15. Below is a browser page again. <properties> <property uom="n/a" formatted="Auto" value="8" id="CLIFS"/> <property uom="n/a" formatted=" " value=" " id="CLIHCS"/> <property uom="%" formatted="50.00" value="50" id="CLIHUM"/> <property uom="n/a" formatted="Cool" value="2" id="CLIMD"/> <property uom="degrees" formatted="71.00" value="142" id="CLISPC"/> <property uom="degrees" formatted="63.00" value="126" id="CLISPH"/> <property uom="degrees" formatted="69.50" value="139" id="ST"/> </properties> Now the values are in the same order as your sample (uom first). As you can see, I still do not have an HCS value. I suspect this early version of the thermostat does not support it. The SoftConsole still crashes when I try to select thermostat screen via nav buttons. I discovered a new issue. Went to Maintenance screen and selected Set Flags as you asked. When I pressed the MAIN button -- it crashes. In fact, if I tap any button on the Set Flags screen it crashes. All of the other Maintenance screens seem to work. (I have not tried any of the Select Version buttons yet.) -Emile

Kevin, Your post earlier today was at 12:36 PM. My post was at 12:38 pm. I was typing my 12:38 post when your post came in and did not see it until tonight. The logs I sent you earlier did not have the flags set as you asked. I will do that shortly after this post. Below is the result I get when enter http://192.168.200.25/rest/nodes/1D%206D%208C%201 in my browser. This is the Downstais-AC thermostat, address 1D 6D 8C. Both thermostats are older 2441TH Insteon Thermostats, firmware v.00 and I use F. Notice the CLIHCS values are spaces. Attached is an image in the ISY <properties> <property uom="n/a" formatted="Auto" value="8" id="CLIFS"/> <property uom="n/a" formatted=" " value=" " id="CLIHCS"/> <property uom="%" formatted="51.00" value="51" id="CLIHUM"/> <property uom="n/a" formatted="Auto" value="3" id="CLIMD"/> <property uom="degrees" formatted="72.00" value="144" id="CLISPC"/> <property uom="degrees" formatted="63.00" value="126" id="CLISPH"/> <property uom="degrees" formatted="69.00" value="138" id="ST"/> </properties> I have had them for several years. I have upgraded my ISY firmware many times since first adding them to the ISY. I have seen other cases where I have needed to uninstall and reinstall devices in the ISY to get the latest support offered by ISY firmware releases (remotelincs, leak sensors, etc.). I may try deleting and reinstalling one of my thermostats. Or, it may be that the early thermostats did not offer as much functionality as later versions. -Emile

Kevin, Attached is a zip file containing logs and copy of config.txt and tstat-DN.cfg files. I looked at the log files before I pressed the navigation button to enter the thermostat screen. The Console.log did not change when I pressed the button. In other words, nothing was added to the Console.log when I pressed the button and it crashed. However, the log.txt did get the lines below added as a result of my pressing the Downstairs-AC button. ----------------------- Traceback (most recent call last): File "console.py", line 237, in <module> config.DS.MainControlLoop(config.HomeScreen) File "/home/pi/consolestable/displayscreen.py", line 207, in MainControlLoop K.Proc(config.PRESS) # same action whether single or double tap File "/home/pi/consolestable/displayscreen.py", line 103, in NavPress self.SwitchScreen(NS, 'Bright', 'NonHome', 'Nav Press') File "/home/pi/consolestable/displayscreen.py", line 99, in SwitchScreen self.AS.InitDisplay(nav) File "/home/pi/consolestable/screens/thermostatscreen.py", line 144, in InitDisplay self.ShowScreen() File "/home/pi/consolestable/screens/thermostatscreen.py", line 110, in ShowScreen self.info[item["@id"]] = (int(item['@value']), item['@formatted']) ValueError: invalid literal for int() with base 10: '' -Emile Thermo Crash.zip

You are correct regarding the thermostats. When on the screen before the thermostat screen, the right navigation button shows the label of the next screen. I am pressing the navigation button for the thermostat. The console quickly tries to start display something but quickly crashes, All I can catch is that its a relatively dark screen with two lighter buttons laid out in the center of the screen. Could very well be the thermostat display. Thinking this was related to the Section name I gave the screen being able to link to the thermostat name in the ISY, I tried experimenting with the names. In my ISY the thermostats were named Downstairs AC and Upstairs AC. Therefore I named the thermostat sections [Downstairs AC] and [upstairs AC] respectively. Thinking that the space character was messing up the linking, I renamed the thermostat to Downstairs-AC and even DownstairsAC in both ISY and SoftConsole Section names. None of this made any difference. I am at work and the raspberry pi is setup on my bench at home. It is unplugged at the moment so I will have to get this for you later tonight. -Emile

Kevin, With your help, I have managed to get the Soft-Console functioning. The issue was with the X10 'L7- TV Scene' device as you suspected. Although I have the word 'Scene' in the name of this device, it is NOT a member of any ISY scene. X10/A10 devices created with the X10 Module cannot be added to ISY scenes. The first thing I did was open a browser and run a .../rest/nodes page. Please see the attached 'Before Changes.png' snapshot. The X10 device (FF 0C 07 2) had a node flag="0" value. I have 30 X10 devices added to my system. The majority of them are used as aliases for X10 8-button RF keypads. All of the other X10 devices have a flag="128" value. Also, this was the only X10 device that had a node number in the address of 2 as all others had a node 1. As I mentioned earlier, I have had the X10 Module since I purchased the ISY many years ago. This particular device has probably been part of my configuration for many years and has been carried forward through many ISY firmware upgrades. I suspect that somewhere along the way, it became corrupt. What I did to fix it was delete this X10 device then recreate it. Once I recreated it, the device showed up differently in the node list. Please see the attached 'After Changes.png' image. After re-creating the X10 device, it now has a flag="128" like all of the other X10 devices. The Soft-Console now runs. ISSUE #2: I am having an unrelated issue. I am having trouble adding a thermostat. I have two ISY (2441TH) thermostats in my system named Downstairs-AC and Upstairs-AC. I have attached the two cfg files I have configured for them. When I attempt to add either thermostat into Soft-Console, the button does show up in the console. However, if I tap the thermostat button, the Soft-Console briefly displays a screen showing two buttons and then crashes. QUESTION: I have an unrelated question. My Console.log file is showing a line (in red here) as follows: 01-02-17 20:02:34 Sev: 3 ---MAN-Weather 01-02-17 20:02:34 Sev: 4 Not on a screen list (unavailable) What does this mean? The Soft-Console appears to run anyway. From what I can see so far, Soft-Console is great!. I may build one of the wall-mounted versions in the future. Thank you for your help and for sharing this application. -Emile Thermostats.zip

Kevin, I have an ISY 994i/IR PRO running firmware v4.5.4. I have the Networking Module, the X10 Module, and the Z-wave module. I do not have any Z-wave devices as of yet. Yesterday I also saw the FF 0C 07 2 posted in the log.txt log file as well. Yesterday I searched through my entire ISY setup and could not find an Insteon device with that address in use anywhere. However, after reading your post I went back looking again and found the offending device. With the X10 Module, you can create A10/X10 devices that can then be used within programs. ISY will track the status of the X10 device as best it can. You cannot add X10 devices to scenes though. The offending device is an X10 device called 'L7- TV Scene'. Apparently, the ISY assigns these A10/X10 devices an Insteon type address because as you can see this device has the address FF 0C 07 2. (Looks like the FF is on all X10 devices, the 0C equates to the house code L, and the 07 equates to the device code 7.) Please see the attached image showing what the X10 type device looks like in the ISY admin console. I cannot assess the Raspberry Pi now as I am at work and the Pi is at home and powered off. I am pretty sure I have not tried to map to the name 'L7- TV Scene' device in my cfg files. This ISY X10 device object is left over from the past. When I first moved to ISY, I had a lot of X10 devices, which is why I purchased the X10 module. However, today the only X10 devices I have are 8-button RF remotes, 2-3 RF motion sensors, and a whole-house X10 RF transciever. This particular device was added as an alias, meaning I do not actually have an X10 appliance or switch device using code L7. I have a program that listens for a change in the 'L7- TV Scene' device and then executes a program to turn on TV, dim lights, etc. I used the X10 alias device in the ISY program instead of testing for X10 signals directly in programs for convenience. I am phasing out the X10 devices. Could it be that your program is encountering the X10 device and does not know how to deal with it? If there is anything you need me to provide, just let me know. -Emile

Forgot to mention, I am using version 2.0 that I just downloaded over last few days. Thanks

Kevin, I am attempting to install the Soft-Console onto a Raspberry Pi 2 B+ with a 3.5in PiTFT. I have created a config.txt file, a cfglib directory and several .cfg files based on your examples. When I try to start the console, the little screen turns blue, it loads all of my configuration files. At the end of this, it looks like it is attempting to login to the ISY and I believe that is where it is failing. The little display shows the http://192.168.x.x/rest/ URL right before it fails. I can use a browser on my PC to query the ISY using rest commands with no issue. If I change either the ISY username or password to a known bad value, the Soft-Console fails differently as it displays a red page indicating an incorrect username or password. I am using the auth.cfg file to hold the ISY logon information. ISYaddr = "192.168.x.x" ISYuser = "myuser" ISYpassword = "mypassword" I have tried the above lines with and without the double-quotes. My ISY password has an asterisk (*) within the password. Thinking it was the culprit, I temporarily removed the * from the password but had same results. My ISY does NOT have the self-signed cert installed as its behind NAT and I do not need it. Attached are the log.txt and console.log files. They were zipped using 7zip. Do you have any ideas as to what is wrong? PS: Looks like a great program. Thanks for all your hard work! Mr Emile Victory Logs.zip

That took care of the issue. Thank you!

I just upgraded my ISY 994i/IR Pro from firmware v3.3.10 to v4.0.5. I noticed that the backup performed during the upgrade processed failed. Luckily, the upgrade appears to have worked as I am now running at v4.0.5 and all appears OK. I then tried to backup again. And again it failed where I received a popup message 'Could Not Retrieve File /CONF/172.PRP'. After clicking OK on this message, I receive another message 'Could Not Create the Zip File.' When I look in the PC folder where I was going to store the backup file, there is a file there but it is only 1K in size. Any ideas on what is causing this and how to clear it?

Mechel, Just spoke with SmartHome today and they indicate that TouchLinc is not discontinued and they have no plans to do so any time soon. I purchased one after the July 2012 date of your post. (Had not seen this post.) In fact, you can still purchase them today. However a recent update to HouseLinc broke support for TouchLinc and SmartHome could not give a date when this would be fixed. (I had to roll back to an earlier version of HouseLinc.) Houselinc is good at allowing easy configuration of many Insteon device options. But the way you setup TouchLinc in HouseLinc leaves much to be desired. It would really be nice if TouchLinc were supported in ISY. Can you provide any more information on your comment in the earlier post that 'TouchLinc is now discontinued'?