Harmony Hub trigger

This is on C7 running 2.4.4.146.

This was working fine I think it may have broke when I got new receiver and changed harmony activities and devices.
I want the Table lamps in living room to come on at 100% when the TV goes on. It is not working. Some screenshots.



Just to make sure it is clear... You completely replaced your old Logitech Harmony Hub with a new/different Logitech Harmony Hub?

If yes, did you keep the same IP address for the new Harmony Hub? Or did you switch to a different IP address? In either case, did you make sure to reserve that IP address in your Router to make sure the IP address of the new Harmony Hub does not change?

On the Hubitat hub side, please explain what steps you did to swap out the old Harmony Hub with a new Harmony hub. It is very difficult to provide any assistance without more information.

In general, my approach would have been:

  1. Get the new Harmony up and running using the Logitech Harmony mobile phone app. Configure all of the Activities as desired.
  2. Make sure to reserve the IP address for the new Harmony hub in the router's DHCP settings.
  3. Add a new Hubitat Virtual Device, using the Logitech Harmony Hub Parent driver. Configure the IP address of the new Harmony hub in the driver's Preferences and click SAVE. This will create all of the new Actitivity child devices.
  4. Verify the Hubitat can control the Activities and that the status of the Activities match those of the Harmony Remote control. Make sure changing the Activity on the remote properly updates the Hubitat hub's corresponding Activity.
  5. Modify any existing rules/automations to use the new Activity child devices
  6. Remove the original Harmony Hub Parent device, which will cause it to remove all of its child devices as well.

Also, just an FYI - The Harmony Hub Parent device on the HE hub includes the "Switch" attribute. This single attribute can be used in any automation/rule to know if any of the Activities are on OR if they are all off. This might help simplify your rules instead of trying to include every acitivity.

Also, the PowerOff Activity is one that I added to originally try to help with this as well. However, its logic is reverse of the Parent Device's "switch" attribute. If all other Activities are OFF, the PowerOff activity will be ON. Your rule above includes the PowerOff Activity incorrectly, meaning that if everything turns off, your rule will run and try to turn on the lights.

My take is that he got a new AV receiver and had to remove the old AVR, add the new one then add that device into the existing activities.

It looks as though the Harmony hub has simply dropped off the network. I had similar with mine a few months back but can't for the life of me remember what the issue was that caused it now...

2 Likes

Ah, that’s the part that didn’t click when I first read it. Thanks!

Yeah - the failed initialise and ping are coming from device 330 and the Harmony device page is showing that it's device 330. Mine was a pain to get reconnected but I can't remember why

1 Like

Once the Harmony is connected to WiFi, and the LED is green on it, you should be able to just click INITIALIZE on the Harmony Hub Parent device and it should reconnect.

That was no issue in my case; once it was reconnected to WiFi that one click sorted it. The problem for me was something between the Harmony hub and my Unifi network. It disconnected from the WiFi (has reserved DHCP IP), but no amount of rebooting would reconnect it (visible on network but couldn't ping)

1 Like

no, same harmony hub. Only change I am aware of that might have broke it is new stereo receiver. I removed old Onkyo and added new Marantz. Same ip address, it has not changed.
I tried initialize harmonyHub330 and this is what I am seeing:

Blockquote
dev:3302026-03-18 03:38:06.699 PM

info

websocket is open

dev:3302026-03-18 03:38:06.483 PM

warn

WebSocket connection closing.

dev:3302026-03-18 03:38:06.328 PM

info

initialize() called

dev:3302026-03-17 11:14:04.708 AM

info

websocket is open

dev:3302026-03-17 11:14:04.330 AM

info

initialize() called

dev:3302026-03-17 11:13:56.353 AM

debug

Failed to connect to /192.168.1.59:8088

dev:3302026-03-17 11:13:56.301 AM

warn

failure message from web socket failure: Failed to connect to /192.168.1.59:8088

dev:3302026-03-17 11:13:56.259 AM

info

initialize() called

dev:3302026-03-17 11:13:52.269 AM

debug

Failed to connect to /192.168.1.59:8088

dev:3302026-03-17 11:13:52.232 AM

warn

failure message from web socket failure: Failed to connect to /192.168.1.59:8088

dev:3302026-03-17 11:13:51.891 AM

info

initialize() called

dev:3302026-03-17 11:13:49.947 AM

debug

sent ping but didn't receive pong within 30000ms (after 3608 successful ping/pongs)

dev:3302026-03-17 11:13:49.859 AM

warn

failure message from web socket failure: sent ping but didn't receive pong within 30000ms (after 3608 successful ping/pongs)

dev:3302026-03-16 05:08:42.101 AM

info

websocket is open

dev:3302026-03-16 05:08:41.952 AM

info

initialize() called

dev:3302026-03-16 05:08:25.968 AM

debug

Failed to connect to /192.168.1.59:8088

dev:3302026-03-16 05:08:25.920 AM

warn

failure message from web socket failure: Failed to connect to /192.168.1.59:8088

dev:3302026-03-16 05:08:25.881 AM

info

initialize() called

dev:3302026-03-16 05:08:17.901 AM

debug

Failed to connect to /192.168.1.59:8088

dev:3302026-03-16 05:08:17.852 AM

warn

failure message from web socket failure: Failed to connect to /192.168.1.59:8088

dev:3302026-03-16 05:08:17.742 AM

info

initialize() called

dev:3302026-03-16 05:08:13.760 AM

debug

No route to host (Host unreachable)

dev:3302026-03-16 05:08:13.709 AM

warn

failure message from web socket failure: No route to host (Host unreachable)

dev:3302026-03-16 05:08:12.799 AM

info

initialize() called

dev:3302026-03-16 05:08:10.841 AM

debug

sent ping but didn't receive pong within 30000ms (after 3042 successful ping/pongs)

dev:3302026-03-16 05:08:10.765 AM

warn

failure message from web socket failure: sent ping but didn't receive pong within 30000ms (after 3042 successful ping/pongs)

If you open up the device details page for the Harmony Hub Parent device, and then change Activities, do you see the corresponding changes in the web browser? Let’s ignore the automations/rules for now, until we know whether or not the HE hub is properly communicating with, and staying connected to, the Logitech Harmony Hub.

If the web socket connection keeps going down and then reconnecting, it sounds like a network issues. Either the Harmony Hub is not staying connected to your home’s WiFi system, or the Hubitat Hub is not staying connected, or some piece of network hardware is having an issue.

You could start a series of continuous PING commands on a PC, pinging the Harmony Hub in one window and the Hubitat hub in another window, to see which one may be having issues staying connected.

This type of issue is really hard to troubleshoot from afar.

1 Like

Along similar lines, has there been any other network changes during this time?

1 Like

no network changes. It is connected to deco wifi mesh sitting on top of the cabinet harmony hub is on. Deco app shows it connected to that unit. Ping is solid. Current states on device details mirror what harmony activity is current. I rebooted harmony hub before this and it came back with same ip number.

jack-mcgee@jack-mcgee-GA-870A-UD3:~/My Documents$ ping -D 192.168.1.59
PING 192.168.1.59 (192.168.1.59) 56(84) bytes of data.
[1773916634.153207] 64 bytes from 192.168.1.59: icmp_seq=1 ttl=64 time=1.27 ms
[1773916635.157353] 64 bytes from 192.168.1.59: icmp_seq=2 ttl=64 time=3.90 ms
[1773916636.155828] 64 bytes from 192.168.1.59: icmp_seq=3 ttl=64 time=1.29 ms
[1773916637.158096] 64 bytes from 192.168.1.59: icmp_seq=4 ttl=64 time=2.72 ms
[1773916638.158718] 64 bytes from 192.168.1.59: icmp_seq=5 ttl=64 time=1.05 ms
[1773916639.159626] 64 bytes from 192.168.1.59: icmp_seq=6 ttl=64 time=1.30 ms
[1773916640.163803] 64 bytes from 192.168.1.59: icmp_seq=7 ttl=64 time=3.93 ms
[1773916641.162366] 64 bytes from 192.168.1.59: icmp_seq=8 ttl=64 time=2.02 ms
[1773916642.162788] 64 bytes from 192.168.1.59: icmp_seq=9 ttl=64 time=1.44 ms
[1773916643.164470] 64 bytes from 192.168.1.59: icmp_seq=10 ttl=64 time=2.35 ms
[1773916644.169627] 64 bytes from 192.168.1.59: icmp_seq=11 ttl=64 time=1.50 ms
[1773916645.170311] 64 bytes from 192.168.1.59: icmp_seq=12 ttl=64 time=1.53 ms
[1773916646.179336] 64 bytes from 192.168.1.59: icmp_seq=13 ttl=64 time=9.71 ms
[1773916647.174985] 64 bytes from 192.168.1.59: icmp_seq=14 ttl=64 time=2.76 ms

jack-mcgee@jack-mcgee-GA-870A-UD3:~/My Documents$ ping -D 192.168.1.106
PING 192.168.1.106 (192.168.1.106) 56(84) bytes of data.
[1773916673.773440] 64 bytes from 192.168.1.106: icmp_seq=1 ttl=64 time=0.879 ms
[1773916674.774133] 64 bytes from 192.168.1.106: icmp_seq=2 ttl=64 time=0.788 ms
[1773916675.805248] 64 bytes from 192.168.1.106: icmp_seq=3 ttl=64 time=0.780 ms
[1773916676.829015] 64 bytes from 192.168.1.106: icmp_seq=4 ttl=64 time=0.738 ms
[1773916677.854266] 64 bytes from 192.168.1.106: icmp_seq=5 ttl=64 time=0.788 ms
[1773916678.855039] 64 bytes from 192.168.1.106: icmp_seq=6 ttl=64 time=0.688 ms
[1773916679.901112] 64 bytes from 192.168.1.106: icmp_seq=7 ttl=64 time=0.765 ms
[1773916680.925223] 64 bytes from 192.168.1.106: icmp_seq=8 ttl=64 time=0.775 ms
[

Great. Sounds like the Harmony Hub integration is working correctly.

If you’re still having an issue with your Rule Machine rule, I’d recommend deleting it and creating a new one just to make sure nothing else is still lingering within that old rule. Since your rule is so simple, it should not take too long to recreate it.

Once you have a fresh new rule, please enable the logging in the rule. If things misbehave, please share a screenshot of the logs showing the output from the new rule.

1 Like

Don't know why it started working again, maybe the initialize command. but all good now. Did not have to remake rule.

2 Likes

@ogiewon - So I just had the issue again yesterday/today. My rule to turn off the TV during my Goodnight routine failed. The logs showed similar to @jack4 (failed to connect, no route to host etc):

  • Harmony Hub LED green
  • Harmony iOS app controlling TV fine, but was connecting to the hub via cloud
  • Harmony Hub connected to WiFi confirmed in Unifi Network
  • However - unable to ping from macOS terminal. Ping worked fine from the Unifi Network client settings panel.

I tried dropping and reconnecting the Harmony hub in Unifi Network client panel but it still wouldn't ping from macOS.

The Unifi UDR had to be rebooted and at that point ping from the network was restored and the Harmony hub became controllable again from Hubitat. The Harmony is connected to my IoT WiFi SSID but there's no VLANS and nothing set up to stop communication between SSIDs or LAN. So in my case it looks to be a Unifi network issue.

1 Like

I have a full UniFi network stack here as well. I have never experienced this issue, however. :man_shrugging:t2:

Thanks for the info. Hopefully it helps others.

did you assign your harmony hub a fixed address in your dhcp?

It’s fixed IP in Unifi (reserved DHCP). It’s not a common occurrence; this is the second time it’s happened in maybe 6 months. As it remains connected and showing the correct IP address in both Unifi Network and my IP Scanner app it appears that communication between the Harmony on my IoT WiFi SSID, gets blocked to devices on the wired LAN (my C8) and my other WiFi SSID (my MacBook).