It’s auto-generated. Open the hamburger menu in upper left corner of HA, choose ESPHome, select RatGDO, edit the YAML to comment out the encryption key.
one of us is not using HA 
I do have hoobs tho
If you have a separate/standalone ESPHome install then the code change would be done there.
My ratGDO is my first and only ESPHome device and I have no HA running, so I had to pick between MQTT and ESPHome when setting it up. Since MQTT requires an extra moving part, I opted for ESPHome using @jonathanb’s ESPHome library and worked my way up to getting it to work with the garage door. I avoided HA for the same reason, an extra moving part. Simpler is sometimes better 
Ultimately, this is why some choose to bring up and install alternate products in the first place. Sometimes, there are products that are just the best solution to a problem and they're not always going to work with a single hub. I agree that simple is good in a lot of cases, but there's definite value in flexibility as well. For me, the combination of Hubitat and HA (even with a standard, no frills installation) allows coverage for the vast majority of smart devices out there. Hubitat simply doesn't do wifi devices well... HA has it front and center (take a look at the Green version). With Hubitat <--> HADB <--> HA, you never really have to worry about device selection again.
I believe that the ESPHome update yesterday has issues. HPM gives an error when trying to update or repair or even install after deleting everything. The problem seems to be that the bundle has bad metadata, as shown even if a manual update is attempted:
PR #31 this afternoon fixed things. All better now, thanks.
Looking to try this on the konnected pro device. I have windows, doors, motion, switches and digital temperature sensors on it.
Does this directly talk to HE?
I applied the most recent update to ESPHome & the esphome ratgdo package using HPM yesterday. I didn't get any error messages or other indications the update went awry. But, since the update both my ratgdo devices are offline from Hubitat. Going directly to the IP of each shows the ratgdo devices still work perfectly, all functionality as expected. In hubitat events for one of them I see:
Large Garage Door is offline: Cannot invoke method multiply() on null object
In the hubitat logs I see the same, with more detail:
java.lang.NullPointerException: Cannot invoke method multiply() on null object on line 257 (method updated)
Several entries are like that, with just the last parenthetical different, like I get java.lang.NullPointerException: Cannot invoke method multiply() on null object on line 257 (method initialize) if I click on Initialize in hubitat, for example. I can't find 'multiply' being called anywhere in the esphome API library groovy file, nor in the ratgdo driver file. I tried deleting and re-creating the devices, but I get the same error. Any ideas?
Did you disable (comment out) the encryption lines in the RatGDO yaml file? Every time the RatGDO firmware gets updated, the RatGDO yaml file gets recreated/restored with ESPHome encryption re-enabled. See discussion upthread.
I read that part of the thread, but can't find where that yaml file lives. I never saw that file or did anything with regards to encryption when I first installed the ratgdo driver through HPM last month
Edited to add, just to be clear, I am not using HA or MQTT. This is the esphome firmware on the ratgdo and the esphome/ratgdo driver from J Bradshaw, all installed through HPM.
Ok, glad you added this information because it wasn’t clear.
If you were using HA (and I understand that you are not), you would access and edit the RatGDO configuration yaml file by going to the HA “hamburger” menu in the upper left corner, choose ESPHome, then select the RatGDO device, choose Edit.
But you are not using HA. There are only two other ways to update the firmware on RatGDO of which I am aware. I don’t know the method that you used to update the ESPHome firmware on your RatGDO, so I probably can’t help you with your issue.
The first, which I have only done once, was the initial firmware flash by attaching the RatGDO to my computer using a USB cable and the ESPHome web page installer from Paul Wieland.
Again, I only used the ESPHome web page installer for the initial ESPHome firmware flash, and all of my updates and configurations past that have been through HA. I would expect that you could re-flash the RatGDO and set parameters through the ESPHome web page installer using a USB cable.
There are instructions there regarding the yaml.
The second is to upload the firmware file directly to the RatGDO onboard server, using the setting at the very bottom of that page. I have never done that.
The ESPhome web portal will not allow you to modify the firmware configuration. The only way to modify the configuration is to do it manually either with the ESPhome add-on in HA or by installing the ESPhome python library on a PC.
Well you can always run the full ESPhome as a separate docker container as well.
That's how I do it, because I don't like everything running inside my HAOS - too limiting for me, too hard to fix if things break.
I haven't touched the firmware on the ratgdo side since the initial deployment and I don't see any evidence that the native hubitat esphome/ratgdo drivers will do anything with regards to firmware on the actual ratgdo hardware itself. I have tried to go through the code changes ady624 made in the most recent release to try and find the source of the issue, but I haven't found anything that even remotely lines up with the error I am seeing. I am guessing it is in a call made by doParseEntity based on how quickly it errors. I see the attempt to connect to the ratgdo IP then an immediate error Cannot invoke method multiply() on null object. But, since the word 'multiply' doesn't exist anywhere in the esphome API library or ratgdo driver, I think what is happening is the driver is somehow making a mistake when passing an object to an underlying library. I am going to try and back out to the earlier version of esphome/ratgdo and see if that helps.
I reverted to the prior version of the esphome/ratgdo driver by copying the older code from here:
Add ratGDO driver · bradsjm/hubitat-public@6015892 · GitHub
And pasting it in over the top of the new version installed by HPM. That fixed my issue.
Did you revert the library or the driver? If only the driver, then the driver has an issue, please let me know so I can fix it. Afaik I have NOT used the multiply() function in the ratGDO driver, so it may be an error surfacing in a lib method.
Thank you
I only reverted the driver to start with, and that fixed it. I also posted an issue in the github to make sure it was tracked, Mr Bradshaw has already replied to that issue with this:
"Thanks, looks like when @ady624 did some refactoring the null checks were removed for some reason. I've added a null check for message.position back to hopefully fix your problem."
I haven't tried the fix yet from him, but will do so as soon as I get a chance.
I sincerely appreciate the help on this!
The fix by Mr Bradshaw worked for me, I am back in business. I appreciate the replies!
oh boy, I fumbled. Funnily enough, am using the same code and eez workingz for meez 
Sorry about that and thank you for reporting it as well as to @jonathanb who seems to have fixed it. Thank you!