Announcement

Collapse
No announcement yet.

Cant activate plugins on newly installed HomeSeer on Linux

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Cant activate plugins on newly installed HomeSeer on Linux

    Hi!

    After finally fixing a problem related to getting HomeSeer to start up at boot I had to reinstall the HomeSeer server.

    I have followed the steps in https://forums.homeseer.com/showthread.php?t=162813 and installed HomeSeer. HomeSeer starts up beautifully, but when I add plugins and activate them they fail.

    The error message in the plugins page is the following:
    Code:
    WARNING: Failed getting InterfaceStatus from Z-Wave - the interface was not found in the list of active interfaces, the list may need to be refreshed.
    And the logs show these errors:
    Code:
    Sep-24 6:41:17 AM	 	Info	System connected to MyHS Service successfully with license ID 0.
    Sep-24 6:41:17 AM	 	Info	System connected to MyHS Service, waiting for acknowledge...
    Sep-24 6:41:17 AM	 	Startup	Start up complete.
    Sep-24 6:41:17 AM	 	Startup	HSSentry is disabled in Setup, sentry will not be started.
    Sep-24 6:41:17 AM	 	Startup	Starting Event Scheduler...
    Sep-24 6:41:17 AM	 	Error	Compiling script Startup.vb: Visual Basic.Net Compiler version 0.0.0.5943 (Mono 4.0.1 - tarball) Copyright (C) 2004-2010 Rolf Bjarne Kvinge. All rights reserved. vbnc : Command line : error VBNC2017: The library 'System.Data.DataSetExtensions.dll' could not be found. There were 1 errors and 0 warnings. Compilation took 00:00:00.1828890
    Sep-24 6:41:16 AM	 	Startup	Running the startup script Startup.vb
    Sep-24 6:41:16 AM	 	Startup	Starting Find service...
    Sep-24 6:41:16 AM	 	Startup	Updater services starting...
    Sep-24 6:41:16 AM	 	Database	Opening (Mode=Read/Write) up HomeSeer Energy database /home/christian/HomeSeer/Data/Energy/Energy.hsd
    Sep-24 6:41:16 AM	 	Speech	Listening for remote speaker connections on port 10401
    Sep-24 6:41:16 AM	 	Startup	Initializing Speaker Client Interface
    Sep-24 6:41:16 AM	 	Startup	Start automation engine...
    Sep-24 6:41:16 AM	 	Web Server	UPNP Discovery started
    Sep-24 6:41:16 AM	 	Web Server	Web Server started on port 80
    Sep-24 6:41:16 AM	 	Web Server	Local IP address is: 10.10.10.68
    Sep-24 6:41:16 AM	 	Startup	HStouch server started, waiting for clients to connect.
    Sep-24 6:41:16 AM	 	HSTouch Server	Server started on port 10200
    Sep-24 6:41:16 AM	 	Plug-In	Finished initializing plug-in Z-Wave
    Sep-24 6:41:13 AM	 	Error	Initializing plug-in(1): Z-Wave Instance::Error registering web pages with the HomeSeer server.
    Sep-24 6:41:13 AM	 	Z-Wave	Created new database /home/christian/HomeSeer/Data/Z-Wave/Z-Wave2.db
    Sep-24 6:41:13 AM	 	Z-Wave Warning	Z-Wave database file does not exist, so a new database is being created in /home/christian/HomeSeer/Data/Z-Wave/Z-Wave2.db
    Sep-24 6:41:13 AM	 	Z-Wave	InitIO called, plug-in version 3.0.1.130 is being initialized...
    Sep-24 6:41:13 AM	 	Info	Plugin Z-Wave has connected. IP:127.0.0.1:44928
    Sep-24 6:41:12 AM	 	Startup	Initializing Plug-Ins
    Sep-24 6:41:12 AM	 	Plug-In	Found plug-in: Z-Wave, version: 3.0.1.130
    Sep-24 6:41:12 AM	 	Plug-In	Found plug-in: Nest, version: 3.0.0.28
    Sep-24 6:41:12 AM	 	Plug-In	Found plug-in: MediaController, version: 3.0.0.28
    Sep-24 6:41:12 AM	 	Error	Warning, Cannot load EXE file (possibly missing dependencies) HSPI_JowiHue.exe: The classes in the module cannot be loaded.Warning, Error details with EXE HSPI_JowiHue.exe: Could not load file or assembly or one of its dependencies.Warning, Error details with EXE HSPI_JowiHue.exe: Could not load file or assembly or one of its dependencies.Warning, Error details with EXE HSPI_JowiHue.exe: Could not load file or assembly or one of its dependencies.Warning, Error details with EXE HSPI_JowiHue.exe: Could not load file or assembly or one of its dependencies.Warning, Error details with EXE HSPI_JowiHue.exe: Could not load file or assembly or one of its dependencies.Warning, Error details with EXE HSPI_JowiHue.exe: Could not load file or assembly or one of its dependencies.Warning, Error details with EXE HSPI_JowiHue.exe: Could not load file or assembly or one of its dependencies.Warning, Error details with EXE HSPI_JowiHue.exe: Could not load file or assembly or one of its dependencies.Warning, Error details with EXE HSPI_JowiHue.exe: Could not load file or assembly or one of its dependencies.Warning, Error details with EXE HSPI_JowiHue.exe: Could not load file or assembly or one of its dependencies.
    Sep-24 6:41:11 AM	 	Plug-In	Found plug-in: IFTTT, version: 3.0.1.2
    Sep-24 6:41:11 AM	 	Plug-In	Found plug-in: BLLAN, version: 2.0.35.0
    Sep-24 6:41:11 AM	 	Plug-In	Found plug-in: BLInterface, version: 2.0.4.0
    Sep-24 6:41:11 AM	 	Plug-In	Found plug-in: BLEbayMonitor, version: 2.0.6.0
    Sep-24 6:41:10 AM	 	Plug-In	Found plug-in: BLBackup, version: 2.0.47.0
    Sep-24 6:41:10 AM	 	Startup	Checking for available plug-ins
    Sep-24 6:41:10 AM	 	Info	Remote plug-in API interface started on port 10400
    Sep-24 6:41:10 AM	 	Warning	This HS3PRO version of HomeSeer is not registered and is running as a trial, 7 days remaining.
    Sep-24 6:41:10 AM	 	Startup	Creating Speaker Client Interface Object...
    Sep-24 6:41:10 AM	 	Startup	HomeSeer version is: 3.0.0.362
    Sep-24 6:41:10 AM	 	Load Config	Loading TIMERS...
    Sep-24 6:41:10 AM	 	Load Config	Loading COUNTERS...
    Sep-24 6:41:10 AM	 	Load Config	0 total events loaded.
    Sep-24 6:41:10 AM	 	Load Config	Loading Events...
    Sep-24 6:41:10 AM	 	Load Config	Loading Event Groups...
    Sep-24 6:41:10 AM	 	Load Config	0 total devices loaded.
    Sep-24 6:41:10 AM	 	Database	Loading Devices...
    Sep-24 6:41:10 AM	 	Warning	Configuration database has no devices in it: /home/christian/HomeSeer/Data/HomeSeerData.hsd
    Sep-24 6:41:10 AM	 	Database	Opening (Mode=Read Only) up HomeSeer database /home/christian/HomeSeer/Data/HomeSeerData.hsd
    Sep-24 6:41:10 AM	 	Startup	Loading configuration file ...
    Sep-24 6:41:10 AM	 	Startup	Database SAVE process started.
    Sep-24 6:41:10 AM	 	Startup	Local voice recognition class started.
    Sep-24 6:41:10 AM	 	Startup	Plug-In Interface class started.
    Sep-24 6:41:10 AM	 	Startup	E-Mail RECEIVE class started.
    Sep-24 6:41:10 AM	 	Startup	E-Mail SEND class started.
    Sep-24 6:41:10 AM	 	Startup	Web server class started.
    Sep-24 6:41:10 AM	 	Startup	Application interface class started.
    Sep-24 6:41:10 AM	 	Startup	COM port classes started.
    Sep-24 6:41:10 AM	 	Startup	Creating Class Objects...
    Sep-24 6:41:10 AM	 	Startup	 
    Sep-24 6:41:10 AM	 	Startup	********************************************************************************
    Sep-24 6:41:10 AM	 	Startup	HomeSeer version 3.0.0.362 Edition: HS3 Pro Starting Now
    Sep-24 6:41:10 AM	 	Startup	********************************************************************************
    Sep-24 6:41:10 AM	 	Startup	 
    Sep-24 6:41:10 AM	 	Startup	Settings Loaded.
    I have no idea where to even begin troubleshooting this, so all help is welcome!

    #2
    What device are you using for you Z-Wave controller?

    ZNet or USB stick?

    If USB stick do you see the device going to the /dev directory on your Ubuntu VM?

    It should be a /dev/ttyUSBXX device. If you have more than one USB device you may need to statically configure the devices in Linux.

    For the HSPI_JowiHue.exe error I would ask the author relating to what dependencies it needs to run.
    - Pete

    Auto mator
    Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
    Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
    HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

    HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
    HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

    X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

    Comment


      #3
      Christian,

      For the JowiHue plugin, there is more needed then the standard install. I do not know to much about Linux, but check this thread for more info.

      Thanks,

      Wim
      -- Wim

      Plugins: JowiHue, RFXCOM, Sonos4, Jon00's Perfmon and Network monitor, EasyTrigger, Pushover 3P, rnbWeather, BLBackup, AK SmartDevice, Pushover, PHLocation, Zwave, GCalseer, SDJ-Health, Device History, BLGData

      1210 devices/features ---- 392 events ----- 40 scripts

      Comment


        #4
        Thanks for the replies, but I do not think it is related to the plugins as this happens to whatever plugin I activate. I activated IFTTT and NEST and got the same error:
        Code:
        WARNING: Failed getting InterfaceStatus from IFTTT - the interface was not found in the list of active interfaces, the list may need to be refreshed.
        Code:
        WARNING: Failed getting InterfaceStatus from Nest - the interface was not found in the list of active interfaces, the list may need to be refreshed.
        Code:
        Sep-24 8:11:02 AM	 	Plug-In	Finished initializing plug-in Nest
        Sep-24 8:10:59 AM	 	Info	Plugin Nest with instance: has disconnected
        Sep-24 8:10:59 AM	 	Nest	INFO Connection lost, exiting
        Sep-24 8:10:59 AM	 	Error	Initializing plug-in(1): Nest Instance::System.BadImageFormatException: Could not resolve field token 0x04000b09 File name: 'Scheduler' at A.c50372b7acae91f8c739d7107e5598a0b.cf066f1952189192c754f9a4315ad10ed (System.String cbbedb59e8a61b98a7d476a6040f87642, System.String c37ae3928805bd7b7c00e1adfe3f21976, System.String cbd92a9fb44227a9ec629386ce1f0f272, System.String cfaceb49d27a3a19f398479e1bb473778, System.String c81dfe5004cb7a743d3af637d597139b1) [0x000b3] in <93c961f040e647f7b132f89548986d3d>:0 at Scheduler.PageBuilderAndMenu+clsPageBuilder..ctor (System.String pagename) [0x00171] in <93c961f040e647f7b132f89548986d3d>:0 at HSPI_Nest.WebConfig..ctor (System.String pageName) [0x0000b] in <111ef61c67414da8b80be505775a6644>:0 at HSPI_Nest.NestApp.Init () [0x00090] in <111ef61c67414da8b80be505775a6644>:0
        Sep-24 8:10:59 AM	 	Nest	ERROR System.BadImageFormatException: Could not resolve field token 0x04000b09 File name: 'Scheduler' at A.c50372b7acae91f8c739d7107e5598a0b.cf066f1952189192c754f9a4315ad10ed (System.String cbbedb59e8a61b98a7d476a6040f87642, System.String c37ae3928805bd7b7c00e1adfe3f21976, System.String cbd92a9fb44227a9ec629386ce1f0f272, System.String cfaceb49d27a3a19f398479e1bb473778, System.String c81dfe5004cb7a743d3af637d597139b1) [0x000b3] in <93c961f040e647f7b132f89548986d3d>:0 at Scheduler.PageBuilderAndMenu+clsPageBuilder..ctor (System.String pagename) [0x00171] in <93c961f040e647f7b132f89548986d3d>:0 at HSPI_Nest.WebConfig..ctor (System.String pageName) [0x0000b] in <111ef61c67414da8b80be505775a6644>:0 at HSPI_Nest.NestApp.Init () [0x00090] in <111ef61c67414da8b80be505775a6644>:0
        Sep-24 8:10:59 AM	 	Nest	INFO Nest version 3.0.0.28
        Sep-24 8:10:59 AM	 	Info	Plugin Nest has connected. IP:127.0.0.1:45140
        Sep-24 8:10:59 AM	 	Plug-In	Interface Nest is running as a trial, 30 days remaining.
        Sep-24 8:10:59 AM	 	Plug-In	Finished initializing plug-in IFTTT
        Sep-24 8:10:56 AM	 	Info	Plugin IFTTT with instance: has disconnected
        Sep-24 8:10:56 AM	 	Error	Initializing plug-in(1): IFTTT Instance::System.BadImageFormatException: Could not resolve field token 0x04000b09 File name: 'Scheduler' at A.c50372b7acae91f8c739d7107e5598a0b.cf066f1952189192c754f9a4315ad10ed (System.String cbbedb59e8a61b98a7d476a6040f87642, System.String c37ae3928805bd7b7c00e1adfe3f21976, System.String cbd92a9fb44227a9ec629386ce1f0f272, System.String cfaceb49d27a3a19f398479e1bb473778, System.String c81dfe5004cb7a743d3af637d597139b1) [0x000b3] in <93c961f040e647f7b132f89548986d3d>:0 at Scheduler.PageBuilderAndMenu+clsPageBuilder..ctor (System.String pagename) [0x00171] in <93c961f040e647f7b132f89548986d3d>:0 at HSPI_IFTTT.WebConfig..ctor (System.String pageName) [0x00016] in :0 at HSPI_IFTTT.IFTTTApp.Init () [0x00090] in :0
        Sep-24 8:10:56 AM	 	IFTTT	ERROR System.BadImageFormatException: Could not resolve field token 0x04000b09 File name: 'Scheduler' at A.c50372b7acae91f8c739d7107e5598a0b.cf066f1952189192c754f9a4315ad10ed (System.String cbbedb59e8a61b98a7d476a6040f87642, System.String c37ae3928805bd7b7c00e1adfe3f21976, System.String cbd92a9fb44227a9ec629386ce1f0f272, System.String cfaceb49d27a3a19f398479e1bb473778, System.String c81dfe5004cb7a743d3af637d597139b1) [0x000b3] in <93c961f040e647f7b132f89548986d3d>:0 at Scheduler.PageBuilderAndMenu+clsPageBuilder..ctor (System.String pagename) [0x00171] in <93c961f040e647f7b132f89548986d3d>:0 at HSPI_IFTTT.WebConfig..ctor (System.String pageName) [0x00016] in :0 at HSPI_IFTTT.IFTTTApp.Init () [0x00090] in :0
        Sep-24 8:10:56 AM	 	IFTTT	INFO IFTTT version 3.0.1.2
        Sep-24 8:10:56 AM	 	Info	Plugin IFTTT has connected. IP:127.0.0.1:45128
        Sep-24 8:10:56 AM	 	Plug-In	Interface IFTTT is running as a trial, 30 days remaining.

        Comment


          #5
          Try disabling all of the plugins,shut down HS3 and updating to HS3 Pro Version 367.
          - Pete

          Auto mator
          Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
          Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
          HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

          HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
          HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

          X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

          Comment


            #6
            I expect you mean 357? Downgraded to 357 now and it works, expected a distribution to be made available on the main download page to have been tested.. Thanks!

            Comment


              #7
              Well there are release and beta versions.

              The V.357 started off life as a release version coming from the V.318 release version to betas between V.318 to V.356.

              It does get a bit confusing.

              Read this entire thread to give you a historical on this stuff.

              Discussions related to HomeSeer Beta 3.0.0.332->356

              The validation or release of a release version mostly depends on the users here on the forum and communications / dialog reporting any issues with beta versions. Homeseer is a small company and doesn't employ thousands of individuals.


              There have been core changes in the base of the Homeseer 3 engine. One was integration of Homeseer touch to Homeseer core. Other changes relate to what DLL's are utilized by 3rd party plugin authors and where they sit in the Homeseer directory structure.

              Note this is for Homeseer 3 running in Windows and Linux (mono).

              Personally here it took much for to go from Ubuntu 14.04 to Ubuntu 16.04. I did not want to do it as I felt comfortable with Ubuntu 14.04.

              The changes though between Ubuntu 14.04 and 16.04 and 17.04 can be difficult if you are used to doing stuff in a certain manner.

              I have left my stuff here at 16.04 64 bit. Helped a user utilize Ubuntu 16.10 and it works great. Ubuntu 17.04 is still too new for me and why fix something that is not broken.

              BTW guessing here you are probably one of 2-3 users running Homeseer 3 in Ubuntu Linux 17.04/10 today and a majority of Homeseer users run Homeseer on one computer (whatever OS) versus a minority of users running Homeseer in a VM. There are advantages and disadvantages to both methodologies.
              Last edited by Pete; September 24, 2017, 01:46 PM.
              - Pete

              Auto mator
              Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
              Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
              HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

              HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
              HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

              X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

              Comment


                #8
                That is interesting information, as I am quite new to Linux this was not on my radar.. Trying out a 16.10 installation now to see if there is any difference!

                Comment


                  #9
                  Here configured a Homeseer user that wanted to utilize Ubuntu 16.10. I did not see much difference between 16.10 and 16.04.

                  Note this user did all of the Homeseer configuration stuff via the GUI as it is very unique to his stuff.

                  I did mostly the OS and other non Homeseer stuff on his computer. Personally I didn't agree much with all of the multitasking stuff until I saw it running on this box. It is using a base of Ubuntu 16.10 and using Oracle Virtual box for Wintel VMs (virtual boxes).

                  My current hardware is similar except the box only does Homeseer (iSeries / 16Gb of memory).

                  Personally the "proof is in the pudding" as typically I do not believe anything until I see it working...that is me though.

                  His Homeseer box is multitasking running:

                  1 - Linux software NAS using an LSi 8 port RAID card
                  2 - WeeWx weather software running on Apache 2
                  3 - Media player and video and audio stuff.
                  4 - iOS stuff running on an Oracle Virtual box.
                  5 - Homeseer 3
                  6 - CCTV NVR stuff
                  7 - connectivity alarm panel with central services monitoring.

                  Thinking there is more on his 16.10 64bit Intel iSeries box with 16 Gb of memory.

                  I have not seen any issues with it. He has kept his OS updated but does not frequently update Homeseer as it is working fine (V.297 / 318?).

                  ~# lsb_release -a
                  No LSB modules are available.
                  Distributor ID: Ubuntu
                  Description: Ubuntu 16.10
                  Release: 16.10
                  Codename: yakkety

                  Utilization with HTop.

                  [ATTACH]63510[/ATTACH]

                  Homeseer version and plugins show:

                  Current Date/Time: 9/24/2017 1:10:08 PM
                  HomeSeer Version: HS3 Pro Edition 3.0.0.297
                  Linux version: Linux Box 4.8.0-59-generic #64-Ubuntu SMP Thu Jun 29 19:38:34 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux System Uptime: 20 Days 18 Hours 34 Minutes 0 Seconds
                  IP Address: www.xxx.yyy.zzz
                  Number of Devices: 295
                  Number of Events: 16
                  Available Threads: 400
                  License: Registered
                  License: number
                  User Name and Access Level: username
                  WAN IP Address: www.xxx.yyy.zzz
                  Web Server Port: whatever
                  Location: (Latitude) xxx (Longitude) yyy

                  Enabled Plug-Ins
                  2.0.47.0: BLBackup
                  3.0.0.18: DirecTV
                  3.0.0.18: DirecTV
                  3.0.0.18: DirecTV
                  3.0.0.18: DirecTV
                  1.1.11.0: Honeywell WiFi Thermostat
                  1.1.3.1: JowiHue
                  2.1.6.0: OpenSprinkler
                  30.0.0.35: RFXCOM
                  3.0.1.144: Z-Wave

                  BTW relating to autostarting Homeseer as a program and as a service there are many many ways to do this. I would recommend though a manual start in a terminal window left open such that you can watch the console first for any issues.

                  Then after a few days build your autostart baby steps while concurrently testing it. The autostart stuff is the easiest piece to Homeseer. What you want to validate is that Homeseer runs with no issues first.
                  Last edited by Pete; September 24, 2017, 04:26 PM.
                  - Pete

                  Auto mator
                  Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb
                  Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro
                  HS4 Lite - Ubuntu 22.04 / Lenovo Tiny M900 / 32Gb Ram

                  HS4 Pro - V4.1.18.1 - Ubuntu 22.04 / Lenova Tiny M900 / 32Gb Ram
                  HSTouch on Intel tabletop tablets (Jogglers) - Asus AIO - Windows 11

                  X10, UPB, Zigbee, ZWave and Wifi MQTT automation-Tasmota-Espurna. OmniPro 2, Russound zoned audio, Alexa, Cheaper RFID, W800 and Home Assistant

                  Comment


                    #10
                    Thanks for the info! Looking good so far on 17.04 with .318 release of HomeSeer Will continue testing, but reliability is what I am after now...

                    Comment

                    Working...
                    X