Announcement

Collapse
No announcement yet.

Duplicate Z-wave interface after migrating to Linux

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

  • Duplicate Z-wave interface after migrating to Linux

    Hi,

    I get a duplicate interface after restoring Homeseer config in Linux from a Windows installation. Having spent some time now trying backup/restore in Homeseer (Setup - Backup/Restore) and manually copying Data / Config but I get the same results.

    Z-wave does not work. See attached screenshot.


    I have made a backup of the Z-wave interface as well in Windows. But I dare not reset the UZB1 as I can still fire up the Windows installation if this does not work.

    Any suggestions?

    Log:
    Code:
    root@e032b50f9892:/HomeSeer# ./go
    HomeSeer Linux starting...
    01:04:24:9266:[Database]->Opening (Mode=Read Only) up HomeSeer LOG database /HomeSeer/Logs/HomeSeerLog.hsd
    01:04:24:9797:[Startup]->Loading Settings
    01:04:25:0096:[Startup]->Settings Loaded.
    01:04:26:0341:[Startup]->
    01:04:26:0344:[Startup]->********************************************************************************
    01:04:26:0350:[Startup]->            HomeSeer version 3.0.0.500 Edition: HS3 Pro Starting Now
    01:04:26:0352:[Startup]->********************************************************************************
    01:04:26:0354:[Startup]->
    01:04:26:0416:[Startup]->Creating Class Objects...
    01:04:26:0428:[Startup]->COM port classes started.
    01:04:26:0453:[Startup]->Application interface class started.
    01:04:26:0476:[Startup]->Web server class started.
    01:04:26:0482:[Startup]->E-Mail SEND class started.
    01:04:26:0486:[Startup]->E-Mail RECEIVE class started.
    01:04:26:0501:[Startup]->Plug-In Interface class started.
    01:04:26:0510:[Startup]->Local voice recognition class started.
    01:04:26:0524:[Startup]->Database SAVE process started.
    01:04:26:0527:[Startup]->Loading configuration file ...
    01:04:26:0603:[Database]->Opening (Mode=Read Only) up HomeSeer database /HomeSeer/Data/HomeSeerData.hsd
    01:04:26:5663:[Database]->Loading Devices...
    01:04:26:5753:[Load Config]->344 total devices loaded.
    01:04:26:5781:[Load Config]->Loading Event Groups...
    01:04:26:5883:[Load Config]->Loading Events...
    01:04:26:6278:[Load Config]->26 total events loaded.
    01:04:26:6281:[Load Config]->Loading COUNTERS...
    01:04:26:6313:[Load Config]->Loading TIMERS...
    01:04:26:6413:[Startup]->HomeSeer version is: 3.0.0.500
    01:04:26:6417:[Startup]->Creating Speaker Client Interface Object...
    01:04:26:6435:[Startup]->This version of HomeSeer is registered as a HS3PRO version.
    01:04:26:6537:[Web Server]->Local IP address is: 172.17.0.2
    01:04:26:6567:[Web Server]->Web Server started on port 80
    01:04:26:6869:[Info]->Remote plug-in API interface started on port 10400
    01:04:26:6871:[Startup]->Checking for available plug-ins
    01:04:27:0428:[Plug-In]->Found plug-in: Z-Wave, version: 3.0.1.252
    01:04:27:0436:[Startup]->Initializing Plug-Ins
    Connecting to server at 127.0.0.1...
    01:04:27:7748:[Info]->Plugin Z-Wave has connected. IP:127.0.0.1:46480
    Connected, waiting to be initialized...
    01:04:27:8466:[Starting Plug-In]->Initializing plugin Z-Wave ...
    01:04:27:8524:[Z-Wave]->InitIO called, plug-in version 3.0.1.252 is being initialized...
    Z-Wave Plugin: OS Type is Linux
    01:04:27:9923:[Z-Wave]->Database: Opening (Mode=Read Only) up HomeSeer database /HomeSeer/Data/Z-Wave/Z-Wave2.db
    01:04:28:3509:[Z-Wave]->Loading Z-Wave Data Objects...
    01:04:28:3535:[Z-Wave]->1 Networks were restored from the data in the database... Building data connections.
    01:04:28:3544:[Z-Wave]->Network EC93C615 has 178 device data elements.
    01:04:28:3690:[Z-Wave]->178 total Z-Wave Data Objects loaded.
    01:04:28:6036:[Starting Plug-In]->Plugin Z-Wave started successfully in 756 milliseconds
    01:04:28:6074:[Z-Wave]->0 event actions were loaded from HomeSeer.
    01:04:28:6077:[Z-Wave]->0 event triggers were loaded from HomeSeer.
    01:04:28:6195:[Z-Wave]->465 Simple AV Control Command Class Control Commands have been loaded successfully.
    01:04:28:6248:[Z-Wave]->UZB1: ======================================================================
    01:04:28:6256:[Z-Wave]->UZB1: ----------------------------------------------------------------------
    01:04:28:6269:[Z-Wave]->  Initializing Z-Wave interface UZB1 (Z-Wave.me UZB) on /dev/ttyUSB0
    01:04:28:6276:[Z-Wave]->UZB1: ----------------------------------------------------------------------
    01:04:28:6305:[Z-Wave]->UZB1: The Z-Wave Command Execution Thread was Started or Restarted.
    01:04:28:6587:[Z-Wave]->UZB1: The Z-Wave API Execution Thread was Started or Restarted.
    01:04:28:6593:[Starting Plug-In]->Z-Wave loaded in 1602 milliseconds
    01:04:28:6596:[Plug-In]->Finished initializing plug-in Z-Wave
    01:04:28:6646:[HSTouch Server]->Server started on port 10200
    01:04:28:6651:[Z-Wave]->UZB1: Getting node information from controller...
    01:04:28:6683:[Startup]->HStouch server started, waiting for clients to connect.
    01:04:28:6729:[Startup]->Start automation engine...
    01:04:28:6745:[Startup]->Initializing Speaker Client Interface
    01:04:28:6779:[Speech]->Listening for remote speaker connections on port 10401
    01:04:28:6830:[Database]->Opening (Mode=Read/Write) up HomeSeer Energy database /HomeSeer/Data/Energy/Energy.hsd
    01:04:28:9892:[Startup]->Updater services starting...
    01:04:28:9903:[Startup]->Starting Find service...
    01:04:28:9928:[Startup]->Running the startup script Startup.vb
    01:04:30:4808:[Startup]->Starting Event Scheduler...
    01:04:30:4819:[Startup]->HSSentry is disabled in Setup, sentry will not be started.
    01:04:30:4828:[Startup]->Start up complete.
    Type 'shutdown' to shutdown HomeSeer
    
    > 01:04:30:4921:[Startup]->(Startup.vb script) Scripting is OK and is now running Startup.vb
    01:04:30:4934:[Startup]->(Startup.vb script) No speaker clients detected, waiting up to 30 seconds for any to connect...
    01:04:30:6201:[Info]->System connected to MyHS Service, waiting for acknowledge...
    01:04:30:7525:[Info]->System connected to MyHS Service successfully with license ID 112990.
    01:04:40:6763:[Z-Wave]->Note: Only one system may connect to an Ethernet interface at one time. If 2 systems are connecting to your Z-Wave interface, HomeSeer will not connect.
    01:04:40:7067:[Z-Wave]->UZB1: Getting node information from controller...
    01:04:42:1531:[Z-Wave]->*******************************************************************************
    01:04:42:1539:[Z-Wave]->   STARTUP COMPLETE: All configured interfaces were successfully initialized.
    01:04:42:1547:[Z-Wave]->*******************************************************************************
    01:04:42:7081:[Z-Wave]->Note: Only one system may connect to an Ethernet interface at one time. If 2 systems are connecting to your Z-Wave interface, HomeSeer will not connect.
    01:04:42:7457:[Z-Wave]->UZB1: Getting node information from controller...
    01:04:54:7489:[Z-Wave]->Note: Only one system may connect to an Ethernet interface at one time. If 2 systems are connecting to your Z-Wave interface, HomeSeer will not connect.
    01:04:54:7747:[Z-Wave]->UZB1: Getting node information from controller...
    01:05:01:5269:[TTS]->Speak ():Welcome to Home-Seer
    /HomeSeer/./speak.sh: 3: /HomeSeer/./speak.sh: pico2wave: not found
    /HomeSeer/./speak.sh: 4: /HomeSeer/./speak.sh: aplay: not found
    01:05:02:7123:[Z-Wave]->Note: Only one system may connect to an Ethernet interface at one time. If 2 systems are connecting to your Z-Wave interface, HomeSeer will not connect.
    01:05:02:7496:[Z-Wave]->UZB1: Getting node information from controller...
    01:05:14:7529:[Z-Wave]->Note: Only one system may connect to an Ethernet interface at one time. If 2 systems are connecting to your Z-Wave interface, HomeSeer will not connect.
    01:05:14:7917:[Z-Wave]->UZB1: Getting node information from controller...
    01:05:26:7941:[Z-Wave]->Note: Only one system may connect to an Ethernet interface at one time. If 2 systems are connecting to your Z-Wave interface, HomeSeer will not connect.
    01:05:26:8336:[Z-Wave]->UZB1: Getting node information from controller...
    01:05:38:8368:[Z-Wave]->Note: Only one system may connect to an Ethernet interface at one time. If 2 systems are connecting to your Z-Wave interface, HomeSeer will not connect.
    01:05:38:8768:[Z-Wave]->UZB1: Getting node information from controller...
    01:06:00:1348:[Energy DB Info]->Energy database compaction initiated.
    01:06:00:1367:[Energy DB Info]->No Records. Vacuuming database to condense.
    01:06:00:1847:[Energy DB Info]->All energy database compacting routines completed.
    Error: UZB1: The UZB1 interface did not respond to the request for the controller capabilities - it may be disconnected or malfunctioning (3).
    01:06:33:7253:[Z-Wave Error]->UZB1: The UZB1 interface did not respond to the request for the controller capabilities - it may be disconnected or malfunctioning (3).
    01:06:33:7638:[Z-Wave]->UZB1: Getting node information from controller...
    01:06:45:7679:[Z-Wave]->Note: Only one system may connect to an Ethernet interface at one time. If 2 systems are connecting to your Z-Wave interface, HomeSeer will not connect.
    01:06:45:8067:[Z-Wave]->UZB1: Getting node information from controller...
    01:06:47:8081:[Z-Wave]->Note: Only one system may connect to an Ethernet interface at one time. If 2 systems are connecting to your Z-Wave interface, HomeSeer will not connect.
    01:06:47:8406:[Z-Wave]->UZB1: Getting node information from controller...
    01:06:59:8433:[Z-Wave]->Note: Only one system may connect to an Ethernet interface at one time. If 2 systems are connecting to your Z-Wave interface, HomeSeer will not connect.
    01:06:59:8648:[Z-Wave]->UZB1: Getting node information from controller...
    ...

  • #2
    UZB will appear as /dev/ttyACM0, not /dev/ttyUSB0. Do you have that available as a selection?

    Comment


    • #3
      Originally posted by zwolfpack View Post
      UZB will appear as /dev/ttyACM0, not /dev/ttyUSB0. Do you have that available as a selection?
      You are right. Copy-pasting someone else docker run command got me fooled.

      Now I will have to see if I can get those z-wave devices to come alive.

      Comment

      Working...
      X