Creating a Group using powershell makes creater a member too

I am using the following commands to create a group and add a member as owner to group;
 New-UnifiedGroup -AccessType Public -Alias $groupIdentity -DisplayName $groupDisplayName  Add-UnifiedGroupLinks -Identity $groupIdentity -LinkType Members -links $smtpAddress  Add-UnifiedGroupLinks -Identity $groupIdentity -LinkType Owners -Links $smtpAddress
I see after doing above the group contains the member $smtpAddress as owner(This is what I am trying to do), in addition to that group has the admin smtp address as owner and member too(admin credentials using which, I logged into O365 exchange, msonline and azuread), Is there a way I can create a group with only specified members as Group members using powershell?

Yes, this is by design. An Owner is both an Owner and a Member of a Group. This way they have access to all services, e.g. Planner.

Yes, this is by design. An Owner is both an Owner and a Member of a Group. This way they have access to all services, e.g. Planner.

@tseward , Yeah that is right, what I am asking is totally different thing, Let me rephrase it.
The credentials I use to logging into azureAd,exchangeonline and msonline so that I can execute those commands, I see that those credentials username is also part of the group.  I don't want that to  happen, is there any workaround for that?

@officedocsbot assign @yogkumgit

Hi @asajrawat211993,
When you create a group it should have an owner. If you don't specify one when you run New-UnifiedGroup, the user who create the group will be the default owner.
Try using -Owner parameter:
New-UnifiedGroup -AccessType Public -Alias $groupIdentity -DisplayName $groupDisplayName -Owner $groupOwner

@dariomws306 Thank you very much for the contribution and digging deep into it. @asajrawat211993 If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Please keep contributing with your suggestions to improve the documentation.


Invalid argument: shape must be a vector of {int32,int64}, got shape []

I try to use the interface of RandomUniform as follows:
func TestRandomUniform(t *testing.T) {
	root := op.NewScope()

	T := op.Placeholder(root.SubScope("input"), tf.Int64)

	seed := op.RandomUniformSeed(-1.0)
	seed2 := op.RandomUniformSeed2(1.0)
	product := op.RandomUniform(root,T,tf.Float,seed,seed2)

	graph, err := root.Finalize()
	if err != nil {
		panic(err.Error())
	}

	var sess *tf.Session
	sess, err = tf.NewSession(graph, &tf.SessionOptions{})
	if err != nil {
		panic(err.Error())
	}

	var A *tf.Tensor

	if A, err = tf.NewTensor(int64(1)); err != nil {
		panic(err.Error())
	}

	var results []*tf.Tensor
	if results, err = sess.Run(
		map[tf.Output]*tf.Tensor{
			T: A,
		},
		[]tf.Output{product}, nil); err != nil {
			panic(err.Error())
	}
	for _, result := range results {
		fmt.Println(result.Value().([]int64))
	}

}

Invalid argument: shape must be a vector of {int32,int64}, got shape []
panic: shape must be a vector of {int32,int64}, got shape []
	 [[Node: RandomUniform = RandomUniform[T=DT_INT64, _class=[], dtype=DT_FLOAT, seed=-1, seed2=1, _device="/job:localhost/replica:0/task:0/cpu:0"](_arg_input/Placeholder_0_0)]] [recovered]
	panic: shape must be a vector of {int32,int64}, got shape []
	 [[Node: RandomUniform = RandomUniform[T=DT_INT64, _class=[], dtype=DT_FLOAT, seed=-1, seed2=1, _device="/job:localhost/replica:0/task:0/cpu:0"](_arg_input/Placeholder_0_0)]]

goroutine 5 [running]

But it  prints the error for me. What's it means?I am not good at c++.
And i try to use your tfgo.I get the same result.

Hey @xiajohnnyxia I just replyed to your email.
However, I'm gonna copy my reply here in order to help you and anyone else that'll face your same problem.
Now, you can easily find out that your problem is in the invocation of op.RandomUniform.
Let's look at the godoc: https://godoc.org/github.com/tensorflow/tensorflow/tensorflow/go/op#RandomUniform
Here's the signature:
func RandomUniform(scope *Scope, shape tf.Output, dtype tf.DataType, optional ...RandomUniformAttr) (output tf.Output)
Here's your invocation:
output := op.RandomUniform(root,T,tf.Float,seed,seed2)
The first parameter is scope *Scope : you're passing root that's a *Scope -> perfect.
The second parameter is shape tf.Output: the tf.Output is a terrible type. It means "anything". The compiler can't help you raising an error and it will accept any parameter of tf.Output type.
The check if the right parameter is executed during runtime into the tensorflow environment.
We have to read the documentation: shape: The shape of the output tensor.
That's not really helpful if you are not familiar with tensorflow. But instead, if you are familiar with it, you know that the shape (even when using tensorflow in python) is always a list or tuple.
This means, in the context of tensorflow + go, that the shape parameter must be a vector of int32 or int64. (remember that a scalar value is a tensor with shape = () [ in python] that means a shape of []int32{} in go).
You're passing T as a shape. Your Tparameter is a placeholder. A scalar placeholder, NOT a vector.
Thus you first have to change the definition of T, making it a vector of integers (with shape 0 -> that means empty tuple in python () -> that means the shape of a scalr value).
T := op.Placeholder(root.SubScope("input"), tf.Int32, op.PlaceholderShape(tf.MakeShape(0)))
Now you should be fine. First error fixed.
Let's go on comparing the signature and your function call:
The third parameter is: dtype tf.DataType: you're passing tf.Float that's a tf.DataType -> perect.
The 4th, 5h, ... parameters are optional ...RandomUniforAttr: you're passing seed and seed2 that are RandomUniforAttr: -> perfect.
There's another problem in your code, in the Go side: when you execute the graph sess.run(...) you are fetching the value of output that's a tf.float32 value.
This means that your cast result.Value().([]int32) will fail.
Instead, you have to cast the resulting interface to []float32.
Complete code
package testTensorflow

import (
	"fmt"
	tf "github.com/tensorflow/tensorflow/tensorflow/go"
	"github.com/tensorflow/tensorflow/tensorflow/go/op"
	"testing"
)

func TestRandomUniform(t *testing.T) {
	root := op.NewScope()
	T := op.Placeholder(root.SubScope("input"), tf.Int32, op.PlaceholderShape(tf.MakeShape(0)))
	seed := op.RandomUniformSeed(-1.0)
	seed2 := op.RandomUniformSeed2(1.0)
	output := op.RandomUniform(root, T, tf.Float, seed, seed2)

	graph, err := root.Finalize()
	if err != nil {
		panic(err.Error())
	}

	var sess *tf.Session
	sess, err = tf.NewSession(graph, &tf.SessionOptions{})
	if err != nil {
		panic(err.Error())
	}

	var A *tf.Tensor
	if A, err = tf.NewTensor([]int32{1}); err != nil {
		panic(err.Error())
	}

	var results []*tf.Tensor
	if results, err = sess.Run(
		map[tf.Output]*tf.Tensor{
			T: A,
		},
		[]tf.Output{output}, nil); err != nil {
		panic(err.Error())
	}
	for _, result := range results {
		fmt.Println(result.Value().([]float32))
	}

}

Any question?

However, seriously, try to use tfgo as much as possible instead of using only the op package.
I know that's not the case where tfgo could help, but whatever. Also, when you'll become an expert, I'd love to have someone that contribute actively to tfgo

Thank you for your reply.It is work for me.Is tf.MakeShape 's param's value doesn't matter?

Yes, tf.MakeShape is useless when you define a placeholder because the placeholder is overwritten at runtime, thus its shape will be overwritten as well.
In fact you could change your placeholder definiition with:
T := op.Placeholder(root.SubScope("input"), tf.Int32)

and the code will work without any problem.
In the context of placeholder what it matters is the shape of the tensor you feed.

thanks for your help.


visual studio 2017 (15.6.6) python intellisense

System: windows 10 64-bit, visual studio 2017 15.6.6.
I'm using the New Style Intellisense for auto-completion, which doesn't work for contexts like these:

with open(...) as file:
...

In the above context, the intellisense is unable to recognize the type of "file".

Thanks, I've added it to https://github.com/Microsoft/PTVS/issues/3046 and will close this one as duplicate.


Should we add break; after this line ?

https://github.com/pixijs/pixi-tilemap/blob/7baa397a05a90aa66d3e7afc7e2b2b22060a045d/src/CompositeRectTileLayer.ts#L86

I dont think it matters

if no break , the texture will be added to every child.  Is it necessary ?

Ok, you're right.


unregister plottable

Hey bower,
I'm the new maintainer of the Plottable open source project (https://github.com/palantir/plottable) and we're moving away from bower - I tried to follow the unregister steps at https://bower.io/docs/creating-packages/#unregister but I don't know the credentials for the Plottable bower account. Could we get the package removed?
Thanks,
Xiaohan

Hey bower,
I'm the new maintainer of the Plottable open source project (https://github.com/AkcentChester/html-pack) and we're moving away from bower - I tried to follow the unregister steps at https://bower.io/docs/creating-packages/#unregister but I don't know the credentials for the Plottable bower account. Could we get the package removed?
Thanks,
Chester

If you still want to unregister / modify this package (these packages) you can send PR against this repository that modifies db/packages.json file. Please include proof that you are owner of this package (these packages). Please also mind that even if we remove/modify entry in bower registry, bower clients can have cache saved which needs to be cleaned with bower cache clean for each user. At this point it's better to leave registry entries unmodified, they won't hurt anyone.


Support for Docker under Windows

With the native support of Docker under Windows Server 2016, it will be necessary to add support for Windows on the Docker Puppet module.

The compose resource works out of the box (assuming you have the docker-compose binary in path on your Windows box).  For most of the other stuff that is based on execs it shouldn't be too much work to make it compatible with Windows.  Stuff like the images manifest may be a bit trickier though as it's based on a shell script.

Could we use DSC to manage docker & containers? https://docs.docker.com/engine/admin/dsc/


inspect-job lists latest image for the pipeline, rather than the image that was actually used

What happened?:
While trying to debug some older pipeline runs, I noticed that inspect-job is returning the latest image specified for the pipeline, rather than the image used for a particular job. Note that we are using docker image digests to specify images, instead of tags.
-- 21:31 $ pachctl inspect-job 05b8336b98c64cc59dc3c0e666aa000b
ID: 05b8336b98c64cc59dc3c0e666aa000b
Pipeline: <pipeline name>
Started: 22 hours ago
Duration: 27 seconds
State: success
Reason:
Processed: 1
Failed: 0
Skipped: 0
Total: 1
Data Downloaded: 1.276MiB
Data Uploaded: 0B
Download Time: Less than a second
Process Time: Less than a second
Upload Time: 11 seconds
Datum Timeout: (duration: nil Duration)
Job Timeout: (duration: nil Duration)
Worker Status:
WORKER              JOB                 DATUM               STARTED             QUEUE
Restarts: 3
ParallelismSpec: constant:1
ResourceRequests:
	CPU: 0
	Memory: 64M

Input:
{
  "atom": {
    "name": "<pipeline name>",
    "repo": "<pipeline name>",
    "branch": "master",
    "commit": "0e8f18bb4b9446ea831368cb03a041f8",
    "glob": "/*"
  }
}

Transform:
{
  "image": "<image>@sha256:1accbc5cf0886e34a6b1da88bda7a50776b0a3c310f3332fcef7ab740e376599",
  "cmd": [
    "<cmd>"
  ]
}
Output Commit: 73b511b7ca594fcbbfcca2113e047c1a

Note in the above that the job ran 22 hours ago, and references an image with digest 1accbc5cf0886e34a6b1da88bda7a50776b0a3c310f3332fcef7ab740e376599. Looking in our container registry, the image with that digest was uploaded 2 hours ago, so it's impossible that it was used in a job run 22 hours ago. Note that 1accbc5cf0886e34a6b1da88bda7a50776b0a3c310f3332fcef7ab740e376599 is the current digest used in the latest update of the pipeline.
What you expected to happen?:
I expect the job metadata to retain the exact image digest used for the job.
How to reproduce it (as minimally and precisely as possible)?:
Create a pipeline using an image with a digest instead of a tag. Run the pipeline. Push a new version of the image, and update the pipeline with the new image digest. inspect-job on the old job, and note that it lists the new image digest.
Environment?:

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.7", GitCommit:"dd5e1a2978fd0b97d9b78e1564398aeea7e7fe92", GitTreeState:"clean", BuildDate:"2018-04-19T00:05:56Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.4-gke.2", GitCommit:"eb2e43842aaa21d6f0bb65d6adf5a84bbdc62eaf", GitTreeState:"clean", BuildDate:"2018-06-15T21:48:39Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}

Pachyderm CLI version (use pachctl version):

COMPONENT           VERSION
pachctl             1.7.1
pachd               1.7.1

Cloud provider (e.g. aws, azure, gke) or local deployment (e.g. minikube vs dockerized k8s): gke

@gabrielgrant I haven't tried with tags, and unfortunately it's not trivial for me to switch things around - digests are fairly baked into how we push images & pipelines right now.

@jdelfino no worries, we understand the issue and have enough to fix it. And I don't think tags are going to work as a workaround.


Eslint not recognizing alias path

Hello,
I am trying to create a project with react-app-rewired with alias path. The project works fine but having trouble with the alias lints as the eslint is unable to identify the alias
tsconfig.json
{
  "extends": "./paths.json",
  "compilerOptions": {
    "target": "es5",
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "removeComments": true,
    "allowJs": true,
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "noFallthroughCasesInSwitch": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "react-jsx",
    "baseUrl": "src"
  },
  "include": [
    "src"
  ],
  "exclude": [
    "node_modules"
  ]
}

path.json
{
    "compilerOptions": {
        "paths": {
            "@components/*": [
                "src/components/*"
            ],
            "@layouts/*": [
                "src/layouts/*"
            ]
        }
    }
}

eslintrc.js
module.exports = {
  env: {
    browser: true,
    es2021: true,
  },
  extends: [
    'plugin:@typescript-eslint/recommended',
    'plugin:@typescript-eslint/recommended-requiring-type-checking',
  ],
  parser: '@typescript-eslint/parser',
  parserOptions: {
    project: './tsconfig.json',
    tsconfigRootDir: './'
  },
  plugins: [
    '@typescript-eslint',
    'import',
  ],
  rules: {

  },
  settings: {
    'import/resolver': {
      typescript: {
        "alwaysTryTypes": true,
      },
    },
  }
};

config-overrides.js
const {
  override,
  disableChunk,
  addBabelPlugins,
  removeModuleScopePlugin,
  addBabelPresets,
  addWebpackAlias,
} = require('customize-cra');

const path = require('path')
module.exports = override(
  ...addBabelPresets('@babel/preset-env', '@babel/preset-react'),
  ...addBabelPlugins(
    [
      'import',
      { libraryName: 'antd-mobile', libraryDirectory: 'lib', style: 'css' },
      'antd-mobile',
    ],
    [
      'import',
      { libraryName: 'antd', libraryDirectory: 'lib', style: true },
      'antd',
    ],
  ),
  disableChunk(),
  removeModuleScopePlugin(),
  addWebpackAlias({
    ['@components']: path.resolve(__dirname, 'src/components'),
    ['@layouts']: path.resolve(__dirname, 'src/layouts')
  })
);

Thank you for your time
Edit
Repo link : https://github.com/harikautilya/events

Please provide a minimal and runnable reproduction.

I had a very similar issue in a way, and I noticed that tsconfig-paths was prepending the alias path with the baseUrl. Therefore, if your baseUrl is src. Try removing src from your alias path, such as "@components/*": ["components/*"]

@tleunen got it let me try it today and get back to you
@JounQin will edit the issue soon

@tleunen Tired it. Didnt not work out.
@JounQin Make my repo public as it does nto contain any important information.
Will make it private as soon as the issue closes

@harikautilya Your reproduction is too huge, and I didn't know what command to run to reproduce even...

A rough guess:
// paths.json
{
    "compilerOptions": {
        "baseUrl": "src",
        "paths": {
            "@components/*": ["components/*"],
            "@components": ["components"],
            "@layouts/*": ["layouts/*"],
            "@layouts": ["layouts"]
        }
    }
}

@JounQin Oh.
here are steps.

Clone the repo
Npm install
Npm run start

You should see the following error
Cannot find module '@layouts' or its corresponding type declarations.
but the project fine on port http://localhost:3000/

@JounQin The fix you suggested works!!!!
But what is surprising is in tsconfig.json  "baseUrl": "src" does exisit. Any particular reason why this happens only when present in paths.json

@JounQin Oh. here are steps.

Clone the repo
Npm install
Npm run start

You should see the following error Cannot find module '@layouts' or its corresponding type declarations.
but the project fine on port http://localhost:3000/

This is nothing related to ESLint or this resolver. @layouts/* and @layouts are different.


Support the Solr /export interface to transfer result sets from Solar to Spark

https://cwiki.apache.org/confluence/display/solr/Exporting+Result+Sets

Duplicate to #7


make a suggestion about DUBBO plugin

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] discussion

Question
Dubbo plugin will have the following problems when retrying:
If the current link is triggered by other components that are not monitored, and it does not have EntrySpan, the stackDepth of the link is 0 when the dubbo is called internally. The traceId generated by the call is different. however, if the dubbo call timeout and retry, the traceId is the same, because the sw3 parameter of the last call is reused. In this scenario, The effect of multiple dubbo calls and dubbo retry  should be the same. I think the problem needs to be fixed, that is, update the value of sw3 when retrying.

@tzy1316106836 can you please send a pull request to fix this?

https://github.com/apache/skywalking/pull/4187/files

@tzy1316106836 can you please send a pull request to fix this?

fixed by #4187


Better feature flags for backends.

I think we should revisit the name of our feature flags and backends. To make things simple we should have:

tch => libtorch
wgpu-spirv => vulkan
wgpu => webgpu
cuda-jit => cuda

Some feature flags are meant to customize a backend, they should be specific for that backend:

cuda => candle-cuda, libtorch-cuda
metal => candle-metal, libtorch-metal
openblas => ndarray-openblas
accelerate => ndarray-accelerate

Essentially, we're making backends made with cubecl first class, meaning we don't need to prefix things with cubecl like cubecl-vulkan, cubecl-cuda or cubecl-fusion, but for the third-party backends, I think it's more flexible, since we won't have feature flags that may clash with our own. In that sense, we may also rename burn-jit to burn-cubecl, since it's pretty much the backend built on top of cubecl.

Just to be clear these feature flags are part of the meta package burn?


[16:40:07][I][ant_bms_ble:373]:   Balanced cell bitmask: 0
[16:40:07][D][sensor:094]: 'ant-bms-ble-monitor max cell voltage': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:07][D][sensor:094]: 'ant-bms-ble-monitor max voltage cell': Sending state 2.00000  with 0 decimals of accuracy
[16:40:07][D][sensor:094]: 'ant-bms-ble-monitor min cell voltage': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:07][D][sensor:094]: 'ant-bms-ble-monitor min voltage cell': Sending state 1.00000  with 0 decimals of accuracy
[16:40:07][D][sensor:094]: 'ant-bms-ble-monitor delta cell voltage': Sending state 0.00100 V with 3 decimals of accuracy
[16:40:07][D][sensor:094]: 'ant-bms-ble-monitor average cell voltage': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:07][I][ant_bms_ble:400]:   Accumulated discharging capacity: 299.67 Ah
[16:40:07][I][ant_bms_ble:403]:   Accumulated charging capacity: 351.60 Ah
[16:40:07][I][ant_bms_ble:406]:   Accumulated discharging time: 14h
[16:40:07][I][ant_bms_ble:409]:   Accumulated charging time: 2d 20h
[16:40:07][W][component:214]: Component esp32_ble took a long time for an operation (0.85 s).
[16:40:07][W][component:215]: Components should block for at most 20-30ms.
[16:40:11][VV][ant_bms_ble:673]: Send command: 7E.A<IP_ADDRESS>.BE.18.55.AA.55 (10)
[16:40:11][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=4 gattc_if=3
[16:40:11][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:11][VV][ant_bms_ble:145]: Notification received: 7E.A<IP_ADDRESS>.AE.<IP_ADDRESS>E.<IP_ADDRESS>.<IP_ADDRESS>.00.00 (20)
[16:40:11][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:11][VV][ant_bms_ble:145]: Notification received: <IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.00.00.E3.0F.E4.0F.E4.0F (20)
[16:40:11][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:11][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F (20)
[16:40:11][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:11][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F (20)
[16:40:11][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:11][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.<IP_ADDRESS>.16.00 (20)
[16:40:11][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:11][VV][ant_bms_ble:145]: Notification received: D8.FF.<IP_ADDRESS>.AB.2F.00.00.5B.<IP_ADDRESS>.01.00.00.C0.9B (20)
[16:40:11][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:11][VV][ant_bms_ble:145]: Notification received: C0.01.8D.2D.94.01.02.F<IP_ADDRESS>.00.00.00.B8.F7.C<IP_ADDRESS> (20)
[16:40:11][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:11][VV][ant_bms_ble:145]: Notification received: 00.00.E4.0F.02.00.E3.0F.<IP_ADDRESS>.E3.0F.00.00.6B.00.69.00 (20)
[16:40:11][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:11][VV][ant_bms_ble:145]: Notification received: AE.02.F1.FA.<IP_ADDRESS>.72.5D.05.00.D1.CE.00.00.77.C1.03.00 (20)
[16:40:11][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:11][VV][ant_bms_ble:145]: Notification received: 11.37.AA.55
[16:40:11][I][ant_bms_ble:232]: Status frame (184 bytes):
[16:40:11][D][ant_bms_ble:233]:   7E.A<IP_ADDRESS>.AE.<IP_ADDRESS>E.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.E3.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.<IP_ADDRESS>.16.00.D8.FF.<IP_ADDRESS>.AB.2F.00.00.5B.<IP_ADDRESS>.01.00.00.C0.9B.C0.01.8D.2D.94.01.02.F<IP_ADDRESS>.00.00.00.B8.F7.C<IP_ADDRESS>.00.00.E4.0F.02.00.E3.0F.<IP_ADDRESS>.E3.0F.00.00.6B.00.69.00.
[16:40:11][I][ant_bms_ble:251]:   Permissions: 5
[16:40:11][I][ant_bms_ble:254]:   Battery status: 1
[16:40:11][I][ant_bms_ble:258]:   Number of temperature sensors: 4
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor battery strings': Sending state 30.00000  with 0 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 1': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 2': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 3': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 4': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 5': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 6': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 7': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 8': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 9': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 10': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 11': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 12': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 13': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 14': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 15': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 16': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 17': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 18': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 19': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 20': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 21': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 22': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 23': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 24': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 25': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 26': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 27': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 28': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 29': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 30': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor temperature 1': Sending state 20.00000 °C with 0 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor temperature 2': Sending state 22.00000 °C with 0 decimals of accuracy
[16:40:11][D][sensor:094]: 'ant-bms-ble-monitor temperature 3': Sending state 22.00000 °C with 0 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor temperature 4': Sending state -40.00000 °C with 0 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor temperature 5': Sending state 20.00000 °C with 0 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor temperature 6': Sending state 19.00000 °C with 0 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor total voltage': Sending state 122.03000 V with 2 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor current': Sending state 0.00000 A with 1 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor soc': Sending state 91.00000 % with 0 decimals of accuracy
[16:40:12][I][ant_bms_ble:319]:   State of health: 100 %
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor charge mosfet status code': Sending state 1.00000  with 0 decimals of accuracy
[16:40:12][V][text_sensor:013]: 'ant-bms-ble-monitor charge mosfet status': Received new state On
[16:40:12][D][text_sensor:064]: 'ant-bms-ble-monitor charge mosfet status': Sending state 'On'
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor discharge mosfet status code': Sending state 1.00000  with 0 decimals of accuracy
[16:40:12][V][text_sensor:013]: 'ant-bms-ble-monitor discharge mosfet status': Received new state On
[16:40:12][D][text_sensor:064]: 'ant-bms-ble-monitor discharge mosfet status': Sending state 'On'
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor balancer status code': Sending state 0.00000  with 0 decimals of accuracy
[16:40:12][V][text_sensor:013]: 'ant-bms-ble-monitor balancer status': Received new state Off
[16:40:12][D][text_sensor:064]: 'ant-bms-ble-monitor balancer status': Sending state 'Off'
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor total battery capacity setting': Sending state 29.40000 Ah with 2 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor capacity remaining': Sending state 26.48820 Ah with 2 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor battery cycle capacity': Sending state 325.63400 Ah with 3 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor power': Sending state 0.00000 W with 2 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor total runtime': Sending state 29554616.00000 s with 0 decimals of accuracy
[16:40:12][V][text_sensor:013]: 'ant-bms-ble-monitor total runtime formatted': Received new state 342d 1h
[16:40:12][D][text_sensor:064]: 'ant-bms-ble-monitor total runtime formatted': Sending state '342d 1h'
[16:40:12][I][ant_bms_ble:373]:   Balanced cell bitmask: 0
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor max cell voltage': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor max voltage cell': Sending state 2.00000  with 0 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor min cell voltage': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor min voltage cell': Sending state 1.00000  with 0 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor delta cell voltage': Sending state 0.00100 V with 3 decimals of accuracy
[16:40:12][D][sensor:094]: 'ant-bms-ble-monitor average cell voltage': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:12][I][ant_bms_ble:400]:   Accumulated discharging capacity: 299.67 Ah
[16:40:12][I][ant_bms_ble:403]:   Accumulated charging capacity: 351.60 Ah
[16:40:12][I][ant_bms_ble:406]:   Accumulated discharging time: 14h
[16:40:12][I][ant_bms_ble:409]:   Accumulated charging time: 2d 20h
[16:40:12][W][component:214]: Component esp32_ble took a long time for an operation (0.84 s).
[16:40:12][W][component:215]: Components should block for at most 20-30ms.
[16:40:16][VV][ant_bms_ble:673]: Send command: 7E.A<IP_ADDRESS>.BE.18.55.AA.55 (10)
[16:40:16][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=4 gattc_if=3
[16:40:16][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:16][VV][ant_bms_ble:145]: Notification received: 7E.A<IP_ADDRESS>.AE.<IP_ADDRESS>E.<IP_ADDRESS>.<IP_ADDRESS>.00.00 (20)
[16:40:16][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:16][VV][ant_bms_ble:145]: Notification received: <IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.00.00.E3.0F.E4.0F.E4.0F (20)
[16:40:16][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:16][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F (20)
[16:40:16][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:16][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F (20)
[16:40:16][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:16][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.<IP_ADDRESS>.16.00 (20)
[16:40:16][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:16][VV][ant_bms_ble:145]: Notification received: D8.FF.<IP_ADDRESS>.AB.2F.00.00.5B.<IP_ADDRESS>.01.00.00.C0.9B (20)
[16:40:16][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:16][VV][ant_bms_ble:145]: Notification received: C0.01.8D.2D.94.01.02.F<IP_ADDRESS>.00.00.00.BD.F7.C<IP_ADDRESS> (20)
[16:40:16][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:16][VV][ant_bms_ble:145]: Notification received: 00.00.E4.0F.02.00.E3.0F.<IP_ADDRESS>.E3.0F.00.00.6B.00.69.00 (20)
[16:40:16][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:16][VV][ant_bms_ble:145]: Notification received: AE.02.F1.FA.<IP_ADDRESS>.72.5D.05.00.D1.CE.00.00.77.C1.03.00 (20)
[16:40:16][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:16][VV][ant_bms_ble:145]: Notification received: C2.A9.AA.55
[16:40:16][I][ant_bms_ble:232]: Status frame (184 bytes):
[16:40:16][D][ant_bms_ble:233]:   7E.A<IP_ADDRESS>.AE.<IP_ADDRESS>E.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.E3.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.<IP_ADDRESS>.16.00.D8.FF.<IP_ADDRESS>.AB.2F.00.00.5B.<IP_ADDRESS>.01.00.00.C0.9B.C0.01.8D.2D.94.01.02.F<IP_ADDRESS>.00.00.00.BD.F7.C<IP_ADDRESS>.00.00.E4.0F.02.00.E3.0F.<IP_ADDRESS>.E3.0F.00.00.6B.00.69.00.
[16:40:16][I][ant_bms_ble:251]:   Permissions: 5
[16:40:16][I][ant_bms_ble:254]:   Battery status: 1
[16:40:16][I][ant_bms_ble:258]:   Number of temperature sensors: 4
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor battery strings': Sending state 30.00000  with 0 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 1': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 2': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 3': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 4': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 5': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 6': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 7': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 8': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 9': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 10': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 11': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 12': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 13': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 14': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 15': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 16': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 17': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 18': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 19': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 20': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 21': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 22': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 23': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 24': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 25': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 26': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 27': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 28': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 29': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 30': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:16][D][sensor:094]: 'ant-bms-ble-monitor temperature 1': Sending state 20.00000 °C with 0 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor temperature 2': Sending state 22.00000 °C with 0 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor temperature 3': Sending state 22.00000 °C with 0 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor temperature 4': Sending state -40.00000 °C with 0 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor temperature 5': Sending state 20.00000 °C with 0 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor temperature 6': Sending state 19.00000 °C with 0 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor total voltage': Sending state 122.03000 V with 2 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor current': Sending state 0.00000 A with 1 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor soc': Sending state 91.00000 % with 0 decimals of accuracy
[16:40:17][I][ant_bms_ble:319]:   State of health: 100 %
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor charge mosfet status code': Sending state 1.00000  with 0 decimals of accuracy
[16:40:17][V][text_sensor:013]: 'ant-bms-ble-monitor charge mosfet status': Received new state On
[16:40:17][D][text_sensor:064]: 'ant-bms-ble-monitor charge mosfet status': Sending state 'On'
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor discharge mosfet status code': Sending state 1.00000  with 0 decimals of accuracy
[16:40:17][V][text_sensor:013]: 'ant-bms-ble-monitor discharge mosfet status': Received new state On
[16:40:17][D][text_sensor:064]: 'ant-bms-ble-monitor discharge mosfet status': Sending state 'On'
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor balancer status code': Sending state 0.00000  with 0 decimals of accuracy
[16:40:17][V][text_sensor:013]: 'ant-bms-ble-monitor balancer status': Received new state Off
[16:40:17][D][text_sensor:064]: 'ant-bms-ble-monitor balancer status': Sending state 'Off'
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor total battery capacity setting': Sending state 29.40000 Ah with 2 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor capacity remaining': Sending state 26.48820 Ah with 2 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor battery cycle capacity': Sending state 325.63400 Ah with 3 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor power': Sending state 0.00000 W with 2 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor total runtime': Sending state 29554620.00000 s with 0 decimals of accuracy
[16:40:17][V][text_sensor:013]: 'ant-bms-ble-monitor total runtime formatted': Received new state 342d 1h
[16:40:17][D][text_sensor:064]: 'ant-bms-ble-monitor total runtime formatted': Sending state '342d 1h'
[16:40:17][I][ant_bms_ble:373]:   Balanced cell bitmask: 0
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor max cell voltage': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor max voltage cell': Sending state 2.00000  with 0 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor min cell voltage': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor min voltage cell': Sending state 1.00000  with 0 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor delta cell voltage': Sending state 0.00100 V with 3 decimals of accuracy
[16:40:17][D][sensor:094]: 'ant-bms-ble-monitor average cell voltage': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:17][I][ant_bms_ble:400]:   Accumulated discharging capacity: 299.67 Ah
[16:40:17][I][ant_bms_ble:403]:   Accumulated charging capacity: 351.60 Ah
[16:40:17][I][ant_bms_ble:406]:   Accumulated discharging time: 14h
[16:40:17][I][ant_bms_ble:409]:   Accumulated charging time: 2d 20h
[16:40:17][W][component:214]: Component esp32_ble took a long time for an operation (0.88 s).
[16:40:17][W][component:215]: Components should block for at most 20-30ms.
[16:40:21][VV][ant_bms_ble:673]: Send command: 7E.A<IP_ADDRESS>.BE.18.55.AA.55 (10)
[16:40:21][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=4 gattc_if=3
[16:40:21][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:21][VV][ant_bms_ble:145]: Notification received: 7E.A<IP_ADDRESS>.AE.<IP_ADDRESS>E.<IP_ADDRESS>.<IP_ADDRESS>.00.00 (20)
[16:40:21][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:21][VV][ant_bms_ble:145]: Notification received: <IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.00.00.E3.0F.E4.0F.E4.0F (20)
[16:40:21][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:21][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F (20)
[16:40:21][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:21][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F (20)
[16:40:21][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:21][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.<IP_ADDRESS>.16.00 (20)
[16:40:21][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:21][VV][ant_bms_ble:145]: Notification received: D8.FF.<IP_ADDRESS>.AB.2F.00.00.5B.<IP_ADDRESS>.01.00.00.C0.9B (20)
[16:40:21][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:21][VV][ant_bms_ble:145]: Notification received: C0.01.8D.2D.94.01.02.F<IP_ADDRESS>.00.00.00.C2.F7.C<IP_ADDRESS> (20)
[16:40:21][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:21][VV][ant_bms_ble:145]: Notification received: 00.00.E4.0F.02.00.E3.0F.<IP_ADDRESS>.E3.0F.00.00.6B.00.69.00 (20)
[16:40:21][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:21][VV][ant_bms_ble:145]: Notification received: AE.02.F1.FA.<IP_ADDRESS>.72.5D.05.00.D1.CE.00.00.77.C1.03.00 (20)
[16:40:21][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:21][VV][ant_bms_ble:145]: Notification received: 8A.B5.AA.55
[16:40:21][I][ant_bms_ble:232]: Status frame (184 bytes):
[16:40:21][D][ant_bms_ble:233]:   7E.A<IP_ADDRESS>.AE.<IP_ADDRESS>E.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.E3.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.<IP_ADDRESS>.16.00.D8.FF.<IP_ADDRESS>.AB.2F.00.00.5B.<IP_ADDRESS>.01.00.00.C0.9B.C0.01.8D.2D.94.01.02.F<IP_ADDRESS>.00.00.00.C2.F7.C<IP_ADDRESS>.00.00.E4.0F.02.00.E3.0F.<IP_ADDRESS>.E3.0F.00.00.6B.00.69.00.
[16:40:21][I][ant_bms_ble:251]:   Permissions: 5
[16:40:21][I][ant_bms_ble:254]:   Battery status: 1
[16:40:21][I][ant_bms_ble:258]:   Number of temperature sensors: 4
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor battery strings': Sending state 30.00000  with 0 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 1': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 2': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 3': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 4': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 5': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 6': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 7': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 8': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 9': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 10': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 11': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 12': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 13': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 14': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 15': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 16': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 17': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 18': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 19': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 20': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 21': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 22': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 23': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 24': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 25': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 26': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 27': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 28': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 29': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 30': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor temperature 1': Sending state 20.00000 °C with 0 decimals of accuracy
[16:40:21][D][sensor:094]: 'ant-bms-ble-monitor temperature 2': Sending state 22.00000 °C with 0 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor temperature 3': Sending state 22.00000 °C with 0 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor temperature 4': Sending state -40.00000 °C with 0 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor temperature 5': Sending state 20.00000 °C with 0 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor temperature 6': Sending state 19.00000 °C with 0 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor total voltage': Sending state 122.03000 V with 2 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor current': Sending state 0.00000 A with 1 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor soc': Sending state 91.00000 % with 0 decimals of accuracy
[16:40:22][I][ant_bms_ble:319]:   State of health: 100 %
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor charge mosfet status code': Sending state 1.00000  with 0 decimals of accuracy
[16:40:22][V][text_sensor:013]: 'ant-bms-ble-monitor charge mosfet status': Received new state On
[16:40:22][D][text_sensor:064]: 'ant-bms-ble-monitor charge mosfet status': Sending state 'On'
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor discharge mosfet status code': Sending state 1.00000  with 0 decimals of accuracy
[16:40:22][V][text_sensor:013]: 'ant-bms-ble-monitor discharge mosfet status': Received new state On
[16:40:22][D][text_sensor:064]: 'ant-bms-ble-monitor discharge mosfet status': Sending state 'On'
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor balancer status code': Sending state 0.00000  with 0 decimals of accuracy
[16:40:22][V][text_sensor:013]: 'ant-bms-ble-monitor balancer status': Received new state Off
[16:40:22][D][text_sensor:064]: 'ant-bms-ble-monitor balancer status': Sending state 'Off'
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor total battery capacity setting': Sending state 29.40000 Ah with 2 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor capacity remaining': Sending state 26.48820 Ah with 2 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor battery cycle capacity': Sending state 325.63400 Ah with 3 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor power': Sending state 0.00000 W with 2 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor total runtime': Sending state 29554626.00000 s with 0 decimals of accuracy
[16:40:22][V][text_sensor:013]: 'ant-bms-ble-monitor total runtime formatted': Received new state 342d 1h
[16:40:22][D][text_sensor:064]: 'ant-bms-ble-monitor total runtime formatted': Sending state '342d 1h'
[16:40:22][I][ant_bms_ble:373]:   Balanced cell bitmask: 0
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor max cell voltage': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor max voltage cell': Sending state 2.00000  with 0 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor min cell voltage': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor min voltage cell': Sending state 1.00000  with 0 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor delta cell voltage': Sending state 0.00100 V with 3 decimals of accuracy
[16:40:22][D][sensor:094]: 'ant-bms-ble-monitor average cell voltage': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:22][I][ant_bms_ble:400]:   Accumulated discharging capacity: 299.67 Ah
[16:40:22][I][ant_bms_ble:403]:   Accumulated charging capacity: 351.60 Ah
[16:40:22][I][ant_bms_ble:406]:   Accumulated discharging time: 14h
[16:40:22][I][ant_bms_ble:409]:   Accumulated charging time: 2d 20h
[16:40:22][W][component:214]: Component esp32_ble took a long time for an operation (0.84 s).
[16:40:22][W][component:215]: Components should block for at most 20-30ms.
[16:40:26][VV][ant_bms_ble:673]: Send command: 7E.A<IP_ADDRESS>.BE.18.55.AA.55 (10)
[16:40:26][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=4 gattc_if=3
[16:40:26][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:26][VV][ant_bms_ble:145]: Notification received: 7E.A<IP_ADDRESS>.AE.<IP_ADDRESS>E.<IP_ADDRESS>.<IP_ADDRESS>.00.00 (20)
[16:40:26][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:26][VV][ant_bms_ble:145]: Notification received: <IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.00.00.E3.0F.E4.0F.E4.0F (20)
[16:40:26][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:26][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F (20)
[16:40:26][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:26][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F (20)
[16:40:26][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:26][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.<IP_ADDRESS>.16.00 (20)
[16:40:26][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:26][VV][ant_bms_ble:145]: Notification received: D8.FF.<IP_ADDRESS>.AB.2F.00.00.5B.<IP_ADDRESS>.01.00.00.C0.9B (20)
[16:40:26][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:26][VV][ant_bms_ble:145]: Notification received: C0.01.8D.2D.94.01.02.F<IP_ADDRESS>.00.00.00.C7.F7.C<IP_ADDRESS> (20)
[16:40:26][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:26][VV][ant_bms_ble:145]: Notification received: 00.00.E4.0F.02.00.E3.0F.<IP_ADDRESS>.E3.0F.00.00.6B.00.69.00 (20)
[16:40:26][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:26][VV][ant_bms_ble:145]: Notification received: AE.02.F1.FA.<IP_ADDRESS>.72.5D.05.00.D1.CE.00.00.77.C1.03.00 (20)
[16:40:26][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:26][VV][ant_bms_ble:145]: Notification received: 59.2B.AA.55
[16:40:26][I][ant_bms_ble:232]: Status frame (184 bytes):
[16:40:26][D][ant_bms_ble:233]:   7E.A<IP_ADDRESS>.AE.<IP_ADDRESS>E.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.E3.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.<IP_ADDRESS>.16.00.D8.FF.<IP_ADDRESS>.AB.2F.00.00.5B.<IP_ADDRESS>.01.00.00.C0.9B.C0.01.8D.2D.94.01.02.F<IP_ADDRESS>.00.00.00.C7.F7.C<IP_ADDRESS>.00.00.E4.0F.02.00.E3.0F.<IP_ADDRESS>.E3.0F.00.00.6B.00.69.00.
[16:40:26][I][ant_bms_ble:251]:   Permissions: 5
[16:40:26][I][ant_bms_ble:254]:   Battery status: 1
[16:40:26][I][ant_bms_ble:258]:   Number of temperature sensors: 4
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor battery strings': Sending state 30.00000  with 0 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 1': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 2': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 3': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 4': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 5': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 6': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 7': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 8': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 9': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 10': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 11': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 12': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 13': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 14': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 15': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 16': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 17': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 18': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 19': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 20': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 21': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 22': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 23': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 24': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 25': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 26': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 27': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 28': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 29': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 30': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor temperature 1': Sending state 20.00000 °C with 0 decimals of accuracy
[16:40:26][D][sensor:094]: 'ant-bms-ble-monitor temperature 2': Sending state 22.00000 °C with 0 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor temperature 3': Sending state 22.00000 °C with 0 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor temperature 4': Sending state -40.00000 °C with 0 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor temperature 5': Sending state 20.00000 °C with 0 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor temperature 6': Sending state 19.00000 °C with 0 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor total voltage': Sending state 122.03000 V with 2 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor current': Sending state 0.00000 A with 1 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor soc': Sending state 91.00000 % with 0 decimals of accuracy
[16:40:27][I][ant_bms_ble:319]:   State of health: 100 %
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor charge mosfet status code': Sending state 1.00000  with 0 decimals of accuracy
[16:40:27][V][text_sensor:013]: 'ant-bms-ble-monitor charge mosfet status': Received new state On
[16:40:27][D][text_sensor:064]: 'ant-bms-ble-monitor charge mosfet status': Sending state 'On'
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor discharge mosfet status code': Sending state 1.00000  with 0 decimals of accuracy
[16:40:27][V][text_sensor:013]: 'ant-bms-ble-monitor discharge mosfet status': Received new state On
[16:40:27][D][text_sensor:064]: 'ant-bms-ble-monitor discharge mosfet status': Sending state 'On'
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor balancer status code': Sending state 0.00000  with 0 decimals of accuracy
[16:40:27][V][text_sensor:013]: 'ant-bms-ble-monitor balancer status': Received new state Off
[16:40:27][D][text_sensor:064]: 'ant-bms-ble-monitor balancer status': Sending state 'Off'
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor total battery capacity setting': Sending state 29.40000 Ah with 2 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor capacity remaining': Sending state 26.48820 Ah with 2 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor battery cycle capacity': Sending state 325.63400 Ah with 3 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor power': Sending state 0.00000 W with 2 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor total runtime': Sending state 29554632.00000 s with 0 decimals of accuracy
[16:40:27][V][text_sensor:013]: 'ant-bms-ble-monitor total runtime formatted': Received new state 342d 1h
[16:40:27][D][text_sensor:064]: 'ant-bms-ble-monitor total runtime formatted': Sending state '342d 1h'
[16:40:27][I][ant_bms_ble:373]:   Balanced cell bitmask: 0
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor max cell voltage': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor max voltage cell': Sending state 2.00000  with 0 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor min cell voltage': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor min voltage cell': Sending state 1.00000  with 0 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor delta cell voltage': Sending state 0.00100 V with 3 decimals of accuracy
[16:40:27][D][sensor:094]: 'ant-bms-ble-monitor average cell voltage': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:27][I][ant_bms_ble:400]:   Accumulated discharging capacity: 299.67 Ah
[16:40:27][I][ant_bms_ble:403]:   Accumulated charging capacity: 351.60 Ah
[16:40:27][I][ant_bms_ble:406]:   Accumulated discharging time: 14h
[16:40:27][I][ant_bms_ble:409]:   Accumulated charging time: 2d 20h
[16:40:27][W][component:214]: Component esp32_ble took a long time for an operation (0.88 s).
[16:40:27][W][component:215]: Components should block for at most 20-30ms.
[16:40:31][VV][ant_bms_ble:673]: Send command: 7E.A<IP_ADDRESS>.BE.18.55.AA.55 (10)
[16:40:31][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=4 gattc_if=3
[16:40:31][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:31][VV][ant_bms_ble:145]: Notification received: 7E.A<IP_ADDRESS>.AE.<IP_ADDRESS>E.<IP_ADDRESS>.<IP_ADDRESS>.00.00 (20)
[16:40:31][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:31][VV][ant_bms_ble:145]: Notification received: <IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.00.00.E3.0F.E4.0F.E4.0F (20)
[16:40:31][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:31][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F (20)
[16:40:31][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:31][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F (20)
[16:40:31][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:31][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.<IP_ADDRESS>.16.00 (20)
[16:40:31][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:31][VV][ant_bms_ble:145]: Notification received: D8.FF.<IP_ADDRESS>.AB.2F.00.00.5B.<IP_ADDRESS>.01.00.00.C0.9B (20)
[16:40:31][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:31][VV][ant_bms_ble:145]: Notification received: C0.01.8D.2D.94.01.02.F<IP_ADDRESS>.00.00.00.CC.F7.C<IP_ADDRESS> (20)
[16:40:31][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:31][VV][ant_bms_ble:145]: Notification received: 00.00.E4.0F.02.00.E3.0F.<IP_ADDRESS>.E3.0F.00.00.6B.00.69.00 (20)
[16:40:31][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:31][VV][ant_bms_ble:145]: Notification received: AE.02.F1.FA.<IP_ADDRESS>.72.5D.05.00.D1.CE.00.00.77.C1.03.00 (20)
[16:40:31][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:31][VV][ant_bms_ble:145]: Notification received: 6D.FA.AA.55
[16:40:31][I][ant_bms_ble:232]: Status frame (184 bytes):
[16:40:31][D][ant_bms_ble:233]:   7E.A<IP_ADDRESS>.AE.<IP_ADDRESS>E.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.E3.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.<IP_ADDRESS>.16.00.D8.FF.<IP_ADDRESS>.AB.2F.00.00.5B.<IP_ADDRESS>.01.00.00.C0.9B.C0.01.8D.2D.94.01.02.F<IP_ADDRESS>.00.00.00.CC.F7.C<IP_ADDRESS>.00.00.E4.0F.02.00.E3.0F.<IP_ADDRESS>.E3.0F.00.00.6B.00.69.00.
[16:40:31][I][ant_bms_ble:251]:   Permissions: 5
[16:40:31][I][ant_bms_ble:254]:   Battery status: 1
[16:40:31][I][ant_bms_ble:258]:   Number of temperature sensors: 4
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor battery strings': Sending state 30.00000  with 0 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 1': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 2': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 3': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 4': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 5': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 6': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 7': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 8': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 9': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 10': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 11': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 12': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 13': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 14': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 15': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 16': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 17': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 18': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 19': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 20': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 21': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 22': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 23': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 24': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 25': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 26': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 27': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 28': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 29': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 30': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor temperature 1': Sending state 20.00000 °C with 0 decimals of accuracy
[16:40:31][D][sensor:094]: 'ant-bms-ble-monitor temperature 2': Sending state 22.00000 °C with 0 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor temperature 3': Sending state 22.00000 °C with 0 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor temperature 4': Sending state -40.00000 °C with 0 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor temperature 5': Sending state 20.00000 °C with 0 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor temperature 6': Sending state 19.00000 °C with 0 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor total voltage': Sending state 122.03000 V with 2 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor current': Sending state 0.00000 A with 1 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor soc': Sending state 91.00000 % with 0 decimals of accuracy
[16:40:32][I][ant_bms_ble:319]:   State of health: 100 %
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor charge mosfet status code': Sending state 1.00000  with 0 decimals of accuracy
[16:40:32][V][text_sensor:013]: 'ant-bms-ble-monitor charge mosfet status': Received new state On
[16:40:32][D][text_sensor:064]: 'ant-bms-ble-monitor charge mosfet status': Sending state 'On'
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor discharge mosfet status code': Sending state 1.00000  with 0 decimals of accuracy
[16:40:32][V][text_sensor:013]: 'ant-bms-ble-monitor discharge mosfet status': Received new state On
[16:40:32][D][text_sensor:064]: 'ant-bms-ble-monitor discharge mosfet status': Sending state 'On'
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor balancer status code': Sending state 0.00000  with 0 decimals of accuracy
[16:40:32][V][text_sensor:013]: 'ant-bms-ble-monitor balancer status': Received new state Off
[16:40:32][D][text_sensor:064]: 'ant-bms-ble-monitor balancer status': Sending state 'Off'
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor total battery capacity setting': Sending state 29.40000 Ah with 2 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor capacity remaining': Sending state 26.48820 Ah with 2 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor battery cycle capacity': Sending state 325.63400 Ah with 3 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor power': Sending state 0.00000 W with 2 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor total runtime': Sending state 29554636.00000 s with 0 decimals of accuracy
[16:40:32][V][text_sensor:013]: 'ant-bms-ble-monitor total runtime formatted': Received new state 342d 1h
[16:40:32][D][text_sensor:064]: 'ant-bms-ble-monitor total runtime formatted': Sending state '342d 1h'
[16:40:32][I][ant_bms_ble:373]:   Balanced cell bitmask: 0
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor max cell voltage': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor max voltage cell': Sending state 2.00000  with 0 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor min cell voltage': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor min voltage cell': Sending state 1.00000  with 0 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor delta cell voltage': Sending state 0.00100 V with 3 decimals of accuracy
[16:40:32][D][sensor:094]: 'ant-bms-ble-monitor average cell voltage': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:32][I][ant_bms_ble:400]:   Accumulated discharging capacity: 299.67 Ah
[16:40:32][I][ant_bms_ble:403]:   Accumulated charging capacity: 351.60 Ah
[16:40:32][I][ant_bms_ble:406]:   Accumulated discharging time: 14h
[16:40:32][I][ant_bms_ble:409]:   Accumulated charging time: 2d 20h
[16:40:32][W][component:214]: Component esp32_ble took a long time for an operation (0.88 s).
[16:40:32][W][component:215]: Components should block for at most 20-30ms.
[16:40:36][VV][ant_bms_ble:673]: Send command: 7E.A<IP_ADDRESS>.BE.18.55.AA.55 (10)
[16:40:36][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=4 gattc_if=3
[16:40:36][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:36][VV][ant_bms_ble:145]: Notification received: 7E.A<IP_ADDRESS>.AE.<IP_ADDRESS>E.<IP_ADDRESS>.<IP_ADDRESS>.00.00 (20)
[16:40:36][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:36][VV][ant_bms_ble:145]: Notification received: <IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.00.00.E3.0F.E4.0F.E4.0F (20)
[16:40:36][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:36][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F (20)
[16:40:36][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:36][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F (20)
[16:40:36][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:36][VV][ant_bms_ble:145]: Notification received: E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.<IP_ADDRESS>.16.00 (20)
[16:40:36][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:36][VV][ant_bms_ble:145]: Notification received: D8.FF.<IP_ADDRESS>.AB.2F.00.00.5B.<IP_ADDRESS>.01.00.00.C0.9B (20)
[16:40:36][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:36][VV][ant_bms_ble:145]: Notification received: C0.01.8D.2D.94.01.02.F<IP_ADDRESS>.00.00.00.D1.F7.C<IP_ADDRESS> (20)
[16:40:36][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:36][VV][ant_bms_ble:145]: Notification received: 00.00.E4.0F.02.00.E3.0F.<IP_ADDRESS>.E3.0F.00.00.6B.00.69.00 (20)
[16:40:36][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:36][VV][ant_bms_ble:145]: Notification received: AE.02.F1.FA.<IP_ADDRESS>.72.5D.05.00.D1.CE.00.00.77.C1.03.00 (20)
[16:40:36][V][esp32_ble_client:119]: [0] [32:E3:2E:02:23:45] gattc_event_handler: event=10 gattc_if=3
[16:40:36][VV][ant_bms_ble:145]: Notification received: 32.C9.AA.55
[16:40:36][I][ant_bms_ble:232]: Status frame (184 bytes):
[16:40:36][D][ant_bms_ble:233]:   7E.A<IP_ADDRESS>.AE.<IP_ADDRESS>E.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.E3.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.E4.0F.<IP_ADDRESS>.16.00.D8.FF.<IP_ADDRESS>.AB.2F.00.00.5B.<IP_ADDRESS>.01.00.00.C0.9B.C0.01.8D.2D.94.01.02.F<IP_ADDRESS>.00.00.00.D1.F7.C<IP_ADDRESS>.00.00.E4.0F.02.00.E3.0F.<IP_ADDRESS>.E3.0F.00.00.6B.00.69.00.
[16:40:36][I][ant_bms_ble:251]:   Permissions: 5
[16:40:36][I][ant_bms_ble:254]:   Battery status: 1
[16:40:36][I][ant_bms_ble:258]:   Number of temperature sensors: 4
[16:40:36][D][sensor:094]: 'ant-bms-ble-monitor battery strings': Sending state 30.00000  with 0 decimals of accuracy
[16:40:36][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 1': Sending state 4.06700 V with 3 decimals of accuracy
[16:40:36][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 2': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:36][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 3': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:36][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 4': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:36][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 5': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:36][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 6': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:36][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 7': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:36][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 8': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:36][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 9': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:36][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 10': Sending state 4.06800 V with 3 decimals of accuracy
[16:40:36][D][sensor:094]: 'ant-bms-ble-monitor cell voltage 11': Sending state 4.06800 V with 3 decimals of accuracy


Improving accessibility with ARIA attributes in templates

Description
This PR aims to enhance accessibility across templates tool. The changes involve the addition of appropriate attributes, such as role attributes and those related to content narration, to improve the user experience for individuals with limited capabilities.
The motivation behind these changes is to create a more inclusive and user-friendly environment within the tool.

@matthiask I'm not sure if attributes would be useful for use in Django. But when debugging site availability in Wagtail, the lack of attributes gets in the way.

@ACK1D it looks like the changes are also causing problems with the test suite. Can you look into getting that to pass? I suspect getting it to pass one environment will resolve it for all of them.

@tim-schilling done.

@sabderemane Feel free to ignore this, but I saw in #1842 that you're (probably/surely) much more knowledgeable in a11y than I am and I would appreciate a review or a few opinions on this.

@sabderemane Feel free to ignore this, but I saw in #1842 that you're (probably/surely) much more knowledgeable in a11y than I am and I would appreciate a review or a few opinions on this.

I will have a look !

I wouldn’t recommend proceeding with those changes as-is. There’s lots of attributes added that wouldn’t do anything, lots where using the more correct HTML elements to start with would be a better fix, and lots where ARIA is used incorrectly.
I think it’d be simpler to assess those fixes if the issues were defined in isolation from one-another, and solutions devised separately, rather than a blanket addition of ARIA attributes.
For example,

Adding role="link" on a a element with a href does nothing. It’s already a link.
Panel button list items can’t be role="checkbox" and have interactive elements inside, nor can a ul have descendants that are  role="checkbox"
<h4 role="heading" aria-level="2"> should just be an h2.

Please have a look at the first rule of ARIA. In particular, use of the role attribute should be a last resort and I can’t imagine it would ever be the right approach except for ARIA roles with no corresponding HTML element (and if so, follow ARIA authoring practices). See ARIA in HTML for a list of HTML elements’ built-in roles.
@ACK1D if you want to spend more time on this I would recommend to start by sharing the results of accessibility testing (#1842), possibly from automated tests. Then report those findings, and fix the issues one by one, making sure to test appropriately. If you want to add ARIA attributes in particular, I would recommend testing with at least one screen reader. See https://github.com/django/django/pull/17338 for recommended accessibility testing steps for Django contributors.

@thibaudcolas Thank you, that's very helpful!

I'm closing this in favor of Thibaud's direction here: https://github.com/jazzband/django-debug-toolbar/pull/1865#issuecomment-1891286544


Enable Linkerd and Calico application layer policies (similar to what is done with Istio)

Expected Behavior

I would like to be able to create application layer policies with Calico using Linkerd as the service mesh, as opposed to Istio.
Current Behavior

Calico application layer policies only integrate with Istio: https://docs.projectcalico.org/security/app-layer-policy
Possible Solution

No suggestions, as I am unfamiliar with how this kind of integration could be implemented.
Context

For some people, Linkerd is a preferable service mesh because:

performance benchmarks: https://linkerd.io/2021/05/27/linkerd-vs-istio-benchmarks/
it is a CNCF graduated project: https://www.cncf.io/announcements/2021/07/28/cloud-native-computing-foundation-announces-linkerd-graduation/

Your Environment (probably not relevant)

Calico version v3.20.0
Orchestrator version (e.g. kubernetes, mesos, rkt): k3s v1.21.2+k3s1
Operating System and version: Centos 7 (kernel 3.10)

Agreed - was just talking about this recently.


fix: handle uncaught HTTP exceptions in PipelineMiddleware

Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[x] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[ ] Testing: Have you written and run sufficient tests for validating the changes?
[x] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[x] Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:

BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry
Description

Fixed the handling of HTTPException in PipelineMiddleware to ensure proper error responses are returned to the user instead of generic 500 server errors.

Fixed

Fixed an issue where HTTPException errors were not properly handled, resulting in generic 500 server error responses to the user instead

Additional Information

Issue was detected when testing out the functionality added in #7041

Thanks!


Provide easy programmatic access to components

Components and columns of known type should be accessible more conveniently, e.g. latitude and longitude of languages.

This raises another question: how do we proceed with evaluation? For the partial cognates and the morphology structure, which we implement in our Burmish data, we need to check if the number of segments are identical across two columns. Do we have a generic way to register format evaluators?

It's not yet fully implemented, but the idea is that ontology URIs can be used to register validators. E.g. you could register a validator for PartialCognatesTable (by adding to pycldf.validators.VALIDATORS), which will then be run on each row in that table.


Tutorial: An extra left arrow key in the instruction of the tutorial

Describe the bug
Tutorial: An extra left arrow key in the instruction of the tutorial
Steps to reproduce the behavior
1.Navigate to https://arcade.makecode.com/beta#
2.Click any tutorials, eg: Chase the Pizza
Actual behavior
Tutorial: An extra left arrow key in the instruction of the tutorial

Additional context
1.OS: Windows(rs6)
2.arcade version: 1.6.5
3.Microsoft MakeCode version: 7.2.8

fixed in beta


Failed to install add-on

Issue related to
Sunsynk / mbusd Home Assistant Add-On
Describe the issue/bug
Following error message when attempting to install add-on:
"The command '/bin/ash -o pipefail -c pip3 install --no-cache-dir --disable-pip-version-check paho-mqtt~=1.5.0 pyyaml~=5.4.1 sunsynk[pymodbus,umodbus]==0.2.5' returned a non-zero code: 1"
Expected behavior
A clear and concise description of what you expected to happen.
Your environment

Home Assistant version: 2022.12.1
Addon version:2022.11.29-0.2.5
Inverter make: Sunsynk
Inverter Model: __
Inverter Firmware: __

Logs
paste logs in 3x backticks...

You can try installing the dev version of the addon, but my first thought would be that you have bad DNS/Internet connectivity
Can you configure static IP&DNS on your HASS/raspberry pi?

Thanks for your response. I've tried the dev version but it throws the same error. I've reconfigured my network with five different DNS servers now and each one also produces the same error. My Home Assistant instance is running in VirtualBox on a Windows 10 machine, if that helps at all. Happy to try changing various parameters at home to test this.

Any feedback?

Hi All,
Not sure how to address my HF2221 Modbus server to Ethernet, - Port, Device & Driver ?  Any suggestions ?

)

The driver is ok, and device is ignored when you have a port

The driver is ok, and device is ignored when you have a port

Perhaps the wiring to the inverter id my problem.  I understand you tried a HF5142B, what was your wiring ?
I've currently
Green/White to T-
Green to T+
Orange/White to GND
Thoughts please

Got it working and so very happy and 3 or 4 days pulling my hair out. Feeling rather proud of myself now :-)
My mistake was the wiring of the CAT 5 cable to the Modbus Server,  it wasn't
Green/White to T-
Green to T+
Orange/White to GND
Ended up being Wires 2 & 7 to A  and  1 & 8 to B.  Modbus Poll imediately :-) 👍

Ideally you should not have to wire both 1&2 AND 7&8, but if this is working for you its probably ok. The are other people on powerforum also doing this

Closing as there is no response from @timclark0000 and his problem is related to the environment rather than the addon