restored backup and now its dead

[mworsnop]

I have a Z2 and just got a SEL. I did the backup on the Z2 and restored to the SEL. It rebooted but now there is no web HS3.

I can get to the shell but have no idea what to look for

Anyone have an idea?

Support phone call no one answered gave up there.

[rmasonjr]

at the prompt, let's look at the startup log:

cat /usr/local/HomeSeer/Logs/Startup.log

[mworsnop]

I dont have a ZWave stick on USB0. That is my WX Cumulus connection

How do I start HS without rebooting?


root@hometrollerSEL:/# cat /usr/local/HomeSeer/Logs/Startup.log
5/24/2017 12:41:24 PM ~!~Startup~!~Settings Loaded.
5/24/2017 12:41:26 PM ~!~Startup~!~
5/24/2017 12:41:26 PM ~!~Startup~!~*********************************************** *********************************
5/24/2017 12:41:26 PM ~!~Startup~!~ HomeSeer version 3.0.0.318 Edition: HS3 Standard (SEL) Starting Now
5/24/2017 12:41:26 PM ~!~Startup~!~*********************************************** *********************************
5/24/2017 12:41:26 PM ~!~Startup~!~
5/24/2017 12:41:26 PM ~!~Startup~!~Creating Class Objects...
5/24/2017 12:41:26 PM ~!~Startup~!~COM port classes started.
5/24/2017 12:41:26 PM ~!~Startup~!~Application interface class started.
5/24/2017 12:41:26 PM ~!~Startup~!~Web server class started.
5/24/2017 12:41:26 PM ~!~Startup~!~E-Mail SEND class started.
5/24/2017 12:41:26 PM ~!~Startup~!~E-Mail RECEIVE class started.
5/24/2017 12:41:26 PM ~!~Startup~!~Plug-In Interface class started.
5/24/2017 12:41:26 PM ~!~Startup~!~Local voice recognition class started.
5/24/2017 12:41:26 PM ~!~Startup~!~Database SAVE process started.
5/24/2017 12:41:26 PM ~!~Startup~!~Loading configuration file ...
5/24/2017 12:41:26 PM ~!~Database~!~Opening (Mode=Read Only) up HomeSeer database /usr/local/HomeSeer/Data/HomeSeerData.hsd
5/24/2017 12:41:26 PM ~!~Database~!~Loading Devices...
5/24/2017 12:41:26 PM ~!~Load Config~!~4 total devices loaded.
5/24/2017 12:41:26 PM ~!~Load Config~!~Loading Event Groups...
5/24/2017 12:41:26 PM ~!~Load Config~!~Loading Events...
5/24/2017 12:41:26 PM ~!~Load Config~!~0 total events loaded.
5/24/2017 12:41:26 PM ~!~Load Config~!~Loading COUNTERS...
5/24/2017 12:41:26 PM ~!~Load Config~!~Loading TIMERS...
5/24/2017 12:41:26 PM ~!~Startup~!~HomeSeer version is: 3.0.0.318
5/24/2017 12:41:26 PM ~!~Startup~!~Creating Speaker Client Interface Object...
5/24/2017 12:41:26 PM ~!~Startup~!~This version of HomeSeer is registered as a HS3STANDARD version.
5/24/2017 12:41:27 PM ~!~Info~!~Remote plug-in API interface started on port 10400
5/24/2017 12:41:27 PM ~!~Startup~!~Checking for available plug-ins
5/24/2017 12:41:27 PM ~!~Plug-In~!~Found plug-in: HSTouch Server, version: 3.0.0.68
5/24/2017 12:41:28 PM ~!~Plug-In~!~Found plug-in: Z-Wave, version: 3.0.1.83
5/24/2017 12:41:28 PM ~!~Startup~!~Initializing Plug-Ins
5/24/2017 12:41:28 PM ~!~Info~!~Plugin HSTouch Server has connected. IP:127.0.0.1:38060
5/24/2017 12:41:29 PM ~!~Plug-In~!~Finished initializing plug-in HSTouch Server
5/24/2017 12:41:30 PM ~!~Info~!~Plugin Z-Wave has connected. IP:127.0.0.1:38062
5/24/2017 12:41:30 PM ~!~Z-Wave~!~InitIO called, plug-in version 3.0.1.83 is being initialized...
5/24/2017 12:41:30 PM ~!~Z-Wave~!~Database: Opening (Mode=Read Only) up HomeSeer database /usr/local/HomeSeer/Data/Z-Wave/Z-Wave2.db
5/24/2017 12:41:30 PM ~!~Z-Wave~!~0 event actions were loaded from HomeSeer.
5/24/2017 12:41:30 PM ~!~Z-Wave~!~0 event triggers were loaded from HomeSeer.
5/24/2017 12:41:30 PM ~!~Z-Wave~!~New Interface: ============================================================ ==========
5/24/2017 12:41:30 PM ~!~Z-Wave~!~New Interface: ----------------------------------------------------------------------
5/24/2017 12:41:30 PM ~!~Z-Wave~!~Initializing Z-Wave interface New Interface (HomeSeer SmartStick +) on /dev/ttyUSB0
5/24/2017 12:41:30 PM ~!~Z-Wave~!~New Interface: ----------------------------------------------------------------------
5/24/2017 12:41:30 PM ~!~Z-Wave~!~New Interface: The Z-Wave Command Execution Thread was Started or Restarted.
5/24/2017 12:41:30 PM ~!~Plug-In~!~Finished initializing plug-in Z-Wave
5/24/2017 12:41:30 PM ~!~Web Server~!~Local IP address is: 10.215.81.4
5/24/2017 12:41:30 PM ~!~Web Server~!~Web Server started on port 80
5/24/2017 12:41:30 PM ~!~Web Server~!~UPNP Discovery started
5/24/2017 12:41:30 PM ~!~Z-Wave~!~New Interface: The Z-Wave API Execution Thread was Started or Restarted.
5/24/2017 12:41:30 PM ~!~Startup~!~Start automation engine...
5/24/2017 12:41:30 PM ~!~Startup~!~Initializing Speaker Client Interface
5/24/2017 12:41:30 PM ~!~Speech~!~Listening for remote speaker connections on port 10401
5/24/2017 12:41:30 PM ~!~Database~!~Opening (Mode=Read/Write) up HomeSeer Energy database /usr/local/HomeSeer/Data/Energy/Energy.hsd
5/24/2017 12:41:30 PM ~!~Startup~!~Updater services starting...
5/24/2017 12:41:30 PM ~!~Startup~!~Starting DDNS service...
root@hometrollerSEL:/#

[rmasonjr]

to see if HS is indeed running:

ps -ef |grep -i mono

If you see one or more mono processes, then it is running.
If it is not running, do this to run HS manually:

cd /usr/local/HomeSeer
./go

[mworsnop]

I got it online by unplugging the USB cable for the WX Station.
I then installed the plugins and it seems to work ok so far.

BUT ALL of the events are not there!

Ideas?

[rmasonjr]

Yikes - not sure - maybe try the restore again?

[mworsnop]

I cleared out the Logs first and made a new backup.

Last time it asked me to register the software again but then said it was already registered. Hoping it will work this time.

[Pete]

For a static USB named port I put in a UDev rule which will provide same name / port with a reboot.

IE: for Davis / Meteostick / WeeWx / RFX Stuff do this:

SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="AI02XA5J", SYMLINK+="davis", MODE="0666"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="04XF1RQZ", SYMLINK+="ttyUSB-RFXrec433-A", MODE="0666"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="A1Y0QACC", SYMLINK+="ttyUSB-RFXtrx433-A", MODE="0666"

To check for the USB Z-Wave stick serial number do this:

udevadm info -a -p $(udevadm info -q path -n /dev/ttyUSB0) *or ttyUSB1,2,3,4

Note too that the Z-Wave stick saves the node information and no events. Homeseer saves the events.

[mworsnop]

Where does this info need to go? I assume a file somewhere?

But first problem is the events didnt load from the backup. I started another thread on this

[Pete]

There is a help item on USB static stuff; it might be buried a bit in the help thread.

Have a look at the back up HS directory for restoring your events. Try the back up before the last backup.

Or

Look at the database back ups and use one of those.

/HomeSeer/Data# ls
1-wire HAI HomeSeerData_2.hsd HomeSeerData_5.hsd HomeSeerData_8.hsd Z-Wave
Backup HomeSeerData_10.hsd HomeSeerData_3.hsd HomeSeerData_6.hsd HomeSeerData_9.hsd
Energy HomeSeerData_1.hsd HomeSeerData_4.hsd HomeSeerData_7.hsd HomeSeerData.hsd

[mstukel]

BUT ALL of the events are not there!

Ideas?

Which version of the ZeeS2 did you have - ZeeS2V2 or ZeeS2V1? If it was the former then there might be a Mono version issue. I was under the impression that the Mono 4 update applied to the ZeeS2V2 but the SEL line was still on the Mono 3.x version. If this is the case, then I believe you will encounter problems restoring events due to the changes from Mono 3.x to Mono 4.x. You may want to check with HomeSeer support just to confirm Mono Version levels between the Zee and SEL.

[mworsnop]

How do I find the version or the hardware?

The Z2 is mono 4.5.1
The SEL I updated to 3.2.8

[Pete]

With a running Homeseer RPI set up that mono has been upgraded the events look like they are there as the names are all there. It is the triggers that go away.

Mono 4.X to 5.X shouldn't affect anything. It was only Mono 3.X to 4.X

In retrospect looking at your stuff:

homeseer@hometrollerSEL:~$ mono --version
Mono JIT compiler version 3.2.8 (Debian 3.2.8+dfsg-4ubuntu1)===>

homeseer@hometrollerSEL:~$ mono --version
Mono JIT compiler version 5.0.0 (Stable 5.0.0.100/9667aa6 Thu May 11 14:27:20 UTC 2017)

Would in fact mangle your events. (listed and meatless).

The fix is not to update Mono on a running system with Mono 3.X or rewrite all of your events.

Or

Restore an old image with Mono 3.X on it.

Here on my two HS3 builds I am currently at Mono 5.X.

I did lose all of my stuff when I updated from mono 3.X to mono 4.X and rewrote them all. It was a PITA.

I did it manually using page prints of my events bit by bit.

Note that this is not just a Z-Wave thing rather it is a Homeseer Event thing and it will affect all of your events.

It is better now to have Mono 4.X or higher up these days any how.

[mworsnop]

I havent looked to even see what mono does. So the RPI is running 3. If I update it I will loose my events?

I probably have 50 events. sigh.

What kind of DB is does HS use? I really dont understand how this happens.

What actually is the problem? Somehow HS needs to address this.

[Pete]

I havent looked to even see what mono does. So the RPI is running 3. If I update it I will loose my events?

I probably have 50 events. sigh.

What kind of DB is does HS use? I really dont understand how this happens.

What actually is the problem? Somehow HS needs to address this.

Yes

Leave your RPI at 3.28.

Sent from my TouchPad using Tapatalk