Sensative Strips Comfort - silly temperature values

[muc 1]

Hurra, a 10 years outside temperature sensor (senecomfort)!

But 9 times during 16 days an absurd value was sent (far more than 2°C away from the last sent value).

I sent it back, and they sent another one.

Surprise: during the 1st day after inclusion this one sent 19°C, an hour later 1°C (one!), an hour later 20°C.

Anyone knows this strange behavior, or can explain it, or knows what to do to avoid it?

A bug? a feature? bad connection to HC2 (4.540)?

Thanks!

 

[andersmyr 0]

I am having similar problems with a Sensative Strips Comfort, trying to make it work with HCL v.4.550.

 

After the sensor device is added, it reports 'not configured'. I get temperature readings, but they are about 13 deg low. Reconfiguration does not work.

[10der 832]

In some articles by @petergebruers he wrote about lack of CRC in zwave (without plus) packets. So if you have not stable connection or your devices has routing via nearby devices this is ok (sure not ok but alas) 

[smilfinken 0]

On 8/23/2019 at 9:45 AM, andersmyr said:

I am having similar problems with a Sensative Strips Comfort, trying to make it work with HCL v.4.550.

 

After the sensor device is added, it reports 'not configured'. I get temperature readings, but they are about 13 deg low. Reconfiguration does not work.

I'm having the same configuration problems with this device and same HC version (but HC2, though), did you get it to work? I haven't really considered if the readings are correct yet, I would just like to get it configured in the first place.

[andersmyr 0]

12 minutes ago, smilfinken said:

I'm having the same configuration problems with this device and same HC version (but HC2, though), did you get it to work? I haven't really considered if the readings are correct yet, I would just like to get it configured in the first place.

 

Not working. The Strip is on ice, awaiting next update of the HCL firmware.

If it still doesn't work I'll try Fibaro support.

[smilfinken 0]

27 minutes ago, andersmyr said:

 

Not working. The Strip is on ice, awaiting next update of the HCL firmware.

If it still doesn't work I'll try Fibaro support.

Thanks for the update. I've logged support cases with both Fibaro and Sensative, so maybe I'll get some responses soon.

[smilfinken 0]

On 9/5/2019 at 9:32 AM, andersmyr said:

 

Not working. The Strip is on ice, awaiting next update of the HCL firmware.

If it still doesn't work I'll try Fibaro support.

 

I got a reply from Sensative which says that this is a known bug in firmware 4.550 that Fibaro is working on and that reverting to a previous backup (4.540 or earlier) should make it work, but I haven't had a chance to try that myself yet. According to Fibaro support (who did not seem to know about it :) ) the next release is in a couple of weeks, but it's not entirely clear to me if a fix for this will be included or not.

[kroeatschge 29]

hey guys,

I have the same experience and was also in contact with sensative and fibaro support.

The error is in Fibaro firmware.

 

I narrowed it down to the false values only appearing when the automatic wakeup of the device sends data to HC2.

HC2 mixes then up some values. It stays wrong until the device sends the next value (e.g because of light/temperature change).

 

What you can do is to increase the wake up interval so this doesn't happen that often anymore.

 

BR - kro

 

Please login or register to see this spoiler.

 

[muc 1]

perhaps solved:

since HC2 firmware 4.560 both strips only send values correspondent with other sensors

even parameter 3 could be changed

hopefully

muc

 

[smilfinken 0]

13 hours ago, muc said:

perhaps solved:

since HC2 firmware 4.560 both strips only send values correspondent with other sensors

even parameter 3 could be changed

hopefully

muc

 

Mine still doesn't complete configuration of the Sensative strip at version 4.560, unfortunately. The values they do still report may be correct, but the device is not usable in scripts since it's not configured.