OH cool. I guess I have tons more to learn thank you for your help

Editing the json took care of all the junk. I appreciate the help.

Thanks! That fixed everything.

Thanks! That fixed everything.

not sure if this error helps at all.

Logger: mysensors.sensor
Source: /usr/local/lib/python3.8/site-packages/mysensors/sensor.py:96
First occurred: 13 June 2021, 22:41:13 (14 occurrences)
Last logged: 9:54:39

child_id 8 already exists in children of node 0, cannot add child
child_id 2 already exists in children of node 2, cannot add child
child_id 21 already exists in children of node 2, cannot add child
child_id 3 already exists in children of node 2, cannot add child
child_id 4 already exists in children of node 2, cannot add child

I recently wiped and re created my homeassistant and mysensors integration on my raspberry pi 3 before, I used the config integration. With the new build I used the Add-on integration and I am now getting the following error ```
Logger: mysensors
Source: /usr/local/lib/python3.8/site-packages/mysensors/init.py:61
First occurred: 13 June 2021, 22:41:28 (7490 occurrences)
Last logged: 9:33:58

Invalid <Message data="2;255;3;0;32;500">: Not valid message sub-type: 32 for object value @ data['sub_type']. Got 32 not a valid value for object value @ data['payload']. Got '500'
Invalid <Message data="3;255;3;0;33;900000">: Not valid message sub-type: 33 for object value @ data['sub_type']. Got 33 not a valid value for object value @ data['payload']. Got '900000'
Invalid <Message data="3;21;1;0;43;F">: Not valid message sub-type: 43 for object value @ data['sub_type']. Got 43 not a valid value for object value @ data['payload']. Got 'F'
Invalid <Message data="3;17;1;0;43;Lux">: Not valid message sub-type: 43 for object value @ data['sub_type']. Got 43 not a valid value for object value @ data['payload']. Got 'Lux'
Invalid <Message data="3;255;3;0;32;500">: Not valid message sub-type: 32 for object value @ data['sub_type']. Got 32 not a valid value for object value @ data['payload']. Got '500'

I have a rain gauge, temperature and humidity entities that function properly but, my soil moisture, lux and prefix items are failing to be recognised. I assume it is a version issue. I have attempted to use the following in my config file to fix it

mysensors:
  gateways:
    - device: ...
      # other things ...
  version: "2.3"

I attempted to use /dev/ttyACM0 as a device but begin to get a persistence file error that I could not get solved.

any ideas?

OH cool. I guess I have tons more to learn thank you for your help

@gohan it appears as though I need SLC and SDA for the sensor it will prevent me from using a second SLC/SDA device. I was assuming that they were utilizing the analog input. My comment may be deleted as it is clearly not applicable

Where do the pin assignments live?

Editing the json took care of all the junk. I appreciate the help.

Try assigning a node ID. Sometimes controllers will provide an ID but the gateway will not. Currently it is using the ID of 255. I think the line of code to add to the sketch is

#define node_ID #

Where the # at the end is the number of your node. Any value between 1 and 254 should work.

I have previously assigned the node and for testing purposes I don't mind it remaining the same. It was surprising to me that Home Assistant doesn't automatically detect sketch adjustments when the node connects. My next step is to learn how to clean up home assistants records to remove unwanted test data.

I feel smart now, After resetting the home assistant server I noticed that my motion sensor (Previously tested) was assigned to that node on child_id 1 After changing my temperature child_id to 2 The temperature showed up properly.