EVictory

I have figured this out. The problem was that I needed to add the Java Runtime Parameter -Xmx512m to my Java. I had done this in the past due to slow response but had not realized the setting is removed when you upgrade from one version of Java to the next. Now that this is figured out, I am upgrading to a faster micro SD card. I am going to try a SanDisk Industrial 16GB card at 50/80mb/s. The Industrial grade supposedly is tougher card. Thanks to all that offered help. This forum is awesome.

I am running malwarebytes AV and I disabled it and firewall on all attempts. This is standard practice anytime I upgrade firmware. Yes, I am using the ZIP file and not decompressing it. Yes, I always download the launcher, dashboard, and admin jnlp files along with the firmware. Yes, I tried clearing the java cache, all three boxes as always. I am on a Windows 10 Pro PC. Have used this PC many times to do upgrades in the past. I have had the replacement SD card for a few years which is why I used the FS command to format it during the rebuild. Right now, I suspect the SD card. I do have new Sandisk cards on order. They will arrive Tuesday I will try it with a brand new card. This one has me stumped.

The replacement SD card is a PNY 16GB SDHC device. I have had this card for a year or two. I have ordered two SanDisk Industrial 16GB cards but they will not arrive until Tuesday. I mention this in case this card is not fast enough.

I am attempting to upgrade from firmware 5.3.1 to 5.3.4. The process proceeds to about 9%, then I get the two popups in the attached image. BACKGROUND: My ISY is a 994i/IR Pro (with 500 Z-Wave). I do not have any Z-wave devices yet. Today I noticed the ISY was not functioning (programs were not running). Visual inspection revealed the red Error LED was flashing (memory LED OK) which indicates the SD card had failed. I then went through process to replace the SD card. 1. Connected with TELNET and did FS command to format SD card. 2. Then logged into admin console and loaded firmware 5.3.1, which was the level of the last good backup I have. 3. After loading firmware 5.3.1, I then restored my last good backup. 4. At this point the ISY appeared to be working. I then made a few changes that were not in the last backup file. For example, I had changed three Motion Sensor II's from battery power to AC power. (I removed the Battery node). 5. After making a few minor changes, I performed another backup. 6. After this, I attempted to upgrade the firmware to 5.3.4 and received the 2 errors. WHAT I HAVE DONE: 1. I read on this forum that I may need to reboot the ISY. I rebooted via the admin console but still received the 2 errors. I then rebooted by cycling the power to the ISY but still received the 2 errors. 2. I downloaded the 5.3.4 zip file again from this forum but still received the 2 errors. 3. I downloaded the 5.3.3 zip file and tried upgrading to it. I got the same 2 errors. \ Does anyone have any ideas?

Thanks for all of the suggestions. Everyone was on track. I had an extra dimmer module that I added to my ISY. I was then able to fully control it and it DID post its manual activity to the ISY. This confirmed that the issue had to do with the PLM's links table. I did as suggested. I restored factory defaults to the PLM (hold in button while powering up). I then restored the PLM from the ISY. This worked! Smarthome has the 2413S as unavailable and I have read the threads where SH indicates it has been discontinued. I also read that at least two people were able to order PLMs in September before they went unavailable again. I have four PLMs where this one is the newest. All of the others were replaced because of issues. I have an electronics background so I replaced the electrolytic capacitors on two of the older PLMs and also on this newest one on Saturday thinking that was the issue. My older PLMs have not been tried and may or may not work. I also have a 2413U left over from an old Houselink. When taking it apart, I noticed the main board looks the same as with the 2413S's main board. It looks like the only difference is the seral vs the USB daughter board. I read the thread where someone made a USB to serial adapter out of a Raspberry Pi zero. Has anyone tried installing a serial daughter board in a new 2413U? What are you doing about failing PLMs and replacing them?

My ISY is a ISY 994i/IR Pro running v5.3.1 firmware and UI. My PLM is a 2413S v9E and shows as Connected. About 5 days ago I lost power for a bit. When power came back, I noticed none of my motion programs were working. I tried powering off the ISY and PLM. Then powering on the PLM, waiting a minute, then powering on the ISY. This made no difference. At first I thought it was just effecting my motion sensors (several 2844-222's). The motion sensors do appear to be sending. In one hallway, I have two motion sensors where either sensor will directly turn on the hallway light. By directly I mean I have the motion sensors linked directly to the light for ON activity. Normally, either motion sensor turning on will also trigger a program to turn off the light after a few minutes. Motion does turn on the light but the light never goes off. (My program never gets tripped - I checked.) All of my other rooms with motion sensors, the ISY normally receives the motion ON and triggers a program. None of these motion programs are working. But then noticed it is not limited to just motion sensors but the ISY seems unable to see any insteon device activity. For example, if I manually turn ON a wall switch, the ISY does not see the change and will not trigger any programs tied to that switch. The strange thing is I can query any device and they are updated as expected. My motion sensors are connected to wall power (no batteries). If I query one of them, the ISY is updated. If I manually turn ON a light at the wall switch, the ISY does not see this. If I then query that light switch in the admin console, its status will change. Programs that trigger off of a keypad link button action, never run. However, if I also have a light linked to that button, the light does turn ON with the keypad link button press. The ISY is able to control devices. For example I can turn a light ON/OFF from the admin console and scheduled programs do turn devices ON/OFF. I have set debug level to 'Details' and have used the Event Viewer to monitor traffic. I never see an event coming in from devices. If I manually press a wall switch, nothing is received by the ISY in Event Viewer. Yet if I query a device from the admin console, I do see two way communications in Event Viewer. That is, I see the query be sent and the device respond back. This is very strange. Any ideas?

To find the latest firmware version, do the following: Open Chrome browser to forum's home page at: https://forum.universal-devices.com/. The sixth grouping down is titled 'Current Release, Betas, and Bug Reports'. Click on this link. The resulting page shows the latest firmware versions. Currently the latest version is 5.3.0. Click on the 'Release4 5.3.0 is now available' item. (Version 5.3.1 is a test version if you want cutting edge.) The resulting page has information about the latest release, including links to download the latest firmware. There are two versions of firmware for different ISY hardware configurations. Download the one that matches your ISY.

Kevin, I am working on re-doing all of my consoles to use Buster (instead of Stretch) and the latest version of SoftConsole. To this end, I upgraded my oldest console with a Raspberry Pi 3 B+ to take advantage of the built-in wi-fi. (The USB Wi-Fi adapter I was previously using on the model 2 Pi was not not working every now and then.) I installed SoftConsole from scratch using pisetup.sh. I found the Adafruit 3.5" screen was not configured correctly upon completion. I got it working by referring to old documentation I had and to another SoftConsole also running an Adafruit 3.5" touchscreen. However, I thought you may be interested in what I found. During the pisetup questions, I indicated I wanted a 35r touchscreen. However, after setup finished the /boot/config.txt file contained the following: # --- added by adafruit-pitft-helper Thu 23 Jul 2020 10:20:27 PM CDT --- dtparam=spi=on dtparam=i2c1=on dtparam=i2c_arm=on dtoverlay=pitft28-capacitive,speed=64000000,fps=30 dtoverlay=pitft28-capacitive,rotate=0,touch-invx=true,touch-invy=true # --- end adafruit-pitft-helper Thu 23 Jul 2020 10:20:27 PM CDT --- To get the SoftConsole to work with the 3.5" screen, I changed this to the following as this is what was used on my working 3.5" SoftConsole. I decided to just comment out the original dtoverlay lines. # --- added by adafruit-pitft-helper Thu 23 Jul 2020 10:20:27 PM CDT --- dtparam=spi=on dtparam=i2c1=on dtparam=i2c_arm=on dtoverlay=pitft35-resistive,rotate=0,speed=20000000,fps=20 #dtoverlay=pitft28-capacitive,speed=64000000,fps=30 #dtoverlay=pitft28-capacitive,rotate=0,touch-invx=true,touch-invy=true # --- end adafruit-pitft-helper Thu 23 Jul 2020 10:20:27 PM CDT --- I think the pisetup program may not be handling the 3.5" screen setup correctly. Thought you might want to know. PS: I noticed you had the 2.8" screen using a speed of 64000000 and frames per second of 30. What is the best speed and fps settings for a 3.5" screen? Am I missing anything? -Emile

Kevin, That fixed it. I added a line to the touchdefinitions file containing the new definition. Having been in IT for many years, I am well aware how 'updates' can have unintended consequences. Thanks for your quick help.

Kevin, I have had a Softconsole running for several years using a 7" touchscreen from the raspberry foundation. My screen connects to the RPi with a flat ribbon cable and it is in landscape mode. The micro SD card in this softconsole died (ie, became unreadable). Therefore, I have been attempting to build the softconsole from scratch using a new SD card and the latest version of buster. I am having trouble getting the softconsole to run correctly and it appears to have something to do with the 7" screen. I have ran pisetup twice now with the same results. The 7" screen shows the desktop while booting but either continues to show the desktop are goes dark, once softconsole starts. If I do a 'sudo systemctl status softconsole', the service appears to be running. (See below). No Console.log file is generated. pi@console-22:~ $ sudo systemctl status softconsole ● softconsole.service - SoftConsole Loaded: loaded (/usr/lib/systemd/system/softconsole.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-07-21 22:44:24 CDT; 1s ago Process: 1702 ExecStartPre=/bin/sleep 5 (code=exited, status=0/SUCCESS) Process: 1703 ExecStart=/home/pi/consolestable/runconsole.py (code=exited, status=0/SUCCESS) Main PID: 1704 (python3) Tasks: 1 (limit: 2068) CGroup: /system.slice/softconsole.service └─1704 python3 console.py Jul 21 22:44:18 console-22 systemd[1]: Starting SoftConsole... Jul 21 22:44:24 console-22 softconsole[1703]: Starting using directory: consolestable Jul 21 22:44:24 console-22 systemd[1]: Started SoftConsole. I then stopped the service and attempted to manually start the softconsole as shown below. After both attempts to install with pisetup, I got the 'touchscreen device cannot be found' error and also the file not found error for the .HistoryBuffer/hlog file. During the pisetup questions, I specified a pi7 screen with the power connector on top (flipped screen). When the 7" screen does show the desktop, it is flipped as requested. pi@console-22:~ $ sudo systemctl stop softconsole pi@console-22:~ $ sudo python -u ./consolestable/console.py pygame 1.9.4.post1 Hello from the pygame community. https://www.pygame.org/contribute.html 07-21-20 22:46:17 Console ( 1764) starting in /home/pi/consolestable Traceback (most recent call last): File "./consolestable/console.py", line 182, in <module> utilities.InitializeEnvironment() File "/home/pi/consolestable/utilities.py", line 107, in InitializeEnvironment ts = Touchscreen(os.path.dirname(config.sysStore.configfile)) File "/home/pi/consolestable/touchhandler.py", line 160, in __init__ self._f_device = io.open(self._touch_device(), 'rb', self.EVENT_SIZE) File "/home/pi/consolestable/touchhandler.py", line 308, in _touch_device raise RuntimeError('Unable to locate touchscreen device') RuntimeError: Unable to locate touchscreen device exitlogging 07-21-20 22:46:17 Exiting with history trace (0) 07-21-20 22:46:17 Suppressing History Buffer Dump for Exit Trace Process AsyncLogger: Traceback (most recent call last): File "/home/pi/consolestable/logsupport.py", line 225, in LogProcess with open('/home/pi/Console/.HistoryBuffer/hlog', 'a') as f: FileNotFoundError: [Errno 2] No such file or directory: '/home/pi/Console/.HistoryBuffer/hlog' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap self.run() File "/usr/lib/python3.7/multiprocessing/process.py", line 99, in run self._target(*self._args, **self._kwargs) File "/home/pi/consolestable/logsupport.py", line 253, in LogProcess with open('/home/pi/Console/.HistoryBuffer/hlog', 'a') as f: FileNotFoundError: [Errno 2] No such file or directory: '/home/pi/Console/.HistoryBuffer/hlog' pi@console-22:~ $ Do you have any idea what I am doing wrong? -Emile

Kevin, The dir(wiringpi) returned a short list and len(dir(wiringpi)) returned 8. So, wiringpi was corrupt. Uninstalling wiringpi and reinstalling it fixed the issue. After reinstalling wiringpi, there were 203 items returned by dir(wiring). I did update pip and removed homeassistant as maintenance measures. After all of this, I was able to start SoftConsole!!! Thanks so much for your help. I think SoftConsole is a great piece of software. I will be retiring in about two months. After retirement, one of my projects is to rework all of my SoftConsoles where I rethink all of the screen layouts and leverage MQTT. Below are two pics of my control center in the utility room. At the top is an 8-port network switch, the ISY, and network patch panel for incoming network. At bottom is modified PC power supply and home brew power distribution for ISY, network switch and all the RPis. In middle (shown below) are three RPis. One on right is my Ubiquiti wireless access point controller. The second RPi from right has PolyGlot installed. The third RPi has an RPI3 1-Wire Host Adapter hat (Sheepwalk Electronics) installed. On the third RPi I run NodeLink by Automation Shack. I have 1-wire temperature and humidity sensors installed in bathrooms, in the attic, under the back porch, etc. NodeLink makes these values available in ISY. I can add several more RPis to the right and second from right positions by stacking them.

Kevin, I moved the previousversions directory, deleted the versioninfo file, and manually downloaded again. As expected, the download worked this time. I received the on-screen messages you indicated and have attached the stagelog.log file from the new previosversions directory. However, when I try to start softconsole I get the same messages on screen about wiringpi has no attributes (see attached screen shot). The Console.log file remains unchanged since yesterday, so I do not think softconsole is getting far enough to initialize it. All throughout stagelog.log file there are notes about pip. Also, I do not use a homeassistant. You are using pip version 10.0.1, however version 20.1 is available. You should consider upgrading via the 'pip install --upgrade pip' command. Should upgrade pip? I will look into setting up a pi with mosquitto. stagelog.log

Kevin, Thanks for your response. Sorry for the delay. 1. This SoftConsole has RPi 2 Model B v1.1, an Adafruit PiTFT 3.5" touchscreen, a PiFace Shim real time clock, and a USB WiFi. Raspbian is Stretch. 2. wiringpi is 2.60.0 3. The fetch line is the last line in the comsole.log file. This looked odd to me as well. It is as if the updated started but never finished. It may have hung during download. I started update from the maintenance screen. Then left it and went into kitchen, got coffee, talked with wife, etc. When I came back to console about 10-15 minutes later, the console was unresponsive. That is, it would not respond to touch. That is when I removed power, counted to 10, restored power. Not sure what happened. We did have a power outage two nights ago where whole house generator ran for about 2 hours to provide power. I have noticed that sometimes electronics do not like generator power. At any rate, I do think something happened during update where it never finished. 4. Tried sudo python ./domanualdownload.py and it showed sha already matches. Tried sudo python -u console.py again but still get black screen. I notice the screen is black (not powered) as opposed to lit but displaying black where you can still see light behind screen. On power up, the screen does light up and displays raspbian X GUI briefly. 5. I am still using darksky. I have three softconsoles but all three show same weather data. I have not played with MQTT yet. What are you using for MQTT server?

Kevin, This morning I attempted to upgrade one of my three softconsoles to the latest v3.6.1. I believe my previous version was v3.5.1. I selected Download Stable from the maintenance screen and button briefly changed color. I left the console alone for a quite while to give it time to download but it never responded. I eventually manually rebooted it. Now, the softconsole will not start. I logged into RPi using Putty and attempted to manually start the soft console. I have included a screen shot of errors shown in Putty. Below are the last 8 entries from the console.log file. It shows my fetching new version as the last entry. 05-16-20 09:49:51 Sev: 3 Long term: Humid and Partly Cloudy generically shortened to: Humid&Partly Cloudy 05-16-20 09:49:51 Sev: 4 Long term: Mostly cloudy throughout the day. 05-16-20 09:53:07 Sev: 4 ISY Extra info in event: ST/Status/139/1D 6D 8C 1/NoneOrderedDict([('fmtName', 'Temperature')]) 05-16-20 10:40:18 Sev: 4 Long term: Mostly cloudy throughout the day. 05-16-20 11:07:32 Sev: 3 ISY: busy for 22.1313 seconds 05-16-20 11:30:44 Sev: 4 Long term: Mostly cloudy throughout the day. 05-16-20 11:36:03 Sev: 3 Entering Console Maintenance 05-16-20 11:36:33 Sev: 3 New version fetch(currentrelease) I am not sure what happened but it looks like it hung attempting a download. Do you have any ideas on how to recover?

@Michel Kohanim, I am having a similar backup issue. I am on 5.0.16B. When I try to backup, I get 'Could Note Create the Zip File' and 'Could Not Retrieve File /CONF/NODES/4F9553.REC' errors. I can telnet in and delete this file. Is it safe to delete this REC file? -Emile