Best posts made by archiijs

Hi, all this is awesome, about the same what I would like to make as I'm heating the house with wood boiler (actually wood gasification boiler to be correct), and accumulation tank. Still working on hot water boiler, but that's not far.

For now, I got working Individually DS18b20 node (still with automatic addressing) and one node that reads the temperature in my boilers second burning chamber with a k-type thermocouple but still struggling to get them bout working with one node.
It would be very helpful for some guidance or example for this.

So my goal is to get 2x thermocouples (additional for smoke temperatures) and some 18b20s in one node + some standard stuff what I am not still sure about.

But for now big thanks to mysensors team and community for this.

@mfalkvidd said in Too frequent updates form DHT:

wait

That was easier than expected, thanks for your advice, seems to do the trick. Will apply this to all my nodes now and test.

Thanks for your fast replays.

Hi, not sure if @Floca get his nodes working, but for me, the problem got fixed with this

#define MY_RF69_IRQ_NUM MY_RF69_IRQ_PIN

as mentioned by @mfalkvidd Thanks!

When I started this was my intent as well. Not exactly 15 but 6-10 for some nodes. It starts to get hard and messy really fast. I was abble to get some basic stuff combined but nothing more. But that's because I am not so good with programming.
So for me I ended up going mostly to esphome and tasmota as almost all my sensors are powered by mains and that matches my knowledge more. But that all depends on your skills mostly.

Hi, well issue resolved and unsurprisingly it was me

So the first I got home and took a look at logs again and saw that node two has rejected connection and indeed, it not responded from any UI and even from the light switch, restart fixed it, but now I wonder if it will happen again.

After that, I used light switches on the third node manualy and they imidietly appeared in HA, but still nothing from DHT sensor. So I took a look at my code and found my error
I got mixed some things around. I got code like this before

#define CHILD_TEMP         2   // Id of sensor dht
#define CHILD_HUM          3   // Id of sensor dht

MyMessage msgHum(CHILD_TEMP, V_HUM);
MyMessage msgTemp(CHILD_HUM, V_TEMP);

So I fixed this like this

#define CHILD_TEMP         2   // Id of sensor dht
#define CHILD_HUM          3   // Id of sensor dht

MyMessage msgHum(CHILD_HUM, V_HUM);
MyMessage msgTemp(CHILD_TEMP, V_TEMP);

After that, all started to work as expected. Thanks for your input.

@mfalkvidd Superb, I will study your suggestions and report back. Thanks again for your patience with me.

Thanks for your help, could not wait and already downloaded portabble verssion on my work pc to test this thing out, seems to work as expected, thanks again for your recomendation.

Hi @mfalkvidd and others.

Yesterday after work I tried to get my head around code suggestions but somehow I cold not make them work so I did some google search and after some time I find something that I implemented in my nodes for testing.
Interestingly it works as expected for two of my nodes, but one still keeps jumping around, not that often, but that's still strange, I will compare code to other two to see what I've done wrong there.
So I used Hysteresis approach by doing this.

#define HYSTERISIS    0.5        // Hysteresis for sensor 

...

  float temperature = dht.getTemperature();
  if (isnan(temperature)) {
    Serial.println("Failed reading temperature from DHT!");
  } else if (abs(temperature - lastTemp ) > HYSTERISIS) {
    // 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);
    }

And the same for humidity.

Still not sure that this will work as expected in long run, but will see.
But now it is way better than before. Thanks.

@maty said in MySensor on Hass.io - can't get it work:

e code isn't mine (made by my friend), I've been using it with Domoticz for almost a year, and it worked perfectly. But recently i decided to give a try to Hass.io, and I really like it. But I still have a problem with lights connected via MySensors (Arduino Mega conected to Rpi via USB), can't get it work with Hass.io. Config part in configuration.yaml look

Hi @MaTy
I have no experience with hass.io, but some comments arise.

1. Your configuration.yaml file path seems to be incorrect. You have to edit this to real path, something like "/user/.homeassistant/mysensors.json" or whatever. The path should exist, file there will be created if it is correct and writeable.
2. You should check if your USB port is really /dev/ttyUSB0 usually command "lsusb" is used, but I'm not sure how to do this in hass.io
3. Also, check if USB port speed is the same as in mysensors gateway and your configuration. 38400 seems different than the standard what usually is 115200 if I'm not mistaken.
   EDIT: Ok, baud seems to match, so that should not be an issue.

@Steve-Hadley said in Idiot newbie question:

f I build a node using another nodemcu

Hi @Steve-Hadley as @gohan said In your case (when using esp8266 based boards) your gateways are the nodes at the same time because they connect to the controller by themselves. Just edit your code to accommodate your sensor and you got easily deployable node anywhere where in your wi-fi coverage zone without additional gateways.

@maty said in MySensor on Hass.io - can't get it work:

/config/mysensor

Default path seems to be generic and not really useful, at the beginning I had problems with understanding this as well. Take a look at the full location where your home assistant configuration files are located, this could be a good location. and add "mysensors.json" at the end (this file will be created and you can name it anything.yson).
like mine is "/root/.homeassistant/mysensors.json"