AzCopy sync uploads truncated file contents

Which version of the AzCopy was used?
azcopy version 10.0.7-Preview
Which platform are you using? (ex: Windows, Mac, Linux)
Same behaviour observed on Mac and Linux version
What command did you run?
azcopy sync "$PWD/public/" "https://storageaccount.blob.core.windows.net/\$web/$sas" --recursive
What problem was encountered?
All files in source directory are synchronised, however a large number of the files were truncated in the destination BLOB storage

The directory being synchronised contains 969 files
The number of files being updated in a sync include ~260 files (the remainder are considered the same and are not sync'd)
The directory is typical contents of a static website: images, HTML, CSS, etc
Example files being truncated include index.html (61KB)

How can we reproduce the problem in the simplest way?
Take a copy of my site's output (not publicly available, but can be provided on request), and sync with a BLOB storage account with static site enabled
Have you found a mitigation/solution?
I'm using the VSCode Azure Storage to successfully upload all files, albeit performing a full upload each time

Hi @mpowney, thanks for reaching out!
How were you observing that the files were truncated? Were there any pattern in the files being affected? Were the files being modified as they are being synced?

The files are text files like html and css etc.  The behaviour described in this bug seems to only occurs when a file already exists, but the contents has changed.  Any new files uploaded are uploaded in full.  I'll do some more digging to find out more ...

When the contents of the truncated file is copied back from the BLOB storage to my local machine, compared to the original file it is the same file size in bytes:
-rw-r--r--@ 1 mark  staff  59525 23 Feb 12:54 public/index-fail1.html
-rw-r--r--  1 mark  staff  59525 17 Feb 19:46 public/index.html

Although the file size is the same, the azcopy'd file seems to have extra characters embedded that pushes it out, it's as if the transfer has added extra data, but has stopped at the same byte size therefore truncating the last parts of the file.
It might be interesting to know, although it is an HTML (text) file, it does contain some binary data.

I may have found a similar problem investigating this bug further.  And can reliably reproduce it.  I've created a gist with three files:

first-index.html
second-index.html
third-index.html

If you take all three, then follow these steps:

Copy first-index.html to a clean folder, and rename it to index.html
Execute azcopy sync "$PWD/" "https://storageaccount.blob.core.windows.net/container/$sas" --recursive
Copy second-index.html to the same folder, renaming it to index.html
Execute azcopy sync "$PWD/" "https://storageaccount.blob.core.windows.net/container/$sas" --recursive

(these steps were performed using azcopy-preview 10.0.7 for Mac OS)
Observed behaviour:
The last portion of index.html when viewing it in the Azure web interface contains a series of unknown characters at the end.

Following from the previous comment, the originally described behaviour can be reproduced with the three files from the gist:

Copy third-index.html to a clean folder, and rename it to index.html
Execute azcopy sync "$PWD/" "https://storageaccount.blob.core.windows.net/container/$sas" --recursive
Copy first-index.html to the same folder, and rename it to index.html
Execute azcopy sync "$PWD/" "https://storageaccount.blob.core.windows.net/container/$sas" --recursive

Observed behaviour:
The contents of index.html, when viewed via the Azure portal web interface, is truncated

Hi @mpowney, thank you so much for the detailed description on repro steps! We'll investigate and get back to you soon.

Hi @mpowney, I'm extremely sorry for the inconvenience. I've confirmed there is indeed a corruption bug. Thank you for your awesome repro steps! I really appreciate your help!
Luckily, I rewrote the sync command recently(it's sitting on dev branch) and I've validated that this bug is fixed there. I'll update this thread once it is released(very soon).

Hi @mpowney, sorry for the inconvenience, and I really appreciate your patience!
I've rewritten the sync command and released it in 10.0.8. This issue should be fixed. Please let us know if you still encounter any problem.
Here is a wiki explaining how the new sync command works. Please feel free to reach out if you have any question or concern.

Great, thanks for the quick responses and turn-around


KakaoTalkAdBlock: Add version 2.1.4

Adds KakaoTalkAdBlock (2.0.0) to the bucket.
Closes #12883

[x] I have read the Contributing Guide.

/verify

Please add autoupdate section as well.

/verify

/verify

Virustotal reports a lot of problems:
https://www.virustotal.com/gui/file/951e277d65ac26c15437c24f0cd40983690321c104c491791035a420d62f8623
Even if false positive (blurfx/KakaoTalkAdBlock#83, blurfx/KakaoTalkAdBlock#85), guess this could cause problems on installation via scoop, when antivirus blocks installation or quarantines downloaded binaries in case of threat detection.

I apologize for making a pull request for a possibly malicious app.
To get things straight, I'd have to admit that I was partially aware of this. When writing the manifest for version 2.0.0, Windows Defender's inhibition was the main reason I couldn't include the 32bit version. There was no problem with 64bit version though. Since the program was regionally well known (at least I thought so), I regarded the 64bit version as safe. Never considered of running VirusTotal.
And yesterday, when writing the manifest for version 2.1.4, Windows Defender didn't raise any issues for downloading both 32bit and 64bit versions. I vaguely assumed that the false positive got fixed. Therefore, I proceeded to make a second commit.
Now I come to think of it, for transparency, I must have elaborated any issues upon opening the pull request. As this is my first time contributing to a large project on GitHub, I am still learning how to contribute 'well'. Though I know this is a mere excuse. I deeply apologize for all this inconvenience.
According to https://github.com/blurfx/KakaoTalkAdBlock/issues/85#issuecomment-2076390482, the dev managed to get the 2.1.4 version binaries removed from the malware detection list. With this, is there any chance that this manifest could be added to the Extras bucket?
Thank you.

Closed because there haven't been new releases since 2.1.4 which were problematic on VirusTotal.


Antgoolen

Type of issue
Missing information
Description
[Enter feedback here]
System.Collections.IList
Page URL
https://learn.microsoft.com/en-us/dotnet/standard/collections/selecting-a-collection-class
Content source URL
https://github.com/dotnet/docs/blob/main/docs/standard/collections/selecting-a-collection-class.md
Document Version Independent Id
da3b31b2-54bf-14c2-56d3-872d4c1c109c
Article author
@IEvangelist
Metadata

ID: e84850a4-05a8-5bab-ea8c-80df1ed0133f
Product: dotnet-fundamentals

Closing this as IList is not a class.


Excel support for the metadata template validator

Description
As a developer, I want validator to work on the Excel files.
Acceptance criteria

[x] done

Changes are pushed to dev branch. Done. @zperova


hello.py does not pass ruff format

uv version 0.4.0 creates a hello.py file by default when running
$ uv init my_project

The contents of hello.py are
$ cat hello.py
def main():
    print("Hello from my-project!")

if __name__ == "__main__":
    main()

Which is completely reasonable. But I noticed that this does not pass ruff format.
$ uv add ruff
$ uv run ruff format --diff .
--- hello.py
+++ hello.py
@@ -1,5 +1,6 @@
 def main():
     print("Hello from my-project!")

+
 if __name__ == "__main__":
     main()

1 file would be reformatted

Maybe you want hello.py to be ruff approved out the box? It's a minor thing though.

Lol, thank you. Yes. (PR welcome or we'll fix soon.)

Thanks :) the problem with writing Python manually in a Rust string...


Enhancement in Delete folder option

Deliverable:

[ ] The cursor should be made to pointer as soon as we hover on trash icon on the folder
[ ] As soon as we click on the trash icon a modal should appear asking Are you sure you want to delete this workspace? along with having the button of cancel and yes
[ ] Clicking on yes should delete the workspace and clicking on cancel` should not do anything, just close the modal
[ ] Remove the sure? popup that we get currently after clicking on the trash icon

example of the modal we are looking for deleting workspace

@Kajol-Kumari I would like to work on this issue also.

@Kajol-Kumari I would like to work on this issue also.

Sure @sakshikhachane


Removed duplicated code in tinydb_hashfs.py

Coverage decreased (-0.02%) to 85.073% when pulling 0b8109a2ef5c5273ed06963a14e6c6c59b10c7a5 on gabrieldemarmiesse:remove_duplicate_tinydb into 37e6fc3bdf4ca7dfc72735742bd90044ef697057 on IDSIA:master.


Bump Carbon Identity Framework Version

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7456051822

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7456051822
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7456870690


update kubernetes version from 1.14 to 1.18

Hi
I've updated PWK to make enable the user to play with the major version.
I remove some not supported options based on kubernetes official documentation

Nice @diranetafen!
Have you tried this locally? Does it work?

Hi
It's work perfectly
I'm using it on my own PWD

you can see that the master is up and the version is 1.18.0
I will do another PR after this to install automatically the auto-completion

Nice.. In your image I see that CNI hasn't been initialized. Does CNI
installing works?
On Wed, Jun 17, 2020 at 7:11 PM diranetafen<EMAIL_ADDRESS>wrote:

you can see that the master is up and the version is 1.18.0
I will do another PR after this to install automatically the
auto-completion
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/play-with-docker/play-with-docker/pull/405#issuecomment-645652826,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMBLWWOJY2YG4NQ3WQC6LTRXE5QHANCNFSM4OA776UA
.

yes
Weanet is working correctly using the command listed in motd

In the previous capture, the CNI was not ready yet hihi
So all is ok now after CNI up

Awesome!
I'll update the official environment tonight! I was looking forward to do
this but I haven't had the time. Much appreciated @diranetafen
On Wed, Jun 17, 2020 at 7:30 PM diranetafen<EMAIL_ADDRESS>wrote:

In the previous capture, the CNI was not ready yet hihi
So all is ok now after CNI up
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/play-with-docker/play-with-docker/pull/405#issuecomment-645659750,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMBLWVISSXODZR54K4W53DRXE7YJANCNFSM4OA776UA
.

You are welcome @marcosnils , another PR is in preparation. I will submit it after this PR will be merged :-)

hey @diranetafen I just tried to build your dockerfile and I'm getting the following error:
#8 25.20 ---> Package tcp_wrappers-libs.x86_64 0:7.6-77.el7 will be installed
#8 25.26 --> Finished Dependency Resolution
#8 25.26 Error: Package: kubeadm-1.18.0-0.x86_64 (kubernetes)
#8 25.26            Requires: kubernetes-cni >= 0.7.5
#8 25.26            Available: kubernetes-cni-<IP_ADDRESS>-0.07a8a2.x86_64 (kubernetes)
#8 25.26                kubernetes-cni = <IP_ADDRESS>-0.07a8a2
#8 25.26            Available: kubernetes-cni-0.5.1-0.x86_64 (kubernetes)
#8 25.26                kubernetes-cni = 0.5.1-0
#8 25.26            Available: kubernetes-cni-0.5.1-1.x86_64 (kubernetes)
#8 25.26                kubernetes-cni = 0.5.1-1
#8 25.26            Available: kubernetes-cni-0.6.0-0.x86_64 (kubernetes)
#8 25.26                kubernetes-cni = 0.6.0-0
#8 25.26            Available: kubernetes-cni-0.7.5-0.x86_64 (kubernetes)
#8 25.26                kubernetes-cni = 0.7.5-0
#8 25.26 Error: Package: kubelet-1.18.0-0.x86_64 (kubernetes)
#8 25.26            Requires: kubernetes-cni >= 0.7.5
#8 25.26            Available: kubernetes-cni-<IP_ADDRESS>-0.07a8a2.x86_64 (kubernetes)
#8 25.26                kubernetes-cni = <IP_ADDRESS>-0.07a8a2
#8 25.26            Available: kubernetes-cni-0.5.1-0.x86_64 (kubernetes)
#8 25.26                kubernetes-cni = 0.5.1-0
#8 25.26            Available: kubernetes-cni-0.5.1-1.x86_64 (kubernetes)
#8 25.26                kubernetes-cni = 0.5.1-1
#8 25.26            Available: kubernetes-cni-0.6.0-0.x86_64 (kubernetes)
#8 25.26                kubernetes-cni = 0.6.0-0
#8 25.26            Available: kubernetes-cni-0.7.5-0.x86_64 (kubernetes)
#8 25.26                kubernetes-cni = 0.7.5-0
#8 25.26  You could try using --skip-broken to work around the problem
#8 25.31  You could try running: rpm -Va --nofiles --nodigest
------
failed to solve with frontend dockerfile.v0: failed to build LLB: executor failed running [/bin/sh -c yum install -y kubectl-1.18.0 kubeadm-1.18.0 kubelet-1.18.0     && yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo     && yum install -y docker-ce git     && sed -i -e '4d;5d;8d' /lib/systemd/system/docker.service     && yum clean all]: runc did not terminate sucessfully

Thoughts?

Hi @marcosnils
I had the same problem, i think there is an issue with centos repo, because after 5 hours the build pass.
I can't explain that because I were using those same lines(yum install kube...) and they always worked
Did you fix it before merging ?


call Cancel if signalStart fails

this allows for any goroutines started in Start to be stopped before exiting the activity

Missed this, nice!


Always generate body for python code elements

Since
class Service:

without a body or pass is invalid Python, we ensure an empty documentation comment is always generated to make the generated code always valid.
Fixes https://github.com/grpc/grpc/issues/9451

Performance differences noted:
Benchmark                   cpu_time    real_time
------------------------  ----------  -----------
BM_ErrorCreateFromCopied      +89.50       +89.50

No significant performance differences

Performance differences noted:
Benchmark                                  cpu_time    real_time
---------------------------------------  ----------  -----------
BM_PollEmptyPollset_SpeedOfLight/1/1000      +11.50       +11.50

No significant performance differences

Test failures:
Basic Tests Windows: #10107
Bazel Tests: Not yet in effect
gRPC Interop: https://github.com/grpc/grpc/issues/10624
gRPC Performance: https://github.com/grpc/grpc/issues/10690


image in hidden div

Hi,
I have a lazy load image in a hidden div above the fold. (div open on hover)
It's seems that image load immediately.
is there a way to avoid this?
thanks

Images that are inside of the view but are hidden (using visibility: hidden) are loaded delayed but preloaded after load so you can animate them in. If you want not load visibility: hidden elements you can change this using a documented configuration property. (see loadHidden)


Fix #306 Folder name encoding error in appendMessage()

Create a folder containing a special character e.g. 'sent & trash'.
Then add a message to that folder.
$client->connect();
$folder = $client->getFolder('sent & trash');
$folder->appendMessage($message); // Not working, showing error
ERROR:
failed to send literal string.
TAG3 APPEND "INBOX.sent & trash"   The folder name should be UTF7-IMAP.
In the appendMessage () function, changing $this->full_name to $this->path solves the problem.

Hi @rskrzypczak ,
many thanks for your pull request!
Best regards,


Creating a texture3D distorts the values (unwanted filtering?)

Godot version:
3.2.1.stable.mono
OS/device including version:
Windows 10
Issue description:
When creating a Texture3D in code, the texture data is distorted. An entered byte value of 1 becomes 13 when read back for example. When doing the same procedure on an ImageTexture with the same setup, this problem does not occur.
Steps to reproduce:
Create a Texture3d in code with Image.Format_r8 and flags = 0.
Create an Image from a poolbytearray containg values between 0 and 255.
Set the Image as one of the Texture3D's layer data.
Retrieve the data from the same layer and read the bytearray.
Minimal reproduction project:
GD-script, uploaded as .txt. Attach sript to a node and run.
Node.txt
Bugsquad edit: Complete minimal reproduction project for easier testing: test_texture_3d.zip

Disabling filtering on the Texture3D using texture3d.flags = 0 doesn't seem to fix it, so it must be something else.

I've looked into the values some more and found that the values stored in Texture3D corresponds exactly to the square root of the input values as floats (0-1).
That is to say, input a color value to Texture3D and when you read it back you get the square root of that number.
I don't know what it means, but maybe it can help someone to track down the issue.

Ah. Looks like your texture is being converted to sRGB somewhere.

That's probably it! I cannot seem to find a way to disable this conversion though.

I can still reproduce this as of 3.5.3. I haven't managed to update the script so it works with 4.x to test there though.


Rename ReferenceFlag to ReferenceFlags (plural)

All the other semantic flags have plural names - ScopeFlags, SymbolFlags, NodeFlags. ReferenceFlag is the outlier.
Rename:

ReferenceFlag to ReferenceFlags.
Reference::flag field to flags.
Reference::flag method to flags.
Reference::flag_mut method to flags_mut.
All vars called flag to flags.

Only reason I'm opening an issue for this rather than just submitting a PR is it'd cause merge conflicts with PR stack #4973, so will wait for that to get merged first.

Good idea. How do I mark the export as deprecated? (not done that before)
Ditto for the Reference::flag + Reference::flag_mut methods?

Actually, on 2nd thoughts, I'm not sure we should get into deprecation for such a simple change. Oxc is not at v1.0.0 yet, and we're making breaking changes all the time. This change is extremely minor compared to most of them, and if we leave an extra flag_mut method doubling the new flags_mut then we'll just have to remember to go and remove it later on (and discuss when!).
What do you think?

If it's not too much effort, deprecating for a single release could be worth it. It is definitely appreciated when upgrades do not break your code without warning :)
If you think we won't remember to clean it up, then adding a deprecation is not worth it.

Personally, my view is that it's not worth it. I do understand that breaking changes are always painful, but we are nowhere near a stable API for Semantic, and this change is small beer. If we try to keep deprecated methods etc around for every change to Semantic over next few months I imagine it'll add up to a sizeable workload for us, and for fairly little benefit - people are still going to have to change their code at some point soon.
But also: If we also exported ReferenceFlags and ReferenceFlag, I'm not clear how do you mark ReferenceFlag as deprecated (in a way where people know it's deprecated). If there's no good way of doing that, the deprecation process would seem a bit pointless as no-one will notice the deprecation, and then they'll just experience it as a breaking change later on when we finally do remove the old name.


Concurrency back-deployment fixes for exclusivity & isolated parameters

Fix two issues that would case crashes for programs using Swift Concurrency in back-deployed scenarios:

Cannot back-deploy mangled names including isolated parameters.
Exclusivity checking was broken in some cases (rdar://83064974).
Don't refer to the isa mask any more; we don't back-deploy far enough for it to matter.
Make sure we set rpaths properly when linking.
Properly re-export the SwiftNativeNSObject class from libswiftCore to libswift_Concurrency and embed it in the back-deployment library.

@swift-ci please test

@DougGregor LFG man, see a lot of PR for back-deploy and feeling that you are doing a lot of hard working during this weekend to be able put all new changes in new xcode release which i feel will be tommorow 💪🏻

@swift-ci please test

@swift-ci please test


feat(cgroup): Add podman support

This commit simplifies the containerID from Cgroup path parsing logic.
All container IDs from all supported runtimes (including podman) are
64 character alphanumeric strings.
As such we can simply strip the .scope suffix and take the last 64
characters.

I've tested this on my local system and confirm that both rootful and rootless podman containers now show up when querying kepler metrics.


Move duplicate get/delete code up into FileSystemStateManager

This diff is rendering messy but basically all get/delete/exists interface methods do the same thing across curator and local filesystem if we abstract out the following:
abstract protected ListenableFuture<Boolean> nodeExists(String path);
abstract protected ListenableFuture<Boolean> deleteNode(String path);
abstract protected <M extends Message> ListenableFuture<M> getNodeData(WatchCallback watcher,
                                                                         String path,
                                                                         Message.Builder builder);

This removes duplicate code and makes it easier to add new state manager methods. Creates are handled differently since ZK has the notion of ephemeral nodes and local FS has the notion of overwrites.

looks good to me. 👍


Best practice for storing passwords for web tests

Hello,
It would be great if there are details on how to store passwords/secrets for web tests.

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

ID: a6ab3fdb-a3b6-ee8a-1487-b14a1c3a28bb
Version Independent ID: d5d2659b-5959-74d6-4a3f-59caaa4e7d47
Content: Monitor your web application with multi-step web tests and Azure Application Insights
Content Source: articles/azure-monitor/app/availability-multistep.md
Service: azure-monitor
Sub-service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@JohnPhamous Thanks for the comment. We are actively investigating on the issue and will get back to you shortly with an update.

@BharathNimmala-MSFT can you please help take a peek at this?

@JohnPhamous  Thank for reaching out to us and sharing your feedback. Apologies for delayed response on this. Currently the web test file is encrypted only when it is stored, however must be uploaded as plain text.
If not already , please do check out other sign-in options listed in the documentation and see if it would cater your needs.
If you do any further feedback for the product team, please share your feedback here. Which would help our product team to evaulate the ask and also for rest of the community to upvote.

@JohnPhamous At this point it appears that there's no further edits needed for the exisiting documentation. We will go ahead and close this thread. However if any further information is needed please feel free to tag us in your reply and will be happy to take the conversation forward. Thank you.


HDFS-16661. Improve Code With Lambda in AsyncLoggerSet class

Description of PR
Improve Code With Lambda in AsyncLoggerSet class

@goiri Can help me push this pr forward? After this, I will create a PR try to improve codes with Lambda in the whole hadoop-hdfs module.

some checkStyle need fix
./hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/client/AsyncLoggerSet.java:208:  public QuorumCall<AsyncLogger,NewEpochResponseProto> newEpoch(long epoch) {:32: ',' is not followed by whitespace. [WhitespaceAfter]
./hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/client/AsyncLoggerSet.java:253:  QuorumCall<AsyncLogger,Void> acceptRecovery(SegmentStateProto log, URL fromURL) {:25: ',' is not followed by whitespace. [WhitespaceAfter]

Thanks @slfan1989 . Please review the latest patch, I have fixed these check style.

@goiri Hi, master, can you help me merge it into the trunk?  I will move to improve codes with Lambda in the whole hadoop-hdfs module.


feat: added docusaurus and morfeo logo

Proposed changes
Introduces docusaurus to add documentations and use cases of morfeo
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation Update (if none of the other choices apply)

Checklist

[x] I have read the CONTRIBUTING doc
[x] Lint and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in downstream modules

Codecov Report

Merging #27 (3dc54f4) into main (448c76a) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #27   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           31        31
  Lines          444       444
  Branches        84        84
=========================================
  Hits           444       444

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 448c76a...3dc54f4. Read the comment docs.


restyling-text

Just realised your branch is 2 behind main, and this is why ur package-lock.json has changed! U need to pull main and merge into your branch! Plz don’t open pull requests if you are behind main!!!!


Add three vertical dots button to show other options for items instead of only through context menu

Duplicate #458


Brightness warning

@milo526  im getting the bellow warning:  This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100.

[08/12/2021, 09:42:12] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[08/12/2021, 09:42:12] [@milo526/homebridge-tuya-web] Error:
at Brightness.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2074:105)
at Brightness.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1986:16)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1569:24
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at BrightnessCharacteristic.updateValue (/usr/local/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/characteristics/brightness.ts:75:19)
at /usr/local/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/characteristics/brightness.ts:34:14
at processTicksAndRejections (node:internal/process/task_queues:96:5)

I have the same problem, HB 1.3.8 + TuyaWeb v.1.2.1:
12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 256 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 200 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 229 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.

I have the same problem, HB 1.3.8 + TuyaWeb v.1.2.1:
12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 256 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 200 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 229 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/8/2021, 1:21:28 PM] [@ottimis/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.

@boboxx put your homebridge into debug mode (in home bridge settings) and then copy the extra info in the status area, as they will need that extra detail to create a fix.

[12/9/2021, 7:07:26 AM] Homebridge v1.3.8 (HAP v0.9.7) (Homebridge MBCC) is running on port 51709.
[12/9/2021, 7:07:29 AM] [TuyaWebPlatform] Sending HTTP GET request to /homeassistant/skill - Header: {"name":"Discovery","namespace":"discovery","payloadVersion":1}.
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Den front" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Ensuite" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Stairs" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Den" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Island sink" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Hall" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Lobby" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Master" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Front Sconce" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Ensuite Pot Lights" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Living room" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Island" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Front Pot Lights" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Back Pot Lights" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Device type for "Entrance" is overruled in config from light to: "dimmer"
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Den front] deviceConfig: {
data: { brightness: '1000', online: true, state: 'false' },
name: 'Den front',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'eb24222ad9a55292ddf6a3',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Den front] [Tuya ID: eb24222ad9a55292ddf6a3] [HomeBridge ID: 7fe1ff09-536a-4bc5-8c60-8ba9537ba9a4]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Den front)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service eb24222ad9a55292ddf6a3
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Den front] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Den front] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Den front] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Ensuite] deviceConfig: {
data: { brightness: '1000', online: true, state: 'false' },
name: 'Ensuite',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'eb04c2dbd717af5f41wlaj',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Ensuite] [Tuya ID: eb04c2dbd717af5f41wlaj] [HomeBridge ID: a16a8eb8-ad0c-4dcb-80df-01550573f5bd]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Ensuite)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service eb04c2dbd717af5f41wlaj
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Ensuite] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Ensuite] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Ensuite] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Stairs] deviceConfig: {
data: { brightness: '1000', online: true, state: 'false' },
name: 'Stairs',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'eb58074f36a2a203a2wpo9',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Stairs] [Tuya ID: eb58074f36a2a203a2wpo9] [HomeBridge ID: 055f9143-0b3b-42dd-985a-cbb868c01bb6]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Stairs)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service eb58074f36a2a203a2wpo9
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Stairs] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Stairs] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Stairs] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Den] deviceConfig: {
data: { brightness: '100', online: true, state: 'false' },
name: 'Den',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'eb76ec4d31c106f36a4syc',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Den] [Tuya ID: eb76ec4d31c106f36a4syc] [HomeBridge ID: 27b632c0-4f04-47e1-acd7-4e906f317dbe]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Den)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service eb76ec4d31c106f36a4syc
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Den] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Den] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Den] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Island sink] deviceConfig: {
data: { brightness: '505', online: true, state: 'false' },
name: 'Island sink',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'ebf55c3b77cdf5fcc0aiwz',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Island sink] [Tuya ID: ebf55c3b77cdf5fcc0aiwz] [HomeBridge ID: ac2d4784-16c7-43f4-aac5-bf6963a7d50a]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Island sink)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service ebf55c3b77cdf5fcc0aiwz
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Island sink] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Island sink] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Island sink] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Hall] deviceConfig: {
data: { brightness: '237', online: true, state: 'false' },
name: 'Hall',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'eba2f5448033eaee29fsbl',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Hall] [Tuya ID: eba2f5448033eaee29fsbl] [HomeBridge ID: 95ad06d5-6864-48da-8210-a19dc1838aa0]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Hall)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service eba2f5448033eaee29fsbl
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Hall] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Hall] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Hall] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Lobby] deviceConfig: {
data: { brightness: '653', online: true, state: 'false' },
name: 'Lobby',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'eb54ab8101c75f763as0e8',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Lobby] [Tuya ID: eb54ab8101c75f763as0e8] [HomeBridge ID: 3b4fe154-05a0-4bf7-8240-bf87a100e2ea]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Lobby)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service eb54ab8101c75f763as0e8
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Lobby] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Lobby] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Lobby] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Master] deviceConfig: {
data: { brightness: '10', online: true, state: 'false' },
name: 'Master',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'eb2554e195f85fcce2wuyj',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Master] [Tuya ID: eb2554e195f85fcce2wuyj] [HomeBridge ID: dbf0253d-fbb5-47db-8790-5cda02db2708]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Master)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service eb2554e195f85fcce2wuyj
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Master] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Master] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Master] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Front Sconce] deviceConfig: {
data: { brightness: '1000', online: true, state: 'false' },
name: 'Front Sconce',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'ebe512a9dd1191700ft4ns',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Front Sconce] [Tuya ID: ebe512a9dd1191700ft4ns] [HomeBridge ID: d1ff2199-82d5-41d8-a2b5-0a2e6aad7272]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Front Sconce)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service ebe512a9dd1191700ft4ns
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Front Sconce] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Front Sconce] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Front Sconce] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Ensuite Pot Lights] deviceConfig: {
data: { brightness: '100', online: true, state: 'false' },
name: 'Ensuite Pot Lights',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'eb2217d841aef69c45cxa1',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Ensuite Pot Lights] [Tuya ID: eb2217d841aef69c45cxa1] [HomeBridge ID: b0b24bcb-58eb-47ad-8ede-c457f46a7811]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Ensuite Pot Lights)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service eb2217d841aef69c45cxa1
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Ensuite Pot Lights] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Ensuite Pot Lights] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Ensuite Pot Lights] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Living room] deviceConfig: {
data: { brightness: '100', online: true, state: 'false' },
name: 'Living room',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'eb966d2ae294631aafg8pl',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Living room] [Tuya ID: eb966d2ae294631aafg8pl] [HomeBridge ID: e4cf1409-0a25-4f2e-a317-0067d25676a7]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Living room)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service eb966d2ae294631aafg8pl
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Living room] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Living room] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Living room] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Bathroom Pot Lights] deviceConfig: {
data: { online: true, state: false },
name: 'Bathroom Pot Lights',
icon: 'https://images.tuyaus.com/smart/icon/ay14906729310721fNjn/1568861668b73fbe9c073.jpg',
id: '034137343c6105cbf46d',
dev_type: 'switch',
ha_type: 'switch',
config: { old_dev_type: 'switch' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Bathroom Pot Lights] [Tuya ID: 034137343c6105cbf46d] [HomeBridge ID: a0f0c59b-d1e7-41da-98eb-060991eba2fd]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Bathroom Pot Lights)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service 034137343c6105cbf46d
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Bathroom Pot Lights] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Bathroom Pot Lights] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Island] deviceConfig: {
data: { brightness: '100', online: true, state: 'false' },
name: 'Island',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'eb9a4397a9afd5a393xwiv',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Island] [Tuya ID: eb9a4397a9afd5a393xwiv] [HomeBridge ID: 9f1283d0-d300-4563-b849-be547d23dca8]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Island)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service eb9a4397a9afd5a393xwiv
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Island] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Island] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Island] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Front Pot Lights] deviceConfig: {
data: { brightness: '376', online: true, state: 'false' },
name: 'Front Pot Lights',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'eb8538cc2753423ee4eimx',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Front Pot Lights] [Tuya ID: eb8538cc2753423ee4eimx] [HomeBridge ID: b5911cb1-0e75-41e1-89f2-3b5aad54c9ab]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Front Pot Lights)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service eb8538cc2753423ee4eimx
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Front Pot Lights] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Front Pot Lights] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Front Pot Lights] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Bathroom Shower] deviceConfig: {
data: { online: true, state: false },
name: 'Bathroom Shower',
icon: 'https://images.tuyaus.com/smart/icon/ay14906729310721fNjn/1568862727a52b550fe9a.jpg',
id: '455832118cce4edc0a21',
dev_type: 'switch',
ha_type: 'switch',
config: { old_dev_type: 'switch' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Bathroom Shower] [Tuya ID: 455832118cce4edc0a21] [HomeBridge ID: 5b4f5412-c9c7-4740-bce9-39f58278175d]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Bathroom Shower)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service 455832118cce4edc0a21
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Bathroom Shower] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Bathroom Shower] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Back Pot Lights] deviceConfig: {
data: { brightness: '1000', online: true, state: 'false' },
name: 'Back Pot Lights',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'eb0d814f3f54f32458fvim',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Back Pot Lights] [Tuya ID: eb0d814f3f54f32458fvim] [HomeBridge ID: b7d3f25c-fa25-46e8-b12e-8e4d34f815ec]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Back Pot Lights)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service eb0d814f3f54f32458fvim
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Back Pot Lights] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Back Pot Lights] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Back Pot Lights] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Entrance] deviceConfig: {
data: { brightness: '100', online: true, state: 'false' },
name: 'Entrance',
icon: 'https://images.tuyaus.com/smart/icon/ay1555569556653Lg790/1614222015d118798d6e9.jpg',
id: 'ebb89cee50e128ab5drbpm',
dev_type: 'dimmer',
ha_type: 'light',
config: { dimmer_characteristics: [ 'Brightness' ], old_dev_type: 'light' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Entrance] [Tuya ID: ebb89cee50e128ab5drbpm] [HomeBridge ID: 2b439a58-07be-4c92-b2c9-610a34be4aef]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Entrance)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service ebb89cee50e128ab5drbpm
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Entrance] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Entrance] Characteristic.Brightness - {"format":"int","perms":["ev","pr","pw"],"unit":"percentage","minValue":0,"maxValue":100,"minStep":1}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Entrance] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Bathroom] deviceConfig: {
data: { online: true, state: false },
name: 'Bathroom',
icon: 'https://images.tuyaus.com/smart/icon/ay14906729310721fNjn/1568861668b73fbe9c073.jpg',
id: '034137343c6105cd49ca',
dev_type: 'switch',
ha_type: 'switch',
config: { old_dev_type: 'switch' }
}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Created new Accessory [Name: Bathroom] [Tuya ID: 034137343c6105cd49ca] [HomeBridge ID: 9dd01405-24d2-4a46-9a05-603af255ec6b]
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Register Platform Accessory (Bathroom)
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] Creating New Service 034137343c6105cd49ca
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Bathroom] Characteristic.On - {"format":"bool","perms":["ev","pr","pw"]}
[12/9/2021, 7:07:30 AM] [TuyaWebPlatform] [Bathroom] - Characteristic Name not supported
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] Error:
at Brightness.Characteristic.characteristicWarning (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2074:105)
at Brightness.Characteristic.validateUserInput (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1986:16)
at Brightness.Characteristic.updateValue (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1415:20)
at DimmerAccessory.setCharacteristic (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:272:55)
at BrightnessCharacteristic.updateValue (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/characteristics/brightness.ts:70:22)
at DimmerAccessory.updateState (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:409:9)
at DimmerAccessory.updateAccessory (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:402:10)
at TuyaWebPlatform.refreshDeviceStates (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:190:41)
at TuyaWebPlatform.discoverDevices (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:312:16)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at TuyaWebPlatform.postLaunchSetup (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:119:7)
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] Error:
at Brightness.Characteristic.characteristicWarning (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2074:105)
at Brightness.Characteristic.validateUserInput (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1986:16)
at Brightness.Characteristic.updateValue (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1415:20)
at DimmerAccessory.setCharacteristic (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:272:55)
at BrightnessCharacteristic.updateValue (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/characteristics/brightness.ts:70:22)
at DimmerAccessory.updateState (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:409:9)
at DimmerAccessory.updateAccessory (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:402:10)
at TuyaWebPlatform.refreshDeviceStates (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:190:41)
at TuyaWebPlatform.discoverDevices (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:312:16)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at TuyaWebPlatform.postLaunchSetup (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:119:7)
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] Error:
at Brightness.Characteristic.characteristicWarning (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2074:105)
at Brightness.Characteristic.validateUserInput (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1986:16)
at Brightness.Characteristic.updateValue (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1415:20)
at DimmerAccessory.setCharacteristic (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:272:55)
at BrightnessCharacteristic.updateValue (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/characteristics/brightness.ts:70:22)
at DimmerAccessory.updateState (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:409:9)
at DimmerAccessory.updateAccessory (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:402:10)
at TuyaWebPlatform.refreshDeviceStates (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:190:41)
at TuyaWebPlatform.discoverDevices (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:312:16)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at TuyaWebPlatform.postLaunchSetup (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:119:7)
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 198 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] Error:
at Brightness.Characteristic.characteristicWarning (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2074:105)
at Brightness.Characteristic.validateUserInput (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1986:16)
at Brightness.Characteristic.updateValue (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1415:20)
at DimmerAccessory.setCharacteristic (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:272:55)
at BrightnessCharacteristic.updateValue (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/characteristics/brightness.ts:70:22)
at DimmerAccessory.updateState (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:409:9)
at DimmerAccessory.updateAccessory (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:402:10)
at TuyaWebPlatform.refreshDeviceStates (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:190:41)
at TuyaWebPlatform.discoverDevices (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:312:16)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at TuyaWebPlatform.postLaunchSetup (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:119:7)
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 256 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] Error:
at Brightness.Characteristic.characteristicWarning (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2074:105)
at Brightness.Characteristic.validateUserInput (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1986:16)
at Brightness.Characteristic.updateValue (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1415:20)
at DimmerAccessory.setCharacteristic (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:272:55)
at BrightnessCharacteristic.updateValue (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/characteristics/brightness.ts:70:22)
at DimmerAccessory.updateState (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:409:9)
at DimmerAccessory.updateAccessory (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:402:10)
at TuyaWebPlatform.refreshDeviceStates (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:190:41)
at TuyaWebPlatform.discoverDevices (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:312:16)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at TuyaWebPlatform.postLaunchSetup (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:119:7)
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] Error:
at Brightness.Characteristic.characteristicWarning (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2074:105)
at Brightness.Characteristic.validateUserInput (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1986:16)
at Brightness.Characteristic.updateValue (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1415:20)
at DimmerAccessory.setCharacteristic (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:272:55)
at BrightnessCharacteristic.updateValue (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/characteristics/brightness.ts:70:22)
at DimmerAccessory.updateState (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:409:9)
at DimmerAccessory.updateAccessory (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:402:10)
at TuyaWebPlatform.refreshDeviceStates (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:190:41)
at TuyaWebPlatform.discoverDevices (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:312:16)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at TuyaWebPlatform.postLaunchSetup (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:119:7)
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 147 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] Error:
at Brightness.Characteristic.characteristicWarning (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2074:105)
at Brightness.Characteristic.validateUserInput (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1986:16)
at Brightness.Characteristic.updateValue (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1415:20)
at DimmerAccessory.setCharacteristic (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:272:55)
at BrightnessCharacteristic.updateValue (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/characteristics/brightness.ts:70:22)
at DimmerAccessory.updateState (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:409:9)
at DimmerAccessory.updateAccessory (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:402:10)
at TuyaWebPlatform.refreshDeviceStates (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:190:41)
at TuyaWebPlatform.discoverDevices (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:312:16)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at TuyaWebPlatform.postLaunchSetup (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:119:7)
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 392 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/9/2021, 7:07:30 AM] [@milo526/homebridge-tuya-web] Error:
at Brightness.Characteristic.characteristicWarning (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2074:105)
at Brightness.Characteristic.validateUserInput (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1986:16)
at Brightness.Characteristic.updateValue (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1415:20)
at DimmerAccessory.setCharacteristic (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:272:55)
at BrightnessCharacteristic.updateValue (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/characteristics/brightness.ts:70:22)
at DimmerAccessory.updateState (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:409:9)
at DimmerAccessory.updateAccessory (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/accessories/BaseAccessory.ts:402:10)
at TuyaWebPlatform.refreshDeviceStates (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:190:41)
at TuyaWebPlatform.discoverDevices (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:312:16)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at TuyaWebPlatform.postLaunchSetup (/usr/lib/node_modules/@milo526/homebridge-tuya-web/src/platform.ts:119:7)

@milo526 any fix for this error yet pls?

Duplicate of #149
Please try the just released pre-release 1.1.0-1 and see if that solves your problems.
If it does not, please respond to the mentioned issue.

[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Missing required id property on device configuration, received:
{
"device_type": "form"
}
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Den front] [Tuya ID: eb24222ad9a55292ddf6a3] [HomeBridge ID: 7fe1ff09-536a-4bc5-8c60-8ba9537ba9a4]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Ensuite] [Tuya ID: eb04c2dbd717af5f41wlaj] [HomeBridge ID: a16a8eb8-ad0c-4dcb-80df-01550573f5bd]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Stairs] [Tuya ID: eb58074f36a2a203a2wpo9] [HomeBridge ID: 055f9143-0b3b-42dd-985a-cbb868c01bb6]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Den] [Tuya ID: eb76ec4d31c106f36a4syc] [HomeBridge ID: 27b632c0-4f04-47e1-acd7-4e906f317dbe]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Island sink] [Tuya ID: ebf55c3b77cdf5fcc0aiwz] [HomeBridge ID: ac2d4784-16c7-43f4-aac5-bf6963a7d50a]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Hall] [Tuya ID: eba2f5448033eaee29fsbl] [HomeBridge ID: 95ad06d5-6864-48da-8210-a19dc1838aa0]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Lobby] [Tuya ID: eb54ab8101c75f763as0e8] [HomeBridge ID: 3b4fe154-05a0-4bf7-8240-bf87a100e2ea]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Master] [Tuya ID: eb2554e195f85fcce2wuyj] [HomeBridge ID: dbf0253d-fbb5-47db-8790-5cda02db2708]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Front Sconce] [Tuya ID: ebe512a9dd1191700ft4ns] [HomeBridge ID: d1ff2199-82d5-41d8-a2b5-0a2e6aad7272]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Table] [Tuya ID: ebb1719dfde47a156cxwxa] [HomeBridge ID: 2040216e-c382-4fed-89ef-cac8a784a357]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Ensuite Pot Lights] [Tuya ID: eb2217d841aef69c45cxa1] [HomeBridge ID: b0b24bcb-58eb-47ad-8ede-c457f46a7811]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Living room] [Tuya ID: eb966d2ae294631aafg8pl] [HomeBridge ID: e4cf1409-0a25-4f2e-a317-0067d25676a7]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Bathroom Pot Lights] [Tuya ID: 034137343c6105cbf46d] [HomeBridge ID: a0f0c59b-d1e7-41da-98eb-060991eba2fd]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Island] [Tuya ID: eb9a4397a9afd5a393xwiv] [HomeBridge ID: 9f1283d0-d300-4563-b849-be547d23dca8]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Front Pot Lights] [Tuya ID: eb8538cc2753423ee4eimx] [HomeBridge ID: b5911cb1-0e75-41e1-89f2-3b5aad54c9ab]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Bathroom Shower] [Tuya ID: 455832118cce4edc0a21] [HomeBridge ID: 5b4f5412-c9c7-4740-bce9-39f58278175d]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Back Pot Lights] [Tuya ID: eb0d814f3f54f32458fvim] [HomeBridge ID: b7d3f25c-fa25-46e8-b12e-8e4d34f815ec]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Entrance] [Tuya ID: ebb89cee50e128ab5drbpm] [HomeBridge ID: 2b439a58-07be-4c92-b2c9-610a34be4aef]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] Existing Accessory found [Name: Bathroom] [Tuya ID: 034137343c6105cd49ca] [HomeBridge ID: 9dd01405-24d2-4a46-9a05-603af255ec6b]
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] [Den front] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed<PHONE_NUMBER>4444446) since provided Tuya value (140) exceeds configured maximum Tuya value (100). Please update your configuration!
[12/13/2021, 8:56:22 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number<PHONE_NUMBER>4444446 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] [Ensuite] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed<PHONE_NUMBER>1111111) since provided Tuya value (110) exceeds configured maximum Tuya value (100). Please update your configuration!
[12/13/2021, 8:56:22 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number<PHONE_NUMBER>1111111 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] [Stairs] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1088.888888888889) since provided Tuya value (990) exceeds configured maximum Tuya value (100). Please update your configuration!
[12/13/2021, 8:56:22 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1088.888888888889 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] [Island sink] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed<PHONE_NUMBER>7777777) since provided Tuya value (350) exceeds configured maximum Tuya value (100). Please update your configuration!
[12/13/2021, 8:56:22 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number<PHONE_NUMBER>7777777 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] [Hall] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed<PHONE_NUMBER>2222223) since provided Tuya value (237) exceeds configured maximum Tuya value (100). Please update your configuration!
[12/13/2021, 8:56:22 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number<PHONE_NUMBER>2222223 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] [Lobby] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[12/13/2021, 8:56:22 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] [Master] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[12/13/2021, 8:56:22 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] [Front Sconce] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[12/13/2021, 8:56:22 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[12/13/2021, 8:56:22 AM] [TuyaWebPlatform] [Table] Characteristic.Brightness - Characteristic 'Brightness' will receive value higher than allowed (1100) since provided Tuya value (1000) exceeds configured maximum Tuya value (100). Please update your configuration!
[12/13/2021, 8:56:22 AM] [@milo526/homebridge-tuya-web] This plugin generated a warning from the characteristic 'Brightness': characteristic was supplied illegal value: number 1100 exceeded maximum of 100. See https://git.io/JtMGR for more info.


Difficult to select portion of the message

It is difficult to select portion of the message, when some icons appear in the end and block the view of entire message. Can they be outside of message box or have a separate row as it is visible on second image?
Image 1

Image 2

We are working on a fix for this problem, but we don't have a firm date for when it will be released.

Can one help with it? Any description on planned solution?


Make docker_install configurable by flattening its structure

Is your feature request related to a problem? Please describe.
In order to modify anything under the docker_install variable (https://github.com/MVladislav/ansible-docker/blob/main/defaults/main.yml#L19-L37) one needs to make a copy of the whole dict and modify what he needs. This is due to an Ansible design decision to not merge dicts (https://stackoverflow.com/a/23855364) and consequently one can not just override a specific value.
Describe the solution you'd like
It would be easy to configure anything if the docker_install variable would be flattened into variables with simple types (e.g. docker_install_version: stable).
Describe alternatives you've considered
/
Additional context
/

docker_install variable is flatten for each variable as docker_install_*,
to not need copy the whole dict and modify only few needs.
docker_install_gpg:
  id: 0EBFCD88
  url: https://download.docker.com/linux/ubuntu/gpg
  name: docker_release_ce.gpg
docker_install_repo: https://download.docker.com/linux/ubuntu
docker_install_version: stable
# NOTE: manual update when newer version available
# NOTE: will fallback when current install under lunar
docker_install_release_fallback: jammy
docker_install_release_skip_lunar: lunar
docker_install_apt:
  - docker-ce
  - docker-ce-cli
  - docker-ce-rootless-extras
  - containerd.io
  - docker-compose-plugin
docker_install_pip: []

Awesome! :+1:


Issue Related to agent?.createVerifiablePresentation()

step 1 i was assinged a new Vc to the DID (user 1) like:

Profile = {
  name ="sam",
  age = "18"
}

step 2 then User 2 create a SDR request for getting the name and age from the (user 1) Did.
step 3 then i was able to see the SDR request Message in the "requests" page of the agent explorer UI.
step 4 when i click on that Message then some time app crash and some time i am able to see the SDR page.
step 5 after this i was selected the data that i want to share. but when i click on share button then {"error":"Cannot read properties of undefined (reading 'jwt')"}  this error comes.

@vijay05155 Hi, I'm looking into this now. Is it possible for you to share the arguments you passed into the createVerifiablePresentation function? Also, are you sure that the DID used to generate the SDR has a Secp256k1 signing key? That function will throw an exception if that type of key is not found

I wasn't able to repro this exactly, but I believe this may have been fixed by my recent PR to improve SDR flows. At minimum, it should handle the error more gracefully and give more context to the error if we are able to repro still. Closing this issue for now but will re-open if we find repro steps on latest


Translate documentation to Chinese & Russian

Many users of Cameradar are not english-speakers but Chinese and Russian speakers. I saw already that @wxylssy started translating the README to Simplified Chinese on his fork.
It would be nice to have official translations to help new users that are not english-speakers understand the project, so @wxylssy if you'd like to contribute you are more than welcome, and if anyone is interested in translating to Russian, feel free as well :)
The best would be to have three README files:

README.md in english
README_ZH.md in chinese
README_RU.md in russian

And to add links to the different languages in the headers.

ello,  i want to help you!
I speak Russian and can translate the readme file


Planned updates and enhancements

A few things that could use enhancing:
Issuer load balancing
CertMagic currently tries issuers in order to get a certificate, and later ones are only fallbacks. This is already more than most certificate automators do, but load balancing would be a useful option: still fall back if one is down, but first choose (randomly? round-robin?) from among the selection rather than always trying the first one first.
For renewals, CertMagic tries the same issuer as last time, if configured/present. But this could also be load-balanced.
Private key rotation
Currently, CertMagic reuses the private key when renewing a certificate. This is the expected behavior most of the time, but can be problematic if the key is compromised (without knowing; CertMagic will already replace a private key if a certificate is revoked with reason keyCompromise, but this seldom if ever happens in practice). If the key was compromised by unauthorized access to storage, for example, rotating the key will simply give the attacker the new key. If the compromise is known, the cert will typically be revoked.
One argument is made against this: that the hole may be patched serendipitously, i.e. via felix culpa, such as applying a system upgrade or fixing an ACL. You didn't know a leak occurred but you fixed it anyway. In that case the cert would not be revoked, but it would still be useful to rotate the key.
Probably these days, CertMagic should use new keys for every cert rather than reusing keys.
ARI
ACME Renewal Information or ARI is an extension to ACME that hints at when to renew a certificate. I have mixed feelings on the utility of this extension, and I think it is unfortunate that it complicates already-complex infrastructure regarding revocation, which is broken anyway, and should be phased out in favor short-lived certificates instead.
Brief digression: If ARI tells you to renew early, the server may optionally include a URL which explains the reason. If the reason is impending revocation, then why continue to trust the certificate at all? If you know it will be revoked, the certificate might as well not be trusted. Or maybe the reason is to smooth out load; only respectful clients will do this anyway, and I don't know if it will help the stampeding herd problem that CAs sometimes face. But anyways...
We can support ARI to be a good Internet citizen.

My thoughts:

Regarding issuers, I agree in theory that load balancing would be a good idea, but in practice (in the case of Caddy anyway), ZeroSSL has been somewhat less reliable than Let's Encrypt, so it feels better to use as a fallback rather than a "shared primary".

Regarding private keys, it might also be a good time to support https://github.com/caddyserver/caddy/issues/2854 which would help with things like key pinning, and to do that they need the server to be using a consistent well-known key, instead of a generated one. Of course that means that it's the user's responsibility to rotate the key if it gets compromised.

Regarding ARI, I agree. Unfortunate, but we should still do it.
I would hope that your errata https://www.rfc-editor.org/errata/eid6317 would get reviewed and implemented, since that would help alleviate pressure on ACME servers with those changes, since we're forced to be wasteful with API calls.

Thanks for your thoughts, Francis:

so it feels better to use as a fallback rather than a "shared primary".

Yeah, or maybe configurable policies... simpler than a reverse proxy's, but, like: "first", "first_random", and "first_round_robin".

Regarding private keys, it might also be a good time to support https://github.com/caddyserver/caddy/issues/2854 which would help with things like key pinning, and to do that they need the server to be using a consistent well-known key, instead of a generated one.

Ok, I'll look into that.

Regarding ARI,

See below...
An update

Issuer LB and private key rotation are still planned. Heck, maybe I should just do those this week and get them done.

ARI is shelved indefinitely. I tentatively added support for it into ACMEz, but stopped when I got to CertMagic due to unresolved questions where currently, ARI does not make any sense as-is. I suspect a fundamental re-thinking of a solution may be needed.

Yeah, the load balancing policy approach is a good idea :+1:

Ok cool -- I've implemented this, and decided to skip "round_robin" for now, since I'm not sure what utility that really has, especially given that configs are short-lived/ephemeral.
Just going to start simple for now. By default, the current behavior is the same: try each issuer in turn. You can configure "first random" which shuffles the list, then tries each issuer in turn.
Since ARI is on hold, I'm going to close this issue and we can open a new one if the spec evolves or there is something actionable to do there.

I just had an idea regarding ARI (probably not the best place to discuss about this, but I value your feedback), would it be imaginable to put the information about "renewal window" into the OCSP response?
Since (according to Wikipedia) the OCSP responder is typically run by the certificate issuer, it could give the info if a renewal should occur soon.

This has already been discussed: https://mailarchive.ietf.org/arch/msg/acme/b-RddSX8TdGYvO3f9c7Lzg6I2I4/
(sorry for the noise)

It's alright, I appreciate careful thinking like that!

New issue tracking ARI: https://github.com/caddyserver/certmagic/issues/284