Update device documentation (zigbee-herdsman-converters 19.62.0) #900
Conversation
![itavero-s-helping-cat[bot]](https://avatars.githubusercontent.com/in/936165?s=60&v=4){kind=small}
test/exposes/bosch/bmct-slz.json
Outdated
There was a problem hiding this comment.
@burmistrzak I think you added this file in #854. It seems that the output from Zigbee2MQTT changed quite a bit, did you expect this to happen? Is there another device that does still have the exposes information we need or can we have this fixed in Zigbee2MQTT?
There was a problem hiding this comment.
@itavero Well, this is a super weird edge case, because the BMCT-SLZ changes its exposes based on the configured mode after pairing, either light or shutter.
The JSON that I've added is from a device in shutter mode.
So when a BMCT-SLZ isn't configured yet, you'll just get the device_mode, and nothing else until you select a mode. The device mode can't be changed afterwards, unless you reset the entire thing.
AFAIK, there's no clear guidance on how to handle such devices in the docs.
There was a problem hiding this comment.
I see. Wasn't aware of that. I'll see if I can somehow mimic that behavior in the documentation generator, or if I'll just move this file to a location where it will not be automatically updated.
itavero-s-helping-cat
bot
force-pushed
the
update-device-docs
branch
from
d069855
to
ca06bb2
Compare
itavero
force-pushed
the
update-device-docs
branch
3 times, most recently
from
133eb3d
to
d711985
Compare
itavero
force-pushed
the
update-device-docs
branch
from
d711985
to
200540c
Compare
|
|
🆗 Published SonarCloud and code coverage data. |
Documentation has been automatically regenerated, because a new version of 🐝 Zigbee2MQTT and/or zigbee-herdsman-converters
was detected or because a forced update was requested.
Based on:
🤖 I am a bot. This action was performed automatically.