To get the battery device running I additionally add a normal device which works fine. Logging of sensor is OK, normal device is OK but multidevice not updated all attributes regulary. Sometimes it updates some attributes and very often not. Strange behaviour which I can’t explain.
-
Problem with MySensorsMulti
-
Please can someone help! Another issue, if battery percentage larger than 100 is received it is not left as it is or truncated to 100 but instead it is set to 0. This makes no sense in my mind. The sensor works properly and the battery is full but the icon on the UI indicates empty.
-
@Heizelmann you have to set it to max 100% in the arduino sketch. The plugin sets it to 0% because an arduino that is on low battery can transmit corrupted data like 300% battery or so.
-
Thanks for the quick reply. I understand. Can you also help with the others problem?
-
Can you post the device config? I’ll try to test it and see what happens to find the problem.
-
@sweebee OK I will summarize things up:
I have one node with a DHT22 hum/temp and additonally a Dallas temperature sensor which is battery powered. What I would like tohave on UI is one device for this node and an entry in a battery device and all data on the graph history. On this thread I learned that battery device can only use real devices an not a multi device I came to the following config:{ "id": "MS14-TMP", "name": "MS14-TMP", "class": "MySensorsDST", "nodeid": 14, "batterySensor": true, "sensorid": 2 }, { "id": "MS14-DHT", "name": "MS14-DHT22", "class": "MySensorsDHT", "nodeid": 14, "batterySensor": true, "sensorid": [ 0, 1 ] }, { "id": "MS14", "name": "MS14-Multi", "class": "MySensorsMulti", "attributes": [ { "name": "HumiditySensor", "nodeid": 14, "sensorid": 0, "sensortype": 1, "type": "round", "acronym": "H: ", "unit": "%" }, { "name": "TemperatureSensor", "nodeid": 14, "sensorid": 1, "sensortype": 0, "type": "float", "acronym": "T: ", "unit": "°C" }, { "name": "TemperatureSensor2", "nodeid": 14, "sensorid": 2, "type": "float", "sensortype": 0, "acronym": "T2: ", "unit": "°C" }, { "name": "Battery", "nodeid": 14, "type": "battery", "acronym": "B", "unit": "%" } ] }, { "id": "MS-Battery", "name": "MS-Batterylevel", "class": "MySensorsBattery", "nodeid": [ 11, 12, 13, 14 ] }
Nodes 11,12,13 are other nodes which work well.
Problem is like reported above that MS14-Multi misses randomly points in the graph while logging shows all values received. If I put MS14-DHT and MS14-TMP to the UI they have correct graphs. -
Missing points in graphs depends on the save interval of the database, by default its set to 5m. so every value within this 5m won’t be saved.
-
@sweebee Yes, but the intervals of missing point are much larger and not even for each attribute.
-
OK, I think I have found the problem. MySensorsMulti only emits a value if it is different from the previous one. So it behaves different as other normal sensor classes. I guess this is a bug and should be corrected.
https://github.com/DheerajKhajuria/pimatic-mysensors/issues/76 -
https://github.com/DheerajKhajuria/pimatic-mysensors/issues/76 solved. Many thanks to @sweebee.
-
@sweebee said in Problem with MySensorsMulti:
May I can add an overwrite function for the battery device to set the name manually.
Still open problem: A MySensorsMulti’s name can not be used in MySensorsBattery without a (fake) real device with same name behind it.
https://github.com/DheerajKhajuria/pimatic-mysensors/issues/77