Neglected might the the correct word.
First of all, your lock is not supported. There is an old KeyMatic device, which is supported. That’s why the lock-platform is available.
The new lock however has some technical changes, which make it impossible to support with the current underlying library (pyhomematic). Other devices that are broken because of the changes eq3 made are especially cover-devices.
That’s why I started a new project to replace pyhomematic. Here I asked for help. But so far the primary response I got was “I can help testing”. But in this early stage I actually need help from someone who can code in Python to do some work. However, either HomeMatic users typically can’t code in Python, or they don’t want to. And I refuse to continue as a single maintainer. Hence there currently is no progress.
The new integration ideally would provide entities and configuration from UI. So pretty much everything you see with other modern integrations. All it takes to bring this forward would be coders who would help with the development.
Regarding your specific problems (apart from the lock):
- Devices with just buttons don’t create entities, as mentioned here. So depending on your device that might be what you’re running into
- Thermostats should be supported fairly well. I have not yet heard complaints of them not working at all. Only some specific feature might not be working.
So to me it seems as if it’s working. I don’t know why the thermostats don’t show valid values though. That’s not normal. And I don’t know how the group-stuff is with the add-on. I know for sure they are working when you are using a real CCU.
For some things to work you actually have to specify a valid user on the CCU (the add-on where you are paring the devices) and use that in the configuration on the HA-side. Maybe that would get some things fixed.