Updated parameter value does not "Stick"

[Lenfors 0]

Hello!

 

I want to turn off the lights in my Fibaro motion sensors but it does not work in some of them. I change parameter 20 to "0 - LED inactive" and save, but the radio button jumps down to option 10 again. Next to "0 - LED inactive" it says "Last set value" but the light does not come off. What am I doing wrong?

 

Best regards, Mikael

 

[devfern24 10]

@Lenfors  After changing the parameters of a battery operated device it must be woken up to receive the changes.

 

In your case, make the parameter changes, click the save button on the right toolbar, then wake up your fibaro motion sensor by taking off the back cover and clicking the little button 3 times rapidly. The eye should light up blue when it "wakes up".

 

Wait a few seconds and refresh your web browser to check if the parameters took.

[Lenfors 0]

Ok, thanks. I thought it "woke up" when it was flashing light when I moved in front of it...

Would it be the same thing to change the parameter and just wait until the next day?

[Alex 32]

Best would be to wake it up manually be tripple clicking B-button near HC2.

Also cou can check the status window of HC2 in your webbrowser.

There you should see something like "sending parameter" and "parameter received".

 

[devfern24 10]

19 hours ago, Lenfors said:

Ok, thanks. I thought it "woke up" when it was flashing light when I moved in front of it...

Would it be the same thing to change the parameter and just wait until the next day?

 

Yeah I think it would do the same thing, although I have read some posts on this forum suggesting the "scheduled" wake-up was not as reliable for transferring parameters as a "manual" wake-up.

 

From what I understand, having devices wake frequently also takes a toll on battery life.

[petergebruers 1,268]

8 minutes ago, devfern24 said:

 

Yeah I think it would do the same thing, although I have read some posts on this forum suggesting the "scheduled" wake-up was not as reliable for transferring parameters as a "manual" wake-up.

 

From what I understand, having devices wake frequently also takes a toll on battery life.

 

Oh, well, it is rather complex.

 

Technically, it doesn't matter how a device wakes up... it always sends an "I'm awake, please tell me what to do" command to the controller. When the controller has done exchanging data, the controller says: "go to sleep". If the controller wouldn't do that or the message got lost, the device might be awake several seconds. If you scrutinised some manuals, you might think there *is* a difference between auto and manual wake up. For example, Aeotec MS6: "Press and hold for 3 seconds: Enable/disable wake up for 10 minutes. (When it is enabled, the orange Led will fast blink)". So... would the device really stay awake that long? Would it respond to parameter settings during that interval? I just double checked, it doesn't. If you wake it up this way, the controller (my HC2) still sends a "go to sleep" after a second or so. Then, if you want to make another change, you have to wake up (click) the device again. Oh, I'm not saying there is *never* a difference between timed wake up and manual wake up. Maybe. I sometimes change something trivial, like the LED response of an FGMS and rely on the auto wake up. But generally, I'm testing things and I don't want to wait an hour for it to have an effect...

 

The "Wake up" dialog between the device and the controller takes longer to complete than a sensor just reporting "Detecting motion" or "Temp is now 20 °C". It depends a bit on the device, I'd say 3600 or higher is "normal". A notable exception is a Danfoss Living Connect TRV, it can be set to 600 or 900 secs. It needs to wake up to exchange the set point... But it has two AA batteries, so lots of capacity. It's a balancing act and devices like the MS6 or the Fibaro FGMS have many parameters, all trading battery life for responsiveness.

 

Does this help?

[Lenfors 0]

Yes, thanks a lot.  Only to bad some of them are located on difficult places....

 

[petergebruers 1,268]

5 minutes ago, Lenfors said:

Yes, thanks a lot.  Only to bad some of them are located on difficult places....

 

 

Assuming they have a valid wake up time I'd change the wake up time to something like 300 seconds, save it, then wait for the previous wake up interval to pass and leave it alone. So if it was 3600, wait an hour. Wake up interval after that should be 5 minutes. Refresh the web page. It's still slow, because after a batch of changes you still have to wait 5 minutes, before they get applied (worst case). But it might be easier than climbing up a ladder

Some devices accept faster wake up, you'll have to check the manual. After a few days, but it back to a "sane" value.

[Jamie mccrostie 82]

On my Fibaro sensors all parameters change fine except #2 which I wont even hiighlight when I click in it.

Is this normal?

Its the same on all 8 of my pir/lux/temp sensors.