I bought a few more Smartwings levitate shades with zwave motor. Using the day/night cellular shade driver. I noticed when I started charging a few to full, I got a warning on the shades for unhandled zwave event (see below). Went away shortly so i let it go.
Last night i charged 3 of these shades (2 connected to hubitat), and forgot to unplug from charging overnight. I'm pretty sure the unhandled zwave event error is when the shade is fully charged, it keep logging all night long and jammed the zwave network a couple times. When I unplugged the shades from the charger, all went back to normal and no more warnings.
First off, wont leave it over night again. Is there an issue with the driver? oddly only 1 of the 2 shades spammed the hub last night, but did see the same warning when I charged other shades 2 days ago to full. Anyone else had this experience?
Seems strange that the device sends so many battery charged events... but they are least a few seconds apart. That doesn't seem like too much to cause a jam, but the logs make it look that way. Are there any other Zwave devices that could be contributing to the jam traffic, and this just puts it over the edge?
You would want to watch the live Zwave logs, the ones you get to from the Zwave settings page. Devices can be spamming your network, but the driver won't necessarily report it in the device logs like the shades are doing. As device messages populate in the Zwave log, click on different devices to see if something looks off, like constant logging filling the log screen from some other device.
Maybe the shade events alone are causing the jam, it is just hard to say. How long do those logs go on for before the status changes to jammed? If you don't unplug the shades, do the charge event logs start populating warnings again until another jam happens?
Regardless, the Smartwings driver is apparently handling that event message, but it is not acting on the charged message itself to do anything, and it is letting you know with the log warning, so it is not like you are getting unhandled exceptions (red errors) from the driver. Seems like it should just handle that event though, maybe with an attribute that shows charging state, but maybe there are reasons for why it can't.
The bigger issue is why this is jamming Zwave, assuming this is normal behavior from the shades to do this when it gets to full charge.
Hi- there were no other logs overnight for any other device, when I looked at zwave logs in settings, nothing was there. it only jammed 2-3 times overnight for ~1.5mins, then was fine.
it went on all night long from 9pm until 5am, almost have 15 seconds...
anyways, its fine since I unplugged it from charging. Today I actually zwave excluded the device and will add back via LR.
Also on Zwave JS, not sure if that makes a difference.
