thexperiments / pimatic-harmonyhub Goto Github PK

ButtonDevice works fine but if I config a PowerSwitch, I get always this error: 'onCommand is not defined'

Logitech disabled local access via XMPP in late 2018 to fix security vulnerabilities as they stated in the release. As the user
community screamed, Logitech decided to re-enable the feature and announced another firmware which has been released
in early 2019. It should be noted however, the newer firmware release have XMPP support disabled by default and can be enabled with Harmony App.
@theX I think it would be I good idea to add a short note to the README about how to enable XMPP support on the hub.

• https://community.logitech.com/s/question/0D55A00008OsX3CSAV/update-to-accessing-harmony-hubs-local-api-via-xmpp

• https://forum.pimatic.org/topic/4503/harmony-plugin-seems-to-stop-working-after-the-last-harmony-update

• https://www.theverge.com/circuitbreaker/2018/12/20/18150011/logitech-harmony-hub-remote-setup-security-update-broken-third-party-local-api

Sorry not an issue but a small request. It whould be great to know wich activity currently is running. Because with that information you dim the light if you start watching TV.

Hi,
have two issues and a request here with the plugin having 2 harmony hubs in the network:
a) 172.16.0.110
b) 172.16.0.111

1. plugin finds both hubs within auto-discovery, but slots all activities/groups etc. under the same IP adress (in some cases the first one, in some cases the second one).
   It seems that the '@hubip' Buffer isn't resetted before the second scan or the plugin gets confused during scan. Something is rotten here in the logic I guess.

2. Naming convention:

2a. you define the name of the hub as id: "activities-#{@hubIP.replace(".","-")}"
-which should lead to (as example abobe: "activities-172-16-0-111)
-In my case the naming comes out with "activities-172-16.0.111" so the last replacements in the IP doesn't work! This gives strange troubles within pimatic with dots in the device-IDs.

2b. in general this convention is not optimal from my PoV:
-IP adress may change

• most important: the generated name is not really 'self-speaking'
• you've to redefine/rename all devices if this happens (which leads to errors in defined rules etc.)

My proposal is to change the ID (and Name template in pimatic) to the name of the hub as defined on the harmony side (e.g. Harmony-HUB Mediaroom). Of course user should take care of unique names here.
As IP adress is a dedicated information within the config and later in the the service calls, IP-adress in the name is redundant and missleading

3. Request: Updates
   How to handle updates? If I initially define devices here within auto discovery and later adding activities on the hub, I've to manually add this activities within the existing pimatic-device (taking the harmony-activity IDs from a new auto-discovery. This is not reall 'handsome'.

Thanks for the plugin!

I have a Logitech Harmony Link Hub (Produktnummer: 815-000072 and when trying to add it I am getting the following message:

21:27:02.054 [pimatic-harmonyhub] Discovered [email protected]
errorhub XMPP authentication failure

I am wondering if my hub is supported and if yes if there is something I can do to debug the error?