Integration does not work if you have a bridge

[andrsinha]

Upgrading to a bridge removes the ability to even see the puck temperatures.

[RobertD502]

Can you elaborate on what exactly you mean?

I have a bridge on my account and puck shows temperature:

The support added for bridges in this integration does not touch any of the code related to pucks.

[andrsinha]

When you add a bridge you switch all your pucks to be sensors and not gateways. That is the point of the bridge ; it give better coverage, stronger signal and takes over the gateway role. When you do this the temp read by the pucks becomes unavailable.

[RobertD502]

Just to clear something up: Adding a bridge to your Flair setup doesn't require you to switch pucks to become sensors instead of gateways. You have the option of converting any gateway pucks to be sensor pucks.

Could you please enable debug logging for the integration and post the log here.

Based on your puck entities being unavailable, it is likely that Flair's API is reporting the puck as being offline, which results in the puck entities becoming unavailable. Once I look at the log, I'll know more.

[andrsinha]

I've turned on debugging. Where is it logged?

I spoke to flair. The point of the bridge is to be the gateway to rule them all. If you have your pucks in gateway mode you dont need a bridge. Either way any puck in send r mode is unavailable.

[RobertD502]

Do this from a computer:

On the integrations page, click on the flair integration, and click on "enable debug logging". Once you have done that, the bug icon will become red. At this point, you need to restart Home Assistant. When Home Assistant is back up again, wait about a minute. Then go back to the integrations page, open the flair integration, and disable debug logging. At this point, Home Assistant will save a log file to your computer. Share that log file here.

I get what the point of the bridge is. I'm merely stating that it is not a hard requirement that you convert gateway pucks to sensor pucks when you add a bridge. Even when setting up the bridge, Flair lets you know that you can convert gateway pucks to sensor pucks, however, this is not something that you HAVE to do. I currently have both a puck and bridge acting as gateways.

[andrsinha]

There you go

home-assistant_flair_2024-06-09T17-43-24.766Z.log

[RobertD502]

All of those pucks seen in the image above are reported as being offline, as indicated by the inactive key reporting true (outlined in red). In addition, you can also tell by the connected-gateway-id key (outlined in blue) which is reported as null meaning that none of those pucks currently have an active connection to your gateway bridge. As a result of those pucks being reported as offline by the Flair API, the entities in Home Assistant appear as unavailable.

You will need to figure out why those pucks are offline and are not connecting to your Flair bridge gateway. You can attempt to run the network repair mode (found in the flair app under Home Settings --> Flair Devices --> Network Repair Mode). If you are unsuccessful, you will need to reach out to Flair for help as this is not related to/not a bug in the Flair integration.

[andrsinha]

Thanks for looking at this. Network repair did not fix it. It looks like the switch over to the bridge had problems and I have to add and remove individual pucks to reset everything.

Fair need diagnostic like yours!

On Jun 9, 2024, at 11:32 AM, Dr. Drinovac @.***> wrote:

Offline.Pucks.png (view on web)https://github.com/RobertD502/home-assistant-flair/assets/52541649/e12752cf-2d40-4db2-8537-4c86fade16e2

All of those pucks seen in the image above are reported as being offline, as indicated by the inactive key reporting true (outlined in red). In addition, you can also tell by the connected-gateway-id key (outlined in blue) which is reported as null meaning that none of those pucks currently have an active connection to your gateway bridge. As a result of those pucks being reported as offline by the Flair API, the entities in Home Assistant appear as unavailable.

You will need to figure out why those pucks are offline and are not connecting to your Flair bridge gateway. You can attempt to run the network repair mode (found in the flair app under Home Settings --> Flair Devices --> Network Repair Mode). If you are unsuccessful, you will need to reach out to Flair for help as this is not related to/not a bug in the Flair integration.

— Reply to this email directly, view it on GitHubhttps://github.com/RobertD502/home-assistant-flair/issues/77#issuecomment-2156730706, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BGI3W5CMXBYKYRAPQ75UXMTZGSNUZAVCNFSM6AAAAABJALTLD2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJWG4ZTANZQGY. You are receiving this because you authored the thread.Message ID: @.***>

[RobertD502]

If you use the Flair app, any vents or pucks that are offline should have a red dot next to them and/or say they are offline.

[andrsinha]

I do. They were online with strong signal then they started falling off. The network rebuild actually made it worse. Turns out I had some old out of data puck and some that just needed an update. A step by step rebuild has fixed all but one.

Thx

On Jun 9, 2024, at 15:36, Dr. Drinovac @.***> wrote:



If you use the Flair app, any vents or pucks that are offline should have a red dot next to them and/or say they are offline.

— Reply to this email directly, view it on GitHubhttps://github.com/RobertD502/home-assistant-flair/issues/77#issuecomment-2156820149, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BGI3W5BGRRRFUSY3Q4XQOJ3ZGTKGHAVCNFSM6AAAAABJALTLD2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJWHAZDAMJUHE. You are receiving this because you authored the thread.Message ID: @.***>

[andrsinha]

Mystery solved. I have reached the limit of supported devices! I need a second bridge.