[ANSWERED]: Everspring ST815, no LUX reading since upgrade

I've upgraded to 6.0.20 and now I can't get a LUX reading off my ST815 sensor. It's just showing as a pair of dashes even though the last update time is changing per wakeup schedule. I've tried deleting and re adding and moving it next to the controller but still nothing. Is there some form of debugging I can turn on as the Event Log doesn't have anything in it anymore?

[matt (support)]

You can turn on the debug logging via the Interfaces->Z-Wave->Configure... menu item (then the debug logging checkbox).

Also try excluding and re-including the module in the Z-Stick (then re-syncing it). Sometimes the modules can get in a bad state and stop working correctly.

I've removed and re-added and re-synced but lux never appears.

I turned debug on, then woke the device up and clicked 'Send Status Request' and got these results:
14 Jan 2015 14:37:13
Z-Wave Debug RCVD requestNodeInfo: 01 11 00 49 84 2B 0B 04 21 01 31 86 72 85 84 80 70 20 33
Z-Wave Debug SENT requestVarSensorStatus: 01 09 00 13 2B 02 31 04 05 5F A3
Z-Wave sent "043 - Luminance" status request
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 2B 02 80 02 05 60 2B
Z-Wave Debug SENT requestBasicStatus: 01 09 00 13 2B 02 20 02 05 61 8A
Z-Wave sent "043 - On Threshold" status request
Z-Wave Debug RCVD requestVarSensorStatus: 01 0C 00 04 00 2B 06 31 05 03 0A 00 64 83
Z-Wave Debug . . requestVarSensorStatus: node 043, endpoint None, type 3, raw value 0A00...
Z-Wave Debug . . requestVarSensorStatus: 100 lux (float: 100.000000)
Z-Wave received "043 - Luminance" sensor update to 100 lux
Z-Wave received "043 - Luminance" units changed to lux
Z-Wave Debug RCVD nodeAwake: 01 08 00 04 00 11 02 84 07 63
Z-Wave Debug . . nodeAwake: node 017
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 11 02 80 02 05 62 13
Z-Wave Debug . . nodeAwake: inhibit count++ to 1
Z-Wave Debug . . nodeAwake: started inhibit sleep timer
Z-Wave Debug RCVD requestBasicStatus: 01 09 00 04 00 2B 03 20 03 64 9D
Z-Wave Debug . . requestBasicStatus: node 043, endpoint None, value 100
Z-Wave Debug . . requestBasicStatus: ignored -- 20 30 replies are too broad
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 11 03 80 03 46 25
Z-Wave Debug . . requestBatteryLevel: node 017, level 70
Z-Wave received "017 - Bathroom.Temperature" status update battery level 70%
Z-Wave Debug . . nodeAwake: inhibit count-- to 0
Z-Wave Debug . . nodeAwake: stopping inhibit sleep timer
Z-Wave Debug SENT goToSleep: 01 09 00 13 11 02 84 08 04 63 1D
Z-Wave Debug RCVD packet: 01 05 00 13 63 00 8A (hex)

The LUX level now appears as 100 but doesn't change.

[matt (support)]

Unfortunately, it looks like the ST815 is stuck reporting an incorrect lux value.

Have you tried fiddling with the different device settings (in the Edit Configuration Settings... dialog)? Specifically, try the Delay between reporting sensor values (0 to disable) setting or the LUX change that must occur before a report setting. Note Indigo won't be able to push the configuration changes to the module until it wakes up. Watch the Event Log to see when it changes them.

If that doesn't help, then I think the module has malfunctioned.

I'll try and reset it, but this was a brand new module as I assumed the previous one was broken...

Just checking to see if this cool lux / illumination sensor ST815 from Everspring is now working in Indigo 7 as it should?

I was so glad when I found them here in Europe so I purchased two before I had thoroughly checked with you guys if this is working in Indigo 7...

I´ve been looking for a pure LUX sensor that is also outdoor rated.
ST815 has IP44, but I haven't yet been able to verify its lowest outdoor temperature for working properly.

Replying myself...

Bought 2 of these Everspring ST815 illumination/lux sensors.

Inclusion into Indigo 7 was easy.
Some minor thing that would be nice to get changed in Indigo:

1. The parameter 6, auto report on change in LUX level should have minimum possible value = 30, not zero as it is now. According to the manual 30 is the lowest possible value.

2. I am not able to change the parameter no 1 (Basic Set Level) from default 99 to something else (which I can read out using the Z-Wave device param config menu after I have wakened up the device according to the manual).

Here is the debug log when reading out the value for parameter no 1:

Code: Select all

    Z-Wave Debug                    SENT readConfigValue: 01 0A 00 13 11 03 70 05 01 25 87 22
   Z-Wave Debug                    RCVD requestConfigVal: 01 0B 00 04 00 11 05 70 06 01 01 63 F1
   Z-Wave Debug                    . .  requestConfigVal: node 017, parm index 1, value 99 (size 1)
   Z-Wave                          retrieved parameter 1 "Basic set level" is 99

And when I wake up the device and try to set the param #1 to for example 10 I only see the node info frame after my wake up of the device in the debug log:

Code: Select all

Z-Wave Debug                    RCVD nodeInfoFrame: 01 11 00 49 84 11 0B 04 21 01 31 86 72 85 84 80 70 20 09

Nothing more happens and I can see the text for the field Param Index getting red when I press "Save New Value To Device"

Besides this the device seems to work fine in Indigo.

Ah, forgot to mention that I found the specs on what outside temps it is specified for: -10 degrees Celsius is the lowest temp according to the specs. Well we get sometimes -20 to -30 degrees C here outside Stockholm where I live so I guess it will be interesting to see how it works for me. I guess it will be mostly the batteries that will take a hit but I´ll replace them now to proper lithium cells that can handle cold weather better than normal cells.

[matt (support)]

The manual I have says that parameter 6 can have values ranged from 30 to 1000 or can be 0 to clear the value. Indigo's UI can only have a min and max range, so I have to set the min to 0 if Indigo is to allow that clear functionality. Note I'm not entirely sure what they mean by clear.

I will enable the ability to set parameter 1 in the next version of Indigo.

Ah yes you are correct.
Value can be in range 30 to 1000 and in order to DISABLE the LUX change reporting level the parameter is set to zero.
I am not sure what happens if the user sets a value that is higher than zero but lower than 30.

Would it be difficult to have a radio button next to the value field labeled "Disable LUX change reports" and if the user clicks that the field for the parameter is disabled?
OR
The user can only enter values between 30 and 1000 as well as the value zero?
Which one of the above would be easiest to implement?

Would be good to at least have a small text below the field "Value can be 30 to 1000. Set 0 to disable reports.".

[matt (support)]

I'm pretty sure there is already a label under the text that explains the range is 30 to 1000 and 0 disables/clears.

The other UI changes are a fine idea, but aren't going to happen anytime soon.

He he you were right (again ).

It does say 0 = disable.
Range says 0 to 1000 though. Maybe you can change that to 30 to 1000...

My testing of the ST815 in my DEV environment is done now and I has been working without problems so I will install both of the ST815's into my PROD environment during the weekend.
One of them will be installed on the outside of my house so lets see how it survives the Nordic winter!

I can easily recommend this device to all of you who are looking for a PURE Lux/Illumination sensor.
I really like the Everspring ST815 and the ST814 temp/humidity sensors in the Z-Wave world.

The issue I had with them was that they would report random lux levels without warning, so if you had triggers that turned lights on and off based on the lux level you would find them being activated at the wrong time.