#HomeSeer HSM200 Firmware Update

1 messages · Page 1 of 1 (latest)

stray hazel
#

has anyone had any luck updating firmware on a HomeSeer HSM200 motion detector? I keep getting
"INFO Z-WAVE: Failed to start the update: A manual authentication event (e.g. button push) was expected! (ZW1503) updateFirmware undefined"

and then if I try again I get
"INFO Z-WAVE: Failed to start the update: A firmware upgrade is already in progress! (ZW1500) updateFirmware undefined"

I can exclude and reinclude and try again, but then I get the first message. I've tried clicking "OK" in Z-Wave JS then immediately pressing the button on the sensor, and also the other way around. One time I did get the firmware update to start, it got to about 50%, then failed. haven't been able to get it to start the update since. is there some super secret sequence I'm not using??

EDIT: using ABORT firmware update doesn't seem to be acknowledged by the sensor

proper latch
#

should be explained in the device manual. The first error comes from the device. Doesn't tell us more than you already know

stray hazel
#

the documentation is ... not great, and assumes you're using HomeSeer software only:
a) Go to your Device Management page (or click Home) and click on the Root device for your HSM200.
b) Click on the Z-Wave tab at the top to go to the Z-Wave Device control page.
c) In the Firmware Update section, click Select File and select the HSM200 Firmware upgrade file.
d) Let the upgrade procedure finish before leaving the page.

proper latch
#

The second error is a bug in node-zwave-js AFAIK, but I'm on parental leave until April, so you'll have to restart zwave-js when that happens

proper latch
stray hazel
#

I'm on parental leave as well -- congrats!!

proper latch
#

You could ask HomeSeer support. They actually use zwave-js now, so maybe they can help.

south surge
#

what firmware version are you upgrading from and to? is it included with or w/o security?

stray hazel
#

from 2.3 to 2.8'

#

included with security

south surge
#

could try w/o, see if it makes a difference.

stray hazel
#

let me try without security see if that changes anything? ... in related news, the QR code on the device decodes to an invalid string according to HA 🙄

#

no change using no security - tried starting firmware then pressing button, and pressing button then starting firmware

#

I'll reach out to HomeSeer support see what they say. if I get something useful, I'll post it here for posterity. thanks for the quick responses!

stray hazel
#

Well for those landing here in the future... I finally got the firmware to update, but I'm not sure what change made it possible. I rebuilt my HA dev box starting with a fresh 11.3 img, updated everything fully as of Jan 10, 2024 including Z-Wave JS. I factory reset my Zooz 800 Z-Wave stick before installing HA on my RPi 3. I included only the HSM200, started the firmware upgrade process, and pressed the button on the side of the sensor once and then IMMEDIATELY clicked "OK" to load the firmware. it was slow and had a lot of hiccups (despite the controller only being about 3 feet from the sensor) but it finally finished. After updating the firmware, the sensor never came back online and completed an interview, so I had to exclude it and include it and then it went through a few hiccups, completed the interview, and it's online.

related thoughts: I'm pretty disappointed in the polish of this sensor given the high price of ~$60 USD. the QR code on the side of the device is not a valid DSK. it contains invalid characters. You have to manually type the DSK string into SMART START and then it will work. the minimum latch time for the motion sensor is 1 minute. I get this for battery devices to limit oscillating, but a powered device should have more flexibility. updating the firmware is a nightmare, though this is a bit of a corner case. being able to control the LED color is 99% of what I wanted this for, but HA doesn't have a great implementation of this out of the box. the SmartThings edge driver absolutely nailed this, but I'm ditching ST completely, so I'll have to work with the HA folks to see how we can improve this.

south surge
#

what's the problem with the LED control?

stray hazel
#

by default, the RGB entity is created as a "light" entity, which has an on/off - and when you click it you get an RGB color wheel with 8 "favorite" colors below. the 8 preselected colors aren't supported (only Red, Green, Blue, Magenta, Cyan, Yellow, White are supported). picking a color on teh wheel does send the RGB value ot the device, but getting exactly FF0000 or 00FF00 etc is extraordinarily difficult. not sure if the 8 favorites below are configurable

#

and the on/off doesn't turn the rgb on or off -- which is i suppose a bit to be expected. "off" is sent as #000000

south surge
#

light would be the appropriate domain

#

there's no off

#

for that RGB, unless you know how

stray hazel
#

I am able to change color using this script:
alias: LED Blue
sequence:

  • service: zwave_js.set_value
    metadata: {}
    data:
    command_class: "51"
    property: hexColor
    value: "#0000FF"
    target:
    device_id: 123456789
    mode: single
    icon: mdi:octagon
south surge
#

the LED is only controlled by the color CC, which doesn't support any kind of off or on

stray hazel
#

oh interesting... i had to cycle the "on/off" and dimmer a few times on the default HA card, and now it does cycle the LED on and off

#

any idea how I can configure the 8 preset color buttons at the bottom of the light card?

south surge
stray hazel
#

thanks for the help - really appreciate it!

#

aha -- to change favorite colors, long press on one and the card will go into edit mode 💡

south surge
#

cool

#

with such limited colors available, maybe a select entity would have been better

#

but I guess light is more "correct"

stray hazel
#

yea, the dimmer is misleading since it cant be dimmed

south surge
#

is the UI providing a brightness control?

#

or do you just mean the other RGB values

stray hazel
#

the UI is providing a brightness control, let me see if i can link a pic

south surge
#

Ok, that's a core thing

#

RGB implies brightness, apparently

stray hazel
#

interesting. not sure if "HomeSeer HSM-200 v1" implies hardware revision 1, or just that it's v1 of that code in discovery.py - but I'm using hardware revision 2

#

i don't know all the differences off hand, but v2 has a tab at the top that allows you to screw it in, and it takes a different firmware file

south surge
#

The V1 version of this sensor does not have the Multilevel Switch CC but does have a Color Switch CC where setting the light to black turns it off.

#

Doesn't sound like your V2 behaves any differently?

stray hazel
#

let me poke around see if i can find something in their docs

south surge
#

the doc from their site said it is controlled by Color Switch CC

stray hazel
#

that's still correct

#

looks like hardware v2 adds:
Initial release using Sigma SDK 6.81.00 which adds security S2 and SmartStart. | Configuration Command Class upgraded to V3 so the parameter names and information can be obtained directly from the device without the need for custom programming. | Multilevel Switch command class was added as required for support of the Color Command class for the color LED. | Multilevel Switch doesn’t dim the LED, it only turns it on/off. (11/30/17)

south surge
#

Interesting, maybe you are just using the default light class

#

Can you attach the device diagnostic?

stray hazel
#

what i'm seeing is what HA added to the "Overview" dashboard automatically

south surge
#

that would happen either way

stray hazel
#

do you mean the Z-Wave JS UI > Debug Info?

south surge
#

no, HA device page, ..., download diagnostic

#

mostly same info

stray hazel
#

preferred paste site?

south surge
#

you can attach here if you want, otherwise I don't care

stray hazel
south surge
#

Hmm, thought anyone could now. Oh well.

#

light.dining_room_motion_sensor is your RGB?

stray hazel
#

yes - that's what HA created

south surge
#

ok, that explains it then

#

HA has no way to know that multilevel switch doesn't dim.

#

That's its entire point of existence

#

Seems that might have been accounted for in the v1 implementation

#

they could have used Binary Switch instead to achieve that (although HA doesn't support it).

stray hazel
#

based on "Multilevel Switch command class was added as required for support of the Color Command class for the color LED. " it sounds like binary switch may not have allowed CC Class?

south surge
stray hazel
#

well then.

south surge
#

I often find the spec docs to be pretty ambiguous, but that one seems clear.

stray hazel
#

LOL. i'm not a developer and that makes sense to me

south surge
#

Dunno, maybe an older version of the doc didn't include it

stray hazel
#

is this something we could override in HA, like in the discovery.py to say for HSM-200 devices yea it's a multilevel, but treat it like a binary?

south surge
#

You'd have to figure out some technique to omit brightness. Currently doesn't exist.

stray hazel
#

OK. now that I understand how it works and what doesn't work - it doesn't bother me too much. I just see a handful of similar topics of others struggling with this device

#

figured maybe this thread might come in handy for someone in the future

#

semi-related question: the QR on the device. scanning it with HA says it contains invalid characters. the QR decodes to:
90013844000330785389803125563058081451257447428193180010017930C0702200031000400010202
which is 5 characters shorter than most of my Zooz devices

south surge
#

Depending on how old those topics are, could be pre-"black is off" addition

proper latch
#

Just scrolled through here. The device uses color switch cc + binary switch cc for brightness. HA supports only the combination of color + multilevel switch.
I'm sure there is an existing issue for it, maybe even from me

#

There are other devices using this combination, so it's a valid use case.

#

For example the LogicGroup Matrix Scene Controller, where you can change color of LEDS and turn them on/off

south surge
#

According to the dump posted above, the device supports Multilevel Switch CC

proper latch
#

Hmm

#

I thought it's the same as I have. Maybe not

south surge
#

The Logic Group device is complicated because Binary Switch CC has different meaning depending on config parameters

#

Maybe that's OK though

#

Same with LED indicators, controlled by config. So light entity would not function correctly for the default config, and behave differently depending on config combinations.

proper latch
#

Oh I remember... The issue was that there are/were? no color controls when there's no multilevel switch.