4481hoods Posted September 8, 2023 Posted September 8, 2023 All of a sudden, I have to restart application to make it work. Tried reinstalling did not seem to help. Any ideas on what has changed?
4481hoods Posted September 8, 2023 Author Posted September 8, 2023 Attached log file. MyQ_9-8-2023_75305-AM.zip
jkosharek Posted September 8, 2023 Posted September 8, 2023 (edited) @Goose66This is what I am seeing in the logs: PG3x Version 3.2.4 Frontend Version: 3.2.4 IoX Version: 5.6.4 MyQ Version: 3.1.21 2023-09-08 10:09:41,753 Thread-11 udi_interface INFO nodes:start: Establishing initial MyQ connection... 2023-09-08 10:09:41,753 Thread-11 udi_interface INFO nodes:start: Establishing initial MyQ connection... 2023-09-08 10:09:41,753 Thread-11 udi_interface INFO myqapi:_oAuthRetrieveToken: Logging in and retrieving access token via oAuth... 2023-09-08 10:09:41,753 Thread-11 udi_interface INFO myqapi:_oAuthRetrieveToken: Logging in and retrieving access token via oAuth... 2023-09-08 10:09:44,834 Thread-11 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-09-08 10:09:44,834 Thread-11 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-09-08 10:09:44,891 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-09-08 10:09:44,891 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-09-08 10:09:57,343 Thread-18 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:09:57,343 Thread-18 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:10:01,578 MQTT udi_interface.interface INFO interface:_message: Successfully set tc00019507633 :: GV1 to 1 UOM 25 2023-09-08 10:10:01,578 MQTT udi_interface.interface INFO interface:_message: Successfully set tc00019507633 :: GV1 to 1 UOM 25 2023-09-08 10:10:01,692 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: ST to 0 UOM 25 2023-09-08 10:10:01,692 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: ST to 0 UOM 25 2023-09-08 10:10:01,732 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV0 to 485823 UOM 58 2023-09-08 10:10:01,732 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV0 to 485823 UOM 58 2023-09-08 10:10:01,772 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV1 to 1 UOM 25 2023-09-08 10:10:01,772 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV1 to 1 UOM 25 2023-09-08 10:10:01,812 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV2 to 1 UOM 25 2023-09-08 10:10:01,812 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV2 to 1 UOM 25 2023-09-08 10:10:01,866 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV3 to 1 UOM 25 2023-09-08 10:10:01,866 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV3 to 1 UOM 25 2023-09-08 10:10:01,906 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV4 to 101 UOM 25 2023-09-08 10:10:01,906 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV4 to 101 UOM 25 2023-09-08 10:10:01,964 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV5 to 101 UOM 25 2023-09-08 10:10:01,964 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV5 to 101 UOM 25 2023-09-08 10:10:02,007 MQTT udi_interface.interface INFO interface:_message: Successfully set gw270009f38a :: ST to 1 UOM 25 2023-09-08 10:10:02,007 MQTT udi_interface.interface INFO interface:_message: Successfully set gw270009f38a :: ST to 1 UOM 25 2023-09-08 10:10:02,066 MQTT udi_interface.interface INFO interface:_message: Successfully set service :: ST to 1 UOM 2 2023-09-08 10:10:02,066 MQTT udi_interface.interface INFO interface:_message: Successfully set service :: ST to 1 UOM 2 2023-09-08 10:10:17,350 Thread-19 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:10:17,350 Thread-19 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:10:17,507 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV0 to 485839 UOM 58 2023-09-08 10:10:17,507 MQTT udi_interface.interface INFO interface:_message: Successfully set cg08200e7aba :: GV0 to 485839 UOM 58 2023-09-08 10:10:37,392 Thread-21 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:10:37,392 Thread-21 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:10:37,422 Thread-21 udi_interface 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/############/Devices 2023-09-08 10:10:37,422 Thread-21 udi_interface 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/############/Devices 2023-09-08 10:10:37,422 Thread-21 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:10:37,422 Thread-21 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:10:37,455 MQTT udi_interface.interface INFO interface:_message: Successfully set service :: ST to 0 UOM 2 2023-09-08 10:10:37,455 MQTT udi_interface.interface INFO interface:_message: Successfully set service :: ST to 0 UOM 2 2023-09-08 10:10:57,405 Thread-22 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:10:57,405 Thread-22 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:10:58,733 Thread-22 udi_interface 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/############/Devices 2023-09-08 10:10:58,733 Thread-22 udi_interface 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/############/Devices 2023-09-08 10:10:58,733 Thread-22 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:10:58,733 Thread-22 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:11:17,410 Thread-23 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:11:17,410 Thread-23 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:11:19,187 Thread-23 udi_interface 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/############/Devices 2023-09-08 10:11:19,187 Thread-23 udi_interface 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/############/Devices 2023-09-08 10:11:19,187 Thread-23 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:11:19,187 Thread-23 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:11:37,411 Thread-25 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:11:37,411 Thread-25 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:11:38,566 Thread-25 udi_interface 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/############/Devices 2023-09-08 10:11:38,566 Thread-25 udi_interface 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/############/Devices 2023-09-08 10:11:38,567 Thread-25 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:11:38,567 Thread-25 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-08 10:11:57,420 Thread-26 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... 2023-09-08 10:11:57,420 Thread-26 udi_interface INFO myqns:shortPoll: Updating node states in shortPoll()... Edited September 8, 2023 by jkosharek
jkosharek Posted September 8, 2023 Posted September 8, 2023 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
hart2hart Posted September 8, 2023 Posted September 8, 2023 I’m seeing it a few times per day recently.
Goose66 Posted September 8, 2023 Posted September 8, 2023 (edited) Ok, let me see if it may be the phase out of older API calls. This happens every year-and-a-half or so. UPDATE: While it could be just a problem with the oAuth servers (a partner to Chamberlain), it looks to me like they have changed access parameters, either the client secret or something else. As I have mentioned, I built this integration based on another integration that exists out there that I couldn't use directly. So I have no way of hacking the mobile app to see what has changed in the authorization structure and instead will have to wait and see what others find. Unfortunately not seeing other integrations having specific issues reported yet, and my mobile app is still working. I will continue to investigate. If you don't restart the node server, your node server may continue to operate for some time. Also, merged the two threads. Edited September 8, 2023 by Goose66
TUhl01 Posted September 8, 2023 Posted September 8, 2023 I have had the same problem for a while going offline. It is usually for a short time. Glad to hear it is not only me. I was thinking it may be a problem on the Liftmaster side.
bigDvette Posted September 9, 2023 Posted September 9, 2023 started having same issue on Home Assistant. They found a fix by modifying one of the python files. https://github.com/home-assistant/core/issues/99947#issuecomment-1712369141 specifically this was the fix. docker exec -it homeassistant bash cd /usr/local/lib/python3.11/site-packages/pymyq/ cp request.py request_bup.py vi request.py i to enter insert mode Modify line 34 Was self._useragent = None Is self._useragent = str("anytexthere") Esc key to exit insert mode :w + enter to write the changes + enter to exit VI I see in the old v2 node server User_Agent was set to "null" Not sure if this will help 1
Goose66 Posted September 10, 2023 Posted September 10, 2023 (edited) I saw the conversation on the pymyq GitHub repository today about the changes. Unfortunately I am traveling until Wednesday, but should be able to look at it then. Edited September 10, 2023 by Goose66 3
dbwarner5 Posted September 10, 2023 Posted September 10, 2023 I am too have problems with MyQ app.. getting errors like this: 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/xxxxx/Devices (account info replaced with XXX.) Restart gets me one or two actions before it stops communicating correctly. Password is correct as I checked it by logging out of the app and then logging back in. 1
captainc Posted September 11, 2023 Posted September 11, 2023 On 9/8/2023 at 3:40 PM, Goose66 said: Ok, let me see if it may be the phase out of older API calls. This happens every year-and-a-half or so. UPDATE: While it could be just a problem with the oAuth servers (a partner to Chamberlain), it looks to me like they have changed access parameters, either the client secret or something else. As I have mentioned, I built this integration based on another integration that exists out there that I couldn't use directly. So I have no way of hacking the mobile app to see what has changed in the authorization structure and instead will have to wait and see what others find. Unfortunately not seeing other integrations having specific issues reported yet, and my mobile app is still working. I will continue to investigate. If you don't restart the node server, your node server may continue to operate for some time. Also, merged the two threads. a very frustrating weekend of google not being able to open the garage door, it's not able to authenticate with chamberlain. the phone app works, opening on the admin console works sometimes and with google home even less. the log.. 2023-09-11 00:00:27,795 Thread-1860 udi_interface INFO myqns:longPoll: Updating node states in longPoll()... 2023-09-11 00:00:27,824 Thread-1860 udi_interface INFO myqapi:_oAuthRetrieveToken: Logging in and retrieving access token via oAuth... 2023-09-11 00:00:27,960 Thread-1860 udi_interface WARNING myqapi:_oAuthRequest: Network/server error logging into MyQ service: 403 Client Error: Forbidden for url: https://partner-identity.myq-cloud.com/connect/authorize?client_id=IOS_CGI_MYQ&code_challenge=JvTCDSVuH2YdlQHACuBejLtZ64O1mZi4v4g7TqvrebM&code_challenge_method=S256&redirect_uri=com.myqops%3A%2F%2Fios&response_type=code&scope=MyQ_Residential+offline_access 2023-09-11 00:00:27,960 Thread-1860 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices. 2023-09-11 00:01:27,848 Thread-1864 udi_interface INFO myqns:longPoll: Updating node states in longPoll()... 2023-09-11 00:01:27,848 Thread-1864 udi_interface INFO myqapi:_oAuthRetrieveToken: Logging in and retrieving access token via oAuth... 2023-09-11 00:01:27,976 Thread-1864 udi_interface WARNING myqapi:_oAuthRequest: Network/server error logging into MyQ service: 403 Client Error: Forbidden for url: https://partner-identity.myq-cloud.com/connect/authorize?client_id=IOS_CGI_MYQ&code_challenge=GeP1WS71pjgbeGrOr2o0IzRwuIOltQ-TPnIatVDQlck&code_challenge_method=S256&redirect_uri=com.myqops%3A%2F%2Fios&response_type=code&scope=MyQ_Residential+offline_access 2023-09-11 00:01:27,977 Thread-1864 udi_interface WARNING nodes:updateNodeStates: getDeviceList() returned no devices.
dbwarner5 Posted September 11, 2023 Posted September 11, 2023 53 minutes ago, captainc said: a very frustrating weekend of google not being able to open the garage door, it's not able to authenticate with chamberlain. the phone app works, opening on the admin console works sometimes and with google home even less. It's funny how much we can learn to depend on the conveniences of home automation! @Goose66 if you need more logs or testing when you get back Wednesday, feel free to reach out. 1
landolfi Posted September 11, 2023 Posted September 11, 2023 In the latest discussion on Github about this problem, which is also occurring on the MyQ Home Assistant integration, a Homebridge MyQ developer says that this is the result of a load balancing issue at MyQ: https://github.com/home-assistant/core/issues/99947#issuecomment-1712966435 1
landolfi Posted September 11, 2023 Posted September 11, 2023 I don't use the MyQ node server but the Home Assistant integration, which was similarly not working, is now. There have been no updates to the integration, implying as discussed above that the issue was on the MyQ side. 1
dbwarner5 Posted September 12, 2023 Posted September 12, 2023 20 hours ago, landolfi said: I don't use the MyQ node server but the Home Assistant integration, which was similarly not working, is now. There have been no updates to the integration, implying as discussed above that the issue was on the MyQ side. Still hasn't resolved for me yet.. still getting these errors: 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...... 1
landolfi Posted September 12, 2023 Posted September 12, 2023 39 minutes ago, dbwarner5 said: Still hasn't resolved for me yet.. still getting these errors: 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...... Where are you located? Last I heard there were still some people who couldn't get in, but the theory was that the load balancing was only fixed for certain regions. I'm most likely in US-East.
gregkinney Posted September 12, 2023 Posted September 12, 2023 (edited) I use the MyQ Home Assistant integration and was able to get mine working again by following the instructions in the conversation @landolfi linked. However, the changes made were in the python files directly in the integration, so I think it's a matter of waiting patiently for @Goose66 to apply the same repair. Edited September 12, 2023 by gregkinney
dbwarner5 Posted September 12, 2023 Posted September 12, 2023 1 hour ago, landolfi said: Where are you located? Last I heard there were still some people who couldn't get in, but the theory was that the load balancing was only fixed for certain regions. I'm most likely in US-East. Midwest.. Michigan. It seems to be hit or miss. sometimes it works, but the NS is reporting that it cant connect to the MyQ server.
landolfi Posted September 12, 2023 Posted September 12, 2023 (edited) 1 hour ago, dbwarner5 said: Midwest.. Michigan. It seems to be hit or miss. sometimes it works, but the NS is reporting that it cant connect to the MyQ server. I'm in Chicagoland, the HA MyQ integration is rock solid since yesterday at this time. Maybe something else needs to be done to reset the NS, or maybe we're in different regions and yours isn't fixed yet. Edited September 12, 2023 by landolfi 1
captainc Posted September 14, 2023 Posted September 14, 2023 On 9/9/2023 at 8:29 PM, Goose66 said: I saw the conversation on the pymyq GitHub repository today about the changes. Unfortunately I am traveling until Wednesday, but should be able to look at it then. Does it look positive for a workaround or mod for this ns? The pain inflicted on me by the wife when any of the system goes down is unbearable
landolfi Posted September 14, 2023 Posted September 14, 2023 16 minutes ago, captainc said: Does it look positive for a workaround or mod for this ns? The pain inflicted on me by the wife when any of the system goes down is unbearable Just FYI, HA myQ users in the East region are still reporting trouble with this 403 error on the myQ integration to Home Assistant, so if you're in an area served by the East myQ servers, it is possible it could turn out to be nothing to do with the NS and it will just start working soon on its own, although since it's a node server you might need to restart when it does start working again. I don't know how to tell what region I'm connecting to, but since my HA integration is working, there's a good chance I'm connecting to the West.
bigDvette Posted September 14, 2023 Posted September 14, 2023 I'm in Texas and have the problem with homeassistant. Not sure which servers for MyQ connected to, but HA isn't working. I haven't seen a bunch of people on the HA boards saying it is working.
bigDvette Posted September 14, 2023 Posted September 14, 2023 (edited) So I just took a shot at fixing myself. ssh in to device sudo find . -name myq*.* find location of myqapi.py in list ( sudo cp {location of myqapi.py}/myqapi.py {location of myqapi.py}/myqapi.py.bk (make backup in case) sudo vi {location of myqapi.py}/myqapi.py There are 2 instance of the below line "User-Agent": "null"^M Find then and change them toi "User-Agent": str("{sometexthere}")^M (I used /Agent to find it, went over before "null" and typed i, then typed str("{sometexthere}") and hit esc key, then d {right arrow key} x 6, :qw, restarted nodeserver obviously {sometexthere} is whatever random text you want to use Essentially same as I did for my homeassitant plugin. Should be able to work around. Maybe we need a new config variable with ability to define a unique user_agent and it get put in instead of "null". No idea. But I'm working again. Edited September 14, 2023 by bigDvette
captainc Posted September 14, 2023 Posted September 14, 2023 2 hours ago, landolfi said: Just FYI, HA myQ users in the East region are still reporting trouble with this 403 error on the myQ integration to Home Assistant, so if you're in an area served by the East myQ servers, it is possible it could turn out to be nothing to do with the NS and it will just start working soon on its own, although since it's a node server you might need to restart when it does start working again. I don't know how to tell what region I'm connecting to, but since my HA integration is working, there's a good chance I'm connecting to the West. I am in RI, from what I see in the 403 error line, the ns pw isn't getting authorized thus not connecting. I have had issues with other connections using the 2 part authorizations that ended up being fixed to work with it. just my thought
Recommended Posts