I had problems with my database size too. It grew to over 25 GB in a mater of days. I went and disabled 67 entities and hid 34 for each switch. I also, went into the recorder and excluded pretty much all of the entities from it.
Each switch has over 100 entities. Inside of each entities attributes each a duplicate of 75 other entities. One of those entities is the current power. So every time the power usage changes, which can happen very often, then all the entities update.
I think the attributes should be removed from all the entities except for maybe the main light entity.
That’s exactly my story, even the 25GB part. I’ve disabled a ton of stuff in the recorder exclusions since to slow the bleed.
As far as logs, I just used this SQLite query to sort by biggest offender and it’s all the Inovelli stuff crushing everything else.
COUNT(*) AS cnt,
COUNT(*) * 100 / (SELECT COUNT(*) FROM states) AS cnt_pct,
SUM(LENGTH(attributes)) AS bytes,
SUM(LENGTH(attributes)) * 100 / (SELECT SUM(LENGTH(attributes)) FROM states) AS bytes_pct,
GROUP BY entity_id
ORDER BY cnt DESC
Here is a sample of the DB size growth where you can see where I’ve excluded most entities from the recorder. I’ve left just the main light and power sensor entities and they are what is causing the continued growth. I only have 2 of them so far but want to get more
Definitely agree on the notion of deduping all those attributes.
Also note the distinction between an “Off” notification and the “Clear” notification:
‘Off’ is an actual ‘effect’ to force the LED off when it might otherwise be on. It’s still considered to be an active notification. If it has a duration, the LED will turn off for the duration and then turn back on. IF it has an indefinite duration then that LED stays off until the notification is cleared
‘Clear’ is not an ‘effect’ but rather, it is the action to stop the notification. Typically this is used to stop (clear) a notification that was set with indefinte duration
Has anyone had any problems in Z2M where the update doesn’t show for some 2-in-1 dimmers? I was able to update 3 of my dimmers to 2.08, but one dimmer only updated to 2.07 and another didn’t find an update and is stuck at 2.00
Hoping for some help from the friendly community. Smarthings user here who recently purchased a Sonoff Zigbee dongle to update firmware on my Blues. Ventured into HA (what a learning curve…) for the first time and managed to get a blue switch paired and controlable through the zigbee stick on HA running on a virtual machine.
I am not clear on steps to update firmware though. I added code to the configuration.yaml following these intructions: Zigbee Home Automation - Home Assistant , and saved the latest Inovelli OTA file in it’s own folder on the HA. Am I missing something? Are there any easy to follow instructions for someone new to HA… thanks in advance.
Once you have added the update code to your config yaml file and you have restarted HA you simply wait for the update to happen. In my experience it starts very quickly within a few minutes of connecting the new switch.
You might not even notice it updating unless you’re watching the LED on the strip. Occasionally I have had one update and I only knew because the firmware version changed on the device page.
I paired my blue switch back to smartthings after having updated firmware using HA.
Now none of the routines involving scenes and button presses will trigger on that switch. I’ve confirmed the switch paired to smartthings as I can control though smarthings app and voice (Alexa) and it was rediscovered as the original device.
Any ideas? Routines all look good. Also it looks like it added back with the original settings on the app, ie… Dimmer mode, but the device itself seems to have all default settings (ie. Set to on/off mode) . Is there a way to “push” a refresh of settings from the hub to the switch on smartthings?
@sdbigio There is a “bind” command that is executed when the device is first added that needs to be ran again after the device has been factory reset. I’ll work on adding that to the driver as well as the ability to re-send the configuration options.