Can't provide live logs. The logs only stay on for 30 minutes. The error is generated from a process on Hubitat that appears to call the device. No error is generated when activating the device. The issue is internal to Hubitat in that whatever call is being made to the device, the parse method throws an error when it receives the request.
if you have zigbee ping enabled, is it enabled for these devices?, and if so can you disable it for them?
I don’t. It’s something else.
other than the ping, there is no other internal process on the hub that calls the device.
Mostly, but not always, anyway I know the logs are only on for 30 minutes, but you should be able to time it with the errors, that for the most part hit each device every hour.
Clicking save changes the repetitive error time. What ever causes it always occurs when the logs are off (minimum 30 minutes). Maybe it’s something internal that runs within the driver. It occurs the same as the other error that was fixed.
Are there any jobs scheduled in the driver details? They would show at the bottom...
No. Nothing.
Error occurs ~45 minutes after device save which exceeds the 30 minute timer.
I don't have one of these, but was able to order one.
I take that back, i do have one, it was at the bottom of the ST pile of boxed devices...
But its not a V4, its a V5...
Can you get a picture of one of these?
I can get you a picture. I have some v5’s, but they do not generate any errors.
That's a 2016 version (v2?). While I have a bunch of them, most aren't in use as I find they go through the CR2450s far too quickly.
I do have one connected to a C-7 (for testing). I too am using the SmartSense Multi Sensor V4 driver. I don't see any errors from it in the logs, however.
well I have 2017 version of that device made in China, not Mexico. model STS-MLT-250.
I'll give it a shot and see what it does on a C8.
1 Like
Did you figure it out?
Heck no, thanks for the poke, I have two NIB sts-mlt-250 units, factory reset multiple times and couldn't get them to join a C8 or a C7...
WTH
I didn't packet trace them, but its like they didn't bother channel scanning the active channels these hubs were using...
Never discovered...
I'll try again after things quiet down a little for me...
3 Likes
Any progress?
If you share the code I can fix the error on my end.
[dev:286](http://192.168.10.10/logs?tab=past&deviceId=286#)2023-07-28 03:50:00.359 PM[debug](http://192.168.10.10/logs?tab=past&deviceId=286#)handleAcceleration: [raw:243301FC020810001800, dni:2433, endpoint:01, cluster:FC02, size:08, attrId:0010, encoding:18, command:0A, value:00, clusterInt:64514, attrInt:16]
[dev:286](http://192.168.10.10/logs?tab=past&deviceId=286#)2023-07-28 03:50:00.356 PM[debug](http://192.168.10.10/logs?tab=past&deviceId=286#)parse: read attr - raw: 243301FC020810001800, dni: 2433, endpoint: 01, cluster: FC02, size: 08, attrId: 0010, encoding: 18, command: 0A, value: 00
[dev:286](http://192.168.10.10/logs?tab=past&deviceId=286#)2023-07-28 03:49:54.407 PM[error](http://192.168.10.10/logs?tab=past&deviceId=286#)java.lang.NumberFormatException: signum-magnitude mismatch on line 310 (method parse)
[dev:286](http://192.168.10.10/logs?tab=past&deviceId=286#)2023-07-28 03:49:54.372 PM[debug](http://192.168.10.10/logs?tab=past&deviceId=286#)handleAcceleration: [raw:243301FC02141200292E001400292C00, dni:2433, endpoint:01, cluster:FC02, size:14, attrId:0012, encoding:29, command:0A, value:002E, clusterInt:64514, attrInt:18, additionalAttrs:[[value:002C, encoding:29, attrId:0014, consumedBytes:5, attrInt:20]]]
[dev:286](http://192.168.10.10/logs?tab=past&deviceId=286#)2023-07-28 03:49:54.369 PM[debug](http://192.168.10.10/logs?tab=past&deviceId=286#)parse: read attr - raw: 243301FC02141200292E001400292C00, dni: 2433, endpoint: 01, cluster: FC02, size: 14, attrId: 0012, encoding: 29, command: 0A, value: 2E001400292C00
[dev:286](http://192.168.10.10/logs?tab=past&deviceId=286#)2023-07-28 02:49:59.334 PM[debug](http://192.168.10.10/logs?tab=past&deviceId=286#)handleAcceleration: [raw:243301FC020810001800, dni:2433, endpoint:01, cluster:FC02, size:08, attrId:0010, encoding:18, command:0A, value:00, clusterInt:64514, attrInt:16]
[dev:286](http://192.168.10.10/logs?tab=past&deviceId=286#)2023-07-28 02:49:59.332 PM[debug](http://192.168.10.10/logs?tab=past&deviceId=286#)parse: read attr - raw: 243301FC020810001800, dni: 2433, endpoint: 01, cluster: FC02, size: 08, attrId: 0010, encoding: 18, command: 0A, value: 00
[dev:286](http://192.168.10.10/logs?tab=past&deviceId=286#)2023-07-28 02:49:53.389 PM[error](http://192.168.10.10/logs?tab=past&deviceId=286#)java.lang.NumberFormatException: signum-magnitude mismatch on line 310 (method parse)
[dev:286](http://192.168.10.10/logs?tab=past&deviceId=286#)2023-07-28 02:49:53.354 PM[debug](http://192.168.10.10/logs?tab=past&deviceId=286#)handleAcceleration: [raw:243301FC02141200292E001400292C00, dni:2433, endpoint:01, cluster:FC02, size:14, attrId:0012, encoding:29, command:0A, value:002E, clusterInt:64514, attrInt:18, additionalAttrs:[[value:002C, encoding:29, attrId:0014, consumedBytes:5, attrInt:20]]]
[dev:286](http://192.168.10.10/logs?tab=past&deviceId=286#)2023-07-28 02:49:53.350 PM[debug](http://192.168.10.10/logs?tab=past&deviceId=286#)parse: read attr - raw: 243301FC02141200292E001400292C00, dni: 2433, endpoint: 01, cluster: FC02, size: 14, attrId: 0012, encoding: 29, command: 0A, value: 2E001400292C00
1 Like
Did you find anything?
Yes, it will be fixed in the first 2.3.6 release
2 Likes
