I arrived at this thread having the same problem, and I’ve fixed it. This is because Open ZWave has only recently (5 months ago) added support for this device. The commit is here:
pip install --upgrade python-openzwave did not cause the ge/46203-dimmer.xml file to appear, as I guess the python project lags the main project by some significant margin. I successfully fixed this problem by manually inserting the XML into openzwave:
- I took the 46203-dimmer.xml file that appears in the commit linked above, put it in /srv/homeassistant/lib/python3.7/site-packages/python_openzwave/ozw_config/ge/
- Added that one line change from manufacter_specific.xml in the linked commit to the GE section of my manufacturer_specific.xml at /srv/homeassistant/lib/python3.7/site-packages/python_openzwave/ozw_config/
- Stopped homeassistant
- Deleted the entire Node entry for this device in ozw_xxxxx.cfg
- Started homeassistant again
- Not sure if I actually had to “Refresh Node”, “Print Node”, or “Heal Node” but did all those things
- Restart homeassistant again
At that point it showed up as the correct device name, was controllable, and had a few options for changing dimming parameters, led mode, switch handling, etc.
Presumably these changes in Open ZWave will propagate to the project that homeassistant depends on in the not too distant future and none of this will be necessary anymore, but this technique is applicable for any new hardware that has been added to OZW recently.