Jump to content

Test comes back failed


Recommended Posts

Posted

I get both ring door bells to install with 2 nodes for each doorbell Front Door and node Front door (motion) 

when I try to run the test it comes back with failed

 
024-07-20 16:37:58.724 Command udi_interface INFO controller:test: Ring API call is successful.
2024-07-20 16:37:58.724 Command udi_interface INFO ringInterface:getPostbackUrl: Store is Production: Using hostname my.isy.io for webhook url
2024-07-20 16:37:58.613 Command udi_interface INFO oauth:getAccessToken: Refresh tokens is still valid, no need to refresh
2024-07-20 16:37:58.724 Command udi_interface INFO controller:test: Ring API call is successful.
2024-07-20 16:37:58.724 Command udi_interface INFO ringInterface:getPostbackUrl: Store is Production: Using hostname my.isy.io for webhook url
2024-07-20 16:37:58.842 Command udi_interface ERROR ringInterface:testWebhook: MQTT connection not online.
On my.isy.io, please check Select Tool | PG3 | Remote connection. It has to be active.
If you don't see the option, your device does not support it. Make sure you are using an eisy at 5.6.0 or more recent, or a Polisy using PG3x.
2024-07-20 16:37:58.842 Command udi_interface ERROR controller:test: Test Ring API call failed: Error sending event to Portal webhook
2024-07-20 16:37:58.842 Command udi_interface ERROR ringInterface:testWebhook: MQTT connection not online.
On my.isy.io, please check Select Tool | PG3 | Remote connection. It has to be active.
If you don't see the option, your device does not support it. Make sure you are using an eisy at 5.6.0 or more recent, or a Polisy using PG3x.
2024-07-20 16:37:58.842 Command udi_interface ERROR controller:test: Test Ring API call failed: Error sending event to Portal webhook
2024-07-20 16:37:58.842 Command udi_interface.node DEBUG node:setDriver: controller:Ring Reporting set GV0 to 4 to Polyglot
2024-07-20 16:37:58.843 Command udi_interface.node DEBUG node:reportDriver: Updating value to 4
2024-07-20 16:37:58.853 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'GV0', 'value': '4', 'uom': 25, 'text': None}]}
2024-07-20 16:37:58.842 Command udi_interface.node DEBUG node:setDriver: controller:Ring Reporting set GV0 to 4 to Polyglot
2024-07-20 16:37:58.843 Command udi_interface.node DEBUG node:reportDriver: Updating value to 4
2024-07-20 16:37:58.853 Thread-1 (send_thread) udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': 'controller', 'driver': 'GV0', 'value': '4', 'uom': 25, 'text': None}]}
2024-07-20 16:37:58.884 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV0 to 4 UOM 25
2024-07-20 16:37:58.884 MQTT udi_interface.interface INFO interface:_message: Successfully set controller :: GV0 to 4 UOM 25
I have checked my portal and it say's that remote connection is true
 
UUID: 00:21:b9:02:65:86
Alias: eisy
Remote connection feature available: Yes
Remote connection configured: Yes
Remote connection active: Yes

 

Please if anyone can tell me what I am doing wrong

 

 
Posted

Thanks for getting back to me I did find the problem. I had an old polisy in my portal that I used to test and write my NS but since the I have unplugged it and put it away.  For some reason the Ring keep coming back with that UUID instead of the UUID for my eisy. I deleted the polisy from my portal and rebooted then reinstalled Ring and it works good.

  • Like 1
Guest
This topic is now closed to further replies.

×
×
  • Create New...