Release v0.13.0

• Fixed: The costs of an Anthropic organisation account were a hundred times too high — the provider counts them in cents, the adapter read them as dollars
• Fixed: The same error was in the adapter-wide cost totals
• Fixed: An account whose values could not be written to the object database kept reporting itself as delivering, with a last-update stamp that went on moving
• Fixed: An answer still waiting on the object database during shutdown could mark accounts online again afterwards, or delete objects
• Fixed: An answer in a shape the adapter does not recognise now counts as a service fault, instead of reading as "this account has nothing"
• Fixed: Limit windows and model channels are no longer deleted when a single answer says nothing about them
• Fixed: Token counters of an organisation account show 0 after UTC midnight instead of keeping yesterday's numbers
• Fixed: Restarting the instance above the warn threshold no longer raises the warning and the notification again
• Fixed: The "limit reached" total now counts a window the provider has closed, the way each account already did
• Fixed: A configured account row the adapter cannot use now says so in the log instead of disappearing
• Improved: The "active window" and DeepSeek "available" flags are written only when they actually change, so their timestamp stops moving on every poll
• Improved: The ChatGPT voucher inventory is fetched about once an hour instead of every poll, halving that account's requests
• Improved: The settings page shows a finished device-code sign-in right away instead of up to half a minute later
• Improved: The provider table now says that Anthropic's cost report leaves out Priority Tier spend, so an organisation on that tier really spends more than the figures show

Release v0.12.1

• Fixed: The last-update stamp of an account no longer moves forward while the provider is only throttling — it dates the values standing next to it, so you can see how old they really are
• Improved: Twenty-five more datapoints explain themselves in the object tree — what "today" means (the provider counts it in UTC), and why the cost totals can be lower than the accounts show

Release v0.12.0

• Fixed: An account that has not been signed in yet no longer reports a rejected sign-in — no warning, no notification, and the settings page keeps offering the sign-in button
• Fixed: An account whose API key is missing or unreadable is now shown as not delivering, instead of leaving its old values standing as though they were current
• Fixed: An answer arriving while the adapter shuts down can no longer mark an account as online again after the shutdown wrote it offline
• Fixed: A throttled account counts as delivering everywhere now — the connection icon and the "reachable accounts" total no longer contradict each other
• Fixed: A limit the provider reports as empty is no longer shown as 0 % used, and a Google quota without a value no longer reads as completely used up
• Fixed: A rejected ChatGPT sign-in now says so at once instead of leaving you waiting for a quarter of an hour, and a Google account keeps delivering when one route is unavailable
• Fixed: A Google account without an AI subscription says so, instead of asking for a sign-in that cannot change the answer
• New: Every limit window shows whether it is the limit currently in force — with Claude the provider states it, elsewhere it is the window that speaks for the account
• Improved: An account is reported as at its limit when the provider says the window is closed, not only when the percentage happens to reach 100
• Improved: A window's reset time is written to the minute, so a recording of it no longer gains an entry on every single query, only on real changes
• Improved: An account that is delivering again says so in the log, instead of leaving the warning about its outage standing as the last word on it
• Improved: The settings page no longer asks the adapter for every status every four seconds — the values now arrive on their own as they change
• Changed: "Balance sufficient for calls" now sits under credits, where it belongs; the datapoint at the old place is removed automatically
• Changed: Each account node shows the readable provider name instead of the internal one — "Claude Max (Claude)" instead of "Claude Max (claude-sub)"
• Fixed: A per-model folder is now named in your ioBroker language as well, instead of carrying the provider's bare model identifier as its only name
• New: The datapoints whose meaning is not obvious from their name now carry a short explanation in eleven languages, shown in the object tree

Release v0.11.0

• Fixed: Signing in from the instance settings works again — a leftover setting from an earlier version had silently closed the adapter's message channel, so none of the three flows reached it
• Fixed: A subscription whose stored sign-in was rejected no longer claims to be signed in — the row now offers the sign-in again instead of showing a green check next to an error
• Fixed: The status badge of an account no longer blanks out for a moment when a single status read is missed — a hiccup in the settings page is not an account without a status
• Fixed: A stored credential whose name sorts high in the alphabet is no longer missing from the account list in the instance settings
• Fixed: The settings page falls back to English for a browser language the adapter does not ship, instead of passing that language on unchecked
• Improved: All object names are now available in eleven languages instead of English only, and a renamed object reaches installations that already exist
• Improved: ChatGPT usage is read with the identity that endpoint expects, the way the Claude query already did — fewer rejected requests on that account
• Improved: Monthly cost reports can no longer be cut short in silence — a report that does not fit is reported in the log instead of producing a figure that is too low
• Changed: "Highest account utilisation" says what it always measured — the fullest limit window or the account's remaining budget

Release v0.10.0

• Fixed: The reset-time datapoint of a limit window no longer disappears and reappears — it stays and simply empties while no window is running
• Fixed: The settings page no longer shows the sign-in screen to a signed-in account, and its rows load without waiting for the credential storage scan
• Improved: Claude usage is read with far fewer rejections — the query now identifies itself the way the endpoint expects
• Changed: New Claude sign-ins request only the profile permission — the stored access can no longer create API keys or run models
• New: ChatGPT accounts show their purchasable limit-reset credits — how many are available and when the next one expires
• Improved: An unreadable provider answer is now reported as a service fault instead of a missing connection

Release v0.9.3

• Fixed: The first start after updating no longer leaves a warning in the log

Release v0.9.2

• Fixed: Stopping the instance now marks the accounts as offline on installations that were updated too, not only on fresh ones — the previous version left them showing as online

Release v0.9.1

• Changed: While an account has nothing to report — the adapter switched off, or started and not asked yet — the reason now reads "Unknown" instead of a sentence about the adapter

Release v0.9.0

• Fixed: Switching the instance off now shows every account as offline in the object tree and the settings, instead of leaving them green for as long as the adapter is not running
• Fixed: After a crash or a hard kill an account no longer keeps claiming to deliver data; every account starts as "not delivering" until its first answer arrives

Release v0.8.0

The 0.8.0 tag never reached npm (red Windows run), so its entry is still open and
the fix belongs in it rather than in a version on top.