Pixel 4 Ecg reading not saving to Fitbit. Notifications greeted out

[Leisurlyj]

New to the pixel 4 watch. I have the Fitbit ECG app on the pixel 4 watch. The app seems to work and gives a result. However the result does not save to the Fitbit app on my phone. I am in the UK so should work.

I have cleared cache/data and restarted phone and watch

I have noticed there are no notifications received. For example one ECG stated atrial fibrillation was detected but a notification was not received. I have got irregular rhythm detection switched on in the phone app. But it's states no irregular rhythm detected

I have checked in settings /apps and Fitbit ECG has notifications greyed and unable to toggle on.

Can anyone help?

Moderator edit: clarified subject

[RiekoC]

Hello @Leisurlyj 

I'm not sure why you're not seeing your ECG results in the Fitbit app. Just to confirm, you're going to the You tab in the Fitbit app and tapping on the ECG tile under Health Assessments. When you tap on that tile, you're not seeing any historical data, correct?

Regarding the irregular rhythm notifications, this help page (<-- click) explains how the Fitbit irregular rhythm notifications work. The notifications are not in real time. 

[Leisurlyj]

Thanks for reply

When I click on the you tab in fit bit on the phone there is not an ECG tile visible.

To confirm Ecg are recording without any problem but just unable to view

The only thing I can in the you tab is irregular rhythm notifications under the title health assessments. And health connect data which shows steps etc.

Not sure why I can't see ECG tile

[Leisurlyj]

I now have the ECG tile in fit bit app. However I have been unable to download a pdf of the ECG. When I click on download pdf it attempts to download but nothing happens 

The other remaining issue is that Fitbit ECG notifications are greyed out and therefore I am not receiving notification of when an ECG has been done. 

Any ideas?

[RiekoC]

Hello @Leisurlyj 

Apparently, there is an issue with the ECG reports on the Fitbit side. Please see this thread (<-- click) where the Moderator acknowledged that this issue has returned and that the team is aware of it. The Moderator also mentioned that the team is working on fixing the problem. However, we currently don't have a timeline for the fix yet. 

Since this is confirmed to be a Fitbit issue, there isn't any troubleshooting for you to do. We'll have to wait for Fitbit to fix the problem.