jkosharek

Looks like the ratgdo v2.5 is on backorder. So the ratgdo v2.5 would connect to a MyQ opener that doesn't work with dry contacts (Chamberlan 8500W) and control it and read the sensors? And this would be another Node server, would that be a locally run connection from the ratgdo v2.5 to the node or cloud?

I only went with the Chamberlain/MyQ hardware option for my opener for the ability to integrate with it. I think I will hack some other IoX locally connected I/O to it and call it a day.

Is there a pay option for more calls, 20 total calls per min seems pretty low. Or maybe I am misunderstanding what a call is, if I had 21 devices would a single query cap me out?

Current Version: 0.9.70 [Production]

@Panda88 any update on the node server real time status? Even with the node server stopped it's always showing connected.

I read 1/4 open air, FCC wouldn't allow 4 miles.

Is the node being actively worked on? If there are new devices will they be added to the node?

Do you have any other YoLink devices? Wondering what the range and reliability is for them. They seem to have some motion sensors that I would be interested in but only if they could directly control scenes in IoX. Also do you know if the YoLink will communicate locally or just through their cloud.

Does that give you door status and control or just control?

I would be fine to pay to play, I would also be just as happy buying a I/O Module - Control & Status Kit but don't know that I can with the Liftmaster 8500w wiring direct. I suppose I could hard wire the I/O Link to a wireless remote. Has anyone done this?

Mine has been working solid since Oct 13th. I have had to restart EISY and PG3X a few times for updates and what not but MyQ is starting and connecting normally(and without waiting an hour or day).

Updated EISY to PG3x v3.2.11 and it isn't reading the non-managed/manually created nodes from the Admin Console. I have a node in slot 1 for NodeLink used for brultech gem emergy monitoring. This time it is still in the admin console and is functioning but doesn't show as unmanaged anymore in PG3x.

I have found that this node is not really be maintained and doesn't really work.

I stopped mine for 45min and started and now it's working

20/60

Looks like the support site is having issues, none of the links work:

Same exact

Node server starts but won't connect to the MyQ Service and displays: There was an error connecting to the MyQ service. Please check the log files and correct the issue before restarting the nodeserver. To try to fix the error above I changed my password and removed special characters and waited 60 min. 2023-10-12 15:20:02,940 Thread-11 udi_interface DEBUG nodes:start: In start() for MyQ Service node... 2023-10-12 15:20:02,940 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '11a7c7c2-f463-4afb-bd8d-fd05f117393e', 'uuid': '00:21:b9:02:5f:c4', 'profileNum': 8, 'address': 'service', 'name': 'MyQ Service', 'nodeDefId': 'SERVICE', 'nls': None, 'hint': '0x00000000', 'controller': 1, 'primaryNode': 'service', 'private': None, 'isPrimary': 1, 'enabled': 1, 'timeAdded': 1672797294115, 'timeModified': 1697138402526, 'dbVersion': 1} 2023-10-12 15:20:02,940 Thread-11 udi_interface INFO nodes:start: Establishing initial MyQ connection... 2023-10-12 15:20:02,941 Thread-11 udi_interface DEBUG myqapi:loginToService: in API loginToService()... 2023-10-12 15:20:02,941 Thread-11 udi_interface INFO myqapi:_oAuthRetrieveToken: Logging in and retrieving access token via oAuth... 2023-10-12 15:20:02,991 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2023-10-12 15:20:02,991 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2023-10-12 15:20:02,992 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': 'c43cc620-7f8a-4d8a-baf2-a38d01051edb', 'uuid': '00:21:b9:02:5f:c4', 'profileNum': 8, 'address': 'gw270009f38a', 'name': 'Garage Door', 'nodeDefId': 'GATEWAY', 'nls': None, 'hint': '0x0101000', 'controller': 0, 'primaryNode': 'gw270009f38a', 'private': None, 'isPrimary': 1, 'enabled': 1, 'timeAdded': 1672797984735, 'timeModified': 1672797984735, 'dbVersion': 1} 2023-10-12 15:20:03,040 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2023-10-12 15:20:03,041 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2023-10-12 15:20:03,041 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '248ff01c-a060-4750-96a4-4fb3f5a31a81', 'uuid': '00:21:b9:02:5f:c4', 'profileNum': 8, 'address': 'cg08200e7aba', 'name': 'Garage Door', 'nodeDefId': 'GARAGE_DOOR_OPENER', 'nls': None, 'hint': '0x01120100', 'controller': 0, 'primaryNode': 'gw270009f38a', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1672797984935, 'timeModified': 1672797984935, 'dbVersion': 1} 2023-10-12 15:20:03,090 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message addnode 2023-10-12 15:20:03,091 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING addnode 2023-10-12 15:20:03,091 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': 'cea8c107-4340-46ca-a5ae-acbc93ef9da0', 'uuid': '00:21:b9:02:5f:c4', 'profileNum': 8, 'address': 'tc00019507633', 'name': 'Garage-camera', 'nodeDefId': 'MYQ_DEVICE', 'nls': None, 'hint': '0x00000000', 'controller': 0, 'primaryNode': 'service', 'private': None, 'isPrimary': 0, 'enabled': 1, 'timeAdded': 1672797984835, 'timeModified': 1672797984835, 'dbVersion': 1} 2023-10-12 15:20:03,954 Thread-11 udi_interface WARNING myqapi:_oAuthRequest: Network/server error logging into MyQ service: 429 Client Error: Too Many Requests for url: https://partner-identity.myq-cloud.com/connect/authorize?client_id=######### 2023-10-12 15:20:03,954 Thread-11 udi_interface DEBUG myqapi:_oAuthRetrieveToken: Error in Step 1 of oAuth flow. 2023-10-12 15:20:03,954 Thread-11 udi_interface.custom DEBUG custom:__setitem__: CUSTOM: login_error = There was an error connecting to the MyQ service. Please check the log files and correct the issue before restarting the nodeserver. ...saving 2023-10-12 15:20:03,954 Thread-11 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-10-12 15:20:03,954 Thread-11 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'key': 'notices', 'value': {'login_error': 'There was an error connecting to the MyQ service. Please check the log files and correct the issue before restarting the nodeserver.'}}]} 2023-10-12 15:20:03,956 Thread-11 udi_interface.node DEBUG node:setDriver: service:MyQ Service Reporting set ST to 0 to Polyglot 2023-10-12 15:20:03,956 Thread-11 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2023-10-12 15:20:03,956 Thread-11 udi_interface.interface DEBUG interface:send: PUBLISHING {'set': [{'address': 'service', 'driver': 'ST', 'value': '0', 'uom': 2, 'text': None}]} 2023-10-12 15:20:03,970 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message notices 2023-10-12 15:20:03,970 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING notices 2023-10-12 15:20:03,970 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-10-12 15:20:03,971 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {'login_error': 'There was an error connecting to the MyQ service. Please check the log files and correct the issue before restarting the nodeserver.'} 2023-10-12 15:20:03,971 Command udi_interface.custom DEBUG custom:load: CUSTOM: -- checking login_error / There was an error connecting to the MyQ service. Please check the log files and correct the issue before restarting the nodeserver. 2023-10-12 15:20:04,012 MQTT udi_interface.interface INFO interface:_message: Successfully set service :: ST to 0 UOM 2 2023-10-12 15:20:18,574 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-10-12 15:20:18,574 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-10-12 15:20:18,575 Thread-18 udi_interface DEBUG myqns:shortPoll: In shortPoll()...

IoX v5.7.0 running on EISY. Ran the PG3 update today which required a reboot and came back to all or almost all of my programs disabled. What a PITA to enable only the ones that are supposed to be enabled. Is there a fix or fix in the works for this?

My MyQ Node displayed blue(ish) notification that there was an update, I then went to Purchases, selected Update (under the subscription one) and it seems to have been updated and stable. Odd even after it was updated, on the Purchases tab it still says Update. I thought when there was an update for a node it showed up as a button on the Node details page.

Awesome, how about about doing the User-Agent as an optional variable in the PG3 web interface?

sudo find / -name myq*.* That seems to be working for me too.

Update from 5.6.4 went very smooth, zero issues. Like all updates I SSH and run this to watch what's going on: sudo tail -f /var/udx/logs/log

Still using NodeLink to connect my Brultech GEM electric monitors to IoX (EISY 5.7.0 and PG3x Version 3.2.4), no issues.

I am seeing the same thing and also see this in my logs when it goes down: WARNING myqapi:_callAPI: Network/server error in HTTP GET in _callAPI(): 403 Client Error: Forbidden for url: https://devices.myq-cloud.com/api/v5.2/Accounts/4adfef7d-250e-4fcb-801a-0109b2820ec7/Devices