@lemme I've tried to change back the user interface but without success...
Which version of MySensors do you use? the latest one (2.3)?

Thanks!

Hi,
I've updated my domoticz to this latest stable version. But now all my MySensors (v2.2) light sensors (photo-resistor sending V_LIGHT_LEVEL numbers) are not working.
I can see all of them sending the number in the Setup tab. But on my devices the reported light is nomore updated and only the last value (acquired before the update of Domoticz) is displayed, as in the image attached

It's not related to MySensors (v2.2) for sure because all my problems arose when I've updated to the latest Domoticz (4.9700).
I'm sending messages of V_LIGHT_LEVEL type for my S_LIGHT_LEVEL sensor.
Again, only after the Domoticz upgrade all the S_LIGHT_LEVEL sensors vales are not displayed...

Do you know any reason? I've opened also a trouble ticket on the Domoticz github page (https://github.com/domoticz/domoticz/issues/2687)
Thanks in advance!

ricmail85 created this issue in domoticz/domoticz

closed [MySensors] Data from light sensors not displayed after upgrade to latest stable #2687

Hi,
I've updated my domoticz to this latest stable version. But now all my light sensors (photo-resistor sending V_LIGHT_LEVEL numbers) are not working.
I can see all of them sending the number in the Setup tab. But on my devices the reported light is nomore updated and only the last value (acquired before the update of Domoticz) is displayed, as in the image below.

Do you know any reason?
Thanks in advance!

@mfalkvidd yes I see only integer numbers here and in devices.

@gohan I've declared the variable temperature as float. However after I bit of debugging I found that it seems to be related to the dht lib included in the mysensors examples. If the model is dht11 the library is set for 0 decimals. For the dht22 it would be 1 decimal.

Am I right? Thanks in advance

I've created a DHT11 sensor based on this sketch. However the temperatures (and humidities) are reported as integer numbers in domoticz (either by looking at the devices and setup tabs). In the sketch I've specified the number of decimals like send(msgHum.set(temperatire, 2)). Even if I try larger decimal numbers, nothing change when the value is received in domoticz. What can I do?
Thanks in advance.

@Yveaux Thanks for your reply. I've done a lot of debugging today. And I guess I found the issue.
It's definitely related to the radio power consumption as you suggested.

I'm currently using the new RFM69 driver, with ATC enabled by default. As long as the power level stays below -4 dB, everything works fine. If the gateway is powered off, the radio power level automatically increases to 100% and the PIR behaves weird. It's always HIGH.

By rebooting the gateway, the node relink itself and gradually lowers its power. As before, when it goes below -4dB the PIR starts to work again.

Since it's a battery powered device I decided to set

#define MY_RFM69_MAX_POWER_LEVEL_DBM (-4)

at the beginning of the sketch file. Even if the gateway fails (shutdown) the PIR does not get HIGH anymore. All the measurements work fine now by limiting the max power to the radio.

By doing so all the sleeps of 1000ms after each send are not needed anymore.

@Yveaux This is my configuration

1. Arduino Pro Mini 3.3V
2. RFM69 radio 433MHz
3. Photo-resistor
4. DHT11 temp sensor
5. Battery voltage measurement through voltage partition.
6. The arduino and radio are powered by a 3.3V MCP1700-3302E voltage regulator

yesterday I've noticed the following. If I shutdown the gateway, the sensors fail to reach it and the PIR goes HIGH forever. By rebooting the gateway there is no chance to get it LOW. I have to remove the batteries and everything starts to work again.

@Yveaux Yes I found a partial fix by adding sleep of 1000 ms after each send. And by doing analogread before digitalread. It seems related to power fluctuations. I ve already added some capacitors to the Pir. Shoul I add akso in parallel to the R2 resistance when reading the battery and light level?

Bye!

@Yveaux yes, it seems to work better by sending before the messages performing analogread and then the one using digitalread...

@LastSamurai
Some more debugging and I see the problems arise when I do analogread, so does not seem related to the radio itself.

If I send a message about a dht sensor (digitalread) it is ok. If I send a message of battery/light measure (analogread), the pir gets high...