#71 Cannot connect to Marmony 525

[jehojakim]

Hi, I decided to reuse my Harmony 525, new devices having entered the home. Some years ago I successfully used congruity/concordance for this remote, so I thought I'd give it a try again.

I downloaded and installed the latest and greatest versions of congruity (20) and concordance (1.4), with the necessary dependancies, including python-six.

lsusb recognizes the attached device:

Bus 001 Device 003: ID 046d:c111 Logitech, Inc. Harmony 525 Remote

I created a u-dev rule for 046d c111 conform the Readme of congruity.

Using Firefox, I went to https://members.harmonyremote.com/EasyZapper/New/ProcCommunication/CommunicationFrames.asp?Start=True and downloaded the latest Connectivity.EZHex. Firefox offered to open it with congruity, so I did.

Congruity starts OK, but when the progress bar has almost reached the end, it reports "A problem occured". Details:

Error connecting or finding the remote
NOTE: if you recently plugged in your remote and you have a newer remote, you
may need to wait a few additional seconds for your remote to be fully connected.
    (libconcord function init_concord error 11)

Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/congruity/congruity.py", line 553, in _WorkerFunction
    False
  File "/usr/local/lib/python2.7/site-packages/congruity/congruity.py", line 168, in worker_body_connect
    libconcord.init_concord()
  File "/usr/lib64/python2.7/site-packages/libconcord.py", line 124, in __call__
    raise LibConcordException(self.func_name, result)
LibConcordException: libconcord function 'init_concord' failed with error code 11 ('Error connecting or finding the remote\nNOTE: if you recently plugged in your remote and you have a newer remote, you\nmay need to wait a few additional seconds for your remote to be fully connected.')

But, as said, the remote is seen by lsusb, so that can't be the issue I suppose.
Any thoughts about what the problem might be?

cheers, Jogchum

[jehojakim]

To be sure, I entered concordance -i, which sees the remote too:

Requesting identity:  100%             done
  Model: Logitech Harmony 525 (Mocha Decaf)
  Firmware Version: 3.0
  Hardware Version: 3.0.0
  Config Flash Used: 25% (100 of 384 KiB)

Success!

[Scott Talbert]

You didn't perhaps run 'concorcordance -i' as root, did you?

You could try running the connectivity test with the concordance binary and see what happens. For example 'concordance -v Connectivity.EZHex'

[jehojakim]

You didn't perhaps run 'concorcordance -i' as root, did you?

Well, I didn't start concordance, but congruity, and started it as non-root.

You could try running the connectivity test with the concordance binary and see what happens. For example 'concordance -v Connectivity.EZHex'

If I do that non-root, I get

concordance -v Connectivity.EZHex
Concordance 1.4
Copyright 2007 Kevin Timmerman and Phil Dibowitz
This software is distributed under the GPLv3.

ERROR: Couldn't initializing libconcord: Error connecting or finding the remote
NOTE: if you recently plugged in your remote and you have a newer remote, you
may need to wait a few additional seconds for your remote to be fully connected.

If I do it as root, it's successfull:

concordance -v Connectivity.EZHex
Concordance 1.4
Copyright 2007 Kevin Timmerman and Phil Dibowitz
This software is distributed under the GPLv3.

Requesting identity:  100%             done
Contacting website:   100%             done
Success!

But running congruity as root gives also error messages, and no connection.

Thanks so far!

[Scott Talbert]

Sounds like a permissions issue and that your udev rule is not working.

[Scott Talbert]

I was talking about in your first reply where you said you ran 'concordance -i'. :P

Can you also try running 'concordance -iv' several times repeatedly and see if it works sometimes and sometimes not?