v1.2.4

This release include support for no_unit setting to suppress unit_of_measurement on a symbol.

v1.2.3

This release takes another approach to bypassing GDPR page. Instead of parsing crumb out of the response, a separate request is made to an alternate end point.

v1.2.2

This release includes

• Processing of consent page when determining crumb/cookie #96, #93. This issue should have been only happening in EU region where consent is required.
• In case crumb parsing fails, the content is also now saved into YahooFinanceCrumbContent.log in config folder.
• Inclusion of 52-week attributes (#100).

v1.2.1

Added crumb/cookie usage to handle data access issues #93.

The crumb itself is obtained by accessing quote for Nasdaq and parsing out of the content. Not a great approach but I couldn't come up with a quicker/reliable solution.

The crumb will be obtained again if data request fails with "Unauthorized" error code. If data retrieval failed then coordinator will attempt another retrieval in 20 seconds which will include crumb retrieval. In worse case scenario, this can keep on going and so there should be some throttling. But I haven't personally ran into it and this approach seems fine for now.

v1.1.11

Addressed #87

v1.1.10

Added support for multiple scan intervals.

• Symbol can now have scan_interval override defined.
• If symbol needs converter symbol, then it will be refreshed on the same interval unless it has already been registered.
• Sensor update now happens through _handle_coordinator_update override instead of available which is more streamlined.
• A symbol is considered not available if it has no market value.

v1.1.9

Supporting long term statistics

v1.1.8

Removed unsupported values from hacs.json

v1.1.7

Fixed twoHundredDayAverageChangePercent and fiftyDayAverageChangePercent values.

v1.1.6

Add more logging to websession get operation