Thanks Andrew, this is some great info. You might consider having the documentation owner add something on configure in the “Building ZigBee Device-Type” documentation section. Thanks for pointing out the enroll is also in the parse()
function. That makes a lot of sense now.
So I have tried adding binding in the configure() function, just for my Occupancy Sensor (0x406) cluster. But this gave me a few other questions:
- If
configure()
is only called once at pairing then how will myzdo bind
commands ever get called if the device doesn’t have a fingerprint that is found properly by ST? Can I forceconfigure()
to get called again somehow? Or should I add thezdo bind
commands to something I can force call likerefresh()
? - I have a log message in my
refresh()
function, and I see the tile on the main UX and it allows me to press it like a button. All great. But I never see thelog.debug
message happen in “live logging”. I do see my device in the “my devices” area, and it even shows “ACTIVE” when I power up the zigbee NXP module. So I think that all means good things about ST communicating with my NXP module. And anyway even if the module isn’t configured totally right for binding etc, shouldn’t I see thelog.debug
fire in the refresh() function since that’s all just ST smart app and hub side of things?
Let me know if you want me to paste my device type code here.
Thanks in advance for any info/ideas you can share.
NOTE: I tried the refresh()
command that’s part of the original SmartSense Motion/Temp Sensor I used as reference for a ZigBee device type, and it’s log.debug works great to live to “live logging” every time I press it.
NOTE2: Some of my reply here is specific to my other thread Trying to use NXP(Jennic) zigbee module (JN5168-001-M00) as a basic sensor:
Justin