Jump to content

Mr B

Members
  • Posts

    9
  • Joined

  • Last visited

Recent Profile Visitors

405 profile views

Mr B's Achievements

Newbie

Newbie (1/6)

1

Reputation

  1. Mr B

    USB Extender Problem

    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.
  2. 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.
  3. 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.
  4. It seems to have corrected itself today.
  5. My HolidaysGoogle Node server is reporting today and tomorrow as one day ahead of the correct days. Anyone else seeing this happening?
  6. 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.
  7. @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.
  8. 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/
  9. 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!
×
×
  • Create New...