LZW30-SN Firmware and Quality Question

Yeah, this is strange. We’re checking with the engineer tonight. Quite possibly they just named 1.19 to 1.20 for certification, but that seems strange that they didn’t tell us.

I’m also wondering who put that barcode over the top of the logo on the box. Is that how it came to you? I’m guessing so because that’s an Amazon barcode. However, we print our own on the back of the box. Just makes me curious why they did that.

We haven’t had any issues with counterfeiting, so I’m not as concerned there. We did have a large scale fraud operation against us where a ring of people used stolen credit cards to purchase our Black Series switches (Secret Service is involved) but nothing with the Red Series. I’m creating a separate post about that shortly.

I can tell this is new packaging (red dot over the “i” – whereas our old packaging it was black), however, so I doubt this was a used item as those shipments just arrived. I will address the QC issue with the team around the plastic screw holder missing.

Date code is located on the front of the switch at the top left (should be a series of four numbers – my guess would be 0820 or 0920).

Thanks for bringing this up – we have a call with the manufacturer tonight and I’ll shoot them a PM as well to see.

I also ordered some LZW30-SN’s from Amazon that have 1.20 firmware (ordered 9/6, received 9/9, installed 9/12). Same barcode label on my boxes as well. Were you able to find anything in regard to 1.19 vs 1.20?

Thanks for bringing this thread back up, I knew there was one I needed to respond to.

Good news is 1.20 is what was put on there. We talked to the engineer and he said he made a slight tweak (would’ve been nice to know!)

Basically it was a bug that allowed the factory to determine whether a devices Z-Wave IC is good or not good during testing. So, not a consumer facing bug.

3 Likes

Thanks for getting back to us. It really is the difference between other manufacturers (especially massive ones like GE and Leviton who I don’t think I have ever received a response for, for anything, none smarthome related inquiries) and yourselves.

3 Likes

I was just raving to my wife about this; transparency and communication is so refreshing. This is how loyal customers are made :slight_smile:

4 Likes

Is this screenshot from a document that is customer-facing? I’d LOVE to get my hands on firmware change logs to understand what is going on.

For example, that specific screenshot tells me how I can have the switch go to “white” from WebCore wheras when I do setColor to White in WebCore it goes to Red.

1 Like

I agree. Release Notes like this are helpful. The only thing to add for Inovelli is to note “Not Released” for the ones that never hit the public streets.

@EricM_Inovelli – when you get a chance, can you update the KB articles with the change-logs?

Agree – no, this was an internal document from the manufacturer. We had no clue they updated to 1.20 which was appalling. When we asked, this is what they sent us.

What do you mean by this? Like, “here’s what we were working on, but we didn’t release it?”

1 Like

I think he means if there was a release that didn’t pass Beta, or was skipped, then maybe say Firmware 1.19.1 - Skipped, New Firmware 1.20…maybe so that the average person doesn’t assume they’re missing a firmware? Possibly?

1 Like

Yeah. Many companies have firmware that was never released…as in Public Release are are internal only. Though they still often have fixes that are important but do not affect large numbers of users or had a short shelf life in testing etc before another release. All the notes are important though for all releases, my point was just to list them all and to avoid questions as to why nobody was informed or cannot find files or info on a previous release, just mark it as not released in some way. Dunno haha. Just my opinion in the way I like to receive release notes for the software and firmware stuff I deal with every day at work.

1 Like

@kreene1987 @Eric_Inovelli The release notes are always in the KB article for the firmware version. For example, the KB article for firmware 1.19 mentions the addition of parameter 51 and the change to parameter 5 that makes the LED white.

@EricM_Inovelli I see 1.21 on http://files.inovelli.com/firmware/LZW30-SN/Beta/ Can you post a KB article on the new firmware? You can’t sneak anything by us. :rofl:

2 Likes

LOL! Sneaky sneaky! I just noticed the 1.20 that came on my new switches and had a “wait… I don’t remember that one” moment. Then found 1.21 when I looked at the firmware files as well. We need a change log! :thinking: :stuck_out_tongue_winking_eye:

1 Like

Now to add another wrench to the works… the same switches that were reporting 1.20 under smartthings are reporting 1.47 under Hubitat. I just switched over the other day, so I am still learning Hubitat.

I’m guessing this may be a red dimmer and not red on/off.

Yes, I have about 10 of the Red Series 2 dimmers and 1 Red Series switch.

On openHAB 3.0, I can confirm the LZW30 black series on/off switch is reporting 1.21 firmware. I got a 10-pack of these switches a few days ago, and it has a 0820 date code on them.

1 Like

heh, there’s now a 1.22 beta for these as well; curious to see the release notes for the past couple betas!

1 Like

It was for Home Assistant users.

1.22 Fixed the bug that the V1 version of Protection Set Command will cause RF state of Protection to not work correctly.

1 Like