Ryobi Garage Door Opener

njschwartz · July 27, 2019, 3:29am

Well that varname is indeed the garage door id, but it should be posting that in the logs. Are you getting an error? It should look like:
dev:4612019-07-26 10:26:58.395 pm infoThe Door ID for a GD201 is: c4be84e87ae6
dev:4612019-07-26 10:26:58.358 pm debugGD201
dev:4612019-07-26 10:26:58.355 pm infoThe Door ID for a GD126 is: 9884e3d90ade
dev:4612019-07-26 10:26:58.351 pm debugGD126
dev:4612019-07-26 10:26:58.337 pm debuggda500hub
dev:4612019-07-26 10:26:58.334 pm debuggda500hub
dev:4612019-07-26 10:26:58.330 pm debuggda500hub
dev:4612019-07-26 10:26:58.316 pm debug[result:[[_id:5b7dca56c23b96f211b6b9e3, varName:587a623568f9, metaData:[name:587a623568f9, version:1, icon:/img/devices/gda_500.png, description:RYOB

Are you not seeing anything like that? Weird. Sounds like you worked around it anyway, but I'd like to figure out why yours is a little weird.

Stat · July 27, 2019, 11:42am

Make sure that you have "Enable debug logging" enabled so that you can see the entire log. If you can not still see the Door ID then remove the device and reinstall. Put in your username (email) and password save then go back and look at the log and you should see it. You are looking for a single line like njschwartz shows in his post.

Stat · July 27, 2019, 11:43am

Here is another log of just the speaker module turned on and turned off for you.

2019-07-27 07:39:17.435 am debugparsed {"jsonrpc":"2.0","method":"wskAttributeUpdateNtfy","params":{"topic":"508cb15d08e8.wskAttributeUpdateNtfy","varName":"508cb15d08e8","btSpeaker_1.moduleState":{"value":true,"lastValue":false,"lastSet":1564227561311}},"id":0}

dev:1952019-07-27 07:38:57.303 am debugparsed {"jsonrpc":"2.0","method":"wskAttributeUpdateNtfy","params":{"topic":"508cb15d08e8.wskAttributeUpdateNtfy","varName":"508cb15d08e8","btSpeaker_1.moduleState":{"value":false,"lastValue":true,"lastSet":1564227541162}},"id":0}

I hope that this helps. I will post just the fan at different stages for you momentarily.

Stat · July 27, 2019, 11:50am

Here is the log of the fan at different speed settings.

dev:1952019-07-27 07:47:42.803 am debugparsed {"jsonrpc":"2.0","method":"wskAttributeUpdateNtfy","params":{"topic":"508cb15d08e8.wskAttributeUpdateNtfy","varName":"508cb15d08e8","fan_2.speed":{"value":0,"lastValue":20,"lastSet":1564228066678}},"id":0}

dev:1952019-07-27 07:47:32.039 am debugparsed {"jsonrpc":"2.0","method":"wskAttributeUpdateNtfy","params":{"topic":"508cb15d08e8.wskAttributeUpdateNtfy","varName":"508cb15d08e8","fan_2.speed":{"value":20,"lastValue":60,"lastSet":1564228055920}},"id":0}

dev:1952019-07-27 07:47:23.721 am debugparsed {"jsonrpc":"2.0","method":"wskAttributeUpdateNtfy","params":{"topic":"508cb15d08e8.wskAttributeUpdateNtfy","varName":"508cb15d08e8","fan_2.speed":{"value":60,"lastValue":100,"lastSet":1564228047602}},"id":0}

dev:1952019-07-27 07:47:14.635 am debugparsed {"jsonrpc":"2.0","method":"wskAttributeUpdateNtfy","params":{"topic":"508cb15d08e8.wskAttributeUpdateNtfy","varName":"508cb15d08e8","fan_2.speed":{"value":100,"lastValue":0,"lastSet":1564228038511}},"id":0}

I hope this helps you.

Again, thank you for all of your assistance and coding with this. It makes life so much easier being able to control the Ryobi GDO with the Hubitat.

matthewschultz92 · July 27, 2019, 1:32pm

Thanks, Stat, Yes that was on, I was confused by the fact that there was nothing in the data, that remotely looked like Garage ID. Additionally, all the data was lumped together (i.e. lack of carriage returns, etc), making it harder to read. What model of GDO do you have? I have the model 200.

I forwarded the nasty looking logs directly to Njschwartz so he can decipher whats going on.

So using VarName got me up and running and it has worked great!

Stat · July 27, 2019, 1:56pm

I have the GD126. I wish I would have gotten the 200.

njschwartz · July 27, 2019, 7:25pm

Hey Matt, so I looked over the initial logs to see what the problem was and I see what was wrong. It appears the older models (I am assuming before they added the extra relay hub we have to use now) have a slightly different response than the new ones. To be honest I didn't even know there was a 200 model. I have the 126 and the 201 so that is what I coded for. Since yours didn't match it didn't find it and post the ID. I think I have that fixed, I will post an updated version for you to test at some point. The reason those logs look so messy is that is posting the raw json response from the ryobi server. You can turn off the debugging logs to clean them up and not show all that unless you need it.

I am also going to look at all the super helpful logs you both gave me regarding the modules and see about getting the child devices built. I will need some help testing those since I don't own those modules and cannot test whether the commands work or not. Getting their status will be simple, but control, I dunno.

Question for you both, when you turn the light on the GDO on/off, do you get messages in the logs? Neither of mine do and I am not sure if that is a glitch or what. I know controlling the light is doable, but I don't know if status is for whatever reason. Thanks!

Stat · July 27, 2019, 10:42pm

I have gone through my logs and I do not see any reference for the light turning on or off on the GDO.

Let me know when you the code ready for the modules and I will put them in and see if they work.

matthewschultz92 · July 28, 2019, 12:42am

Hey Nate, Yes the 200 model was the very first model out the door. So this all makes sense now. Yes, I turned the debug logs off, What a difference that makes! Nice and clean data.

I'll be more than happy to work with you and test any new drivers. Hopefully, the fact that my GDO is dumping more of the raw data from the server works to our advantage. And hopefully, the commands to control the modules is the same for the new and old GDO's Again I really appreciate the work.

In the PM I sent you last night, I should have included the logs for what I was seeing when I turned the lights on and off. Along with enabling/disabling the microphone in the BT speaker. I Re-ran the lights again today, See below for the lights:

Light Off:
dev:6092019-07-27 05:30:48.437 pm debugparsed {"jsonrpc":"2.0","method":"wskAttributeUpdateNtfy","params":{"topic":"987bf310f7bd.wskAttributeUpdateNtfy","varName":"987bf310f7bd","garageLight_7.lightState":{"value":false,"lastValue":true,"lastSet":1564273851771}},"id":0}

Light On:
dev:6092019-07-27 05:30:45.411 pm debugparsed {"jsonrpc":"2.0","method":"wskAttributeUpdateNtfy","params":{"topic":"987bf310f7bd.wskAttributeUpdateNtfy","varName":"987bf310f7bd","garageLight_7.lightState":{"value":true,"lastValue":false,"lastSet":1564273848763}},"id":0}

Let me know if you need me to run anything else.

njschwartz · July 28, 2019, 2:29am

That is super interesting. The newer models (126/201) do not report light status. Not sure what they did or why, but it doesn't work. Annoying, but whatever I suppose. Ok, give me some time to work on it and I will hopefully get it all setup to control those modules. I will let you all know.

Stat · July 28, 2019, 11:54am

Is there a way to get the door position sensing unit battery status? This way we could put that on the dashboard.

matthewschultz92 · July 28, 2019, 2:39pm

@Stat

What's that? That's not the same battery that is used to open the door during a power outage is it?

Stat · July 28, 2019, 2:56pm

That is the position unit that you placed on the garage door that allows the ability to show the state of the door being open/closed. It has batteries in it. And it would be nice to know the battery level of the unit.

matthewschultz92 · July 28, 2019, 3:36pm

Another disadvantage of getting the first model. Mine didn't come with that sensor. That explains why opening to presets stopped working a few years back. They must have been estimating position by knowing the start and stop positions and the counting motor revolutions...

Stat · July 28, 2019, 5:24pm

Here is the door position sensor. The problem with the sensor is it connects to a Bluetooth unit that is plugged in to an outlet and that connects wirelessly to the GDO, which in turns connects to your wireless network. The disadvantage to the GDO126 Is there is no battery backup😞.

matthewschultz92 · July 28, 2019, 5:38pm

That seems kinda kludgy. I wonder what the loop response of that is?

njschwartz · July 28, 2019, 10:00pm

I am not certain on that. Let me look and see if that is in the logs anywhere. Does the app notify you when they are low? I don't think it does so I am guessing not, but I can look.

Stat · July 28, 2019, 10:14pm

No the app doesn't show it.

njschwartz · July 28, 2019, 10:27pm

Yea~I didn't think so. I don't think it comes up in all the json data sent back by Ryobi either. The light thing is crazy too. The old model it works the newer model it doesn't. I think they had to make a rapid change (I am guessing for legal reasons) and did a half ass job of it honestly. Ohh well, I am still overall happy with the stupid thing, but they could have made it better! lol

simon · July 29, 2019, 3:34am

I have 2 GS126's. I've just configured them onto Hubitat today. Like posters before me I had to get the garage door ID from the logs.... no big deal.

I created two devices, one for each door. Working fine. I have Parking assist and the Inflator. Here's the logs for the inflator

dev:652019-07-28 10:32:27.922 pm debugparsed {"jsonrpc":"2.0","method":"wskAttributeUpdateNtfy","params":{"topic":"606405b17e3f.wskAttributeUpdateNtfy","varName":"606405b17e3f","inflator_3.moduleState":{"value":false,"lastValue":true,"lastSet":1564371149609}},"id":0}

dev:652019-07-28 10:32:18.806 pm debugparsed {"jsonrpc":"2.0","method":"wskAttributeUpdateNtfy","params":{"topic":"606405b17e3f.wskAttributeUpdateNtfy","varName":"606405b17e3f","inflator_3.moduleState":{"value":true,"lastValue":false,"lastSet":1564371140492}},"id":0}

Thanks,
Simon