Problems polling the HSM100 light sensor

I have my HSM100 light senser hooked up to an external power supply, in order to get frequent light readings from it without running down the battery. However, I am having trouble obtaining frequent readings from the device.

The sensor transmits the light level every time it wakes up, but the lowest valid setting appears to be 6 minutes, and some experimenting shows that 12 minutes is the lowest setting that actually works.

My next idea was to have the device always on, so that Vera can poll the values regularly. And with the settings below, I can for a fact hit “poll now” at any time to obtain a new light level reading. But Vera doesn’t appear to poll the device automatically; the displayed value still only changes once per “wake up” period, which is 12 minutes. How come the device can be polled manually but doesn’t seem to be polled automatically by Vera, like it does with all other devices?

Settings for the HSM100:

  • Wakeup Interval: 720 s
  • Poll node at most once every: 60 s
  • Device option 2: On time: 3 minutes
  • Device option 4: Stay awake: 255

Right; it goes in 6-minute increments. It seems folks have had various degrees of success with certain values.

[...]How come the device can be polled manually but doesn't seem to be polled automatically by Vera, like it does with all other devices? [...]- Device option 4: Stay awake: 255
I have not tried this, but isn't it option 5, and did you re-include the sensor so Vera knows it's not a battery-operated device anymore?

Also, the polling frequency of a single node will depend on the total number of nodes in your network. So depending on that number, and how often Vera polls a node (default 30 seconds), the polling interval may be slower than the wake-up interval.

Yeah it’s option 5. Anyway, I re-included the device but that didn’t help, and it’s still displayed as a battery powered device.

I have about 30 devices, would that make the polling time too long?

Intveltr,

Did you ever get a better read on this? I’m having similar issues, e.g. can get new report with manual ‘click the poll now button’. Detetermined there is some interaction with the ‘master settings’ documented to an extent (some ambiguity) at http://wiki.micasaverde.com/index.php/Polling_Settings.

However, can’t say I have a practical solution to getting frequent termperature and light updates. (For what its worth, not obvious I’ve gotten the motion sensor to work either, sheesh.)

JohnR

I’ve gone back to running the HSM100 off batteries, they seem to last a good while anyway. I now have the sensor reporting reliably every 6 minutes. After upgrading to UI5, I did have to re-include it into the network to make it report at all…

Can’t thank you enough for quick reply. This gives me two good steers re: what I should be able to achieve. I’m still chewing through trying to understand the different polling parameters, which seem to have areas where they would conflict (and need to determine which parameter trumps which), the wake-up interval setting (whether it’s doing anything), etc. I think it will become more clear as I let the new devices ‘sit’ for a bit over the next week or so and analyze the data I’m logging.

I’m stuck with UI4 for a while, as I’m reliant on an enthusiast-provided data logging module called dataMine, which has issues with UI5. Good to know the battery life might be tolerable with 6 min logging intervals.

Once I get sorted a bit re: polling parameters, etc., I might ping you regarding reactions to settings I have – might be very useful. The 6 min ‘hint’ is itself interesting, as I haven’t seen this documented anywhere. I’m thinking of getting copy of Homeseer software (just for testing, figuring the device might behave best in its native development environment) to try to determine what is Vera-related and what is connected to device itself. Will advise as

Again, many thanks for your help,

@JohnR,

Generally, the polling settings should only come into play for sensors that are not battery powered. Battery powered devices are typically asleep, so you can’t poll them on demand. Such devices either wake up every so often, or report status changes autonomously.

The HSM100 will report motion autonomously, i.e. instantly (otherwise it wouldn’t be very useful). The light and temperature values need to be requested by the controller when the device wakes up. Even though that action could be considered polling, the polling settings that control timing may not play into it, as Vera would need to request the sensor values as soon as she receives a wake-up notification from the device, before it goes back to sleep.

If anything on the wiki page you referenced is ambiguous, not-so-clear, or plain wrong, please post that here, so it can be updated.