Correct. Saving preferences is what queues up configuration, associations, and the version report request for the device on the next wake up. So if you don't save preferences it will never ask for the version report, no matter how are you wake the device.
@JasonJoel have noticed a couple of minor issues with this driver. I was having problems getting the version report to come back even when doing a save and wake up manually so I checked the code. I decided to move the status battery and version checks to the top and the wakeup interval setting as last. I also set the delay to 400 which I have had better luck with on other devices. Not sure which of those things did the trick but it worked perfectly after that and all 'gets' came back.
Also I have noticed the info in the Device Info boxes gets ghosted behind the actual text, but only when using your driver. Not sure if there is a weird character in the parameters or somewhere that is breaking the web interface of Hubitat or what is going on? I peeked through the code and nothing jumped out to me as out of place so not sure what is doing it.
Interesting. The version report returned on all 20 of my devices with the as-is driver. But I'm not against re-arranging it, so I'll do that in the next version. Realistically I shouldn't be setting the wakeup interval every wakeup with data anyway, as that is a one time config thing. Maybe I'll change that around, too.
Yup, I see that too. Don't know why. Any thoughts @bcopeland or @gopher.ny (see pic in post above this one with the text ghosting).
1.2.0 (09/21/2021) - Moved wakeup interval setting to the end of updates, and changed delay from 300 to 500ms to try and make updating the config more reliable.
Mine was from Windows 10, Chrome, should be current-ish version. Also just tried on Edge which just updated this week so it is current as well but also Chome-based.