Express Controls (HSM100) Unusual Behavior

Other Devices & Integrations Door Locks & Sensors
1

I have six express control devices integrated with Vera 2.0 running 1.1.1245 and z-wave 2.78 L:1 and I’ve recently started to notice some unusual behavior in the motion detection, lighting, and temperature updates. For example, and main device indicates tripped=1, while the motion detector associated with the device shows tripped=0.

Has anyone experience this behavior or has any advice on how to correct this?

2

Hi –

I also continue to have bizarre readings on my four hsm100 devices. They will stop working for a period of time (i.e., readings will not update for days). Light reading will be 0 during the day and 100% without any lights on a night. Temperature readings will be more than 10 degrees different for devices 15 feet away from each other. Replacing the batteries has no effect.

Running a network repair and re-configuring the nodes has only a temporary effect. These devices are extremely difficult to configure in comparison with previous firmware updates.

3

Hi,

I have same problem, only the Motion Sensor of the HSM-100 is working, temp and illumination do not.
I´m running Zwave 3.20 and firmware 1.1.1245, I did not migrate my configuration using the wiki “Migrate To Z-wave version 452”, just did a reset zwave network and made everything again.

Regards.

4

Try replacing with fresh batteries.

JOD.

5

Hi JOD –

I have been using the AAA Lithium batteries and have replaced them with each problem… BUT new batteries have had no effect. Thanks

      Don
6

Exact same issue here. Same version and all and the HSM 100 temperature and lighting numbers seem to update only when they want. I tried changing the poll to 360 and 1080 and it makes no difference. I waited several hours and they still show the same.

7

Do you mean the ‘[tt]Wakeup interval (seconds)[/tt]’ field, or something else?

(Note that the default wakeup interval is 1800 seconds; so you should be getting an update every 30 minutes.)

8

Yep, the “Wakeup interval (seconds)” under the settings of the 3 in 1 device.

So last night I wasn’t getting any response from the HSM 100. Vera just said “waiting for wakeup…”, which never occurred and my light and temp values never changed. So I did a reboot in Vera (Advanced → Net/Wifi → Reboot) and that did nothing. Vera still said “waiting for wakeup…”. I then came across this thread (http://forum.micasaverde.com/index.php?topic=4450.0) and pgrover516 mentioned he got some unresponsive ones to respond while doing a power cycle on the box.

So I unplugged my Vera, turned it back on and viola, the HSM 100 is now talking back to Vera and providing temperature and light numbers. (Huge thanks pgrover516!) Unfortunately though, the motion sensor is not tripping when I walk in front of it. Vera never shows it as being marked tripped so now to try and figure that out. sigh

9

Okay, so I just went outside and clicked the blue testing button on the HSM100 and the motion sensor is also now reporting back to Vera. I didn’t move Vera or the HSM100 closer to one another, I simply clicked the blue button and did some testing of motion. After it went out of testing mode, I tripped it and my scene (turn lights on) went off successfully. Additionally, the light and temperature readings continue to increase so it appears all 3 sensors are working (for now). I will share any other experiences I encounter.

10

Glad to hear youre back in business, by the way the blue button is not just “testing” it is also (importantly) “wakeup”, I really hope not to jinx myself here but on the 1245 firmware and the new zwave branch my HSM-100’s have been more reliable than ever, especially the temp and light readings which were the most problematic part before where the motion sensors were better but far from perfect in the past. I still have a few oddities though

  1. after changing batteries some will go back to full operation on their own and others will require a push of the “blue button” (on sensor) quickly followed by “configure node now” (on vera) to become responsive again. Be aware that after this process the sensor may seem unresponsive for 1 or 2 “wakeup cycles” but will eventually respond
  2. I have observed this phenomena all through different firmware versions and though it is rare in current version it still occurs, on the odd occasion one or another sensor will stop responding to motion for a temporary period but left alone will return to function, best I can tell if it lasts over an hour or so it will not return to function without intervention. This seems to happen more if I have been making changes. To complicate matters after making changes (especially using “save”) my dashboard will often partially choke and not update properly and sometimes not even carry out button presses correctly and I will have to close all browsers and reopen to get correct function (once I’ve had errant function I consider this more reliable than a “ctrl F5”) This has at times caused me to believe that sensors were not responding when in fact they were.
  3. I have also had the occasional “stuck tripped” sensor, which I am guessing is simply vera “missing” the untripped signal from the sensor, the good news is that this can be remidied by simply tripping the sensor again so vera will catch the next “untripped” signal, the bad news is if you are offsite by then you are stuck with it until you are onsite next. I dont know if it does any good but I have tried to remedy this by not doing any “intensive” commands while vera should be listening for the “untripped” signal. ex: my 7 HSM-100’s reset after 5 min of no motion, I have a scene when I am leaving the house which will turn off lights (turn on then off some lights),lock doors and after 15 min arm sensors. after having a couple “stuck tripped” sensor exits from home I changed the scene to issue minimal commands until after my 15 min rearm sensors command (turning on just the lights needed for exit) so vera will not be busy (and miss signal)as the 7 sensors randomly “untrip” (ex: for locks, “unchanged and after 20 min lock” rather than just locking upon exit) , all other routine turn off light and especially “lock door” commands come after this (15 min in my case) time frame (locks seem to be especially work intensive for vera, I assume due to the encrypted communication) This is of course not scientific but I havn’t had the issue since making this change
11

Wow, invaluable information. Thanks for taking the time to share all that!!

Per your #1, I was not aware that the blue button also serves as a “wakeup” and absolutely did not know how or when to use the “configure node now” under the settings of the devices. When you perform the configure node now, do you do it ONLY on the 3 in 1 device in Vera or the individual sensors themselves that may not be working?

12

[quote=“SunnysGlimpse, post:11, topic:168542”]Wow, invaluable information. Thanks for taking the time to share all that!!

Per your #1, I was not aware that the blue button also serves as a “wakeup” and absolutely did not know how or when to use the “configure node now” under the settings of the devices. When you perform the configure node now, do you do it ONLY on the 3 in 1 device in Vera or the individual sensors themselves that may not be working?[/quote]
Only on the parent 3-in-1 device, in fact trying to change anything on the “child” devices can create problems

13

Interesting behavior that I noticed recently while trying to “heal” my HSM100’s with “unusual behavior”:
Despite documentation that states that the blue button puts the device into wakeup / test mode for ten minutes:
I find that when the GUI has that “Waiting for device to wake up” tag on it I press the blue button to get it (Vera / GUI) to see the device and do what it needed to. A minute or so later (certainly a lot less than 10 minutes) during a Heal the same “waiting” tag comes up and I have to press the blue button again, and again, as many times as it takes.

Also - I noted that this blue-button-pressing only works within about 10 feet of the Vera, most often the device is mounted further away and the “waiting” message does not go away, even with a button press.

Anyone else seen this behavior, or can confirm/disprove?
bob

14

My HSM100’s appear to stay awake for 10 minutes when you press the blue button. Tried one just now; it’s well over 10 feet away. Polled it a few times during the 10 minutes, without issue. Also did an ‘Update neighbors’ that seems to have completed successfully, etc. The red LED will flicker (assuming it’s picking up motion) during the 10 minutes.

Can you post the Capabilities and Version of your HSM100? Perhaps the behavior is different depending on sensor Z-Wave firmware version?

15

Note: first set of Capabilities comes from 3-in-1 device, second set comes from each child device, ie motion, temperature, light sensors

[quote=“HSM100 factory reset and re-included yesterday”]variable=“VersionInfo” value=“6,2,40,1,13”
variable=“Capabilities” value=“81,140,0,4,33,1,R,RS,|49,96:2,112,114,119,128,132:2,133,134,”
variable=“Capabilities” value="81,140,0,4,33,1,R,RS,|49,[/quote]

[quote=“HSM100 after upgrade”]variable=“VersionInfo” value=“6,2,40,1,13”
variable=“Capabilities” value=“81,140,0,4,33,1,R,RS,|49,96:2,112,114,119,128,132:2,133,134,”
variable=“Capabilities” value=“81,140,0,4,33,1,R,RS,|49,”[/quote]

[quote=“HSM100 before upgrade”]variable=“VersionInfo” value=“6,2,40,1,13”
variable=“Capabilities” value=“81,140,0,4,33,1|49,96:2,112,114,119,128,132:2,133,134,”
variable=“Capabilities” value=“81,140,0,4,33,1|49,”[/quote]

All of this is true for my HSM100’s as well. However, try this:

  1. Let it get past its test/wakeup mode
  2. On the UI select [Configure node right now]
  3. You will get “Waiting for wakeup to configure”

In my experience:

  1. A wakeup period will pass, LastWakeup will record it happened, and the message will not go away.
  2. Pressing the blue button any distance greater than about 10-15 feet from the Vera - the message will not go away.
  3. Press the blue button within 10ft of Vera and message goes away.
  4. Numbers 1&2 above might be the same thing since I normally place the device in its normal spot, more than 10ft away from Vera.
  5. As a result of #4, after a Heal all (or randomly at least most) of my battery devices are left unconfigured.

My point here is that during a Heal, unless the HSM100’s are all brought near the Vera, configuration data does not seem to get properly updated. If this is true - what is the point of “healing” a network (ie detecting neighbors, testing routing)when the devices are not in the “mesh” where they physically belong, or are not updated if they are where they belong?

Or I could be totally wrong - results of above test by someone else please…
bob

16

Current typical example, happening right now:

I have a Temperature / Humidity sensor, battery operated, re-configured as part of a Heal done just last night. The only way to finish the Heal was to hold the device near Vera and activate its Include mode every time the Waiting… message appeared.

It has been showing “Waiting for wakeup to configure” since I first looked at the U14 screen early this morning. I just forced a “Loading Data” reload of the U14 screen - still there.

It is on the second floor, almost directly above the Vera on the first floor.

LastWakeup shows 12 noon, almost 2 hours ago. Wakeup intervals are set for 300 (every 5 minutes).

ADD report shows Last Battery Report 20 hours ago.

I have not excluded / included this device yet.

Many times I have initiated the Include mode with it in place on the 2nd floor, it never works. The only way to get rid of the message is to take the device to Vera and initiate Include (like the 3-in-1 blue button but keypresses). Prior to the upgrade the only device to ever show this behavior is the 3-in-1 150ft from Vera in another building.

Needless to say the sensor data is VERY stale, and very useless.

17

@flyboybob

I have it seen mentioned that on 1.1.1245

a) battery reports are less trustworthy and replacing the batteries helps the device to function properly (even if Vera shows anomalies)

I know you exchanged batteries already for some.

b) i have seen reports of users solving their issues with a powercycle of their Vera (thread linked in other posts of mine).

c) fellow beta testers claim better functionality for their batteryoperated devices on official beta 1.1.1298 (currently tested)
ADD seems to report less drowsy devices.

Just wanted you guys to know…

18

.1245 with Z-Wave 3.20 with MiOS routing enabled?

19

.1245 with Z-Wave 3.20 with MiOS routing enabled?[/quote]
.1245 with Z-Wave 3.20 with and without
“Only update MiOS routing (overrides other settings)”
and
“Use MiOS routing instead of Z-Wave (requires 4.5)”
checked
currently both unchecked.

Recommendations? - I’ll try anything
bob

20

@flyboybob

Maybe go back to defaults for 48 hours?
Mine are shown here:

http://forum.mios.com/index.php?topic=6898.msg44474#msg44474

.1245 with Z-Wave 3.20 with MiOS routing enabled?[/quote]
.1245 with Z-Wave 3.20 with and without
“Only update MiOS routing (overrides other settings)”
and
“Use MiOS routing instead of Z-Wave (requires 4.5)”
checked
currently both unchecked.

Recommendations? - I’ll try anything
bob[/quote]