[dif/alert_handler] Remove artificial alert # limit

Closes https://github.com/lowRISC/opentitan/issues/3826

You may want to add @asb as a reviewer.

You may want to add @asb as a reviewer.

No need for me to review this, as it's had plenty of eyes on it with @msfschaffner and @gkelly.

No need for me to review this, as it's had plenty of eyes on it with @msfschaffner and @gkelly.

Hi @mcy, do you still want to submit this change?

This fix seems outdated now that #6136 has been merged. Specifically, #6136 has been merged, which unpacks the enable/class-assignment registers so there no bit-index computations needed now.
I will simplify this fix in a new PR, and mark as closed upon merge of the new PR.


Azure Files support for Windows Server (on-prem/IaaS) ADDS as well as Azure ADDS

At https://docs.microsoft.com/en-us/azure/virtual-desktop/fslogix-containers-azure-files#azure-files-integration-with-azure-active-directory-domain-service, the article states: "On August 7th, 2019, Microsoft Azure Files announced the general availability of Azure Files authentication with Azure Active Directory Domain Service (AD DS). By addressing both cost and administrative overhead, Azure Files with Azure AD DS Authentication is a premium solution for user profiles in the Windows Virtual Desktop service."
Since that time, Microsoft has now also introduced Azure Files authentication with Active Directory Domain Services (AD DS). See https://docs.microsoft.com/en-us/azure/storage/files/storage-files-identity-auth-active-directory-enable.
Should this article be updated to reflect that the WVD+FSLogix+AzureFiles scenario now supports BOTH Azure ADDS and on-prem ADDS?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4951380a-4f22-1755-43d4-84a90b23e20a
Version Independent ID: 9f7fe2ab-6ee0-cf62-195b-517dba2492b6
Content: Windows Virtual Desktop FSLogix profile containers files - Azure
Content Source: articles/virtual-desktop/fslogix-containers-azure-files.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Closing the loop on this - this section is no longer in the article and we have a how-to guide that covers both AD DS and Azure AD DS: Set up FSLogix Profile Container with Azure Files and Active Directory Domain Services or Azure Active Directory Domain Services.
#please-close


Change nginx 'endpoint' to 'status_url'

@qingling128, I think this was what we agreed on earlier. Let me know if you'd like to see a different name.

I think you have some merge errors - I don't believe there should be any changes to the golden files in this PR.

@quentinmit Good catch. I've tracked this down, and opened #167 to address the unexpected changes.
Some of these changes are expected though, where the renamed parameter is involved in golden test cases.

@quentinmit Good catch. I've tracked this down, and opened #167 to address the unexpected changes.
Some of these changes are expected though, where the renamed parameter is involved in golden test cases.

I expect the changes to input.yaml but not changes to any of the golden_* files. The renamed parameter should still generate exactly the same OT config.

I expect the changes to input.yaml but not changes to any of the golden_* files. The renamed parameter should still generate exactly the same OT config.

I've merged in changed from #167, so the changes should be much clearer now.
Changes to nginx tests:

input.yamls that contained endpoint have been updated to use status_url
Golden error files that called out endpoint, now call out status_url
Test cases that contained the work endpoint renamed to status_url
No changes to otel configs


NWA Connection Issue

Hi,
We have been testing NWA initiated NWC with Mutiny Wallet for a little while now and everything was working fine up until recently. I've noticed any new NWA connections I initiate do not seem to be working in the Mutiny wallet.
Old connections that I have (relay.mutinywallet.com relay from 1 month ago) work perfectly. Any new connection I initiate seems to be setup correctly but then does not work. I receive a 33194 from the new wallet pubkey. NWC requests that I send are stored by your relay, but not shown in the wallet.
Here is a connection I just made that is not working:
33194 Event ID: d71ef2b40b35541664445a1766facfa01ab26976fb7639fe5eef45dc00dfcd62
23194 Event ID (pay_invoice req that was not received by wallet): 9b11439b1f084b21563a81c6a2654d152b34b9ef87210938885693e239f80280
Wallet pubkey: 51a55ebaeb2b6148c835719188bf84cbda8c1a38ce5d9f481fba52e666cc1687
Could you help me figure out what's happening?

Sorry about getting to this late, was at Bitcoin Atlantis. I can reproduce, will try to figure out the exact cause


Cleanup jobs after hash is persisted

There was a lib-common issue where job.DoJob() deleted the Job right after it is succeeded. Then the controller tried to store the hash of the Job in Status. But if that failed (due to e.g. Conflict) then in the next Reconcile call lib-common would re-create and re-run the Job as the hash of the previous Job and the Job itself is lost.
The lib-common is fixed in a way that the automatic Job deletion is removed from DoJob() and that needs to be now done on the caller side via the new job.DeleteAllSuccededJobs() call.
This patch adapts to the new lib-common version by doing the Job cleanup right after the Status.Update() successfully persisted the Job's hash.
Depends-On: openstack-k8s-operators/lib-common#77

/test all

So after this fix was still able to reproduce occasional double Job execution. It turned out that we can read stale data from a cache in operator-sdk. So simply moving the deletion logic after the Job hash is persisted is not enough. @abays suggested to simply delay the Job deletion by setting ttlSecondsAfterFinished on the Job. So with a big enough ttl value we can circumvent this issue.


an error while starting the kernel

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
It's first time i use spyder and i face this problem directly , how can i solved with easy way please ?
What steps reproduce the problem?

install anaconda 2019
open spyder
and the problem was in the Ipython console

What is the expected output? What do you see instead?
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version: 2.7
Python version: 3.7
Qt version:
PyQt version:
Operating System name/version:

Dependencies

Traceback (most recent call last):
File "C:\anaconda\lib\site‑packages\spyder\plugins\ipythonconsole.py", line 1562, in create_kernel_manager_and_kernel_client
config=None, autorestart=True)
File "C:\anaconda\lib\site‑packages\traitlets\config\configurable.py", line 73, in __init__
super(Configurable, self).__init__(**kwargs)
File "C:\anaconda\lib\site‑packages\traitlets\traitlets.py", line 997, in __init__
setattr(self, key, value)
File "C:\anaconda\lib\site‑packages\traitlets\traitlets.py", line 585, in __set__
self.set(obj, value)
File "C:\anaconda\lib\site‑packages\traitlets\traitlets.py", line 559, in set
new_value = self._validate(obj, value)
File "C:\anaconda\lib\site‑packages\traitlets\traitlets.py", line 591, in _validate
value = self.validate(obj, value)
File "C:\anaconda\lib\site‑packages\traitlets\traitlets.py", line 2053, in validate
raise TraitError(msg.format(value, self.name, class_of(obj)))
TraitError: Could not decode 'C:\\Users\\\xe3\xdf\xca\xc8 \xc7\xcd\xe3\xcf \xe1\xe1\xcd\xc7\xd3\xc8\xc7\xca\\AppData\\Roaming\\jupyter\\runtime\\kernel‑cae4b83b15ef.json' for unicode trait 'connection_file' of a QtKernelManager instance.

Spyder version: 2.7
Python version: 3.7

I think this is incorrect. Instead, it seems you're using a Python 2 version of both Anaconda and Spyder.
And this part of the error is very telling:

TraitError: Could not decode 'C:\Users\\xe3\xdf\xca\xc8 \xc7\xcd\xe3\xcf \xe1\xe1\xcd\xc7\xd3\xc8\xc7\xca\AppData\Roaming\jupyter\runtime\kernel‑cae4b83b15ef.json' for unicode trait 'connection_file' of a QtKernelManager instance.

It basically shows that you have a user name with a bunch of non-ascii chars (i.e. letters like ñ, á, Chinese characters, etc).
So you have two possible solutions here:

Change your user name to have only ascii letters (i.e. something like John).
Start using Python 3 (it's about time because Python 2 will reach end-of-life in just two months).


Do not crash if non-prefixed AudioContext isn't available

Safari 11.x only has prefixed webAudioContext: without this patch the polyfill crashes.
Fixes #9

FWIW I usually recommend "polyfilling" AudioContext in Safari globally:
if (!window.AudioContext && window.webkitAudioContext) = window.AudioContext = window.webkitAudioContext;

Shipped in 1.1.1! Cheers.

My app now work perfectly in Safari & Firefox!


Frequentist or Bayesian estimator for Model Fitting?

Hi, during Monday 7th's session, we struggled to understand the authors comparison of Frequentist versus Bayesian estimators for their model fitting algorithm (Bayesian Galaxy Shape Measurement for Weak Lensing Surveys -I., Miller et al). So I reproduced and tried to explain their experiment in a notebook, hopping to make it clearer :)
Maybe this could be a Model Fitting's subsection even though I'm not sure it fits the book format. I am ready to make any necessary changes.

Thanks @b-remy, this notebook is very cool. I think with a bit of work this could easily be the start of the model fitting section of the book. We can discuss the details at the next shear book session.

@b-remy Following today's discussion I recommend that you do the following:

Create a new directory in shearbook called appendix.
Put your notebook in that directory.
Choose an appropriate name for the notebook. I don't have any good ideas yet, but I am sure we can come up with something.
In _toc.yml add a new chapter (i.e. part) after Bias and Calibration called Appendix and add the name of your notebook.

- part: Appendix
  chapters:
    - file: appendix/your-notebook


Can move to typings, but one item remains

@blakeembrey, typed-typings/npm-* naming is my last hesitation, as I still don't see the typings ties to any particular distributing channel.
If the source is distributed in npm, bower, jspm, NuGet, apm (atom), etc, or any combination of them, how should the repo be named?
I like the original typed-* better.

I prefer typed-* better too, but it was redundant when it's the organisation name. I actually noted it in the registry because I saw people following the pattern I did accidentally. I only use <registry>-<name> as a way to avoid possible collisions in the future and not give preferentially treatment in the organisation. In general, that's unlikely to happen (hasn't yet).

The generator currently would suggest user to name the repo as typed-xyz. Are you ok with it?

Perfect :+1:


Add documentation comments for GraphQL APIs, if they are missing

It would be helpful to provide client-side friendly GraphQL API documentation, allowing client-side development to proceed without needing to understand the details of review-web. Developers could simply reference the GraphQL API schema, typically in SDL format. Some APIs have documentation, but not all are documented. So, I think this would mainly involve adding missing documentation comments in the relevant code.

Regarding the APIs to return values parsed from packets, we need to not only fill in the missing ones but also ensure their descriptions are legitimate according to the standard protocols. Since the current API names do not clearly indicate the meaning of the values they return, it would be better to elaborate on them with descriptive texts. I asked Parker and Ben to add proper descriptions to each API in Notion, and I think this issue should be addressed after that is completed.


Modified README.md file as agreed with maintainers

Included new intro, links and info about target boards to better reflect the current situation.

Personally I think updating the verbose information in the README instead of reducing it causes more maintenance work to keep up to date.
In particular keeping the information like:  "to build for target X, add this to your local.conf".
seems redundant and error-prone if those local.conf are already provided in full inside of genivi-dev-platform.git.   The readme refers to genivi-dev-platform.git and that is good, but I think it's important to make sure that reference is not missed.
If the modifications were a simple one-liner that is unlikely to change, perhaps, but it contains quite long blurbs of gstreamer_special_config = whatever...
I also fear people will mistakenly start building their own variants based on meta-dev-platform only, which happened a lot before genivi-demo-platform.git existed (and for some time before people actually changed their method).   Starting with meta-genivi-dev only might make sense for new hardware and experiements, but not really when we are talking about the hardware supported by genivi-dev-platform.git.  IMHO.  Regardless, more strongly recommending genivi-dev-platform.git as the starting point for new ports ought to simplify integration later.

Now. I agree with gunnarx's opinion. Why don't you move this READ.me to genivi-dev-platform.git as starting point.

Maintenance overhead
The attention on Github is so high that you require to take the readme.md as a landing page. This is the route that many relevant projects are taken on Github.
Check https://github.com/matiassingers/awesome-readme
In our case, there are two points that reinforce the need for seen README.md file as a landing page:

We are not using GitHub wiki so there is a strong need to redirect users to our own wiki (this also works for the bug tracker).
Since the migration from the former infrastructure to the new one has not finished, our current URL are not optimal, which makes easier for GitHub pages to become the main ones in Goggle searches for GDP. A simple search test will reinforce this idea. Personal repos of people not heavily involved in GDP but that are using Github, are already in the first page when searching for GDP (at least for me).

So the maintenance risk is in fact, a need. We have to treat GitHub as a landing page and we need to maintain it. This is a hidden cost when moving to GitHub. We need to transform it in an asset by routing people from Github to GENIVI wiki. Keeping it short and technical is not the way to go, in my opinion, in this environment.
The current readme files has been there for several months. It is now that are exposed in Github, so exposed to a wider and different audience, that we need to add general purpose information. As the project evolve and we evaluate the users and contributors behaviours, we will need to reinforce the idea of Readme.me as landing page or not. Examples of big/successful projects point in that direction, in my opinion.

This pull requests is about GDP-194

In response to  humble opinion summarized again:

All repos should have a README, sure.
It can be concise and to the point.
Even if similar content has been here for a long time, I still think find it an improvement if this repository has a short readme saying what it is (Yocto layer) and telling adopters where to find the other relevant info (conf files and/or layer compatibility) inside of genivi-dev-platform.git.  I think it should very early in this README direct readers towards genivi-dev-platform rather than later.
I am not sure I agree that a Github README must include all info and can't point to a public wiki but I understand your argument.   As long as we avoid redundancy there is an open choice where to put the detailed info.  If it goes into README most of it should then still be in genivi-dev-platform.git rather than meta-genivi-dev.git.

Overall, the genivi-dev-platform.git/README needs update.  It should not say "Almost ready for public consumption" anymore.
Please let me know if you want a pull request from me instead of just thoughts and ideas.

The Readme in genivi-dev-platform.git has been updated, my personal opinion is still that the current meta-genivi-dev readme is suitable, and is included with all checkouts of genivi-dev-platform and as such does not need to be replicated there.


Add getwatch command.

+1

:+1:

+1

@ravigadde implemented your remarks

@analytically Still doesn't return resp.Node.Value.
Also thinking more there are a few issues/questions:

after-index is not specified.
If get fails and the key gets created before watch is called, watch will miss that. Need to set watch before get.
Is this supported on a directory? If the directory is not present, but created later, what should be returned?

I will let etcd experts comment more.

Regarding resp.Node.Value: cannot use resp.Node.Value (type string) as type *etcd.Response in return argument

watch blocks, so moving it before the get voids the intention of this command
on a directory it just says '/blah: is a directory' - I copied this behaviour from the watch command

I'm new to Go so I'm not sure how to fix your first point.

@analytically

go Watch(...) followed by get. If get succeeds, stop the watch using stop channel that was provided to Watch. If not, process events on the watch channel.
Regarding the return value, I said incorrectly resp.Node.Value. I meant to say that you are not returning the resp from Watch at all. value is nil at that point and that is what gets returned.

@ravigadde

the watch blocks, so the get never gets executed until there is a value
I copied this code from the watch command, and it sure is working correctly, returning actual values

@xiang90 any chance merging this one?

I like where it's going, but I'd also like to sort of set some etcd terminology. We've been talking about it as Watch and Wait. -- Watch continually watches for updates, and Wait is, much as you've done here, returning once it's been set once. It's a watch-until-first-value.
With some Wait cases you want the block to depend on the previous value. (In this case, value-not-found, actually) -- sometimes you just want to return if the value is anything but what you'd expect. (It's been updated before you can put the wait there)
So maybe we can shape this (which is looking pretty good) into a slightly more general wait subcommand. wait by itself merely waits unilaterally for the next value on the key and returns. wait --wait-empty or wait --wait-value=foo which does the check, and waits only if the value is what you've told it to expect (no value, or a specific value, respectively). Because you want to do it atomically and can't be guaranteed that the wait you're looking for has slipped in between two runs (etcdctl get && etcdctl wait) -- hence why you called it getwatch but I think the more general case is wait [precondition flag])
What do you think?

@analytically Once you get a free moment can you address the concerns raised by @barakmich?

@analytically I'm closing this due to inactivity, please feel free to reopen this once you are ready to resume the review process.


Multiple defstructs

Elixir n00b, bear with me. I put these 2 in my module:
defdata do
    East :: String.t()
    West :: String.t()
end

defdata do
    Dev :: String.t()
    Qa :: String.t()
    Prod :: String.t()
end

But it fails with:
== Compilation error in file lib/aws/types.ex ==
** (ArgumentError) defstruct has already been called for SDP.AWS.Types, defstruct can only be called once per module
    lib/aws/types.ex:35: (module)
    (elixir) lib/kernel/parallel_compiler.ex:121: anonymous fn/4 in Kernel.ParallelCompiler.spawn_compilers/1

If I only put 1, it's fine. Should I just put each one of these in their own module per file?

Cool.


[golden] How to compare multi-line strings with unpredictable values?

Ex: The stdout of docker build includes ids that will change.
golden expects exact values, but maybe we could support some way of templating things so that it can assert the actual result matches a template/pattern.  This could be in a different package, or just a different assertions (AssertPattern() or something).

I looked around for a library that could be used to parse this type of thing but I couldn't find anything that didn't just use regular expressions.

I went with this: https://github.com/docker/cli/pull/709/files, using a map of line -> check function. It seems to work well for this case.


fix toolbar position auto.

Thanks for your submission. This code was already there until https://github.com/peer-calls/peer-calls/commit/9e801fc9c9da42a1b8ecab71220ccfe5278debc8#diff-edfb47e9063b120db0df5b0175df0dcaL23, however the .dropdown-backdrop was not positioned correctly when tranform: translateX(-50%) was used so I had to remove it. See the screenshots below:
With margin-left: -168px:

With tranform: translateX(-50%):


79-BE/import-subscription

Import data from subscription.

We don't migrate this table right now, because it will be part of DSpace 7.5.


got "bad_request:invalid UTF-8 JSON" in test server

Hello, I met this error when trying to connect to the test server:
3/17/2022, 3:41:21 PM->could not connect to https://olstaste.vrtmrz.net/ls-706574657374323339 : obsidian
(bad_request:invalid UTF-8 JSON)

I have two machines, one runs win11 and another runs macOS Monterey, both with Obsidian v0.13.33, and they have the same error.

Sorry! I didn't notice this!
The test server rebooted! and a new connecting method will resolve troubles about connecting.
Could you please try v0.8.1?


Using importlib if on python 3

Thanks for the contribution. Tested locally and integrated as https://github.com/commontk/CTK/commit/da3fd7625ee08dc2e7911ddf272bf2099b0e5e54


Devices with Extended Advertising enabled are not visible in scan

Expected Behavior
Scan should return devices with Extended Advertising
Current Behavior
Scan shows devices with standard advertising, including scan response. Devices that have extended advertising enabled do not appear.
Steps to Reproduce

Turn on peripheral that utilizes extended advertisement
Ensure your device supports extended advertisement, some older phones and tablets do not even if they support bluetooth 5
Call startDeviceScan in react-native app
Verify that callback does not return your device
Open a Bluetooth scanning app like nRF Connect, device appears and extended advertisement data is availiable.
Disable extended advertisement on device
verify startDeviceScan callback picks up the device

Context
I am developing a device and a react-native app that are intended to talk to each other. I would like to use extended advertisement. After enabling extended advertisement in my device's firmware the device is visible to nRF Connect, but not to my react-native app using this library.

Library version: 2.0.2
Platform: Android 11 on a Samsung Galaxy Tab A7

I also encountered the same problem. How can I find it in NRF connect, but this library does not return, or is it incorrectly configured?

From what I understand there are features that are available in Bluetooth 5 that are optional and do not have to be supported for a device to be classified as Bluetooth 5-enabled. Extended Advertising is one of these optional Bluetooth 5 additions that not all devices support.
You can get the "nRF connect" app from the Play store and find the "Device Information" menu option and it will tell you what BT5 features your device supports. The device I was using, the Galaxy Tab 7 should support this function but this library does not.

There is a library between this one an underlying library that does the actual scan call the underlying one has been updated to support extended advertising scans. https://github.com/dariuszseweryn/RxAndroidBle/issues/774
The one in-between however appears to have been abandoned and has had no movement since 2021 https://github.com/dotintent/MultiPlatformBleAdapter/pulls?q=is%3Apr+is%3Aclosed so doesn't use the updated version that supports extended advertising.


fix: add a file guard to indicate if an environment is being installed

Fixes #1577
This adds a .guard file to the prefix which is locked using advisory guards and records the state of the environment. This allows detection if the installation of an environment was aborted and also ensures that if two processes run concurrently they will not interfere.

Should we do this in rattler?

Should we do this in rattler?

Yeah but Im not entirely sure about the API yet, so experimenting here for now. :)

I think this would be great in a high level transaction api

But fine to have it here for now, of course


Error: RuntimeError: index out of bounds

On Debian sid/unstable built
$ git log --oneline --no-decorate -1
33ef47cfb Merge "Normalize timestamp formatting throughout UI"

and captured the trace with
$ out/linux/tracebox -o trace_file.perfetto-trace --txt -c test/configs/scheduling.cfg
[667.455]          service.cc:253 Started traced, listening on @traced-p-471235 @traced-c-471235
[667.565]           probes.cc:104 Starting traced_probes service
[667.565]  probes_producer.cc:341 Connected to the service
[667.568]   perf_producer.cc:1200 Connected to the service
[667.568]    perfetto_cmd.cc:1051 Connected to the Perfetto traced service, TTL: 10s
[667.568] ng_service_impl.cc:1003 Configured tracing session 1, #sources:2, duration:10000 ms, #buffers:1, total buffer size:20480 KB, total sessions:1, uid:5272 session name: ""
[667.594]  probes_producer.cc:141 Ftrace setup (target_buf=1)
[667.595]    ftrace_procfs.cc:445 disabled ftrace in /sys/kernel/tracing/
[667.885]    ftrace_procfs.cc:442 enabled ftrace in /sys/kernel/tracing/
[677.569] ng_service_impl.cc:1970 FlushAndDisableTracing(1) done, success=1
[677.569]  probes_producer.cc:454 Producer stop (id=1)
[677.569]    ftrace_procfs.cc:445 disabled ftrace in /sys/kernel/tracing/
[677.821]    ftrace_procfs.cc:445 disabled ftrace in /sys/kernel/tracing/
[677.821]  probes_producer.cc:454 Producer stop (id=2)
[677.837]    perfetto_cmd.cc:1213 Wrote 4309655 bytes into trace_file.perfetto-trace

Opening this in the Web page results in:
To assist with debugging please attach or link to the trace you were viewing.

Viewed on: https://ui.perfetto.dev

Error: RuntimeError: index out of bounds
protozero::RingBufferMessageReader::Append(void const*, unsigned long)@https://ui.perfetto.dev/v34.0-1b8de4452/engine_bundle.js line 1600 > WebAssembly.Module:wasm-function[5767]:0x3aab8f
perfetto::trace_processor::Rpc::OnRpcRequest(void const*, unsigned long)@https://ui.perfetto.dev/v34.0-1b8de4452/engine_bundle.js line 1600 > WebAssembly.Module:wasm-function[5754]:0x3a82ae
trace_processor_on_rpc_request@https://ui.perfetto.dev/v34.0-1b8de4452/engine_bundle.js line 1600 > WebAssembly.Module:wasm-function[257]:0x1a2bf
createExportWrapper/<@https://ui.perfetto.dev/v34.0-1b8de4452/engine_bundle.js:1569:22
ccall@https://ui.perfetto.dev/v34.0-1b8de4452/engine_bundle.js:1184:19
onMessage@https://ui.perfetto.dev/v34.0-1b8de4452/engine_bundle.js:6972:34

stderr:

v34.0-1b8de4452 1b8de44522f33d371def110325bf31b847c1f5c4
UA: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0

With Canary I get:
To assist with debugging please attach or link to the trace you were viewing.

Viewed on: https://ui.perfetto.dev

CompileError: at offset 0: failed to match magic number

v34.0-5f456dbc0 5f456dbc00731d4dff20ae4e395cf06f96374a2d
UA: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0

It feels like the trace file is malformed. Can you attache the trace that you captured here?

There you go: trace_file.perfetto-trace.gz

Uhm, this file opens perfectly fine on ui.perfetto.dev both on Stable and autopush.
I tried:

Chrome (114.0.5735); both UI Stable and autopush --> ✅
Firefox-esr 102.11; UI: Stable --> ✅
Firefox  114.0.1; UI: Stable --> ✅

Try restarting your browser?

It loads fine in Mozilla Firefox (Debian package firefox 114.0-0). So some thing with Mozilla Nightly.
I updated Nightly<PHONE_NUMBER>2538), and I still get the error:
To assist with debugging please attach or link to the trace you were viewing.

Viewed on: https://ui.perfetto.dev

Error: RuntimeError: index out of bounds
protozero::RingBufferMessageReader::Append(void const*, unsigned long)@https://ui.perfetto.dev/v34.0-5f456dbc0/engine_bundle.js line 1600 > WebAssembly.Module:wasm-function[5770]:0x3b6b1f
perfetto::trace_processor::Rpc::OnRpcRequest(void const*, unsigned long)@https://ui.perfetto.dev/v34.0-5f456dbc0/engine_bundle.js line 1600 > WebAssembly.Module:wasm-function[5757]:0x3b40b6
trace_processor_on_rpc_request@https://ui.perfetto.dev/v34.0-5f456dbc0/engine_bundle.js line 1600 > WebAssembly.Module:wasm-function[290]:0x1e112
createExportWrapper/<@https://ui.perfetto.dev/v34.0-5f456dbc0/engine_bundle.js:1569:22
ccall@https://ui.perfetto.dev/v34.0-5f456dbc0/engine_bundle.js:1184:19
onMessage@https://ui.perfetto.dev/v34.0-5f456dbc0/engine_bundle.js:6972:34

THat sounds like a bug you should file against mozilla. Maybe something in their wasm runtime is doing something different?

In Mozilla’s Bugzilla I created ticket 1840708.

In Mozilla’s Bugzilla I created ticket 1840708.

Thanks for reporting this. We've fixed this in the latest Firefox Nightly. It was an issue with the Nightly-only (for now) WebAssembly.Function implementation when used with a bound function.

Thank you all for fixing this. I can verify it works with Mozilla Firefox (Nightly) 117.0a1<PHONE_NUMBER>3801).


Change Card Methods

Due to the recent Stripe dependency update, the find, get, update, and remove methods in the Card service are pointing to the incorrect Stripe methods. This PR updates the Card service to point to the updated methods (See Cards API reference).
This fixes the issue we faced in #68, and will resolve all card-related issues for anyone upgrading from a previous version of feathers-stripe.

Ah, I thought you were calling them directly in that issue, sorry for closing it prematurely. Thanks for the PR!

Fixed in v0.9.0


M> Dutch Version of Lerner & Nash Foster interview transcript

Goal: a DUTCH.srt file
stored in /RChain/Members/Marketing-Community Dev/YouTube
with a translated transcript in Dutch
Progress indicator: see the evolvement of the doc https://docs.google.com/document/d/105HIluXMni6iLST2fX2KLe7CVUULpN0Ct2USzqiqkIQ/edit?usp=drivesdk&ouid=114592096168227623218
Time: 1 week
Budget: $5000

there is d link for Dutch translation: https://docs.google.com/document/d/105HIluXMni6iLST2fX2KLe7CVUULpN0Ct2USzqiqkIQ/edit?usp=drivesdk&ouid=114592096168227623218

@Tonyprisca13 there is a need to work on your first comment, the links doesn't link.

The doc has been translated with google translate.
Er klopt geen bal van!!! Zet er maar een andere vertaler op. Dit wordt niks.

@lapin7  am working with pmoorman on review of the doc.

I'm happy to help here and can divide and conquer with whoever is working on this already. If someone can let me know the latest status and send through the doc, I can spend a few hours this week.

@dcpnlau I spoke with @Tonyprisca13 yesterday on Discord. He can't complete this issue, because he doesn't speak Dutch.
So: Right now, nobody is working on this issue.

@pmoorman am still on d issue got some Dutch friends who are will to help

@dcpnlau presently working on d review of doc

@dcpnlau  almost done. i will send you the file to review and edit where neccessary.

OK thanks. I'll see if I can make some time to make a start on this.
On Mon, Feb 5, 2018 at 12:53 PM, pmoorman<EMAIL_ADDRESS>wrote:

@dcpnlau https://github.com/dcpnlau I spoke with @Tonyprisca13
https://github.com/tonyprisca13 yesterday on Discord. He can't complete
this issue, because he doesn't speak Dutch.
So: Right now, nobody is working on this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rchain/Members/issues/283#issuecomment-362961298, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AhCvhr__KUtm8-EpZ8ENqT2_UbXiSoXXks5tRl8ygaJpZM4R3391
.

Alright sounds good. Sorry - only saw the other messages now.
Sent on the go

On 5 Feb 2018, at 16:19, Tonyprisca13<EMAIL_ADDRESS>wrote:
@dcpnlau almost done. i will send you the file to review and edit where neccessary.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I have some time too, to contribute. Is it something we can do together @dcpnlau ?

please send me ur email@dcpnlau

Is this project almost finished @tonyprisca13 , or is help still needed to come to a result?

Hi @peetklasen, it was sent to me. Happy to forward to you and we can divide and conquer. Can you send me your email address? I’m dcpnlau on Discord.
Sent on the go

On 9 Feb 2018, at 09:31, peetklasen<EMAIL_ADDRESS>wrote:
Is this project almost finished @Tonyprisca13 , or is help still needed to come to a result?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

My email address is<EMAIL_ADDRESS>Good idea to collaborate and divide the job. Are you Dutch? ( I am)

@dcnplau My email address is<EMAIL_ADDRESS>Great idea to collaborate and divide the job. Are you Dutch? ( I am)

I'm working on the document together with @dcpnlau Can I be assigned?

@peetklasen Great!

So: just to get things clear: the document has been automatically translated with Google translate.
I guess @tonyprisca13 did this job.
The actual translation has still to be done then.
The actual translation from Google translate Dutch to real Dutch (I mean Dutch that makes sense) will be done bij @dcpnlau and me. Afterwards @dcpnlau and me will review each others translations.

Just to get things clear: the original document has been automatically translated with Google translate.  I guess @tonypricsa13 did this job.
Afterwards this document has to be translated to real Dutch (I mean Dutch that makes sense). This job will be done by @dcpnlau and me. Afterwards dcpnlau and me will review each others translations.

@peetklasen writes:

I am working on the translation and will start with lines 800 - 1625. @dcnplau will translate lines 1 - 800. Next we will review each others translations. Until now I have translated lines 800 - 1100 (first draft). Tomorrow I will update the progress.
Good work! Do let me know if you will be needing any assistance from me.

Lines 800 - 1500 have been translated (in draft). For these lines I have now also added the English transcript. This makes reviewing easier. https://docs.google.com/document/d/105HIluXMni6iLST2fX2KLe7CVUULpN0Ct2USzqiqkIQ/edit

@dcplau has translated lines 1-70. She does not have enough time to finish her part of the translation. We have agreed that I will also translate lines 70 - 800.
I'll keep you informed about the progress.

Mooi zo. Ga zo door :-)
Dan kun je de rewards ook aanpassen voor 28 Feb.
https://docs.google.com/spreadsheets/d/1uxuxx8YN17KCIWcH1cUoGuSm2hAnIya2iAc6wxoaq1o/edit#gid=294454559&range=C2636:N2643

283

M> Dutch Version of Lerner & Nash Foster interview transcript
Marketing
3
OPEN
$ 2,000.00
-50.00
1,076.32
2,050.00
Member
Team + Pers Reduce %

283

M> Dutch Version of Lerner & Nash Foster interview transcript
Marketing

OPEN
$ 2,000.00

131.26
250.00
Tonyprisca13
12.50%

283

M> Dutch Version of Lerner & Nash Foster interview transcript
Marketing

OPEN
$ 2,000.00

0.00
0.00
BelovedAquila
0.00%

283

M> Dutch Version of Lerner & Nash Foster interview transcript
Marketing

OPEN
$ 2,000.00

0.00
0.00
lapin7
0.00%

283

M> Dutch Version of Lerner & Nash Foster interview transcript
Marketing

OPEN
$ 2,000.00

446.28
850.00
dcpnlau
42.50%

283

M> Dutch Version of Lerner & Nash Foster interview transcript
Marketing

OPEN
$ 2,000.00

446.28
850.00
peetklasen
42.50%

283

M> Dutch Version of Lerner & Nash Foster interview transcript
Marketing

OPEN
$ 2,000.00

0.00
0.00
kaka56
0.00%

283

M> Dutch Version of Lerner & Nash Foster interview transcript
Marketing

OPEN
$ 2,000.00

52.50
100.00
pmoorman
5.00%

I made some adjustments to the rewards. I am not so used to the voting system. Hope it is OK like this.
I have translated lines 70 - 500 and 800 - 1625 and will translate lines 500 - 800 in the next few days.

The job reaches completion  It looks as if @BelovedAquila also had a role in the process. To me it is not clear what this role is or has been.

@BelovedAquila is indeed listed as budget-setter and as reward-setter. However he doesn't get a reward %. So it's fine.  The collaborators have each the power of carrots and sticks so to speak.

2,000.00
Member
100.00%

275.00
Tonyprisca13
13.75%

0.00
BelovedAquila
0.00%

0.00
lapin7
0.00%

225.00
dcpnlau
11.25%

1,500.00
peetklasen
75.00%

0.00
kaka56
0.00%

0.00
pmoorman
0.00%

0.00
dckc
0.00%

@peetklasen I did an adjustment on it please check it up

I have translated lines 70 to 1625 from the english transcript to Dutch in draft. I have reviewed lines 1-70 that had been translated by @dcnplau. There are still some lines that I have to check / improve. These are marked red. I will also make a comparison with the German translation. That is a nice translation and this can be helpful to improve the current work. I think I can change the status of the document to "final" within a few days. Comments are welcome.

This has been done, so I am closing this, feel free to re-open this if you think it should be open.


refactor: etcd rpc error compat

Closes: #415
Please briefly answer these questions:

what problem are you trying to solve? (or if there's no problem, what's the motivation for this change?)

what changes does this pull request make?

are there any non-obvious implications of these changes? (does it break compatibility with previous versions, etc)

Please squash these eight commit into one or two commits.


Unable to login with local admin account after update

In the updates following 0.6.5, I can no longer login using my admin account. The account is a local account of type 0. Instead, it tries to log in via LDAP, which fails. I see this in the code:
func (source *LoginSource) BeforeSet(colName string, val xorm.Cell) {
switch colName {
case "type":
	switch LoginType((*val).(int64)) {
	case LDAP, DLDAP:
		source.Cfg = new(LDAPConfig)
	case SMTP:
		source.Cfg = new(SMTPConfig)
	case PAM:
		source.Cfg = new(PAMConfig)
	default:
		panic("unrecognized login source type: " + com.ToStr(*val))
	}
}
}

Since the type is 0 for local accounts, it tries LDAP. I'm not too sure how to fix this other than reverting back to 0.6.5

Thanks your feedback!

Instead, it tries to log in via LDAP, which fails.

How do you know?

How do you know?

I can see it in the logs that it attempts to bind via LDAP and does a search on the username.

Same as above.

I checked the DB in the login_sources table.

Thanks.

I checked the DB in the login_sources table.

login_sources table tells you nothing about a account's login type.
Check user table login_type of your admin account.

Sorry I meant the login_type for the user. The login type is 0 as expected.

Thanks.
Then I think you are login without exactly same username or email, so Gogs thinks you're trying to login with new user.
Or, the database you think which Gogs connects to isn't the one gogs actually connected.

But when I downgrade the gogs version to 0.6.5, it works. I'm pretty sure it's not the DB then...

There are a lot information is missing in your description, so I need detailed steps about how you upgrade.

I upgrade using the debian packages from packager.io and use
sudo apt-get upgrade

In that case please check the custom app.ini for db information, some people reported that packager.io may overwrite some configs.

What should I look for? All I see in app.ini are settings to connect to the mysql DB. There isn't anything about login_types
[database]
; Either "mysql", "postgres" or "sqlite3", it's your choice
DB_TYPE = mysql
HOST = <IP_ADDRESS>:3306
NAME = gogs
USER = *******
PASSWD = ******
; For "postgres" only, either "disable", "require" or "verify-full"
SSL_MODE = disable
; For "sqlite3" only
PATH = data/gogs.db

Looks good to me. Can you register a new account after upgrade see if you become an admin automatically.

sorry for the late reply. I boiled it down to a Chrome issue. When I use other browsers or when I use Chrome in the incognito, it works fine. I've tried deleting cookies and cache but I still have this issue. Do you know what it could be from?

@samlcharreyron Great, finally we found the problem!
If it's an issue about auto-fill of form, section Delete Autofill info for computers and Chromebooks on https://support.google.com/chrome/answer/142893?hl=en should help.

Ok I figured it out... I had a typo in the autofilled username in Chrome. Not sure why/if this was only causing a problem in the newer versions of Gogs. Thanks for your help!!

:trollface:


Update scalacheck-1-15 to <IP_ADDRESS>

Updates org.scalatestplus:scalacheck-1-15 from <IP_ADDRESS> to <IP_ADDRESS>.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalatestplus", artifactId = "scalacheck-1-15" } ]

labels: test-library-update, commit-count:1

Codecov Report

Merging #275 (d1b67a1) into master (1f1a458) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #275   +/-   ##
=======================================
  Coverage   96.19%   96.19%
=======================================
  Files           4        4
  Lines         105      105
  Branches        6        4    -2
=======================================
  Hits          101      101
  Misses          4        4

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1f1a458...d1b67a1. Read the comment docs.


Restore dbt. prefix for all migrated cross-db macros

resolves #690
This is a:

[ ] documentation update
[x] bug fix with no breaking changes
[ ] new functionality
[ ] a breaking change

All pull requests from community contributors should target the main branch (default).
Description & motivation
Adding dbt. prefix(namespace) to all the migrated cross database macros to solve the bug that caused unexpected behavior when a project already had a macro named the same as one of the migrated cross-db macros.
I did not touch the macro call in the test folders (they still call dbt_utils
Checklist

[x] This code is associated with an Issue which has been triaged and accepted for development.
[ ] I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)

[ ] BigQuery
[x] Postgres
[ ] Redshift
[ ] Snowflake

[ ] I followed guidelines to ensure that my changes will work on "non-core" adapters by:

[ ] dispatching any new macro(s) so non-core adapters can also use them (e.g. the star() source)
[ ] using the limit_zero() macro in place of the literal string: limit 0
[x] using dbt.type_* macros instead of explicit datatypes (e.g. dbt.type_timestamp() instead of TIMESTAMP

[ ] I have updated the README.md (if applicable)
[ ] I have added tests & descriptions to my models (and macros if applicable)
[x] I have added an entry to CHANGELOG.md

@SimonQuvang bless you!
Could you change this to target the utils-v1 branch please?

@joellabes Changed to utils-v1 and solved the merge conflict


Restart nginx automatically and remove circular dependency

Task linked: QF-1701 Fix docker nginx does not restart


Draft of the spec

The spec is currently being drafted here. It'll be moved into an .md file in this repository shorly.
https://docs.google.com/document/d/1pGJiQhA_5lZsCeswsKDm5v_brkeqaT1Bmn4zANCynGg/edit?usp=sharing

deprecated by the diff in #2


Clarify TVTensor shapes

📚 The doc issue
TVTensor is documented as being a subclass of torch.Tensor specifically for transforms. Perhaps it could be added that they only constrain the shape of torch.Tensor?
For example, I only use the utility functions of transforms.v2 and, when to_image referred me to Image, I still had to check the source code to confirm it is just a torch.Tensor of shape (C x H x W).
Suggest a potential alternative/fix
No response

Hi @mantasu , we've added the main relevant info about TVTensors in this tutorial https://pytorch.org/vision/main/auto_examples/transforms/plot_transforms_getting_started.html#what-are-tvtensors  which is linked to as the main entrypoint for all things related to TVTensors / TransformsV2. Do you think it already contains the info you were looking for, or should we edit it a bit?

My only suggestion would be to add somewhere that TVTensors are just extensions of torch.Tensor with specified shape constraints. But it is just a preference and the tutorial already helps a lot, so this could be safely closed~


[ISSUE #1107]Replace ArcRefCellWrapper with ArcMut

Which Issue(s) This PR Fixes(Closes)

Fixes #1107
Brief Description

How Did You Test This Change?

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥


Autocomplete after colons make coding difficult

After I write something like
try:

Spyder's autocomplete tries to give me suggestions and then I end up putting something nonsense at the end of the colon when I hit return. Insted I find myself typing
try: (then right arrow key)

and that takes up some extra time. Can we not have autocomplete after the colons?
Cheers,
Trav

Should be related to #10833


Fix 'prepare_flexreceptor.py' and 'prepare_gpf.py' files to run with …

…Python3
Signed-off-by: Vitalii Koshura<EMAIL_ADDRESS>

Hi @AenBleidd
Unfortunately these scripts depend on MGLTools, which is written in Python2 and uses old libraries that are now deprecated. MGLTools has its own Python version, and these scripts are meant to be run with that Python version.
We are far more likely to replace MGLTools than to update it, so I'll close this PR.
In any case, thank you.


METRON-256: Make the PCap values returned ordered by timestamp

Right now we are not specifying the partitioner for the MR job to filter PCaps as part of PCap retrieval, so we are getting back packets in the wrong order.

+1

+1 pending once the transient issues in the CI build is resolved


Use the classpath obtained by the launcher for metabuild

Ref #4183
Fixes #3436
This implements isMetaBuild setting that is explicitly for meta build only,
unlike sbtPlugin setting which can be used for both meta build and plugin development purpose.
Fixes #4437
Until now, sbt was resolved twice once by the launcher, and the second time by the metabuild.
This excludes sbt from the metabuild graph, and instead uses app classpath from the launcher.

@muuki88 scripted should make sure that the builds load. I've manually ran reload plugins and then checked show update and show externalDependencyClasspath.

Sounds fair :+1:

Here's a preliminary benchmark running git clean -fdx then time sbt exit on Akka build:
sbt 1.2.6
sbt exit  149.25s user 7.21s system 359% cpu 43.491 total
sbt exit  144.66s user 6.99s system 345% cpu 43.904 total
sbt exit  150.91s user 6.95s system 349% cpu 45.174 total

sbt 1.3.0-bin-LOCAL20181109
sbt exit  137.83s user 6.93s system 354% cpu 40.823 total
sbt exit  136.84s user 6.71s system 365% cpu 39.250 total
sbt exit  133.40s user 6.78s system 353% cpu 39.680 total

So median improved from  43.904s to 39.680s, around 4s faster.


Demo on theme site is broken

Hello @aerohub,
to what url are you referring?

Well, i told about this one. It went to unstyled demo. But now it is okay, sorry

Well, i told about this one. It went to unstyled demo. But now it is okay, sorry

I thought some link would be broken according to the issue title and tested all of them. However, what do you mean with "It went to unstyled demo"?
I'm sorry if I miss anything :smile:

It was this way:

I clicked on link in repo description
And this was opened

Ok, the demo on the theme site is broken. Thanks for reporting this issue :+1:
I'll investigate what causes the issue.

Ok, glad to help)

I'm closing this issue since the demo is working fine via https.


Move Meltano handbook to meltano.com

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1252
Originally created by @DouweM on 2019-11-04 15:26:45

Meltano's handbook currently lives inside the GitLab handbook: https://about.gitlab.com/handbook/meltano/.
It makes sense to have a page that provides context to other people at GitLab on what it is that we do, and this page has served us well so far, but as Meltano has been growing and is quickly starting to look and behave more like a company in its own right than a team in the GitLab organization, it also deserves a dedicated handbook!
One of the purposes of the handbook will be to communicate to potential new team members what it is that we do, how we like to do it, and what it may be like to join the team and work with us.
This handbook should contain:

Cross-links to the GitLab handbook where appropriate
Most of what's currently on https://about.gitlab.com/handbook/meltano/
Some things that are currently in the docs, like:

https://www.meltano.com/docs/roadmap.html
https://www.meltano.com/docs/contributing.html#demo-day

Generally:

Processes
Calendar, common meetings
Team
Core team?

The entire GitLab handbook, and especially the Data team's handbook at https://about.gitlab.com/handbook/business-ops/data-team/, will serve as inspiration.
In terms of where the handbook could live, Danielle suggested about.meltano.com following the example set by about.gitlab.com, but I think that makes less sense here. about.gitlab.com exists to host the marketing website and handbook because gitlab.com is already reserved for the SaaS itself, but we don't have that restriction and could just use meltano.com/handbook.
In terms of stack, we could go with a Git repo, a static site generator, and GitLab Pages, like at https://about.gitlab.com/, or we could use a dedicated tool like https://notion.so (example: https://handbook.remote.com/). I'm currently inclined to go with the former approach since we're all comfortable with Git and the MR flow, and since the Web IDE actually makes it pretty straight forward to quickly make changes.
The most boring solution appears to be to build this on top of the existing Vuepress installation at meltano.com, with path meltano.com/handbook, although that would mean housing the handbook in the very same repo that houses the docs and the project code itself. I wouldn't want to pull the docs out of that repo, but housing the marketing website and handbook in a separate repo (as we've done with about.gitlab.com) does feel more appropriate since these are not attached to a particular version of the code.
We may end up with a marketing website at meltano.com, a handbook at meltano.com/handbook, and product documentation at docs.meltano.com.
To do:

[ ] Decide where handbook will live
[ ] Decide on stack
[ ] Move existing content over
[ ] Add missing content

View 13 previous comments from the original issue on GitLab


ROX-18291: backport to release-4.1

Description
Backport to release-4.1 branch.

/retest

/retest

hmm pretty much everything failing...

/retest

hmm pretty much everything failing...

The 4.1 branch was pretty unstable, but this is too much. The operator ones definitely were not failing.

The problem seems to be that the job to build the operator image fails in https://github.com/stackrox/stackrox/actions/runs/6406757405/job/17392024256.

The problem seems to be that the job to build the operator image fails in https://github.com/stackrox/stackrox/actions/runs/6406757405/job/17392024256.

Yes and it fails because (thanks @porridge for noticing this):
build-and-push-operator (RHACS_BRANDING)
System.IO.IOException: No space left on device : '/home/runner/runners/2.309.0/_diag/Worker_20231005-125427-utc.log'

/retest

Ok now it's looking much more reasonable. I believe the remaining failures are unrelated to this PR.

I'll go ahead with the merge.


Remove the properties of a record class from all Matrix types.

Matrices probably shouldn't be easily copyable to save on memory. It's kind of unnecessary and if need be, a Clone() function will be available.

This has been completed.


Fix the error with selected packages being undefined

Sometimes, with certain customizations, the blueprint fails to depsolve. I do not have an exact example that fails but a good way to replicate is to:

Create a new blueprint and fully customize it.
Reload the page.
Select that newly created blueprint

Loading this blueprint will make a depsolve call which will result in packages: [undefined]

I unfortunately have been unable to replicate. It occurred while I was prepping for the demo but I'm unsure what actually caused it.


Can't control Thermostat after updating to 2.0.4

Describe The Bug:
After updating the plugin to v2.0.4 I can't control my Amazon Smart Thermostat anymore, rollbacking to v2.0.3 seems to fix the issue.
Through the application the Thermostat appears as unreachable, the cached temperature is shown alongside a status message "No response". No matter what kind of update you do in the details screen it will revert back to its previously cached state.

To Reproduce:

Just update to v2.0.4 while using a regular "Amazon Smart Thermostat", Device and Manufactorer Software Version both "16975104", then check the Home app. The thermostat will appear greyed out as it was off (which is not), a "No response" label is shown and whatever you do it will revert back to it's OFF state in its details. I also tried removing the device from HB cache but it didn't change.
As soon as you revert back to plugin v2.0.3 everything appears to be working perfectly without changing anything else.
Expected behavior:

Logs:
[12/12/2023, 14:53:02] [homebridge-alexa-smarthome] Launched child bridge with PID 12956
[12/12/2023, 14:53:02] Registering platform 'homebridge-alexa-smarthome.HomebridgeAlexaSmartHome'
[12/12/2023, 14:53:02] [homebridge-alexa-smarthome] Loaded homebridge-alexa-smarthome v2.0.4 child bridge successfully
[12/12/2023, 14:53:02] Loaded 1 cached accessories from cachedAccessories.0E8E7FEBD75C.
[12/12/2023, 14:53:02] [homebridge-alexa-smarthome] Loading accessory from cache: Thermostat
[12/12/2023, 14:53:02] [homebridge-alexa-smarthome] Alexa-Remote: cookie was provided
[12/12/2023, 14:53:03] Homebridge v1.7.0 (HAP v0.11.1) (homebridge-alexa-smarthome) is running on port 53204.
[12/12/2023, 14:53:03] [homebridge-alexa-smarthome] Alexa-Remote: Authentication checked: true
[12/12/2023, 14:53:03] [homebridge-alexa-smarthome] Alexa-Remote: Change Base URL for API calls to na-api-alexa.amazon.com
[12/12/2023, 14:53:04] [homebridge-alexa-smarthome] Successfully authenticated Alexa account.
[12/12/2023, 14:53:04] [homebridge-alexa-smarthome] Found 1 devices connected to the current Alexa account.
[12/12/2023, 14:53:04] [homebridge-alexa-smarthome] BEGIN devices connected to Alexa account

 [
  {
    "displayName": "Thermostat",
    "deviceType": "THERMOSTAT"
  }
]

END devices connected to Alexa account
[12/12/2023, 14:53:04] [homebridge-alexa-smarthome] Found all 1 devices in plugin settings.
[12/12/2023, 14:53:04] [homebridge-alexa-smarthome] Updating device states
[12/12/2023, 14:53:04] [homebridge-alexa-smarthome] Thermostat ::: Attempting to add accessory(s) for device: {
  "id": "2aafd215-a3d1-4c3c-9193-baef63b85a5a",
  "displayName": "Thermostat",
  "description": "Amazon Smart Thermostat",
  "supportedProperties": [
    "setTargetTemperature",
    "setModeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_5",
    "setRangeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_1",
    "setRangeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_2"
  ],
  "supportedTriggers": [
    "temperatureSensorTrigger"
  ],
  "supportedOperations": [
    "setTargetTemperature",
    "setModeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_5",
    "setRangeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_1",
    "setRangeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_2"
  ],
  "availability": "AVAILABLE",
  "icon": {
    "@iconType": "SmartHomeApplianceType",
    "value": "THERMOSTAT"
  },
  "providerData": {
    "enabled": true,
    "relationships": [],
    "categoryType": "APPLIANCE",
    "deviceType": "THERMOSTAT",
    "dmsDeviceIdentifiers": [
      {
        "deviceSerialNumber": "REDACTED",
        "deviceType": "A39QOBV8YPBZIY"
      }
    ]
  }
}
[12/12/2023, 14:53:04] [homebridge-alexa-smarthome] Thermostat ::: Current state: [
  {
    "namespace": "Alexa.ThermostatController.Schedule",
    "name": "scheduleEnabled",
    "value": true
  },
  {
    "namespace": "Alexa.ThermostatController",
    "name": "targetSetpoint",
    "value": {
      "value": 60,
      "scale": "FAHRENHEIT"
    }
  },
  {
    "namespace": "Alexa.Energy.DemandResponseController",
    "name": "eventStatus",
    "value": {
      "eventId": "",
      "status": "NO_EVENT",
      "activeSignals": []
    }
  },
  {
    "namespace": "Alexa.EndpointHealth",
    "name": "connectivity",
    "value": {
      "value": "OK"
    }
  },
  {
    "namespace": "Alexa.ThermostatController.Configuration",
    "name": "allowedTemperatureRange",
    "value": {
      "heating": {
        "minimum": {
          "value": 50,
          "scale": "FAHRENHEIT"
        },
        "maximum": {
          "value": 87,
          "scale": "FAHRENHEIT"
        }
      },
      "cooling": {
        "minimum": {
          "value": 53,
          "scale": "FAHRENHEIT"
        },
        "maximum": {
          "value": 90,
          "scale": "FAHRENHEIT"
        }
      }
    }
  },
  {
    "namespace": "Alexa.ThermostatController.Schedule",
    "name": "adaptiveRecoveryEnabled",
    "value": true
  },
  {
    "namespace": "Alexa.ThermostatController.Configuration",
    "name": "temperatureScale",
    "value": "FAHRENHEIT"
  },
  {
    "namespace": "Alexa.TemperatureSensor",
    "name": "preciseTemperature",
    "value": {
      "value": 64.859375,
      "scale": "FAHRENHEIT"
    }
  },
  {
    "namespace": "Alexa.HumiditySensor",
    "name": "relativeHumidity",
    "value": 32
  },
  {
    "namespace": "Alexa.ThermostatController.HVAC.Components",
    "name": "coolerOperation",
    "value": "OFF"
  },
  {
    "namespace": "Alexa.ThermostatController.HVAC.Components",
    "name": "fanOperation",
    "value": "OFF"
  },
  {
    "namespace": "Alexa.AutomationManagement",
    "name": "automationStatuses",
    "value": [
      {
        "status": "AUTOMATED",
        "capability": "Alexa.ThermostatController"
      }
    ]
  },
  {
    "namespace": "Alexa.ModeController",
    "name": "mode",
    "value": "2",
    "instance": "5"
  },
  {
    "namespace": "Alexa.ThermostatController",
    "name": "thermostatMode",
    "value": "HEAT"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 3,
    "instance": "1"
  },
  {
    "namespace": "Alexa.TemperatureSensor",
    "name": "temperature",
    "value": {
      "value": 65,
      "scale": "FAHRENHEIT"
    }
  },
  {
    "namespace": "Alexa.ThermostatController",
    "name": "adaptiveRecoveryStatus",
    "value": "INACTIVE"
  },
  {
    "namespace": "Alexa.ThermostatController.Configuration",
    "name": "setupState",
    "value": "REMOTE_CONTROL"
  },
  {
    "namespace": "Alexa.ThermostatController.HVAC.Components",
    "name": "primaryHeaterOperation",
    "value": "OFF"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 3,
    "instance": "2"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 3,
    "instance": "3"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 75,
    "instance": "8"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 3,
    "instance": "6"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 68,
    "instance": "7"
  }
]
[12/12/2023, 14:53:04] [homebridge-alexa-smarthome] Thermostat ::: Range capabilities: {}
[12/12/2023, 14:53:04] [homebridge-alexa-smarthome] Restored existing accessory from cache: Thermostat
[12/12/2023, 14:53:07] [homebridge-alexa-smarthome] Obtained device states from cache
[12/12/2023, 14:53:07] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 18.3
[12/12/2023, 14:53:07] [homebridge-alexa-smarthome] Obtained device states from cache
[12/12/2023, 14:53:07] [homebridge-alexa-smarthome] Obtained device states from cache
[12/12/2023, 14:53:07] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)
[12/12/2023, 14:53:07] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1
[12/12/2023, 14:53:07] [homebridge-alexa-smarthome] Obtained device states from cache
[12/12/2023, 14:53:07] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 15.6
[12/12/2023, 14:53:27] [homebridge-alexa-smarthome] Obtained device states from cache
[12/12/2023, 14:53:27] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)
[12/12/2023, 14:53:28] [homebridge-alexa-smarthome] Obtained device states from cache
[12/12/2023, 14:53:28] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)
[12/12/2023, 14:53:30] [homebridge-alexa-smarthome] Obtained device states from cache
[12/12/2023, 14:53:30] [homebridge-alexa-smarthome] Obtained device states from cache
[12/12/2023, 14:53:30] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)
[12/12/2023, 14:53:30] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 15.6
[12/12/2023, 14:53:30] [homebridge-alexa-smarthome] Obtained device states from cache
[12/12/2023, 14:53:30] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 18.3
[12/12/2023, 14:53:33] [homebridge-alexa-smarthome] Obtained device states from cache
[12/12/2023, 14:53:33] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 18.3
[12/12/2023, 14:53:33] [homebridge-alexa-smarthome] Obtained device states from cache
[12/12/2023, 14:53:33] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 15.6
[12/12/2023, 14:53:33] [homebridge-alexa-smarthome] Obtained device states from cache
[12/12/2023, 14:53:33] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[12/12/2023, 14:53:42] [homebridge-alexa-smarthome] Thermostat - Triggered set target temperature: 18.900000000000002

[12/12/2023, 14:53:50] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:53:50] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1

[12/12/2023, 14:53:50] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:53:50] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[12/12/2023, 14:53:51] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:53:51] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[12/12/2023, 14:53:52] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:53:52] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 18.3

[12/12/2023, 14:53:52] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:53:52] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 18.9

[12/12/2023, 14:53:52] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:53:52] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:53:52] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[12/12/2023, 14:53:53] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1

[12/12/2023, 14:53:55] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:53:55] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:53:55] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[12/12/2023, 14:53:55] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 18.9

[12/12/2023, 14:53:55] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:53:55] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 18.3

[12/12/2023, 14:53:55] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:53:55] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1

[12/12/2023, 14:54:11] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:54:11] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:54:11] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[12/12/2023, 14:54:11] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 18.3

[12/12/2023, 14:54:11] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:54:11] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 18.9

[12/12/2023, 14:54:11] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:54:11] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1

[12/12/2023, 14:54:15] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:54:15] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[12/12/2023, 14:54:16] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:54:16] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[12/12/2023, 14:54:18] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:54:18] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 18.9

[12/12/2023, 14:54:18] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:54:18] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1

[12/12/2023, 14:54:18] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:54:18] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:54:18] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[12/12/2023, 14:54:18] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 18.3

[12/12/2023, 14:54:20] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:54:20] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:54:20] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[12/12/2023, 14:54:20] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 18.9

[12/12/2023, 14:54:20] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:54:20] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 18.3

[12/12/2023, 14:54:20] [homebridge-alexa-smarthome] Obtained device states from cache

[12/12/2023, 14:54:20] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1

It is worth noting that, while collecting this logs, I tried to change the temperature on the Home app and always got DeviceOffline(ENDPOINT_UNREACHABLE) to appear in the logs after each attempt.
Plugin Config:
{
    "devices": [
        "Thermostat"
    ],
    "auth": {
        "refreshInterval": 4,
        "proxy": {
            "clientHost": "REDACTED",
            "port": REDACTED
        }
    },
    "amazonDomain": "amazon.com",
    "language": "en-US",
    "performance": {
        "cacheTTL": 300,
        "backgroundRefresh": true
    },
    "debug": true,
    "_bridge": {
        "username": "REDACTED",
        "port": 53204
    },
    "platform": "HomebridgeAlexaSmartHome"
}

Screenshots:

On v2.0.4

As soon as I rollback to v2.0.3, no other changes applied
Environment:

Plugin Version: 2.0.4
Homebridge Version: 1.7.0
Node.js Version:  20.10.0
NPM Version: 10.2.3
Operating System: Raspbian GNU/Linux Bullseye (11)

I also have the amazon smart thermostats and encountered the exact same issue. Rolling back to v2.0.3 also brings them back into configurable status. Happy to test things if you have any requests.

humm, worked fine on my thermostat , I ll check tonight to adjust the code based on the logs shared. I ll let you know once I update, in the meantime, can you fallback to 2.0.3

Yeah I've been staying on 2.0.3. If there's anything I can do to help just let me know

I created a PR to fix the issue, I don't have the device to test, but should be fine based on the logs shared :)

This issue should be fixed in 2.0.5

This issue should be fixed in 2.0.5

Still having No Response on 2.0.5

hey @QuarterSwede, thanks for testing,  can you please share the logs ? I need to see them since I don't have your device.

@nyirsh can you please test on your side and share the logs if you still have issues ?

[12/27/2023, 12:54:23 PM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Target Heating Cooling State' was slow to respond! See https://homebridge.io/w/JtMGR for more info. [12/27/2023, 12:54:23 PM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Current Temperature' was slow to respond! See https://homebridge.io/w/JtMGR for more info. [12/27/2023, 12:54:23 PM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Target Temperature' was slow to respond! See https://homebridge.io/w/JtMGR for more info. [12/27/2023, 12:54:23 PM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Temperature Display Units' was slow to respond! See https://homebridge.io/w/JtMGR for more info. [12/27/2023, 12:54:29 PM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Target Heating Cooling State' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info. [12/27/2023, 12:54:29 PM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Current Temperature' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info. [12/27/2023, 12:54:29 PM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Target Temperature' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info. [12/27/2023, 12:54:29 PM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Temperature Display Units' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info. [12/27/2023, 3:55:45 PM] [homebridge-alexa-smarthome] Restarting child bridge... [12/27/2023, 3:55:45 PM] Got SIGTERM, shutting down child bridge process... [12/27/2023, 3:55:50 PM] [homebridge-alexa-smarthome] Child bridge process ended [12/27/2023, 3:55:50 PM] [homebridge-alexa-smarthome] Process Ended. Code: 143, Signal: null [12/27/2023, 3:55:57 PM] [homebridge-alexa-smarthome] Restarting Process... [12/27/2023, 3:55:57 PM] [homebridge-alexa-smarthome] Launched child bridge with PID 3605 [12/27/2023, 3:55:57 PM] Registering platform 'homebridge-alexa-smarthome.HomebridgeAlexaSmartHome' [12/27/2023, 3:55:57 PM] [homebridge-alexa-smarthome] Loaded homebridge-alexa-smarthome v2.0.5 child bridge successfully [12/27/2023, 3:55:57 PM] Loaded 1 cached accessories from cachedAccessories.0E633101DC02. [12/27/2023, 3:55:57 PM] [homebridge-alexa-smarthome] Loading accessory from cache: Thermostat [12/27/2023, 3:55:57 PM] Homebridge v1.7.0 (HAP v0.11.1) (homebridge-alexa-smarthome) is running on port 37870. [12/27/2023, 3:55:57 PM] [homebridge-alexa-smarthome] Failed to initialize connection to Alexa. - Error while checking Authentication: Error: getaddrinfo ENOTFOUND alexa.amazon.com [12/27/2023, 3:55:59 PM] [homebridge-alexa-smarthome] Restored existing accessory from cache: Thermostat [12/27/2023, 3:56:33 PM] [homebridge-alexa-smarthome] Launched child bridge with PID 3678 [12/27/2023, 3:56:33 PM] [homebridge-alexa-smarthome] Loaded homebridge-alexa-smarthome v2.0.5 child bridge successfully [12/27/2023, 3:56:33 PM] Registering platform 'homebridge-harmony.HarmonyHubWebSocket' [12/27/2023, 3:56:33 PM] [homebridge-alexa-smarthome] Loading accessory from cache: Thermostat [12/27/2023, 3:56:36 PM] [homebridge-alexa-smarthome] Restored existing accessory from cache: Thermostat [12/27/2023, 3:58:50 PM] [homebridge-alexa-smarthome] Restarting child bridge... [12/27/2023, 3:58:50 PM] Got SIGTERM, shutting down child bridge process... [12/27/2023, 3:58:55 PM] [homebridge-alexa-smarthome] Child bridge process ended [12/27/2023, 3:58:55 PM] [homebridge-alexa-smarthome] Process Ended. Code: 143, Signal: null [12/27/2023, 3:59:02 PM] [homebridge-alexa-smarthome] Restarting Process... [12/27/2023, 3:59:02 PM] [homebridge-alexa-smarthome] Launched child bridge with PID 3981 [12/27/2023, 3:59:02 PM] Registering platform 'homebridge-alexa-smarthome.HomebridgeAlexaSmartHome' [12/27/2023, 3:59:02 PM] [homebridge-alexa-smarthome] Loaded homebridge-alexa-smarthome v2.0.3 child bridge successfully [12/27/2023, 3:59:02 PM] Loaded 1 cached accessories from cachedAccessories.0E633101DC02. [12/27/2023, 3:59:02 PM] [homebridge-alexa-smarthome] Loading accessory from cache: Thermostat [12/27/2023, 3:59:02 PM] Homebridge v1.7.0 (HAP v0.11.1) (homebridge-alexa-smarthome) is running on port 37870. [12/27/2023, 3:59:03 PM] [homebridge-alexa-smarthome] Failed to initialize connection to Alexa. - Error while checking Authentication: Error: getaddrinfo ENOTFOUND alexa.amazon.com [12/27/2023, 3:59:04 PM] [homebridge-alexa-smarthome] Restored existing accessory from cache: Thermostat

Still having the same issue after 2.0.6. No response.

@zouma45  Sorry, I wasn't home for a bit and I couldn't test. I can confirm that the update did not fix the issue.
Here are the updated logs:
[31/12/2023, 19:54:38] Registering platform 'homebridge-alexa-smarthome.HomebridgeAlexaSmartHome'
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Loaded homebridge-alexa-smarthome v2.0.6 child bridge successfully
[31/12/2023, 19:54:38] Loaded 1 cached accessories from cachedAccessories.0E8E7FEBD75C.
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Loading accessory from cache: Thermostat
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Alexa-Remote: cookie was provided
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Alexa-Remote: former registration data exist, try refresh
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Alexa-Cookie: Refresh Token
[31/12/2023, 19:54:38] Homebridge v1.7.0 (HAP v0.11.1) (homebridge-alexa-smarthome) is running on port 53204.
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Alexa-Cookie: Response (200)
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Refresh Token Response: REDACTED
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Alexa-Cookie: Exchange tokens for amazon.com
[31/12/2023, 19:54:39] [homebridge-alexa-smarthome] Alexa-Cookie: Response (200)
… Removing Login to Alexa logs, it worked just fine …
[31/12/2023, 19:54:40] [homebridge-alexa-smarthome] Alexa-Remote: Authentication checked: true
[31/12/2023, 19:54:40] [homebridge-alexa-smarthome] Alexa-Remote: Change Base URL for API calls to na-api-alexa.amazon.com
[31/12/2023, 19:54:41] [homebridge-alexa-smarthome] Successfully authenticated Alexa account.
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] Found 1 devices connected to the current Alexa account.
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] BEGIN devices connected to Alexa account

 [
  {
    "displayName": "Thermostat",
    "deviceType": "THERMOSTAT"
  }
]

END devices connected to Alexa account
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] Found all 1 devices in plugin settings.
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] Updating device states
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] Thermostat ::: Attempting to add accessory(s) for device: {
  "id": "2aafd215-a3d1-4c3c-9193-baef63b85a5a",
  "displayName": "Thermostat",
  "description": "Amazon Smart Thermostat",
  "supportedProperties": [
    "setTargetTemperature",
    "setModeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_5",
    "setRangeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_1",
    "setRangeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_2"
  ],
  "supportedTriggers": [
    "temperatureSensorTrigger"
  ],
  "supportedOperations": [
    "setTargetTemperature",
    "setModeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_5",
    "setRangeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_1",
    "setRangeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_2"
  ],
  "availability": "AVAILABLE",
  "icon": {
    "@iconType": "SmartHomeApplianceType",
    "value": "THERMOSTAT"
  },
  "providerData": {
    "enabled": true,
    "relationships": [],
    "categoryType": "APPLIANCE",
    "deviceType": "THERMOSTAT",
    "dmsDeviceIdentifiers": [
      {
        "deviceSerialNumber": “REDACTED”,
        "deviceType": "A39QOBV8YPBZIY"
      }
    ]
  }
}
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] Thermostat ::: Current state: [
  {
    "namespace": "Alexa.ThermostatController.Schedule",
    "name": "scheduleEnabled",
    "value": true
  },
  {
    "namespace": "Alexa.ThermostatController",
    "name": "targetSetpoint",
    "value": {
      "value": 60,
      "scale": "FAHRENHEIT"
    }
  },
  {
    "namespace": "Alexa.Energy.DemandResponseController",
    "name": "eventStatus",
    "value": {
      "eventId": "",
      "status": "NO_EVENT",
      "activeSignals": []
    }
  },
  {
    "namespace": "Alexa.EndpointHealth",
    "name": "connectivity",
    "value": {
      "value": "OK"
    }
  },
  {
    "namespace": "Alexa.ThermostatController.Configuration",
    "name": "allowedTemperatureRange",
    "value": {
      "heating": {
        "minimum": {
          "value": 50,
          "scale": "FAHRENHEIT"
        },
        "maximum": {
          "value": 87,
          "scale": "FAHRENHEIT"
        }
      },
      "cooling": {
        "minimum": {
          "value": 53,
          "scale": "FAHRENHEIT"
        },
        "maximum": {
          "value": 90,
          "scale": "FAHRENHEIT"
        }
      }
    }
  },
  {
    "namespace": "Alexa.ThermostatController.Schedule",
    "name": "adaptiveRecoveryEnabled",
    "value": true
  },
  {
    "namespace": "Alexa.ThermostatController.Configuration",
    "name": "temperatureScale",
    "value": "FAHRENHEIT"
  },
  {
    "namespace": "Alexa.TemperatureSensor",
    "name": "preciseTemperature",
    "value": {
      "value": 59.484375,
      "scale": "FAHRENHEIT"
    }
  },
  {
    "namespace": "Alexa.HumiditySensor",
    "name": "relativeHumidity",
    "value": 40
  },
  {
    "namespace": "Alexa.ThermostatController.HVAC.Components",
    "name": "coolerOperation",
    "value": "OFF"
  },
  {
    "namespace": "Alexa.ThermostatController.HVAC.Components",
    "name": "fanOperation",
    "value": "STAGE_1"
  },
  {
    "namespace": "Alexa.AutomationManagement",
    "name": "automationStatuses",
    "value": [
      {
        "status": "AUTOMATED",
        "capability": "Alexa.ThermostatController"
      }
    ]
  },
  {
    "namespace": "Alexa.ModeController",
    "name": "mode",
    "value": "2",
    "instance": "5"
  },
  {
    "namespace": "Alexa.ThermostatController",
    "name": "thermostatMode",
    "value": "HEAT"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 3,
    "instance": "1"
  },
  {
    "namespace": "Alexa.TemperatureSensor",
    "name": "temperature",
    "value": {
      "value": 60,
      "scale": "FAHRENHEIT"
    }
  },
  {
    "namespace": "Alexa.ThermostatController",
    "name": "adaptiveRecoveryStatus",
    "value": "INACTIVE"
  },
  {
    "namespace": "Alexa.ThermostatController.Configuration",
    "name": "setupState",
    "value": "REMOTE_CONTROL"
  },
  {
    "namespace": "Alexa.ThermostatController.HVAC.Components",
    "name": "primaryHeaterOperation",
    "value": "STAGE_1"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 3,
    "instance": "2"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 3,
    "instance": "3"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 75,
    "instance": "8"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 3,
    "instance": "6"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 68,
    "instance": "7"
  }
]
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] Thermostat ::: Range capabilities: {}
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] Restored existing accessory from cache: Thermostat

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 15.6

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 15.3

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 15.6

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 15.3

[31/12/2023, 19:55:29] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:29] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[31/12/2023, 19:55:30] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:30] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 15.6

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 15.3

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 15.6

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 15.3

[31/12/2023, 19:58:41] [homebridge-alexa-smarthome] Updating device states

@zouma45  Sorry, I wasn't home for a bit and I couldn't test. I can confirm that the update did not fix the issue.
Here are the updated logs:
[31/12/2023, 19:54:38] Registering platform 'homebridge-alexa-smarthome.HomebridgeAlexaSmartHome'
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Loaded homebridge-alexa-smarthome v2.0.6 child bridge successfully
[31/12/2023, 19:54:38] Loaded 1 cached accessories from cachedAccessories.0E8E7FEBD75C.
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Loading accessory from cache: Thermostat
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Alexa-Remote: cookie was provided
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Alexa-Remote: former registration data exist, try refresh
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Alexa-Cookie: Refresh Token
[31/12/2023, 19:54:38] Homebridge v1.7.0 (HAP v0.11.1) (homebridge-alexa-smarthome) is running on port 53204.
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Alexa-Cookie: Response (200)
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Refresh Token Response: REDACTED
[31/12/2023, 19:54:38] [homebridge-alexa-smarthome] Alexa-Cookie: Exchange tokens for amazon.com
[31/12/2023, 19:54:39] [homebridge-alexa-smarthome] Alexa-Cookie: Response (200)
… Removing Login to Alexa logs, it worked just fine …
[31/12/2023, 19:54:40] [homebridge-alexa-smarthome] Alexa-Remote: Authentication checked: true
[31/12/2023, 19:54:40] [homebridge-alexa-smarthome] Alexa-Remote: Change Base URL for API calls to na-api-alexa.amazon.com
[31/12/2023, 19:54:41] [homebridge-alexa-smarthome] Successfully authenticated Alexa account.
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] Found 1 devices connected to the current Alexa account.
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] BEGIN devices connected to Alexa account

 [
  {
    "displayName": "Thermostat",
    "deviceType": "THERMOSTAT"
  }
]

END devices connected to Alexa account
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] Found all 1 devices in plugin settings.
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] Updating device states
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] Thermostat ::: Attempting to add accessory(s) for device: {
  "id": "2aafd215-a3d1-4c3c-9193-baef63b85a5a",
  "displayName": "Thermostat",
  "description": "Amazon Smart Thermostat",
  "supportedProperties": [
    "setTargetTemperature",
    "setModeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_5",
    "setRangeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_1",
    "setRangeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_2"
  ],
  "supportedTriggers": [
    "temperatureSensorTrigger"
  ],
  "supportedOperations": [
    "setTargetTemperature",
    "setModeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_5",
    "setRangeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_1",
    "setRangeValue@2aafd215-a3d1-4c3c-9193-baef63b85a5a_2"
  ],
  "availability": "AVAILABLE",
  "icon": {
    "@iconType": "SmartHomeApplianceType",
    "value": "THERMOSTAT"
  },
  "providerData": {
    "enabled": true,
    "relationships": [],
    "categoryType": "APPLIANCE",
    "deviceType": "THERMOSTAT",
    "dmsDeviceIdentifiers": [
      {
        "deviceSerialNumber": “REDACTED”,
        "deviceType": "A39QOBV8YPBZIY"
      }
    ]
  }
}
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] Thermostat ::: Current state: [
  {
    "namespace": "Alexa.ThermostatController.Schedule",
    "name": "scheduleEnabled",
    "value": true
  },
  {
    "namespace": "Alexa.ThermostatController",
    "name": "targetSetpoint",
    "value": {
      "value": 60,
      "scale": "FAHRENHEIT"
    }
  },
  {
    "namespace": "Alexa.Energy.DemandResponseController",
    "name": "eventStatus",
    "value": {
      "eventId": "",
      "status": "NO_EVENT",
      "activeSignals": []
    }
  },
  {
    "namespace": "Alexa.EndpointHealth",
    "name": "connectivity",
    "value": {
      "value": "OK"
    }
  },
  {
    "namespace": "Alexa.ThermostatController.Configuration",
    "name": "allowedTemperatureRange",
    "value": {
      "heating": {
        "minimum": {
          "value": 50,
          "scale": "FAHRENHEIT"
        },
        "maximum": {
          "value": 87,
          "scale": "FAHRENHEIT"
        }
      },
      "cooling": {
        "minimum": {
          "value": 53,
          "scale": "FAHRENHEIT"
        },
        "maximum": {
          "value": 90,
          "scale": "FAHRENHEIT"
        }
      }
    }
  },
  {
    "namespace": "Alexa.ThermostatController.Schedule",
    "name": "adaptiveRecoveryEnabled",
    "value": true
  },
  {
    "namespace": "Alexa.ThermostatController.Configuration",
    "name": "temperatureScale",
    "value": "FAHRENHEIT"
  },
  {
    "namespace": "Alexa.TemperatureSensor",
    "name": "preciseTemperature",
    "value": {
      "value": 59.484375,
      "scale": "FAHRENHEIT"
    }
  },
  {
    "namespace": "Alexa.HumiditySensor",
    "name": "relativeHumidity",
    "value": 40
  },
  {
    "namespace": "Alexa.ThermostatController.HVAC.Components",
    "name": "coolerOperation",
    "value": "OFF"
  },
  {
    "namespace": "Alexa.ThermostatController.HVAC.Components",
    "name": "fanOperation",
    "value": "STAGE_1"
  },
  {
    "namespace": "Alexa.AutomationManagement",
    "name": "automationStatuses",
    "value": [
      {
        "status": "AUTOMATED",
        "capability": "Alexa.ThermostatController"
      }
    ]
  },
  {
    "namespace": "Alexa.ModeController",
    "name": "mode",
    "value": "2",
    "instance": "5"
  },
  {
    "namespace": "Alexa.ThermostatController",
    "name": "thermostatMode",
    "value": "HEAT"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 3,
    "instance": "1"
  },
  {
    "namespace": "Alexa.TemperatureSensor",
    "name": "temperature",
    "value": {
      "value": 60,
      "scale": "FAHRENHEIT"
    }
  },
  {
    "namespace": "Alexa.ThermostatController",
    "name": "adaptiveRecoveryStatus",
    "value": "INACTIVE"
  },
  {
    "namespace": "Alexa.ThermostatController.Configuration",
    "name": "setupState",
    "value": "REMOTE_CONTROL"
  },
  {
    "namespace": "Alexa.ThermostatController.HVAC.Components",
    "name": "primaryHeaterOperation",
    "value": "STAGE_1"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 3,
    "instance": "2"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 3,
    "instance": "3"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 75,
    "instance": "8"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 3,
    "instance": "6"
  },
  {
    "namespace": "Alexa.RangeController",
    "name": "rangeValue",
    "value": 68,
    "instance": "7"
  }
]
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] Thermostat ::: Range capabilities: {}
[31/12/2023, 19:54:42] [homebridge-alexa-smarthome] Restored existing accessory from cache: Thermostat

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 15.6

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 15.3

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:11] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 15.6

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:22] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 15.3

[31/12/2023, 19:55:29] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:29] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[31/12/2023, 19:55:30] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:30] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 15.6

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 15.3

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:32] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Thermostat - Get target temperature result: 15.6

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Thermostat - Get power - DeviceOffline(ENDPOINT_UNREACHABLE)

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Thermostat - Get temperature units result: 1

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Obtained device states from cache

[31/12/2023, 19:55:34] [homebridge-alexa-smarthome] Thermostat - Get current temperature result: 15.3

[31/12/2023, 19:58:41] [homebridge-alexa-smarthome] Updating device states

2.0.8 fixed it. Thank you!  🙏

Thank you, @nyirsh!

2.0.8 allows mode setting from homekit with Alexa Thermostats, but does not read back the current mode correctly.
Steps to reproduce.
1.) Press center button on thermostat (changes mode or turns off thermostat)

alternatively change the mode from the Alexa App
2.) Attempt to change the temperature from homekit

This is the error that will be thrown if the temperature is attempted to be changed while the thermostat is 'off' via external control (alexa or button press). Note, this level of 'off' is equivalent to setting 'off' via Homekit, but the issue lies in Homekit not detecting the thermostats current state.
The thermostat can be turned back on via homekit by toggling the thermostat mode to 'off' and then 'heat' but this is not intuitive an should not be required.
[1/2/2024, 10:59:33 AM] [HomebridgeAlexaSmartHome] Office Thermostat - Triggered set target temperature: 18.3
[1/2/2024, 10:59:33 AM] [HomebridgeAlexaSmartHome] Office Thermostat - Set target temperature - RequestUnsuccessful(Error setting smart home device state. Response: {
"controlResponses": [],
"errors": [
{
"entity": {
"entityId": "4f8bfb05-bfc4-4adc-9d2d-2b9420fb2b8c",
"entityType": "APPLIANCE"
},
"code": "IotaServiceException",
"message": "IOTA_SERVICE_EXCEPTION",
"data": null
}
]
}. Error code: IotaServiceException)