Thanks! That fixed everything.
Posts made by Jeff Willecke
-
RE: Switched to the add-on and now some sensors aren't accepted
-
RE: Switched to the add-on and now some sensors aren't accepted
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
-
Switched to the add-on and now some sensors aren't accepted
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:58Invalid <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?
-
RE: 💬 Atmospheric Pressure Sensor
OH cool. I guess I have tons more to learn thank you for your help
-
RE: 💬 Atmospheric Pressure Sensor
@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
-
RE: Multiple Sensors on a single node?
Editing the json took care of all the junk. I appreciate the help.
-
RE: Node dont connect to RaspBerry gateway
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.
-
RE: Multiple Sensors on a single node?
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.
-
RE: Multiple Sensors on a single node?
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.
-
Multiple Sensors on a single node?
I am having a problem getting HA to read multiple sensors from a single node. What am i missing? I am using the sample DHT Code below.
// Enable debug prints #define MY_DEBUG // Enable and select radio type attached #define MY_RADIO_NRF24 //#define MY_RADIO_RFM69 //#define MY_RS485 #include <SPI.h> #include <MySensors.h> #include <DHT.h> // Set this to the pin you connected the DHT's data pin to #define DHT_DATA_PIN 2 // Set this offset if the sensor has a permanent small offset to the real temperatures #define SENSOR_TEMP_OFFSET 0 // Sleep time between sensor updates (in milliseconds) // Must be >1000ms for DHT22 and >2000ms for DHT11 static const uint64_t UPDATE_INTERVAL = 60000; // Force sending an update of the temperature after n sensor reads, so a controller showing the // timestamp of the last update doesn't show something like 3 hours in the unlikely case, that // the value didn't change since; // i.e. the sensor would force sending an update every UPDATE_INTERVAL*FORCE_UPDATE_N_READS [ms] static const uint8_t FORCE_UPDATE_N_READS = 10; #define CHILD_ID_HUM 0 #define CHILD_ID_TEMP 1 float lastTemp; float lastHum; uint8_t nNoUpdatesTemp; uint8_t nNoUpdatesHum; bool metric = true; MyMessage msgHum(CHILD_ID_HUM, V_HUM); MyMessage msgTemp(CHILD_ID_TEMP, V_TEMP); DHT dht; void presentation() { // Send the sketch version information to the gateway sendSketchInfo("TemperatureAndHumidity", "1.1"); // Register all sensors to gw (they will be created as child devices) present(CHILD_ID_TEMP, S_TEMP); present(CHILD_ID_HUM, S_HUM); metric = getControllerConfig().isMetric; } void setup() { dht.setup(DHT_DATA_PIN); // set data pin of DHT sensor if (UPDATE_INTERVAL <= dht.getMinimumSamplingPeriod()) { Serial.println("Warning: UPDATE_INTERVAL is smaller than supported by the sensor!"); } // Sleep for the time of the minimum sampling period to give the sensor time to power up // (otherwise, timeout errors might occure for the first reading) sleep(dht.getMinimumSamplingPeriod()); } void loop() { // Force reading sensor, so it works also after sleep() dht.readSensor(); // Get temperature from DHT library float temperature = dht.getTemperature(); if (isnan(temperature)) { Serial.println("Failed reading temperature from DHT!"); } else if (temperature != lastTemp || nNoUpdatesTemp == FORCE_UPDATE_N_READS) { // Only send temperature if it changed since the last measurement or if we didn't send an update for n times lastTemp = temperature; if (!metric) { temperature = dht.toFahrenheit(temperature); } // Reset no updates counter nNoUpdatesTemp = 0; temperature += SENSOR_TEMP_OFFSET; send(msgTemp.set(temperature, 1)); #ifdef MY_DEBUG Serial.print("T: "); Serial.println(temperature); #endif } else { // Increase no update counter if the temperature stayed the same nNoUpdatesTemp++; } // Get humidity from DHT library float humidity = dht.getHumidity(); if (isnan(humidity)) { Serial.println("Failed reading humidity from DHT"); } else if (humidity != lastHum || nNoUpdatesHum == FORCE_UPDATE_N_READS) { // Only send humidity if it changed since the last measurement or if we didn't send an update for n times lastHum = humidity; // Reset no updates counter nNoUpdatesHum = 0; send(msgHum.set(humidity, 1)); #ifdef MY_DEBUG Serial.print("H: "); Serial.println(humidity); #endif } else { // Increase no update counter if the humidity stayed the same nNoUpdatesHum++; } // Sleep for a while to save energy sleep(UPDATE_INTERVAL```