captainc

I would try momentary C. I just put a 2450 on a liftmaster due to the myq node no longer working and it works correctly with that and with the google home. I now have to say turn on or turn off garage door... I just pulled up what i have it set at. I think I put a magnetic switch for the sensor.

I have found some led bulbs don't like insteon like others. I can have 2 of the same spec bulbs from different mfgs, one will light faster than the other and/or cause it to ramp up when it is suppose to go on, among other things like humming or other noises. Put the clear filament glass bulbs in different locations found some of them burn out in months versus the 20 years and others fine.

I can buy one for half the price and integrate into my isy for less.. https://www.theverge.com/23949612/chamberlain-myq-smart-garage-door-controller-homebridge-integrations

the zooz zen17 has i/o so it can open and close and with a magnetic contact switch show it open or closed. i think my garage door switch comes tomorrow and should have it working this weekend.

I ordered the door/light switch LiftMaster 883LM Security+ 2.0 MyQ Door Control Push Button off amazon for $17 and will solder on dry contact relay for those with a z wave zooz zen52 which I have found work pretty well. Now no need to tie myself to Myq products for other door opener replacements.

sony use to think the same way with their products and patents and now they can enjoy their best days in the rear view mirror.

I have been getting the 429 error even stopping it for a day or 2. I don't understand at that point where it has too many login attempts. I am thinking more of putting zwave dry contacts on the openers with momentary setup if the node can't work with their server anymore.

I updated to 3.2.23, stopped the service and started the next day and it worked.

Thanks for working on it Many times my eisy has to be unplugged to reboot correctly, have not chased that down.

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

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

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.

I just got my J7+ and could not discover it either. The info does not say it works with it I gave it a try. The J7+ is a big seller so hopefully it can get set up for the eisy soon.

i did just figure that out, i guess i wasn't far enough in front of the doorbell for it to see motion. i just thought it was a little strange it had the same switch icon as the insteon motion detection where you use status to control nodes and have more options. i have one last slot on my voice annunciator for people coming to the door for fun. for extra fun after i get my occupancy going i can fire up the alarm and strobe when i'm not home. i have one ring i have to use batteries so getting a notification when the battery is low is nice.

after i got the node server installed each ring doorbell showed a motion node and online node. i played around for a short while can could not get the motion to respond in a scene or program. i didn't have the time to go further and look into how to make it work as a true motion detector which i am hoping to turn on lights and other things. my trial is expired so i will have to buy the node and hopefully get the information to get it working. it's at another house i am at half the week. there did not appear to be any instructions like all the other node servers i have purchased.