THREAD DIVERSION POINT - My posts in this thread, and replies to them, from this point on - relay the story of discovering that a INNR 244 device accepted an inappropriate version of firmware that didn't totally brick the device but "zombied" it. Zigbee communications were still intact but the plug's handling of commands was kaput. What caused and allowed this to happen has been resolved through all involved channels.
Conclusion here: INNR 242 turns off and on due to power spikes - #67 by PunchCardPgmr
Updated, kinda surprised by versioning number difference, like not even slightly the same. Haven't finished trying to shake things up to get this to respond but initially...while the logs act like it's going through the motions of Configure, I am not able to control the outlet.
here's what was there before loading new-
softwareBuild: 1.4.3
here's what is there now after loading new-
softwareBuild: 17173685
and the log got to this point-
manufacturer:innr, imageFileName:1166-0333-17173685, fileVersion:17173685] is 100% complete.
Log entry since:
descMap:[raw:catchall: 0000 0013 00 00 0040 00 3DBB 00 00 0000 00 00 00BB3D6451F203A638C1A48E, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:3DBB, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, BB, 3D, 64, 51, F2, 03, A6, 38, C1, A4, 8E]]
- endpointId: 01
- application: 14
- firmwareMT: 1166-0334-17173685
- inClusters: 0000,0003,0004,0005,0006,0008,1000,0702,0B04,E001
- manufacturer: innr
- model: SP 244
- outClusters: 000A,0019
- powerCluster: 0B04
- softwareBuild: 17173685
