file not found: Resources\Stager.exe

The more description, the faster your problem will be solved...
The target framework of Stager.csproj is set to .NET 3.5 for reasons described in the documentation. You probably need to install that framework version.

The more description, the faster your problem will be solved...
The target framework of Stager.csproj is set to .NET 3.5 for reasons described in the documentation. You probably need to install that framework version.

Thanks ill try that.
I've one more question, If the rootkit hides the registry $77-configuration from which we have to hide the editable, how to write the config programmatically?

@bytecode77
I installed the service, it was working fine. but after reboot its fucked up. when i open the testconsole it said "r77 service is not running"

I've one more question, If the rootkit hides the registry $77-configuration from which we have to hide the executable, how to write to the config programmatically to set keys?

The registry key will not appear, but you can still open it and write to it, even without elevated privileges. There are other ways, too, to hide an executable (see the documentation)

I've one more question, If the rootkit hides the registry $77-configuration from which we have to hide the executable, how to write to the config programmatically to set keys?

The registry key will not appear, but you can still open it and write to it, even without elevated privileges. There are other ways, too, to hide an executable (see the documentation)

Bro, it broked my vm after reboot.

i added simple c++ application to the startup but it didnt started why?

Is your simple C++ app a GUI app, like a MessageBox? If so, then you should know that startup applications start under the SYSTEM user, which doesn't have a desktop. Was that the case?
Have you read the documentation yet to spot potential usage errors?

and how to start the hidden file ? i cant start it programmatically or from cmd

and how to start the hidden file ? i cant start it programmatically or from cmd

I'm not sure where you're at... If you are talking about startup programs, see the documentation for how to configure the $77config\startup key.
To launch a file programmatically that is hidden, you can use the control pipe.
Please help me to help you by asking specific, detailed and elaborated questions.

will it cause any problems like BSOD, or will it no longer be persistent like before?

Excluding these particualr processes will just make hidden stuff more visible, because some processes then can see it. I wouldn't exclude all services (svchost). Crashes should usually never happen, though.


cmake is not resolved on Linux when in path

When cmake is installed in the default path on linux it is not resolved. I believe this is because of https://github.com/patriksvensson/Cake.CMake/blob/master/src/Cake.CMake/CMakeRunner.cs#L71-L74 explicitly requesting cmake.exe.
I'll test this, but I think you could either add "cmake" to the returned list or even just cut the .exe off to fix this issue. Once I verify this I'll submit a pull request and add a relevant unit test.
(As a workaround, you can symlink cmake to cmake.exe on linux and it is then resolved)

@nathansoz Ah, never tested this on Linux to be honest. Adding cmake to the returned list as you suggested should solve the problem. A PR is more than welcome :smile:

Would it be possible to get the nuget package pushed for this? :)

@nathansoz I've published the new package now (v0.1.0) but it might take a while for the package to properly index. Sorry for not doing this sooner. https://www.nuget.org/packages/Cake.CMake


Cannot click "Got it" link after agreeing to receive email notifications  🐛

URL of the Page
https://www.researchequals.com/dashboard
What happened?
I noticed that after clicking yes 👍 to receive email notification, I cannot click "Got it!" button on the confirmation (as below).

Steps to reproduce

Go to dashboard with an account that has not completed the onboarding quest for email notifications
Select "Yes" to receive email notifications
Cannot click "Got it!" (I expected that we can close the card by clicking this.)

What browser(s) did you use?
Chrome
Anything else?
No response

Thanks for writing this up!
This was not intended to be clickable - understand that the link-esque styling made it look that way. I will check the PR and see how it works.


⚠ Carbubu has degraded performance

In e7f4d37, Carbubu (https://carbubu.fr) experienced degraded performance:

HTTP code: 200
Response time: 3884 ms

Resolved: Carbubu performance has improved in 0effb03 after 10 minutes.


Improvement when switching between blockchains

Pages with similar features are retained when switching to another blockchain type

https://github.com/chaineco/blockcare/commit/6461396a0f508420869e468a76f485d0456103c7


feat: implemented res.append

Resolves: #117

Codecov Report

Merging #126 into master will increase coverage by 1.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #126      +/-   ##
==========================================
+ Coverage   62.80%   63.81%   +1.00%
==========================================
  Files          44       46       +2
  Lines        1616     1661      +45
  Branches      417      434      +17
==========================================
+ Hits         1015     1060      +45
  Misses        599      599
  Partials        2        2

Impacted Files
Coverage Δ

packages/res/src/append.ts
100.00% <100.00%> (ø)

packages/res/src/index.ts
100.00% <100.00%> (ø)

packages/unless/src/index.ts
100.00% <0.00%> (ø)

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 733724e...3649220. Read the comment docs.

looks good, tests are already written, and they pass
merging and will soon publish


deposit: autocompletion of from ORCID (author name when entering ORCID)

It happens that authors submit new work with different variations of their name. This could be resolved by letting them enter their ORCID and have Invenio auto complete their name.
I think integrating GET orcid_id API could be helpful?
http://support.orcid.org/knowledgebase/articles/116874-orcid-api-guide
Is this desired by more people?

Issue moved to inveniosoftware/invenio-deposit #90 via ZenHub


Avoid auto capitalize on FasthAuth sign up page

Turning auto capitalizing off for email and account id results in improved UX, especially on mobile. Currently while signing up on mobile, the account id input shows an error since the input automatically capitalizes the first letter, which is not a valid account id.

@Patrick1904 do we need to add the same for sign in page?

@Patrick1904 do we need to add the same for sign in page?

Yes, it would be great if we can apply this wherever we show an input for email or account id.


Hardcode graphql version for 4.8.0 release

DO NOT MERGE
Using branch for hardcoded the graphql version for the 4.8.0 release, and probably also the 4.8.1 release
Should not be using hardcoded versions for the 4.9.0 release

I'm guessing this can be closed?


[SPARK-36605][BUILD] Upgrade Jackson to 2.12.5

What changes were proposed in this pull request?

This PR upgrades Jackson from 2.12.3 to 2.12.5.
Why are the changes needed?

Recently, Jackson 2.12.5 was released and it seems to be expected as the last full patch release for 2.12.x.
This release includes a regression in jackson-databind introduced in 2.12.3 which Spark 3.2 currently depends on.
https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.12.5
Does this PR introduce any user-facing change?

Dependency maintenance.
How was this patch tested?

CIs.

Test build #142841 has started for PR 33860 at commit b192eb9.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47343/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47343/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47343/

Test build #142841 has finished for PR 33860 at commit b192eb9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/142841/

Thanks. Merging to master.

+1, LGTM.


Combining partition, unzip, filter_map

Related to my issue last week, #801, I have a new use case that I cannot do with the tools currently available in rayon. I currently do this:
let ts: Vec<T> = rs
    .par_iter()
    .filter_map(|r| f_yielding_some_t(r))
    .collect();

let us: Vec<U> = rs
    .par_iter()
    .filter_map(|r| f_yielding_some_u(r))
    .collect();

In order to only perform the traversal once (rs is very big and I am actually doing rs.tuple_combinations().par_bridge(), with the IterTools::tuple_combinations adapter), I want to combine these loops:
let (some_ts, some_us): (Vec<Some<T>>, Vec<Some<U>> = rs
    .par_iter()
    .map(|r| (f_yielding_some_t(r), f_yielding_some_u(r))
    .unzip();

But this would require a second pass over the vectors and demand a second allocation.
I am reading #802 to understand it and also the implementation of unzip.

One way is to write a wrapper that does further filtering on the unzipped items, like:
struct OnlySome<T>(Vec<T>);

impl<T: Send> ParallelExtend<Option<T>> for OnlySome<T> {
    fn par_extend<I>(&mut self, par_iter: I)
    where
        I: IntoParallelIterator<Item = Option<T>>,
    {
        let some = par_iter.into_par_iter().filter_map(identity);
        self.0.par_extend(some);
    }
}

Here's a full example:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=5abffae1c70df13fc496fd82b9e77ede

Thank you very much. I just implemented this and it helped me go from 800ms to 900ms for the construction of 2 hashbrown::HashMaps in successive to about 500ms doing it in one go.
Does it make sense to add something like this to rayon proper?

Well, I think are a lot of possible variations along these lines, which we can't hope to enumerate. I'm more inclined to present that as an example of rayon composition tricks, but maybe we can have a module of such things provided in their own right.


Does an application support multiple new WebTracerProvider and register ZoneContextManager?

[ ] This only affects the JavaScript OpenTelemetry library
[ ] This may affect other libraries, but I would like to get opinions here first

In micro applications, can each sub application be initialized once? Is there an endless loop

The global context manager registration can be independent from the global tracer provider registration. However, there should be one single global singleton registered for each one.
Would you mind expanding on what's the expected behavior when you create multiple tracer provider?

The global context manager registration can be independent from the global tracer provider registration. However, there should be one single global singleton registered for each one.
Would you mind expanding on what's the expected behavior when you create multiple tracer provider?
Thank you for your answer. It is normal to register the ZoneContextManager only once in the project. Multiple registrations will cause the browser console to crash, such as memory overflow. We have now deleted the use of other sub applications to solve this problem, but I would like to know why there is such a problem

The global context manager registration can be independent from the global tracer provider registration. However, there should be one single global singleton registered for each one.
Would you mind expanding on what's the expected behavior when you create multiple tracer provider?

Thank you for your answer. It is normal to register the ZoneContextManager only once in the project. Multiple registrations will cause the browser console to crash, such as memory overflow. We have now deleted the use of other sub applications to solve this problem, but I would like to know why there is such a problem


No ice

Description
Reference issue
Fixes #...

Hi @lisay-yan
I am really sorry, but I think we need to make some changes before this is merged. WebRTC doesn't have a NoICE option. If we merge this it will break WASM/interop with other implementations.
What are you trying to achieve?

Do you want to remove signaling requirements?
Are you trying to reduce implementation complexity?
Are you trying to reduce connection times?

Hi @lisay-yan
I am really sorry, but I think we need to make some changes before this is merged. WebRTC doesn't have a NoICE option. If we merge this it will break WASM/interop with other implementations.

[Lisa] ICE is designed for NAT traversal.
https://datatracker.ietf.org/doc/html/rfc8445
Agree that is common need for WASM. That is why introduce ICENone configuration in peerconn, which default is false to guard not impact WASM/interop.
IMSDC (3gpp 26.114) is based on webrtc. In typical IMS deployments, it is expected that no need to use NAT at core network. So, ICE is not necessary for no NAT network.
That is the key trigger to implement ICENone.

What are you trying to achieve?
[Lisa] Try to provide common webrtc based solution for no NAT scenarios.

Do you want to remove signaling requirements?
[Lisa] No NAT, No ICE, stun steps should be skipped.
Are you trying to reduce implementation complexity?
[Lisa] Only turn on ICENone for no NAT deployment.
Are you trying to reduce connection times?
[Lisa] Yes, it is indeed faster than perform ICE full steps. And that is indeed not necessary for no NAT deployment.

I am agreeing with @Sean-Der here, that this is not covered by any RFC and we should be careful to include it.
@lisay-yan I also have some difficulties to understand your use case.
What you describe sounds like you want to have a lite ICE agent?
See: https://www.rfc-editor.org/rfc/rfc8445#section-2.5

I am agreeing with @Sean-Der here, that this is not covered by any RFC and we should be careful to include it.
@lisay-yan I also have some difficulties to understand your use case.
What you describe sounds like you want to have a lite ICE agent?

And for IMS usage:
Access network only deliver c line and port in m line to indicate media path since no NAT in IMS core network.
Pion is used in IMS core network to provide IMSDC service described at 3gpp 36114.
So, ICE lite is useless for IMS core side components.
@Sean-Der  @stv0g
Would you like give more wise proposal for only c line and port in m line based SDP negotiation via pion/webrtc?
Agree my idea is draft and try best to reuse all state in webrtc now.
Appreciate your support in advance.
Lisa

Hi @Sean-Der @stv0g
This is Hank from Nokia. I'm in same group as @lisay-yan.
First of all, thanks you all for providing the great Pion WebRTC stack. The Pion helps us quickly building up IMS data channel solution!
I want to give you more backgroud on how we use the Pion in IMS network as attachment.
Pion no ICE.docx
In short, no-ICE use case is common in IMS Core network since there is NO NAT in IMS deployment. In addtion to ICE case, supporting no-ICE could make Pion more attractive and popular in telecom. If you agree, we can contribute our change on Pion to support no-ICE use case based on configuration/input w/o impact on existing use cases.
Welcome comments/suggestions.
Kind regards,
Hank

Very cool! Thanks for sharing @lisay-yan @hankliu9  You don't want ICE at all because your communicating with a a non-webrtc endpoint.
We totally can make this work. I will work on a PR this weekend to support what you are building.
Having a NoICE mode isn't something I can do (just not part of the standard). I can give you hooks to do whatever you wish though :)

Hi @Sean-Der @stv0g
Thanks for your comments and suggestions! Yes, it's mobile device for IMS Data Channel client, which is not WebRTC client. In IMS Core network, the IMS Data Channel connection is also in between IMS AGW and DCMF, which is network-to-network interface and no NAT.
If the DC Media Function (we're using Pion to build up) supports ICE lite (host candidates only), the IMS AGW (counterpart) is also required to support ICE or ICE lite. Currently, the IMS AGW does NOT support ICE in core side at all. Then still have interworking issue between ICE lite agent and no-ICE agent. For both ICE lite agents case, from my understanding, the RFC8445 doesn't have very details on how it works since ICE lite agent doesn't generate connectivity check and nominating candidates request, just in passive mode.
Thanks for working on https://github.com/pion/ice/issues/623, which shall make NoICE mode implementation much easy. Then we can make NoICE implementation based on it. Once we implementate the NoICE mode, can we contribute it into Pion?
Again, it shall be prefect if you can implementate the NoICE mode in Pion since you're master on Pion. Then the Pion can support both WebRTC and IMS Data Channal cases, which shall increase Pion in leading position in WebRTC stack.
Lisa and I are on holiday for incoming whole week. Looking forward to checking your comments and new implementation once come back.
Cheers,
Hank


Trace ID should always be displayed

Per discussion w/ @TLSteinacker , for analytical purposes the trace ID should always accompany the spot, regardless of whether or not it's participating in a merge structure.

This applies to the "final" spots (merged and singleton, passing all filters).


Several type mismatches.

2023-06-02 23:48:56.103  - info: sainlogic.0 (709070) starting. Version 0.10.3 in /opt/iobroker/node_modules/iobroker.sainlogic, node: v20.2.0, js-controller: 5.0.1-alpha.0-20230525-c580eb7e
2023-06-02 23:48:56.151  - info: sainlogic.0 (709070) Starting Listener
2023-06-02 23:48:56.202  - info: sainlogic.0 (709070) Creating new data point: info.model
2023-06-02 23:48:56.205  - info: sainlogic.0 (709070) Creating new data point: info.freq
2023-06-02 23:48:56.206  - info: sainlogic.0 (709070) Creating new data point: info.last_listener_update
2023-06-02 23:48:56.208  - info: sainlogic.0 (709070) Creating new data point: weather.current.dailyrain
2023-06-02 23:48:56.208  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.dailyrain
2023-06-02 23:48:56.210  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.daily.dailyrain
2023-06-02 23:48:56.211  - info: sainlogic.0 (709070) Creating new data point: weather.current.dailyrain_piezo
2023-06-02 23:48:56.212  - info: sainlogic.0 (709070) Creating new data point: weather.current.indoorhumidity
2023-06-02 23:48:56.213  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.indoorhumidity
2023-06-02 23:48:56.213  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.daily.indoorhumidity
2023-06-02 23:48:56.214  - info: sainlogic.0 (709070) Creating new data point: weather.minvalues.absolut.indoorhumidity
2023-06-02 23:48:56.215  - info: sainlogic.0 (709070) Creating new data point: weather.minvalues.daily.indoorhumidity
2023-06-02 23:48:56.216  - info: sainlogic.0 (709070) Creating new data point: weather.current.indoortemp
2023-06-02 23:48:56.216  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.indoortemp
2023-06-02 23:48:56.217  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.daily.indoortemp
2023-06-02 23:48:56.217  - info: sainlogic.0 (709070) Creating new data point: weather.minvalues.absolut.indoortemp
2023-06-02 23:48:56.218  - info: sainlogic.0 (709070) Creating new data point: weather.minvalues.daily.indoortemp
2023-06-02 23:48:56.218  - info: sainlogic.0 (709070) Creating new data point: weather.current.monthlyrain
2023-06-02 23:48:56.219  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.monthlyrain
2023-06-02 23:48:56.219  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.daily.monthlyrain
2023-06-02 23:48:56.220  - info: sainlogic.0 (709070) Creating new data point: weather.current.monthlyrain_piezo
2023-06-02 23:48:56.220  - info: sainlogic.0 (709070) Creating new data point: weather.current.outdoorhumidity
2023-06-02 23:48:56.220  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.outdoorhumidity
2023-06-02 23:48:56.221  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.daily.outdoorhumidity
2023-06-02 23:48:56.221  - info: sainlogic.0 (709070) Creating new data point: weather.minvalues.absolut.outdoorhumidity
2023-06-02 23:48:56.222  - info: sainlogic.0 (709070) Creating new data point: weather.minvalues.daily.outdoorhumidity
2023-06-02 23:48:56.222  - info: sainlogic.0 (709070) Creating new data point: weather.current.outdoortemp
2023-06-02 23:48:56.222  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.outdoortemp
2023-06-02 23:48:56.222  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.daily.outdoortemp
2023-06-02 23:48:56.223  - info: sainlogic.0 (709070) Creating new data point: weather.minvalues.absolut.outdoortemp
2023-06-02 23:48:56.223  - info: sainlogic.0 (709070) Creating new data point: weather.minvalues.daily.outdoortemp
2023-06-02 23:48:56.224  - info: sainlogic.0 (709070) Creating new data point: weather.current.pressureabs
2023-06-02 23:48:56.224  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.pressureabs
2023-06-02 23:48:56.224  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.daily.pressureabs
2023-06-02 23:48:56.225  - info: sainlogic.0 (709070) Creating new data point: weather.minvalues.absolut.pressureabs
2023-06-02 23:48:56.225  - info: sainlogic.0 (709070) Creating new data point: weather.minvalues.daily.pressureabs
2023-06-02 23:48:56.225  - info: sainlogic.0 (709070) Creating new data point: weather.current.pressurerel
2023-06-02 23:48:56.226  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.pressurerel
2023-06-02 23:48:56.226  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.daily.pressurerel
2023-06-02 23:48:56.227  - info: sainlogic.0 (709070) Creating new data point: weather.minvalues.absolut.pressurerel
2023-06-02 23:48:56.227  - info: sainlogic.0 (709070) Creating new data point: weather.minvalues.daily.pressurerel
2023-06-02 23:48:56.228  - info: sainlogic.0 (709070) Creating new data point: weather.current.rain
2023-06-02 23:48:56.228  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.rain
2023-06-02 23:48:56.228  - info: sainlogic.0 (709070) Creating new data point: weather.current.rain_piezo
2023-06-02 23:48:56.229  - info: sainlogic.0 (709070) Creating new data point: weather.current.solarradiation
2023-06-02 23:48:56.229  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.solarradiation
2023-06-02 23:48:56.229  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.daily.solarradiation
2023-06-02 23:48:56.230  - info: sainlogic.0 (709070) Creating new data point: weather.current.uvi
2023-06-02 23:48:56.230  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.uvi
2023-06-02 23:48:56.231  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.daily.uvi
2023-06-02 23:48:56.231  - info: sainlogic.0 (709070) Creating new data point: weather.current.weeklyrain
2023-06-02 23:48:56.232  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.weeklyrain
2023-06-02 23:48:56.232  - info: sainlogic.0 (709070) Creating new data point: weather.current.weeklyrain_piezo
2023-06-02 23:48:56.232  - info: sainlogic.0 (709070) Creating new data point: weather.current.winddir
2023-06-02 23:48:56.233  - info: sainlogic.0 (709070) Creating new data point: weather.current.windgustspeed
2023-06-02 23:48:56.233  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.windgustspeed
2023-06-02 23:48:56.233  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.daily.windgustspeed
2023-06-02 23:48:56.233  - info: sainlogic.0 (709070) Creating new data point: weather.current.maxdailygust
2023-06-02 23:48:56.234  - info: sainlogic.0 (709070) Creating new data point: weather.current.windspeed
2023-06-02 23:48:56.234  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.windspeed
2023-06-02 23:48:56.234  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.daily.windspeed
2023-06-02 23:48:56.235  - info: sainlogic.0 (709070) Creating new data point: weather.current.yearlyrain
2023-06-02 23:48:56.235  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.yearlyrain
2023-06-02 23:48:56.236  - info: sainlogic.0 (709070) Creating new data point: weather.current.totalrainin
2023-06-02 23:48:56.236  - info: sainlogic.0 (709070) Creating new data point: weather.maxvalues.absolut.totalrainin
2023-06-02 23:48:56.236  - info: sainlogic.0 (709070) Creating new data point: weather.current.yearlyrain_piezo
2023-06-02 23:48:56.237  - info: sainlogic.0 (709070) Creating new data point: weather.current.soilmoisture
2023-06-02 23:48:56.237  - info: sainlogic.0 (709070) Creating new data point: weather.info.soilbatt
2023-06-02 23:48:56.281  - info: sainlogic.0 (709070) Creating new data point: weather.info.wh80batt
2023-06-02 23:48:56.282  - info: sainlogic.0 (709070) Creating new data point: weather.info.wh40batt
2023-06-02 23:48:56.283  - info: sainlogic.0 (709070) Creating new data point: weather.info.wh25batt
2023-06-02 23:48:56.284  - info: sainlogic.0 (709070) Creating new data point: weather.current.tf_ch
2023-06-02 23:48:56.285  - info: sainlogic.0 (709070) Creating new data point: weather.info.tf_batt
2023-06-02 23:48:56.286  - info: sainlogic.0 (709070) Creating new data point: weather.current.tf_co2
2023-06-02 23:48:56.286  - info: sainlogic.0 (709070) Creating new data point: weather.current.humi_co2
2023-06-02 23:48:56.287  - info: sainlogic.0 (709070) Creating new data point: weather.current.pm25_co2
2023-06-02 23:48:56.288  - info: sainlogic.0 (709070) Creating new data point: weather.daily.pm25_24h_co2
2023-06-02 23:48:56.288  - info: sainlogic.0 (709070) Creating new data point: weather.current.pm10_co2
2023-06-02 23:48:56.289  - info: sainlogic.0 (709070) Creating new data point: weather.daily.pm10_24h_co2
2023-06-02 23:48:56.290  - info: sainlogic.0 (709070) Creating new data point: weather.current.co2
2023-06-02 23:48:56.291  - info: sainlogic.0 (709070) Creating new data point: weather.daily.co2_24h
2023-06-02 23:48:56.291  - info: sainlogic.0 (709070) Creating new data point: weather.info.co2_batt
2023-06-02 23:48:56.292  - info: sainlogic.0 (709070) Creating new data point: weather.current.lightning_time
2023-06-02 23:48:56.292  - info: sainlogic.0 (709070) Creating new data point: weather.current.lightning
2023-06-02 23:48:56.293  - info: sainlogic.0 (709070) Creating new data point: weather.daily.lightning_num
2023-06-02 23:48:56.294  - info: sainlogic.0 (709070) Creating new data point: weather.current.eventrain_piezo
2023-06-02 23:48:56.294  - info: sainlogic.0 (709070) Creating new data point: weather.current.hourlyrain_piezo
2023-06-02 23:48:56.298  - warn: sainlogic.0 (709070) Object sainlogic.0.info.model is invalid: Default value has to be type "string" but received type "number"
2023-06-02 23:48:56.298  - warn: sainlogic.0 (709070) This object will not be created in future versions. Please report this to the developer.
2023-06-02 23:48:56.299  - warn: sainlogic.0 (709070) Object sainlogic.0.info.freq is invalid: Default value has to be type "string" but received type "number"
2023-06-02 23:48:56.299  - warn: sainlogic.0 (709070) This object will not be created in future versions. Please report this to the developer.
2023-06-02 23:48:56.300  - warn: sainlogic.0 (709070) Object sainlogic.0.info.last_listener_update is invalid: Default value has to be type "string" but received type "number"
2023-06-02 23:48:56.300  - warn: sainlogic.0 (709070) This object will not be created in future versions. Please report this to the developer.
2023-06-02 23:48:56.741  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.info.model" has to be type "string" but received type "number"
2023-06-02 23:48:56.742  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.info.freq" has to be type "string" but received type "number"
2023-06-02 23:48:56.743  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.info.last_listener_update" has to be type "string" but received type "number"
2023-06-02 23:48:56.979  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.dailyrain" has to be type "number" but received type "string"
2023-06-02 23:48:56.984  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.dailyrain" has to be type "number" but received type "string"
2023-06-02 23:48:56.985  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.daily.dailyrain" has to be type "number" but received type "string"
2023-06-02 23:48:56.986  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.dailyrain_piezo" has to be type "number" but received type "string"
2023-06-02 23:48:56.988  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.indoorhumidity" has to be type "number" but received type "string"
2023-06-02 23:48:56.989  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.indoorhumidity" has to be type "number" but received type "string"
2023-06-02 23:48:56.990  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.daily.indoorhumidity" has to be type "number" but received type "string"
2023-06-02 23:48:56.991  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.minvalues.absolut.indoorhumidity" has to be type "number" but received type "string"
2023-06-02 23:48:56.992  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.minvalues.daily.indoorhumidity" has to be type "number" but received type "string"
2023-06-02 23:48:56.992  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.indoortemp" has to be type "number" but received type "string"
2023-06-02 23:48:56.993  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.indoortemp" has to be type "number" but received type "string"
2023-06-02 23:48:56.994  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.daily.indoortemp" has to be type "number" but received type "string"
2023-06-02 23:48:56.995  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.minvalues.absolut.indoortemp" has to be type "number" but received type "string"
2023-06-02 23:48:56.996  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.minvalues.daily.indoortemp" has to be type "number" but received type "string"
2023-06-02 23:48:56.997  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.monthlyrain" has to be type "number" but received type "string"
2023-06-02 23:48:56.998  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.monthlyrain" has to be type "number" but received type "string"
2023-06-02 23:48:56.998  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.daily.monthlyrain" has to be type "number" but received type "string"
2023-06-02 23:48:56.999  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.monthlyrain_piezo" has to be type "number" but received type "string"
2023-06-02 23:48:57.000  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.outdoorhumidity" has to be type "number" but received type "string"
2023-06-02 23:48:57.001  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.outdoorhumidity" has to be type "number" but received type "string"
2023-06-02 23:48:57.001  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.daily.outdoorhumidity" has to be type "number" but received type "string"
2023-06-02 23:48:57.002  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.minvalues.absolut.outdoorhumidity" has to be type "number" but received type "string"
2023-06-02 23:48:57.003  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.minvalues.daily.outdoorhumidity" has to be type "number" but received type "string"
2023-06-02 23:48:57.004  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.outdoortemp" has to be type "number" but received type "string"
2023-06-02 23:48:57.004  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.outdoortemp" has to be type "number" but received type "string"
2023-06-02 23:48:57.005  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.daily.outdoortemp" has to be type "number" but received type "string"
2023-06-02 23:48:57.006  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.minvalues.absolut.outdoortemp" has to be type "number" but received type "string"
2023-06-02 23:48:57.007  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.minvalues.daily.outdoortemp" has to be type "number" but received type "string"
2023-06-02 23:48:57.007  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.pressureabs" has to be type "number" but received type "string"
2023-06-02 23:48:57.008  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.pressureabs" has to be type "number" but received type "string"
2023-06-02 23:48:57.009  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.daily.pressureabs" has to be type "number" but received type "string"
2023-06-02 23:48:57.011  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.minvalues.absolut.pressureabs" has to be type "number" but received type "string"
2023-06-02 23:48:57.012  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.minvalues.daily.pressureabs" has to be type "number" but received type "string"
2023-06-02 23:48:57.013  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.pressurerel" has to be type "number" but received type "string"
2023-06-02 23:48:57.014  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.pressurerel" has to be type "number" but received type "string"
2023-06-02 23:48:57.015  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.daily.pressurerel" has to be type "number" but received type "string"
2023-06-02 23:48:57.016  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.minvalues.absolut.pressurerel" has to be type "number" but received type "string"
2023-06-02 23:48:57.017  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.minvalues.daily.pressurerel" has to be type "number" but received type "string"
2023-06-02 23:48:57.018  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.rain" has to be type "number" but received type "string"
2023-06-02 23:48:57.019  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.rain" has to be type "number" but received type "string"
2023-06-02 23:48:57.037  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.rain_piezo" has to be type "number" but received type "string"
2023-06-02 23:48:57.043  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.solarradiation" has to be type "number" but received type "string"
2023-06-02 23:48:57.044  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.solarradiation" has to be type "number" but received type "string"
2023-06-02 23:48:57.045  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.daily.solarradiation" has to be type "number" but received type "string"
2023-06-02 23:48:57.046  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.uvi" has to be type "number" but received type "string"
2023-06-02 23:48:57.047  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.uvi" has to be type "number" but received type "string"
2023-06-02 23:48:57.048  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.daily.uvi" has to be type "number" but received type "string"
2023-06-02 23:48:57.049  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.weeklyrain" has to be type "number" but received type "string"
2023-06-02 23:48:57.050  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.weeklyrain" has to be type "number" but received type "string"
2023-06-02 23:48:57.051  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.weeklyrain_piezo" has to be type "number" but received type "string"
2023-06-02 23:48:57.053  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.winddir" has to be type "number" but received type "string"
2023-06-02 23:48:57.126  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.windgustspeed" has to be type "number" but received type "string"
2023-06-02 23:48:57.168  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.windgustspeed" has to be type "number" but received type "string"
2023-06-02 23:48:57.170  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.daily.windgustspeed" has to be type "number" but received type "string"
2023-06-02 23:48:57.170  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.maxdailygust" has to be type "number" but received type "string"
2023-06-02 23:48:57.171  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.windspeed" has to be type "number" but received type "string"
2023-06-02 23:48:57.172  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.windspeed" has to be type "number" but received type "string"
2023-06-02 23:48:57.173  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.daily.windspeed" has to be type "number" but received type "string"
2023-06-02 23:48:57.192  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.yearlyrain" has to be type "number" but received type "string"
2023-06-02 23:48:57.236  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.yearlyrain" has to be type "number" but received type "string"
2023-06-02 23:48:57.237  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.totalrainin" has to be type "number" but received type "string"
2023-06-02 23:48:57.238  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.maxvalues.absolut.totalrainin" has to be type "number" but received type "string"
2023-06-02 23:48:57.239  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.yearlyrain_piezo" has to be type "number" but received type "string"
2023-06-02 23:48:57.240  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.soilmoisture" has to be type "number" but received type "string"
2023-06-02 23:48:57.241  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.info.soilbatt" has to be type "number" but received type "string"
2023-06-02 23:48:57.242  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.info.wh80batt" has to be type "number" but received type "string"
2023-06-02 23:48:57.243  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.info.wh40batt" has to be type "number" but received type "string"
2023-06-02 23:48:57.244  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.info.wh25batt" has to be type "number" but received type "string"
2023-06-02 23:48:57.244  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.tf_ch" has to be type "number" but received type "string"
2023-06-02 23:48:57.245  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.info.tf_batt" has to be type "number" but received type "string"
2023-06-02 23:48:57.246  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.tf_co2" has to be type "number" but received type "string"
2023-06-02 23:48:57.247  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.humi_co2" has to be type "number" but received type "string"
2023-06-02 23:48:57.248  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.pm25_co2" has to be type "number" but received type "string"
2023-06-02 23:48:57.248  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.daily.pm25_24h_co2" has to be type "number" but received type "string"
2023-06-02 23:48:57.249  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.pm10_co2" has to be type "number" but received type "string"
2023-06-02 23:48:57.250  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.daily.pm10_24h_co2" has to be type "number" but received type "string"
2023-06-02 23:48:57.250  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.co2" has to be type "number" but received type "string"
2023-06-02 23:48:57.251  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.daily.co2_24h" has to be type "number" but received type "string"
2023-06-02 23:48:57.252  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.info.co2_batt" has to be type "number" but received type "string"
2023-06-02 23:48:57.253  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.lightning_time" has to be type "number" but received type "string"
2023-06-02 23:48:57.253  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.lightning" has to be type "number" but received type "string"
2023-06-02 23:48:57.254  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.daily.lightning_num" has to be type "number" but received type "string"
2023-06-02 23:48:57.254  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.eventrain_piezo" has to be type "number" but received type "string"
2023-06-02 23:48:57.255  - info: sainlogic.0 (709070) State value to set for "sainlogic.0.weather.current.hourlyrain_piezo" has to be type "number" but received type "string"

That is a bit weird. Can you post your config? Like is it using ecowitt or weatherunderground?

I'm using ecowit protocol. Will send a complete restart of the adapter later. The above is from a complete restart of the whole iobroker. Maybe a a dependent adapter hadn't been startet yet?

 Version 0.10.3 in /opt/iobroker/node_modules/iobroker.sainlogic, node: v18.16.0, js-controller: 5.0.1-alpha.0-20230525-c580eb7e
2023-06-05 06:49:20.880  - info: sainlogic.0 (886895) Starting Listener
2023-06-05 06:49:20.986  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.dailyrain" has to be type "number" but received type "string"
2023-06-05 06:49:20.988  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.dailyrain" has to be type "number" but received type "string"
2023-06-05 06:49:20.990  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.daily.dailyrain" has to be type "number" but received type "string"
2023-06-05 06:49:20.993  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.dailyrain_piezo" has to be type "number" but received type "string"
2023-06-05 06:49:20.994  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.indoorhumidity" has to be type "number" but received type "string"
2023-06-05 06:49:20.996  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.indoorhumidity" has to be type "number" but received type "string"
2023-06-05 06:49:20.998  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.daily.indoorhumidity" has to be type "number" but received type "string"
2023-06-05 06:49:20.999  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.minvalues.absolut.indoorhumidity" has to be type "number" but received type "string"
2023-06-05 06:49:21.000  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.minvalues.daily.indoorhumidity" has to be type "number" but received type "string"
2023-06-05 06:49:21.002  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.indoortemp" has to be type "number" but received type "string"
2023-06-05 06:49:21.004  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.indoortemp" has to be type "number" but received type "string"
2023-06-05 06:49:21.005  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.daily.indoortemp" has to be type "number" but received type "string"
2023-06-05 06:49:21.006  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.minvalues.absolut.indoortemp" has to be type "number" but received type "string"
2023-06-05 06:49:21.007  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.minvalues.daily.indoortemp" has to be type "number" but received type "string"
2023-06-05 06:49:21.008  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.monthlyrain" has to be type "number" but received type "string"
2023-06-05 06:49:21.008  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.monthlyrain" has to be type "number" but received type "string"
2023-06-05 06:49:21.009  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.daily.monthlyrain" has to be type "number" but received type "string"
2023-06-05 06:49:21.010  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.monthlyrain_piezo" has to be type "number" but received type "string"
2023-06-05 06:49:21.012  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.outdoorhumidity" has to be type "number" but received type "string"
2023-06-05 06:49:21.013  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.outdoorhumidity" has to be type "number" but received type "string"
2023-06-05 06:49:21.013  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.daily.outdoorhumidity" has to be type "number" but received type "string"
2023-06-05 06:49:21.014  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.minvalues.absolut.outdoorhumidity" has to be type "number" but received type "string"
2023-06-05 06:49:21.015  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.minvalues.daily.outdoorhumidity" has to be type "number" but received type "string"
2023-06-05 06:49:21.016  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.outdoortemp" has to be type "number" but received type "string"
2023-06-05 06:49:21.017  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.outdoortemp" has to be type "number" but received type "string"
2023-06-05 06:49:21.018  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.daily.outdoortemp" has to be type "number" but received type "string"
2023-06-05 06:49:21.018  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.minvalues.absolut.outdoortemp" has to be type "number" but received type "string"
2023-06-05 06:49:21.019  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.minvalues.daily.outdoortemp" has to be type "number" but received type "string"
2023-06-05 06:49:21.020  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.pressureabs" has to be type "number" but received type "string"
2023-06-05 06:49:21.021  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.pressureabs" has to be type "number" but received type "string"
2023-06-05 06:49:21.022  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.daily.pressureabs" has to be type "number" but received type "string"
2023-06-05 06:49:21.023  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.minvalues.absolut.pressureabs" has to be type "number" but received type "string"
2023-06-05 06:49:21.024  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.minvalues.daily.pressureabs" has to be type "number" but received type "string"
2023-06-05 06:49:21.024  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.pressurerel" has to be type "number" but received type "string"
2023-06-05 06:49:21.025  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.pressurerel" has to be type "number" but received type "string"
2023-06-05 06:49:21.026  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.daily.pressurerel" has to be type "number" but received type "string"
2023-06-05 06:49:21.027  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.minvalues.absolut.pressurerel" has to be type "number" but received type "string"
2023-06-05 06:49:21.028  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.minvalues.daily.pressurerel" has to be type "number" but received type "string"
2023-06-05 06:49:21.029  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.rain" has to be type "number" but received type "string"
2023-06-05 06:49:21.029  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.rain" has to be type "number" but received type "string"
2023-06-05 06:49:21.030  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.rain_piezo" has to be type "number" but received type "string"
2023-06-05 06:49:21.032  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.solarradiation" has to be type "number" but received type "string"
2023-06-05 06:49:21.032  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.solarradiation" has to be type "number" but received type "string"
2023-06-05 06:49:21.033  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.daily.solarradiation" has to be type "number" but received type "string"
2023-06-05 06:49:21.034  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.uvi" has to be type "number" but received type "string"
2023-06-05 06:49:21.035  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.uvi" has to be type "number" but received type "string"
2023-06-05 06:49:21.036  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.daily.uvi" has to be type "number" but received type "string"
2023-06-05 06:49:21.037  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.weeklyrain" has to be type "number" but received type "string"
2023-06-05 06:49:21.038  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.weeklyrain" has to be type "number" but received type "string"
2023-06-05 06:49:21.039  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.weeklyrain_piezo" has to be type "number" but received type "string"
2023-06-05 06:49:21.040  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.winddir" has to be type "number" but received type "string"
2023-06-05 06:49:21.041  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.windgustspeed" has to be type "number" but received type "string"
2023-06-05 06:49:21.042  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.windgustspeed" has to be type "number" but received type "string"
2023-06-05 06:49:21.045  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.daily.windgustspeed" has to be type "number" but received type "string"
2023-06-05 06:49:21.046  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.maxdailygust" has to be type "number" but received type "string"
2023-06-05 06:49:21.047  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.windspeed" has to be type "number" but received type "string"
2023-06-05 06:49:21.047  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.windspeed" has to be type "number" but received type "string"
2023-06-05 06:49:21.048  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.daily.windspeed" has to be type "number" but received type "string"
2023-06-05 06:49:21.049  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.yearlyrain" has to be type "number" but received type "string"
2023-06-05 06:49:21.050  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.yearlyrain" has to be type "number" but received type "string"
2023-06-05 06:49:21.051  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.totalrainin" has to be type "number" but received type "string"
2023-06-05 06:49:21.052  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.maxvalues.absolut.totalrainin" has to be type "number" but received type "string"
2023-06-05 06:49:21.053  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.yearlyrain_piezo" has to be type "number" but received type "string"
2023-06-05 06:49:21.053  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.soilmoisture" has to be type "number" but received type "string"
2023-06-05 06:49:21.054  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.info.soilbatt" has to be type "number" but received type "string"
2023-06-05 06:49:21.055  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.info.wh80batt" has to be type "number" but received type "string"
2023-06-05 06:49:21.056  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.info.wh40batt" has to be type "number" but received type "string"
2023-06-05 06:49:21.057  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.info.wh25batt" has to be type "number" but received type "string"
2023-06-05 06:49:21.058  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.tf_ch" has to be type "number" but received type "string"
2023-06-05 06:49:21.058  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.info.tf_batt" has to be type "number" but received type "string"
2023-06-05 06:49:21.059  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.tf_co2" has to be type "number" but received type "string"
2023-06-05 06:49:21.060  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.humi_co2" has to be type "number" but received type "string"
2023-06-05 06:49:21.061  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.pm25_co2" has to be type "number" but received type "string"
2023-06-05 06:49:21.062  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.daily.pm25_24h_co2" has to be type "number" but received type "string"
2023-06-05 06:49:21.062  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.pm10_co2" has to be type "number" but received type "string"
2023-06-05 06:49:21.109  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.daily.pm10_24h_co2" has to be type "number" but received type "string"
2023-06-05 06:49:21.110  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.co2" has to be type "number" but received type "string"
2023-06-05 06:49:21.222  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.daily.co2_24h" has to be type "number" but received type "string"
2023-06-05 06:49:21.233  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.info.co2_batt" has to be type "number" but received type "string"
2023-06-05 06:49:21.234  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.lightning_time" has to be type "number" but received type "string"
2023-06-05 06:49:21.246  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.lightning" has to be type "number" but received type "string"
2023-06-05 06:49:21.251  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.daily.lightning_num" has to be type "number" but received type "string"
2023-06-05 06:49:21.253  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.eventrain_piezo" has to be type "number" but received type "string"
2023-06-05 06:49:21.254  - info: sainlogic.0 (886895) State value to set for "sainlogic.0.weather.current.hourlyrain_piezo" has to be type "number" but received type "string"

Ic can confirm these info / errors:
Adapter 1.10.3
js-controller 4.0.24
running in lister mode
2023-06-16 18:12:38.860 - info: sainlogic.0 (25805) starting. Version 0.10.3 in /opt/iobroker/node_modules/iobroker.sainlogic, node: v16.19.0, js-controller: 4.0.24
--
2023-06-16 18:12:38.908 - info: sainlogic.0 (25805) Starting Listener
2023-06-16 18:12:38.958 - info: sainlogic.0 (25805) Creating new data point: info.last_listener_update
2023-06-16 18:12:38.960 - info: sainlogic.0 (25805) Creating new data point: weather.current.dailyrain
2023-06-16 18:12:38.961 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.dailyrain
2023-06-16 18:12:38.962 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.daily.dailyrain
2023-06-16 18:12:38.962 - info: sainlogic.0 (25805) Creating new data point: weather.current.dailyrain_piezo
2023-06-16 18:12:38.963 - info: sainlogic.0 (25805) Creating new data point: weather.current.dewpointtemp
2023-06-16 18:12:38.964 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.dewpointtemp
2023-06-16 18:12:38.965 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.daily.dewpointtemp
2023-06-16 18:12:38.965 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.absolut.dewpointtemp
2023-06-16 18:12:38.966 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.daily.dewpointtemp
2023-06-16 18:12:38.967 - info: sainlogic.0 (25805) Creating new data point: weather.current.indoorhumidity
2023-06-16 18:12:38.967 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.indoorhumidity
2023-06-16 18:12:38.968 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.daily.indoorhumidity
2023-06-16 18:12:38.969 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.absolut.indoorhumidity
2023-06-16 18:12:38.969 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.daily.indoorhumidity
2023-06-16 18:12:38.969 - info: sainlogic.0 (25805) Creating new data point: weather.current.indoortemp
2023-06-16 18:12:38.970 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.indoortemp
2023-06-16 18:12:38.970 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.daily.indoortemp
2023-06-16 18:12:38.970 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.absolut.indoortemp
2023-06-16 18:12:38.971 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.daily.indoortemp
2023-06-16 18:12:38.971 - info: sainlogic.0 (25805) Creating new data point: weather.current.monthlyrain
2023-06-16 18:12:38.972 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.monthlyrain
2023-06-16 18:12:38.972 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.daily.monthlyrain
2023-06-16 18:12:38.972 - info: sainlogic.0 (25805) Creating new data point: weather.current.monthlyrain_piezo
2023-06-16 18:12:38.973 - info: sainlogic.0 (25805) Creating new data point: weather.current.outdoorhumidity
2023-06-16 18:12:38.973 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.outdoorhumidity
2023-06-16 18:12:38.973 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.daily.outdoorhumidity
2023-06-16 18:12:38.974 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.absolut.outdoorhumidity
2023-06-16 18:12:38.974 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.daily.outdoorhumidity
2023-06-16 18:12:38.974 - info: sainlogic.0 (25805) Creating new data point: weather.current.outdoortemp
2023-06-16 18:12:38.975 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.outdoortemp
2023-06-16 18:12:38.975 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.daily.outdoortemp
2023-06-16 18:12:38.976 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.absolut.outdoortemp
2023-06-16 18:12:38.976 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.daily.outdoortemp
2023-06-16 18:12:38.977 - info: sainlogic.0 (25805) Creating new data point: weather.current.pressureabs
2023-06-16 18:12:38.977 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.pressureabs
2023-06-16 18:12:38.977 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.daily.pressureabs
2023-06-16 18:12:38.978 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.absolut.pressureabs
2023-06-16 18:12:38.978 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.daily.pressureabs
2023-06-16 18:12:38.978 - info: sainlogic.0 (25805) Creating new data point: weather.current.pressurerel
2023-06-16 18:12:38.979 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.pressurerel
2023-06-16 18:12:38.980 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.daily.pressurerel
2023-06-16 18:12:38.980 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.absolut.pressurerel
2023-06-16 18:12:38.980 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.daily.pressurerel
2023-06-16 18:12:38.981 - info: sainlogic.0 (25805) Creating new data point: weather.current.rain
2023-06-16 18:12:38.981 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.rain
2023-06-16 18:12:38.981 - info: sainlogic.0 (25805) Creating new data point: weather.current.rain_piezo
2023-06-16 18:12:38.982 - info: sainlogic.0 (25805) Creating new data point: weather.current.solarradiation
2023-06-16 18:12:38.982 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.solarradiation
2023-06-16 18:12:38.982 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.daily.solarradiation
2023-06-16 18:12:38.983 - info: sainlogic.0 (25805) Creating new data point: weather.current.uvi
2023-06-16 18:12:38.983 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.uvi
2023-06-16 18:12:38.984 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.daily.uvi
2023-06-16 18:12:38.984 - info: sainlogic.0 (25805) Creating new data point: weather.current.weeklyrain
2023-06-16 18:12:38.985 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.weeklyrain
2023-06-16 18:12:38.985 - info: sainlogic.0 (25805) Creating new data point: weather.current.weeklyrain_piezo
2023-06-16 18:12:38.985 - info: sainlogic.0 (25805) Creating new data point: weather.current.windchilltemp
2023-06-16 18:12:38.986 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.absolut.windchilltemp
2023-06-16 18:12:38.986 - info: sainlogic.0 (25805) Creating new data point: weather.minvalues.daily.windchilltemp
2023-06-16 18:12:38.986 - info: sainlogic.0 (25805) Creating new data point: weather.current.winddir
2023-06-16 18:12:38.987 - info: sainlogic.0 (25805) Creating new data point: weather.current.windgustspeed
2023-06-16 18:12:38.987 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.windgustspeed
2023-06-16 18:12:38.987 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.daily.windgustspeed
2023-06-16 18:12:38.988 - info: sainlogic.0 (25805) Creating new data point: weather.current.windspeed
2023-06-16 18:12:38.988 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.windspeed
2023-06-16 18:12:38.988 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.daily.windspeed
2023-06-16 18:12:38.989 - info: sainlogic.0 (25805) Creating new data point: weather.current.yearlyrain
2023-06-16 18:12:38.989 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.yearlyrain
2023-06-16 18:12:38.989 - info: sainlogic.0 (25805) Creating new data point: weather.current.totalrainin
2023-06-16 18:12:38.990 - info: sainlogic.0 (25805) Creating new data point: weather.maxvalues.absolut.totalrainin
2023-06-16 18:12:38.990 - info: sainlogic.0 (25805) Creating new data point: weather.current.yearlyrain_piezo
2023-06-16 18:12:38.991 - info: sainlogic.0 (25805) Creating new data point: weather.current.soilmoisture
2023-06-16 18:12:38.991 - info: sainlogic.0 (25805) Creating new data point: weather.info.soilbatt
2023-06-16 18:12:38.991 - info: sainlogic.0 (25805) Creating new data point: weather.info.wh80batt
2023-06-16 18:12:38.992 - info: sainlogic.0 (25805) Creating new data point: weather.info.wh40batt
2023-06-16 18:12:38.992 - info: sainlogic.0 (25805) Creating new data point: weather.info.wh25batt
2023-06-16 18:12:38.992 - info: sainlogic.0 (25805) Creating new data point: weather.current.tf_ch
2023-06-16 18:12:38.993 - info: sainlogic.0 (25805) Creating new data point: weather.info.tf_batt
2023-06-16 18:12:38.993 - info: sainlogic.0 (25805) Creating new data point: weather.current.tf_co2
2023-06-16 18:12:38.993 - info: sainlogic.0 (25805) Creating new data point: weather.current.humi_co2
2023-06-16 18:12:38.994 - info: sainlogic.0 (25805) Creating new data point: weather.current.pm25_co2
2023-06-16 18:12:38.994 - info: sainlogic.0 (25805) Creating new data point: weather.daily.pm25_24h_co2
2023-06-16 18:12:38.994 - info: sainlogic.0 (25805) Creating new data point: weather.current.pm10_co2
2023-06-16 18:12:38.994 - info: sainlogic.0 (25805) Creating new data point: weather.daily.pm10_24h_co2
2023-06-16 18:12:38.995 - info: sainlogic.0 (25805) Creating new data point: weather.current.co2
2023-06-16 18:12:38.995 - info: sainlogic.0 (25805) Creating new data point: weather.daily.co2_24h
2023-06-16 18:12:38.995 - info: sainlogic.0 (25805) Creating new data point: weather.info.co2_batt
2023-06-16 18:12:39.084 - warn: sainlogic.0 (25805) Object sainlogic.0.info.last_listener_update is invalid: Default value has to be type "string" but received type "number"
2023-06-16 18:12:39.085 - warn: sainlogic.0 (25805) This object will not be created in future versions. Please report this to the developer.
2023-06-16 18:12:39.089 - info: sainlogic.0 (25805) Creating new data point: weather.current.eventrain_piezo
2023-06-16 18:12:39.090 - info: sainlogic.0 (25805) Creating new data point: weather.current.hourlyrain_piezo
2023-06-16 18:12:39.708 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.info.last_listener_update" has to be type "string" but received type "number"
2023-06-16 18:12:40.078 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.dailyrain" has to be type "number" but received type "string"
2023-06-16 18:12:40.079 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.dailyrain" has to be type "number" but received type "string"
2023-06-16 18:12:40.080 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.daily.dailyrain" has to be type "number" but received type "string"
2023-06-16 18:12:40.081 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.dailyrain_piezo" has to be type "number" but received type "string"
2023-06-16 18:12:40.082 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.dewpointtemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.083 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.dewpointtemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.084 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.daily.dewpointtemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.085 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.absolut.dewpointtemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.086 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.daily.dewpointtemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.087 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.indoorhumidity" has to be type "number" but received type "string"
2023-06-16 18:12:40.087 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.indoorhumidity" has to be type "number" but received type "string"
2023-06-16 18:12:40.088 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.daily.indoorhumidity" has to be type "number" but received type "string"
2023-06-16 18:12:40.089 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.absolut.indoorhumidity" has to be type "number" but received type "string"
2023-06-16 18:12:40.090 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.daily.indoorhumidity" has to be type "number" but received type "string"
2023-06-16 18:12:40.091 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.indoortemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.092 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.indoortemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.093 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.daily.indoortemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.093 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.absolut.indoortemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.094 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.daily.indoortemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.095 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.monthlyrain" has to be type "number" but received type "string"
2023-06-16 18:12:40.096 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.monthlyrain" has to be type "number" but received type "string"
2023-06-16 18:12:40.096 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.daily.monthlyrain" has to be type "number" but received type "string"
2023-06-16 18:12:40.097 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.monthlyrain_piezo" has to be type "number" but received type "string"
2023-06-16 18:12:40.098 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.outdoorhumidity" has to be type "number" but received type "string"
2023-06-16 18:12:40.099 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.outdoorhumidity" has to be type "number" but received type "string"
2023-06-16 18:12:40.099 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.daily.outdoorhumidity" has to be type "number" but received type "string"
2023-06-16 18:12:40.100 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.absolut.outdoorhumidity" has to be type "number" but received type "string"
2023-06-16 18:12:40.101 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.daily.outdoorhumidity" has to be type "number" but received type "string"
2023-06-16 18:12:40.101 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.outdoortemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.102 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.outdoortemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.103 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.daily.outdoortemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.104 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.absolut.outdoortemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.104 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.daily.outdoortemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.105 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.pressureabs" has to be type "number" but received type "string"
2023-06-16 18:12:40.106 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.pressureabs" has to be type "number" but received type "string"
2023-06-16 18:12:40.106 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.daily.pressureabs" has to be type "number" but received type "string"
2023-06-16 18:12:40.107 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.absolut.pressureabs" has to be type "number" but received type "string"
2023-06-16 18:12:40.108 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.daily.pressureabs" has to be type "number" but received type "string"
2023-06-16 18:12:40.109 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.pressurerel" has to be type "number" but received type "string"
2023-06-16 18:12:40.110 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.pressurerel" has to be type "number" but received type "string"
2023-06-16 18:12:40.111 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.daily.pressurerel" has to be type "number" but received type "string"
2023-06-16 18:12:40.112 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.absolut.pressurerel" has to be type "number" but received type "string"
2023-06-16 18:12:40.112 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.daily.pressurerel" has to be type "number" but received type "string"
2023-06-16 18:12:40.113 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.rain" has to be type "number" but received type "string"
2023-06-16 18:12:40.114 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.rain" has to be type "number" but received type "string"
2023-06-16 18:12:40.115 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.rain_piezo" has to be type "number" but received type "string"
2023-06-16 18:12:40.116 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.solarradiation" has to be type "number" but received type "string"
2023-06-16 18:12:40.117 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.solarradiation" has to be type "number" but received type "string"
2023-06-16 18:12:40.117 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.daily.solarradiation" has to be type "number" but received type "string"
2023-06-16 18:12:40.118 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.uvi" has to be type "number" but received type "string"
2023-06-16 18:12:40.119 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.uvi" has to be type "number" but received type "string"
2023-06-16 18:12:40.120 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.daily.uvi" has to be type "number" but received type "string"
2023-06-16 18:12:40.121 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.weeklyrain" has to be type "number" but received type "string"
2023-06-16 18:12:40.121 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.weeklyrain" has to be type "number" but received type "string"
2023-06-16 18:12:40.122 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.weeklyrain_piezo" has to be type "number" but received type "string"
2023-06-16 18:12:40.123 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.windchilltemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.124 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.absolut.windchilltemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.125 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.minvalues.daily.windchilltemp" has to be type "number" but received type "string"
2023-06-16 18:12:40.126 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.winddir" has to be type "number" but received type "string"
2023-06-16 18:12:40.126 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.windgustspeed" has to be type "number" but received type "string"
2023-06-16 18:12:40.127 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.windgustspeed" has to be type "number" but received type "string"
2023-06-16 18:12:40.128 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.daily.windgustspeed" has to be type "number" but received type "string"
2023-06-16 18:12:40.128 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.windspeed" has to be type "number" but received type "string"
2023-06-16 18:12:40.132 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.windspeed" has to be type "number" but received type "string"
2023-06-16 18:12:40.133 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.daily.windspeed" has to be type "number" but received type "string"
2023-06-16 18:12:40.133 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.yearlyrain" has to be type "number" but received type "string"
2023-06-16 18:12:40.134 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.yearlyrain" has to be type "number" but received type "string"
2023-06-16 18:12:40.135 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.totalrainin" has to be type "number" but received type "string"
2023-06-16 18:12:40.136 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.maxvalues.absolut.totalrainin" has to be type "number" but received type "string"
2023-06-16 18:12:40.137 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.yearlyrain_piezo" has to be type "number" but received type "string"
2023-06-16 18:12:40.138 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.soilmoisture" has to be type "number" but received type "string"
2023-06-16 18:12:40.201 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.info.soilbatt" has to be type "number" but received type "string"
2023-06-16 18:12:40.202 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.info.wh80batt" has to be type "number" but received type "string"
2023-06-16 18:12:40.203 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.info.wh40batt" has to be type "number" but received type "string"
2023-06-16 18:12:40.204 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.info.wh25batt" has to be type "number" but received type "string"
2023-06-16 18:12:40.205 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.tf_ch" has to be type "number" but received type "string"
2023-06-16 18:12:40.206 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.info.tf_batt" has to be type "number" but received type "string"
2023-06-16 18:12:40.207 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.tf_co2" has to be type "number" but received type "string"
2023-06-16 18:12:40.343 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.humi_co2" has to be type "number" but received type "string"
2023-06-16 18:12:40.352 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.pm25_co2" has to be type "number" but received type "string"
2023-06-16 18:12:40.353 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.daily.pm25_24h_co2" has to be type "number" but received type "string"
2023-06-16 18:12:40.354 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.pm10_co2" has to be type "number" but received type "string"
2023-06-16 18:12:40.363 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.daily.pm10_24h_co2" has to be type "number" but received type "string"
2023-06-16 18:12:40.364 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.co2" has to be type "number" but received type "string"
2023-06-16 18:12:40.365 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.daily.co2_24h" has to be type "number" but received type "string"
2023-06-16 18:12:40.366 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.info.co2_batt" has to be type "number" but received type "string"
2023-06-16 18:12:40.367 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.eventrain_piezo" has to be type "number" but received type "string"
2023-06-16 18:12:40.367 - info: sainlogic.0 (25805) State value to set for "sainlogic.0.weather.current.hourlyrain_piezo" has to be type "number" but received type "string"
2023-06-16 18:12:50.446 - info: sainlogic.0 (25805) Forward URL: + https://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?ID=IXXXXXX&PASSWORD=XXXXXXX&indoortempf=77.2&tempf=74.7&dewptf=48.7&windchillf=74.7&indoorhumidity=48&humidity=40&windspeedmph=1.6&windgustmph=2.2&winddir=96&absbaromin=29.342&baromin=30.426&rainin=0.000&dailyrainin=0.000&weeklyrainin=0.000&monthlyrainin=4.461&solarradiation=79.40&UV=0&dateutc=2023-06-16+16%3A12%3A48&softwaretype=EasyWeatherV1.6.5&action=updateraw&realtime=1&rtfreq=5&last_listener_update=%7B%22ID%22%3A%22IFAVOR41%22%2C%22PASSWORD%22%3A%22HPyaGJfh%22%2C%22indoortempf%22%3A%2277.2%22%2C%22tempf%22%3A%2274.7%22%2C%22dewptf%22%3A%2248.7%22%2C%22windchillf%22%3A%2274.7%22%2C%22indoorhumidity%22%3A%2248%22%2C%22humidity%22%3A%2240%22%2C%22windspeedmph%22%3A%221.6%22%2C%22windgustmph%22%3A%222.2%22%2C%22winddir%22%3A%2296%22%2C%22absbaromin%22%3A%2229.342%22%2C%22baromin%22%3A%2230.426%22%2C%22rainin%22%3A%220.000%22%2C%22dailyrainin%22%3A%220.000%22%2C%22weeklyrainin%22%3A%220.000%22%2C%22monthlyrainin%22%3A%224.461%22%2C%22solarradiation%22%3A%2279.40%22%2C%22UV%22%3A%220%22%2C%22dateutc%22%3A%222023-06-16+16%3A12%3A48%22%2C%22softwaretype%22%3A%22EasyWeatherV1.6.5%22%2C%22action%22%3A%22updateraw%22%2C%22realtime%22%3A%221%22%2C%22rtfreq%22%3A%225%22%7D
2023-06-16 18:12:50.446 - info: sainlogic.0 (25805) Forward response body: success

<!--EndFragment-->
</body>
</html>

In addition the following log
2023-06-16 18:12:39.084 - warn: sainlogic.0 (25805) Object sainlogic.0.info.last_listener_update is invalid: Default value has to be type "string" but received type "number"
2023-06-16 18:12:39.085 - warn: sainlogic.0 (25805) This object will not be created in future versions. Please report this to the developer.

raises some alarm. Please check wether teh adapter creates the objects still with upcomingjs-.controlle5. It's available as beta (see forum).

Thanks @mcm1957. Sounds like initialization code is using a default - probably empty - string. I'll check into that.

Closed with 0.10.5


Doesn't classify on 10+ classes

When training on 10+, network seems to reduce number of classes to 10.
I found it by printing out target[i] on line 175 in trainer.lua - it shows that classes always numbered from 1 to 10:
    for i = 1, batch_size do
     confusion:add(outputs[i], targets[i])
    print('target '..targets[i])
    end
Also you can see it in debug mode: confusion matrix is always 10x10 sized.
Haven't locate where exactly the issue is yet.

The bug was in the preprocessing step - I've fixed it so it should no longer be an issue.

Indeed! Sorry.


Work on tutorial section from Fall school

I pulled the last version of the py_neuromodulation git repo. I followed the clear instructions on setting up the environment.  I tried
conda env create --file=env.yml --user
but the --user handle was unknown and I had to remove it. Maybe it was probably a noob problem requiring further input or specification what the user is for, from my side but I guess there are more and more noobs starting to switch from Matlab to Python so it may be good to explain or double check this is correct.
I suppose binder would circumvent this problem, but I only found the binder button after a long search. I would suggest mentioning the binder and what it can do explicitly in the readme and definitely add the link to both repo and binder to the presentation.
The main problem I found was the question on how to start the hands-on part. So I checked the repo and started working on the Fall school Notebook_1_Tasks.ipynb and found a few minor bugs (e.g. Y instead of y that is expected further on etc.). Then I checked the Fall school Notebook_2_Tasks.ipynb thinking that would be the more recent or correct version, but this already included solutions so I opened Fall school Notebook_3 which also included solutions but was slightly different to notebooks 1 and 2. I am sure you kept improving everything, so this is clearly just a minor thing, but before times passes by and we don't remember anymore, I would suggest to create one clean version called *_tasks.ipynb & _solutions.ipynb .
Would it be possible to move these notebooks out of the main repo into a tutorial folder?
I found the tasks to be more python coding related than machine learning related. They were great for me but may not be what people are expecting. Potential ML related tasks could be to repeat the cross-validation or chose different feature sets and explore the effects. If you want, we could take some time next week and go through them again and adapt a little?

[ ] Merge part 1 & 2
[ ] Include command running py_neuro for example data


minlength and maxlength rename to max and min

Renaming validation minlength and maxlength to max and min is shorter.

nofix


Trends time period

I'm submitting a ...

[ x ] Feature request

I am using grafana-Zabbix 3.3 and when the Trends is activated, It's impossible to Zoom in to get history before the trend period (7d by default)
I think it's better to add a feature that use trends only if the selected period is greater than a Trend Window.
I changed directly he dist/datasource-zabbix/datasource.js : 229,
            var useTrendsFrom = Math.ceil(dateMath.parse('now-' + this.trendsFrom) / 1000);
            var windowTrends = Math.abs(Math.ceil(dateMath.parse('now') / 1000) - useTrendsFrom);
            var useTrends = (Math.abs(timeTo - timeFrom ) > windowTrends) && this.trends;

More than that
it's better to have this feature by dashboard/Metric,
for example, Per Metric, enable Trend or history and choose the time period .
Thanks

Yes, you're right, datasource should use trends only for range wider than trend period. I can add option like trend range, and allow to control trend usage more flexibly.

@alexanderzobnin  Do you want to fix it and send a PR  ?


Getting a 404 when npm token create

I'm trying to create a token that our Jenkins pipeline process can use to publish.
To Reproduce
npm token create
and I get back:
npm ERR! code E404
npm ERR! 404 Registry returned 404 for POST on https://xxxxx/-/npm/v1/tokens
for the npm password I use the default admin since we haven't changed it yet (still in the eval stage)
We're using 3.11.6

Yeah, this feature is under construction
Relates to #541 and #1271


Too many w's in the name.

@jamierytlewski : Thanks for your contribution! The author, @MashaMSFT, has been notified to review your proposed change.

Hi @jamierytlewski, thank  you for your contribution! You're right, thanks for catching this typo :).


Get to build and run with no errors and possibly reasonable output

Master still has runtime CUDA errors. develop branch might solve this.

Up to 63 Registers are used in a thread at a time. A common max registers per block is 32768. 32768 / 63 is a max of 520 threads per block, which is often seen passed in multiple runs. Clamping threads/block to < max registers per block / 63 will need to be implemented.
OR the files using too many registers may need modifications to use fewer.

completed with f1d334d5b7e904b29579073c3d7236ed884f77f4


Cannot decrypt properties in bootstrap.yml on Config Server

I believe @dsyer is aware of this problem judging from his first comment on #123. For my specific use case, I am trying to provide a username/password for the Git repository backing my configuration server, but I want to encrypt the password so that it is not visible when bootstrap.yml is checked in to source control.
(I do not plan on using this method of authentication if this makes it to production, but it is handy while making a proof of concept that I can check into source control for colleagues to see the code... and I just do not like saving my password in plaintext in a file if avoidable, even on my own PC)
When the config server tries to startup, it has the password as the literal string value of "{cipher}xxxxxxx" and of course authentication fails.
Is encrypted properties in bootstrap.yml/properties a use case that should be supported?

Why does the cipher need to go in bootstrap.yml?
(Of course even if it works in application.yml you need a secret to decrypt it, so you need to get out of the hole somehow with a local file or environment variable.)

Maybe a password isn't the best way to secure the git repo? Ssh would be more common (and people run with a local .ssh configuration that works if they have an account).

Thank you for your quick reply. I agree that the better overall solution in this use case is just to use ssh. I just thought perhaps there might be other use cases that would make it make sense to have cipher available to use in bootstrap.yml. However, I'm not able to think of any. Perhaps the documentation could directly mention that cipher is not usable in bootstrap.yml, at the least, though?

Duplicates #123


⚠ Bofrost.at has degraded performance

In 38c0daf, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1515 ms

Resolved: Bofrost.at performance has improved in 2389de0.


An id must be provided to format a message ，why and how to slove it

Describe the Bug
[@formatjs/intl] An id must be provided to format a message. You can either: 1. Configure your build toolchain with babel-plugin-formatjs or @formatjs/ts-transformer OR 2. Configure your eslint config to include eslint-plugin-formatjs to autofix this issue
Error: [@formatjs/intl] An id must be provided to format a message. You can either:

Configure your build toolchain with babel-plugin-formatjs
or @formatjs/ts-transformer OR
Configure your eslint config to include eslint-plugin-formatjs
to autofix this issue

I use docker-compose to start, the content is as follows：

Database
MySQL
Relevant log output
No response
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response

Please see #2113 . Might need to include some type of notification to update your version.


The readme is wrong about the package name

The readme says that installing this package is done as @componentdriven/csf. But the 0.1.0 release was done for @storybook/csf

:rocket: Issue was released in v0.1.7-next.0 :rocket:

:rocket: Issue was released in v0.1.7 :rocket:


Check if jsTree is destroyed on onmessage and functions that run in timeout

In my application's acceptance tests, I call destroy() on jsTree to cleanup when the test is complete. For tests that are testing other components on the same screen as the tree, these tests end before the tree has finished. So destroy() is called before the worker's onmessage handler is called. This results in test failures with errors "Cannot read property 'find' of null" on this.element.
jsTree should make sure it hasn't already been destroyed before continuing in the onmessage handler and functions that run in a timeout.

Thanks for the report. Unfortunately I can not merge this - this._wrk will always be null in browsers that do not support workers or in any browser if the developer chose to disable workers in the jstree config.
The check should be something else, and ideally - in one place. I will have a look and let you know.

Take a look at the latest commit - it should be resolved now:
https://github.com/vakata/jstree/commit/b6a07e0cad5910c8826da61cff344a5bac32ed08
Once again - thanks for pointing this out.

Yep, that commit fixed it. Thanks.


attestation fix

/azp run automation - sdk

Can one of the admins verify this patch?

@zikalino, is this PR still valid?

/azp run automation - sdk

/azp run automation - sdk

online chat with @zikalino , remove 'Do Not Merge' label and merge this PR.


GridMultiSelect

Similarly to GridSelect that allows only one item to be selected, there should be a component that allows multiple options at the same time to be selected. The value of this component should always be Set<ITEM>. The component should allow maximum selection size. Once it is reached, no new value can be selected (though values can be deselected).
Otherwise, the component should behave like GridSelect. It should not be possible to change selection mode of the underlying grid to single-select.

removed the requirement to work with overflow selection - once limit is reached, simply deselect an item to select something else