Just migrated my C5 to C8 (have not decommissioned the c5 yet but power is disconnected), I also have a C7. I cannot get iFTTT to talk with the migrated C8. Deleted the iFTTT built in app from the c8 and reinstalled, deleted the Hubitat integration from iFTTT and tried reconnecting. Ifttt shows all three hubs, I select the c8 it thinks about it and then an error stating there was a problem (descriptive). However, I can select the c7 without issue but not the c8. Removed ifttt and reloaded, no dice. Oh, also power sequenced the c8. Ideas/help is welcome.
1 Like
Hub is probably disconnected from cloud or having a DNS issue.
I don't feel like typing this again:
Absolutely correct! I had the hub on static ip and evidently that screwed/confused the hub. My c7 is also static iP and it works - whatever.... But it's working now, although I have to rebuild all my applets on ifttt. Thanks for the help. Now all I have to do is figure out why my mesh with the c7 is duplicating devices. 
Did you do a soft reset of the c7 after upgrading? You should reset both radios and do a soft reset.
Is a soft reset different than restarting from the settings menu? I have restarted a number of times.
Yes. You do not want to run the c7 with all the same stuff including radios as your c8, they will interfere with eachother. You want to reset both z-wave and zigbee radios, then do a soft reset from yourhubip:8081 which overall will start your hub from new. Make sure that the zigbee channels on both hubs are different.
Not familiar with zigbee radio channels since I only have z-wave devices. Let me explain my duplicates. The 2 hubs are meshed together, I have linked devices from the c8 (main hub) to the c7. Now on the c7 I have 'deviceLamp' and 'deviceLamp on c8'. It acts like the device is both local and linked on the c7, when in reality, it should be just linked. Should I have not flagged hub mesh enabled on the c8 (main hub)?
Did you soft reset the c7? If not you are going to create duplicates and nothing will work right. Reset both radios, then do a soft reset then make sure your zigbee radio is on a different channel on the c7 than the c8 even if you don't have any zigbee devices. Then when the c7 comes back up enable hub mesh and point it at the c8.
If I reset the z-wave radios, then I will need to exclude include all of my z-wave devices, which is no simple task. Is this correct?
Back up, you migrated the C5 to the C8. So the C5 is the one you would want to reset.
If the C7 is still as-is from before the C8 migration then I would not reset anything on that.
Did you have these devices meshed from the C5 prior? I am not sure how the hub mesh migration works exactly but it sounds like maybe you have the old mesh device from the C5 and now the mesh from the C8 created another device entry?
Screenshots would help.
Prior to this, I had the c5 in mesh with the c7. I migrated the c5 to the c8, the c5 is now out of the picture (power off & off the network). After migration, I did a refresh to both the c8 & c7 to get the mesh active. The linked devices were now visible and active on the c7 as DEVICE on hubnameC8. However after necessary reboots, I now had the devices linked to the c8 duplicated as DEVICE and DEVICE on hubnameC8 with both being the same device. It acted as though the devices are now included onto the c7 as local devices when they are only local to the c8. And the interesting item is that both names actually work and take commands from the c7. What I finally did was delete the devices on the c7 that acted as though they were local, that is DEVICE. So now I only have the linked devices active on the c7 (DEVICES on hubnameC8)
I see it a bit more clearly now...Sorry about that. I'm wondering if the previously meshed devices were still cached from the c5 on the c7 so that when you remeshed everything it brought over those previously meshed devices to the c8 causing the duplicates. I also wonder if simply disabling hub mesh on the c5 rebooting it and then re-enabling it would have cleared that out for you..
Things that may you go hmmm 
I bet that if I would have disabled the mesh prior to the migration but after the cloud backup, it would have been fine. Hindsight, got to love it.
Thanks for your help, it is much appreciated and helpful!
1 Like
Not sure if it would have worked but couldn't hurt!
I'll keep it in mind when the c10 comes out 
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
