Blue Series SmartThings Edge Changelog | VZM31-SN, VZM35-SN

[sdbigio]

@EricM_Inovelli Yes exactly. I just deleted a switch and re-added and that seems to have forced the driver to show the new fields for that particular device. But that results in all programming and routines being deleted so not really sustainable to do multiple times. Also makes the resending Config Option sort of pointless since you have to create a brand new device.

Are you seeing the same behaviour?

[Bry]

@sdbigio

But that results in all programming and routines being deleted so not really sustainable to do multiple times.

If you are going to remove a device that is included in a Routine, create a placeholder virtual device and insert that into the Routine before deleting the “real” device. Since the Routine will still have a device associated with it, it won’t get deleted.

[sdbigio]

Great workaround. TY. Though still laborious if you have many routines. I guess I’m just wondering why this edge driver release requires deleting devices fully first before re adding in order to get access to new features from 2.14. Prior driver updates seem to push automatically and new fields would just show up. Is this a bug…maybe?

[EricM_Inovelli]

Honestly I think this might be something to ask ST support. I guess you could install the smartthings-cli tool and check the logs on the hub to see if anything strange is happening. It isn’t something that I have seen, but it seems like the app isn’t refreshing the options in the settings page even though they have been updated. It also might be just a matter of waiting . . . or clearing cache (and or data) from the ST app and trying again.

[sdbigio]

@EricM_Inovelli, just wanted to flag what @mamber describes as a scaling issue, assuming it might need a driver fix. TY

Blue Series 2-1 Firmware Changelog | VZM31-SN

Interesting. Good catch. For smartthings, I am on the latest driver and don’t see reference to a scaling fix in the update log. I’m assuming that means I should let @EricM_Inovelli know that there might be some sort of a scaling issue in the driver? For Smartthings as far as I know, Inovelli has to update the driver and push it out.

[Eric_Inovelli]

@sdbigio

Sorry, tried to find reference to this but what is single Notification capability?

Just wanted to circle back on this one – I believe this is the ability to mimic our Gen 2 On/Off switches which had a single LED (instead of the long bar like the dimmer had).

[EricM_Inovelli]

April 25, 2023

• Fix scaling issue for param 55 & 56.

[sdbigio]

TY. Seems to work perfectly now.

[EricM_Inovelli]

January 17, 2024

• Adding settings options for firmware 2.17+ of VZM31-SN & firmware 1.05+ of VZM35-SN. See Blue Series Fan Switch Firmware Changelog | VZM35-SN - Switches / Firmware Discussion - Inovelli Community

[justinlindh]

Adding settings options for firmware 2.17+ of VZM31-SN

Where can I find the 2.17 firmware? I didn’t see it on the GitHub. I’d be happy to beta test it out!

[EricM_Inovelli]

It is still in testing, but I will post when it is ready to go!

[SamJWard]

@EricM_Inovelli @Eric_Inovelli
2.17 firmware has a few issues.

Current issues:
-Losing connection between switches in a group. (Did not happen on 2.15)
-Dimming speeds are inverted or random in a two-switch or more binding. (Did not happen on 2.15)

P.S. I think the lost connection is due to the dimming issue with them not being synchronized anymore.

[EricM_Inovelli]

Can you please try a factory reset? There may be corrupt configuration data with all of the configuration option additions. I’m a little confused on the first issue. What is the behavior you are seeing in the group?

[SamJWard]

I did a factory reset as well as wipe it out entirely and re-pair. Same issue. Connection issue isn’t really a connection issue. The dimming speeds aren’t matching the settings. For example, I have it set to turn the light on fast, but dim slower when turning it off. It’s doing the opposite, and randomly, it’ll do both fast or both slow. When this happens, both switches freeze and stop responding for 1 minute or so.

I don’t think it’s a connection issue, it’s a programming issue where something is going wrong in the firmware and it’s waiting for something to happen or something is crashing.

Thus far though, the dimming speeds don’t match and that’s the most obvious problem.

[Eric_Inovelli]

Hey can you share what you have the parameters set to so I can try to replicate it?

[SamJWard]

On both switches I have the same settings.

dimmingSpeedUpRemote - 10
dimmingSpeedDownRemote - 25
dimmingSpeedDownLocal - 25
rampRateOnToOffRemote - 25
rampRateOnToOffLocal - 25

Everything else as far as dimming goes is default.

[Bry]

@Eric_Inovelli

what you have the parameters set

@SamJWard

On both switches I have the same settings.

This is a SmartThings thread and I THINK @SamJWard is on HA/Hubitat. On which hub are you seeing the adverse behavior?

So if @Eric_Inovelli tests on SmartThings, that may not have the same behavior as it would under HA or Hubitat.

[Eric_Inovelli]

Yes, this does not appear to be a SmartThings issue – I just tested it and everything works as intended. Let’s keep this in a Home Assistant or whatever you’re using @SamJWard thread (if there isn’t one, would you mind creating one?)

[EricM_Inovelli]

Going to cross post this here in case anyone is interested. We are certifying some drivers with ST and hoping to have a few people test them since I had to make several changes to them:

SmartThings Edge WWST Drivers - So Hot Right Now - Inovelli Community