Mr B

Thanks for the info @Geddy. My ZMatter dongle would not stay connected on my 3 ft USB extension cable reliably until I overrode the port. It has stayed connected for nearly 2 days now. Hopefully it continues to work now. I had used that exact setup with the eisy at our previous house (sold with the house) with the same type of cable (I had bought a 2 pack) and never had a problem with Z-Wave or Zigbee staying connected.

@mapeter With a lack of any replies to this topic, I finally found some time to do some digging and found at least one post where someone mentioned reseting the port for the ZMatter dongle. Here's what I've done so far: - I followed the instructions in the eisy Wiki under "Can't connect to ZMatter Z-Wave board / dongle" and overrode port detection for the ZMatter dongle to cuaU1, rebooted, and made sure that both Z-Wave and Zigbee were connected. - I shut down my eisy then moved the dongle off of my eisy to an 3 ft USB 3.0 extension cable that was connected to the same USB port that the dongle was in then powered my eisy back up. So far, after over 24 hours, the eisy hasn't lost communication with the either the Z-Wave or Zigbee side of the ZMatter dongle (fingers still crossed). I went the route of the USB extension cable instead of the USB extender because I noticed that when trying to resolve the problem with the extender, rebooting the eisy still didn't reconnect the the ZMatter dongle completely (Z-Wave reconnected but Zigbee did not) unless I power cycled the USB extender when I rebooted the eisy. One of my concerns was that since we are usually away from home for weeks at a time during the summer, being able to reboot my eisy remotely if something like this happened and have Z-Wave and Zigbee reconnect was very important. The USB extension cable moves the dongle far enough away for me and removes the weight of the dongle on the USB port in the eisy which was my primary concern. Not sure if this will be a permanent fix but I'll keep you updated. Update: 6 days with no problems so I'm going to call this fixed.

Having a problem keeping the ZMatter dongle connected when using a USB extender. I purchased this one from Amazon (https://www.amazon.com/dp/B0C5R4DVRF?ref=ppx_yo2ov_dt_b_fed_asin_title) as I had seen that someone else had noted that they were using it and had posted a link in the forums. My problem is that the ZMatter dongle won't stay connected for more than a few hours before either the ZWave or the Zigbee side or both stop communicating. Seems I have to have it plugged directly into the eisy itself for it to stay connected. Anyone have any suggestions? (I had also tried a short USB extension cable in the past with similar results). Thanks in advance for any advice.

I had the same issue with both Alexa and Google Home. Rebooting seems to have fixed it unless it was coincidental with a fix on UDs side. Check that: 45 minutes later neither Alexa nor Google Home is working again. Same issue.

Yesterday morning ours started giving us a "I don't know how to do that" response when we asked an Alexa to turn a light on or off. That problem cleared up a couple hours later except for one Alexa that won't control our Laundry room light. It just says "Sorry, something went wrong". It's weird because the other 4 Alexa devices can control that light. I'm blaming it on Amazon.

It seems to have corrected itself today.

My HolidaysGoogle Node server is reporting today and tomorrow as one day ahead of the correct days. Anyone else seeing this happening?

I'm having the same problem. I'm away from home travelling but can log into another computer at home and run the admin concole. Everything's working, just not connected to the portal. I'm still on 5.8.3 as I didn't want to attempt the upgrade remotely. Don't revoke the portal service because you'll lose the license. I did that once when trouble shooting and had to repurchase the portal license.

@4481hoods I kept getting that error also until I added a custom configuration parameter like in the release notes: Key: gdodevice Value: <ip address of ratgdo>;<Name of ratgdo modified as per the release notes> I have a DHCP reservation for the ratgdo and pulled the name from the ratgdo config page modified as per the release notes (periods and spaces). That modified name was showing up in the logs. Took me several tries to get it right but it's working great now. Restart the plug-in after you add the custom configuration parameter.

Thanks firstone. I was able to get it working. For anyone who needs more detailed instructions, steps 1 through 4B in this instruction sheet work for exposing the API and creating the credentials: https://simplyscheduleappointments.com/guides/google-api-credentials/

Firstone, could you post instructions for creating the API credentials, setting that up in HolidaysGoogle and adding the URL above to Authorized URLs? I created a project in Google, enabled calendar API access, created credentials and added them to the configuration but still get the authentication error. Thanks!