Excessive EDA responses

[Robjoby]

I've just replaced the old Sense watch with the Sense 2  and when I do an EDA scan on my Sense 2, I get lots of EDA responses in the region of 15 to 25 every time, whereas on my old Sense watch I usually got 0 or maybe upto 5 occasionally.

I'm performing the EDA scan in the same situation and environment as I had been doing with the old Sense watch, so I don't know what to believe on this test, with such dramatically different results.

Has anyone else had this sort of result on the EDA test?

[Robjoby]

I've now been wearing my old Sense watch and my Sense 2 watch for a week and I've tried the EDA scan on both watches twice every night within the same five minute period and I get ridiculous differences. My old Sense watch shows between 0 and four responses every time and my wonderful Sense 2 shows between 18 to 28 responses every time. I always feel relaxed and calm when doing this with no distractions so I tend to believe my old Sense watch, but how can Fitbit reconcile these enormous discrepancies between the two versions of the Sense watch? I'm beginning to join the "Sense 2 is rubbish" club as I've also experienced many other issues that have been discussed on the forums and this repeated discrepancy is hard to explain.

Nobody else had a similar experience with the Sense 2 showing excessive EDA responses?

[t.parker]

For that reason I disabled cEDA,. Way too many notifications and it happened now that 4 times it woke me up. Mostly, the notifications were coming when I was experiencing nothing, just when being calm. I don't understand this feature and I don't think I need it so after testing I disabled it.

[jadams7469]

Robjoby,

I am experiencing the same exact thing with my EDA responses.  Like you, the only difference is the new Sense 2 watch.  I am also experiencing other strange things like the watch randomly rebooting several times a day (it just rebooted while typing this!) and while the old Sense always was buggy synching with the app on my iPhone, the new Sense 2 seems to be worse.  I would think that having a Bluetooth connection established would be well-understood and easy to maintain.

John

[rbittman]

cEDA: After two weeks using the watch, I have to agree that cEDA seems pointless. Maybe it’d help people who don’t self reflect when stressed, but I’ll bet most are basically in tune with that already. I see no point in recording my stress type unless that leads to some machine learning which enhances the Watch experience. That isn’t happening so far as I know. 

I don’t get a lot of cEDA notifications though my overall stress level seems to hover in the low 80’s. I never get the notifications at night and I think that’s because I use the “Schedule Mode” for turning off notifications at night (this is in Settings and is very useful. I have it set to not alert me between 9-7).

Note on random reboots: I see those too. Could it be that Fitbit is releasing bug fixes?

[Bearbrook]

Same here. Had the first sense. Now with 2 I'm getting many responses. 

[Barbannc]

I have been experiencing the same after switching from Sense to Sense 2 about a week ago.