Announcement

Collapse
No announcement yet.

Total newbie trying to setup OMNI plugin

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

  • Total newbie trying to setup OMNI plugin

    I've installed the Omni plugin and entered the IP, port, and keys in the panel tab. All the units, flag, temps, etc tabs are empty. The log screen just says to click on 'load log', which, when done, just show an empty screen.

    Any help getting it running greatly appreciated.

  • #2
    Did you restart the plugin after you entered the IP & keys information?

    Comment


    • #3
      If by reset you mean disable and re-enable, then yes.

      Comment


      • #4
        Assuming that you have entered the IP/PORT/KEYS correctly then is there anything shown in the HomeSeer log when you start the plugin that may be of help.

        Also be sure to follow the steps here: https://forums.homeseer.com/forum/se...nection-issues

        Comment


        • #5
          The HomeSeer log is this (sorry, totally new to this... seems that the OMNI plugin did connect):

          Feb-25 10:15:00 AM Log Info The log database is currently 1.04MB in size.
          Feb-25 10:15:00 AM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-25 9:06:00 AM Energy DB Info All energy database compacting routines completed.
          Feb-25 9:06:00 AM Energy DB Info No Records. Vacuuming database to condense.
          Feb-25 9:06:00 AM Energy DB Info Energy database compaction initiated.
          Feb-25 7:15:00 AM Log Info The log database is currently 1.04MB in size.
          Feb-25 7:15:00 AM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-25 5:06:00 AM Energy DB Info All energy database compacting routines completed.
          Feb-25 5:06:00 AM Energy DB Info No Records. Vacuuming database to condense.
          Feb-25 5:06:00 AM Energy DB Info Energy database compaction initiated.
          Feb-25 4:15:00 AM Log Info The log database is currently 1.04MB in size.
          Feb-25 4:15:00 AM Log Maintenance 2 records, selected by date/time, were removed from the log database.
          Feb-25 1:15:00 AM Log Info The log database is currently 1.04MB in size.
          Feb-25 1:15:00 AM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-25 1:06:00 AM Energy DB Info All energy database compacting routines completed.
          Feb-25 1:06:00 AM Energy DB Info No Records. Vacuuming database to condense.
          Feb-25 1:06:00 AM Energy DB Info Energy database compaction initiated.
          Feb-25 1:00:58 AM OMNI --->Parent Device for OMNI added...
          Feb-25 1:00:57 AM Starting Plug-In Plugin OMNI started successfully in 2157 milliseconds
          Feb-25 1:00:55 AM Starting Plug-In Initializing plugin OMNI ...
          Feb-25 1:00:55 AM Info Plugin OMNI has connected. IP:127.0.0.1:42594
          Feb-25 1:00:54 AM Plug-In Finished initializing plug-in OMNI
          Feb-25 1:00:47 AM Error Displaying remotely connected interfaces: Object reference not set to an instance of an object
          Feb-25 1:00:46 AM Info Plugin OMNI with instance: has disconnected
          Feb-25 1:00:46 AM Plug-In Shutting down Plug-In: OMNI
          Feb-24 10:15:00 PM Log Info The log database is currently 1.04MB in size.
          Feb-24 10:15:00 PM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-24 9:06:00 PM Energy DB Info All energy database compacting routines completed.
          Feb-24 9:06:00 PM Energy DB Info No Records. Vacuuming database to condense.
          Feb-24 9:06:00 PM Energy DB Info Energy database compaction initiated.
          Feb-24 7:15:00 PM Log Info The log database is currently 1.04MB in size.
          Feb-24 7:15:00 PM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-24 5:06:00 PM Energy DB Info All energy database compacting routines completed.
          Feb-24 5:06:00 PM Energy DB Info No Records. Vacuuming database to condense.
          Feb-24 5:06:00 PM Energy DB Info Energy database compaction initiated.
          Feb-24 4:15:00 PM Log Info The log database is currently 1.04MB in size.
          Feb-24 4:15:00 PM Log Maintenance 2 records, selected by date/time, were removed from the log database.
          Feb-24 1:15:00 PM Log Info The log database is currently 1.04MB in size.
          Feb-24 1:15:00 PM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-24 1:06:00 PM Energy DB Info All energy database compacting routines completed.
          Feb-24 1:06:00 PM Energy DB Info No Records. Vacuuming database to condense.
          Feb-24 1:06:00 PM Energy DB Info Energy database compaction initiated.
          Feb-24 10:15:00 AM Log Info The log database is currently 1.04MB in size.
          Feb-24 10:15:00 AM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-24 9:06:00 AM Energy DB Info All energy database compacting routines completed.
          Feb-24 9:06:00 AM Energy DB Info No Records. Vacuuming database to condense.
          Feb-24 9:06:00 AM Energy DB Info Energy database compaction initiated.
          Feb-24 8:21:39 AM Info System connected to MyHS Service successfully with license ID 122844.
          Feb-24 8:21:39 AM Info System connected to MyHS Service, waiting for acknowledge...
          Feb-24 7:15:00 AM Log Info The log database is currently 1.04MB in size.
          Feb-24 7:15:00 AM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-24 5:50:36 AM Info System connected to MyHS Service successfully with license ID 122844.
          Feb-24 5:50:36 AM Info System connected to MyHS Service, waiting for acknowledge...
          Feb-24 5:50:24 AM Warning Have not heard from MyHS in over 3 minutes, disconnecting for re-connection.
          Feb-24 5:06:00 AM Energy DB Info All energy database compacting routines completed.
          Feb-24 5:06:00 AM Energy DB Info No Records. Vacuuming database to condense.
          Feb-24 5:06:00 AM Energy DB Info Energy database compaction initiated.
          Feb-24 4:15:00 AM Log Info The log database is currently 1.04MB in size.
          Feb-24 4:15:00 AM Log Maintenance 2 records, selected by date/time, were removed from the log database.
          Feb-24 1:15:00 AM Log Info The log database is currently 1.04MB in size.
          Feb-24 1:15:00 AM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-24 1:06:00 AM Energy DB Info All energy database compacting routines completed.
          Feb-24 1:06:00 AM Energy DB Info No Records. Vacuuming database to condense.
          Feb-24 1:06:00 AM Energy DB Info Energy database compaction initiated.
          Feb-23 10:15:00 PM Log Info The log database is currently 1.04MB in size.
          Feb-23 10:15:00 PM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-23 9:06:00 PM Energy DB Info All energy database compacting routines completed.
          Feb-23 9:06:00 PM Energy DB Info No Records. Vacuuming database to condense.
          Feb-23 9:06:00 PM Energy DB Info Energy database compaction initiated.
          Feb-23 7:15:00 PM Log Info The log database is currently 1.04MB in size.
          Feb-23 7:15:00 PM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-23 5:06:00 PM Energy DB Info All energy database compacting routines completed.
          Feb-23 5:06:00 PM Energy DB Info No Records. Vacuuming database to condense.
          Feb-23 5:06:00 PM Energy DB Info Energy database compaction initiated.
          Feb-23 4:15:00 PM Log Info The log database is currently 1.04MB in size.
          Feb-23 4:15:00 PM Log Maintenance 2 records, selected by date/time, were removed from the log database.
          Feb-23 1:15:00 PM Log Info The log database is currently 1.04MB in size.
          Feb-23 1:15:00 PM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-23 1:06:00 PM Energy DB Info All energy database compacting routines completed.
          Feb-23 1:06:00 PM Energy DB Info No Records. Vacuuming database to condense.
          Feb-23 1:06:00 PM Energy DB Info Energy database compaction initiated.
          Feb-23 10:15:00 AM Log Info The log database is currently 1.04MB in size.
          Feb-23 10:15:00 AM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-23 9:06:00 AM Energy DB Info All energy database compacting routines completed.
          Feb-23 9:06:00 AM Energy DB Info No Records. Vacuuming database to condense.
          Feb-23 9:06:00 AM Energy DB Info Energy database compaction initiated.
          Feb-23 7:15:00 AM Log Info The log database is currently 1.04MB in size.
          Feb-23 7:15:00 AM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-23 5:06:00 AM Energy DB Info All energy database compacting routines completed.
          Feb-23 5:06:00 AM Energy DB Info No Records. Vacuuming database to condense.
          Feb-23 5:06:00 AM Energy DB Info Energy database compaction initiated.
          Feb-23 4:15:00 AM Log Info The log database is currently 1.04MB in size.
          Feb-23 4:15:00 AM Log Maintenance 2 records, selected by date/time, were removed from the log database.
          Feb-23 1:15:00 AM Log Info The log database is currently 1.04MB in size.
          Feb-23 1:15:00 AM Log Maintenance 5 records, selected by date/time, were removed from the log database.
          Feb-23 1:06:00 AM Energy DB Info All energy database compacting routines completed.
          Feb-23 1:06:00 AM Energy DB Info No Records. Vacuuming database to condense.
          Feb-23 1:06:00 AM Energy DB Info Energy database compaction initiated.
          Feb-23 12:56:36 AM Info System connected to MyHS Service successfully with license ID 122844.
          Feb-23 12:56:36 AM Info System connected to MyHS Service, waiting for acknowledge...
          Feb-23 12:56:36 AM Info Starting the MyHS Service...
          Feb-23 12:56:34 AM Info Stopping the MyHS Service...
          Feb-23 12:56:34 AM Info Successfully registered license 673622
          Feb-23 12:56:24 AM OMNI No panels are configured. Configure your panel, then restart the plugin...
          Feb-23 12:56:23 AM Starting Plug-In Plugin OMNI started successfully in 2156 milliseconds
          Feb-23 12:56:21 AM Starting Plug-In Initializing plugin OMNI ...
          Feb-23 12:56:21 AM Info Plugin OMNI has connected. IP:127.0.0.1:40282
          Feb-23 12:56:20 AM Plug-In Finished initializing plug-in OMNI
          Feb-23 12:56:20 AM Plug-In Interface OMNI is running as a trial, 30 days remaining.
          Feb-23 12:56:10 AM Error Warning, Cannot load EXE file (possibly missing dependencies) HSPI_Chromecast.exe: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown.Warning, Error details with EXE HSPI_Chromecast.exe: Could not load file or assembly 'System.Runtime, Version=4.0.10.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.
          Feb-23 12:56:10 AM Updater Install/Update of package OMNI was successful.
          Feb-23 12:56:10 AM Updater Extraction Complete.
          Feb-23 12:56:10 AM Updater Extracting files from zip file: OMNI_Images.zip
          Feb-23 12:56:10 AM Updater Extraction Complete.
          Feb-23 12:56:10 AM Updater Extracting files from zip file: OMNI_Images.zip
          Feb-23 12:56:10 AM Updater Extraction Complete.
          Feb-23 12:56:10 AM Updater Extracting files from zip file: /usr/local/HomeSeer/Updates3/OMNI3.0.2.20/OMNI_Config.zip Destination: /usr/local/HomeSeer/Config/
          Feb-23 12:56:10 AM Updater Extraction Complete.
          Feb-23 12:56:09 AM Updater Extracting files from zip file: OMNI_DLLs.zip
          Feb-23 12:56:09 AM Updater Copying file: /usr/local/HomeSeer/HAI.Controller.dll
          Feb-23 12:56:09 AM Updater Copying file: /usr/local/HomeSeer/HSPI_OMNI.exe.config
          Feb-23 12:56:09 AM Updater Copying file: /usr/local/HomeSeer/HSPI_OMNI.exe
          Feb-23 12:56:09 AM Updater Installing package OMNI
          Feb-23 12:56:09 AM Updater Update hspi_omni.exe downloaded successfully
          Feb-23 12:56:08 AM Updater Downloading update: OMNI
          Feb-23 12:56:08 AM Updater Starting download of updates
          Feb-23 12:17:57 AM Error Displaying remotely connected interfaces: Object reference not set to an instance of an object
          Feb-23 12:17:56 AM Info Plugin Z-Wave with instance: has disconnected
          Feb-23 12:17:56 AM Plug-In Shutting down Plug-In: Z-Wave
          Feb-23 12:17:54 AM Z-Wave Warning New Interface: The serial port (/dev/ttyUSB0) was not found in the system. Will keep waiting for it...
          Feb-23 12:17:54 AM Z-Wave New Interface: The Z-Wave Command Execution Thread was Started or Restarted.
          Feb-23 12:17:54 AM Z-Wave 465 Simple AV Control Command Class Control Commands have been loaded successfully.
          Feb-23 12:17:54 AM Z-Wave New Interface: ----------------------------------------------------------------------
          Feb-23 12:17:54 AM Z-Wave Initializing Z-Wave interface New Interface (HomeSeer SmartStick +) on /dev/ttyUSB0
          Feb-23 12:17:54 AM Z-Wave New Interface: ----------------------------------------------------------------------
          Feb-23 12:17:54 AM Z-Wave New Interface: ============================================================ ==========
          Feb-23 12:17:54 AM Z-Wave 0 event triggers were loaded from HomeSeer.
          Feb-23 12:17:54 AM Starting Plug-In Plugin Z-Wave started successfully in 679 milliseconds
          Feb-23 12:17:54 AM Z-Wave 0 event actions were loaded from HomeSeer.
          Feb-23 12:17:54 AM Z-Wave Database: Opening (Mode=Read Only) up HomeSeer database /usr/local/HomeSeer/Data/Z-Wave/Z-Wave2.db
          Feb-23 12:17:53 AM Z-Wave InitIO called, plug-in version 3.0.1.242 is being initialized...
          Feb-23 12:17:53 AM Starting Plug-In Initializing plugin Z-Wave ...
          Feb-23 12:17:53 AM Info Plugin Z-Wave has connected. IP:127.0.0.1:40238
          Feb-23 12:17:53 AM Plug-In Finished initializing plug-in Z-Wave

          Comment


          • #6
            I am not qualified to give you very much help, but perhaps a little ...

            In your log, this got my attention:

            Feb-23 12:56:24 AM OMNI No panels are configured. Configure your panel, then restart the plugin...
            When my system initializes my OmniPro II, the HS3 log entries look something like this:

            2020-02-15 10:05:21 OMNI Synchronizing OMNI devices with HomeSeer...
            2020-02-15 10:01:31 Plug-In Finished initializing plug-in OMNI
            2020-02-15 10:01:31 Starting Plug-In OMNI loaded in 2806 milliseconds
            2020-02-15 10:01:30 Starting Plug-In Plugin OMNI started successfully in 2143 milliseconds
            2020-02-15 10:01:28 Starting Plug-In Initializing plugin OMNI ...
            2020-02-15 10:01:28 Info Plugin OMNI has connected. IP:127.0.0.1:49841
            The fact that you have connected means that the OMNI plugin found your security panel device. It may not have gotten past the panel's security wall. I would check again, as STCook suggested, to make sure everything is correctly entered in the OMNI->Config page Panel and Configuration tabs.

            Regarding the blank log page: me, too. I never get anything unless I select the detailed log option. I suggest that you do this, then disable and reenable the OMNI plugin. When you thereafter select the OMNI log display option, you might find something useful.

            When you are through, be sure to turn off the detailed logging option. It generates an enormous amount of data that will likely soon overwhelm system resources if left on.

            Sorry I couldn't offer you anything better. Once you have your system working, you'll love it. Good luck!

            Comment


            • #7
              It is connecting:
              Feb-25 11:46:46 PM Starting Plug-In Plugin OMNI started successfully in 2166 milliseconds
              Feb-25 11:46:44 PM Starting Plug-In Initializing plugin OMNI ...
              Feb-25 11:46:44 PM Info Plugin OMNI has connected. IP:127.0.0.1:44981
              Feb-25 11:46:43 PM Plug-In Finished initializing plug-in OMNI
              Feb-25 11:46:39 PM Error Displaying remotely connected interfaces: Object reference not set to an instance of an object
              Feb-25 11:46:35 PM Info Plugin OMNI with instance: has disconnected
              Feb-25 11:46:35 PM Plug-In Shutting down Plug-In: OMNI
              I just need to learn about setting up devices, zones, units, etc. Is this something I start in Homeseer or the OMNI plugin config?

              Also, what is that error?

              Lastly, can anyone point me in the direction of a tutorial for setting up Homeseer and the Omni plugin, like from the ground up with no assumptions about the user already having everything setup themselves in the OMNI panel? I had a company set everything up for us, but they are hard to deal with and I need to learn this all myself. I don't know what are devices, zones, areas, outputs, units, flags, etc. The guide that Homeseer sent me for setting up the OMNI plugin assumes I understand all of that and have them all set up and just need to interface everything.

              Comment


              • #8
                I just need to learn about setting up devices, zones, units, etc. Is this something I start in Homeseer or the OMNI plugin config?

                You can not configure the Omnipro panel with the Omni Plugin. You can only read and utilize the configuration already configured in to the panel.

                The Omni plugin reads the configuration on the panel and creates devices, zones, units et al.

                Have you utilized PCA (PC Access) for users or the dealer version?

                Personally easiest way to get familiar with the OmniPro 2 panel is to utilize PCA. For making changes to the panel it is best to get a copy of PCA for dealers.

                PC Access Dealer Software, Multi Lingual

                Here is a quickie couple of videos which provide a nice overview.



                - Pete

                Auto mator
                Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.8X
                Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.8X
                HS4 Pro - V4.0.9.0 - Ubuntu 18.04/W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono 6.8X
                HS4 Lite -

                X10, UPB, Zigbee, ZWave and Wifi MQTT automation. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

                Comment


                • #9
                  Originally posted by Pete View Post
                  I just need to learn about setting up devices, zones, units, etc. Is this something I start in Homeseer or the OMNI plugin config?

                  You can not configure the Omnipro panel with the Omni Plugin. You can only read and utilize the configuration already configured in to the panel.

                  The Omni plugin reads the configuration on the panel and creates devices, zones, units et al.

                  Have you utilized PCA (PC Access) for users or the dealer version?

                  Personally easiest way to get familiar with the OmniPro 2 panel is to utilize PCA. For making changes to the panel it is best to get a copy of PCA for dealers.

                  PC Access Dealer Software, Multi Lingual

                  Here is a quickie couple of videos which provide a nice overview.



                  Thanks Pete. Watching videos now.

                  Comment


                  • #10
                    Did the installer leave the OmniPanel configuration file / installer access code with you?
                    - Pete

                    Auto mator
                    Homeseer 3 Pro - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU 16Gb- Mono 6.8X
                    Homeseer Zee2 (Lite) - 3.0.0.548 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.8X
                    HS4 Pro - V4.0.9.0 - Ubuntu 18.04/W7e 64 bit Intel Kaby Lake CPU - 32Gb - Mono 6.8X
                    HS4 Lite -

                    X10, UPB, Zigbee, ZWave and Wifi MQTT automation. OmniPro 2, Russound zoned audio, Smartthings hub, Hubitat Hub, and Home Assistant

                    Comment

                    Working...
                    X