Error since last update: Error while getting feature

[dwg]

I have the same - appears to be a Samjin sensor - about every min the log has :

10:25:44.8096483 -- (DeCONZCache.UpdateBridgeCache) exit; Update running =False
10:26:12.3615037 -- (WebCommander.HandleWebQueue) Dequeue command: json {"e":"changed","id":"16","r":"sensors","state":{"lastupda ted ":"2021-02-04T18:26:12","temperature":2176},"t":"event","uniqueid":"00: 15:8d:00:04:27:23:4a-01-0402"} new queue size is 0 on 00212E054189
10:26:12.3635039 -- (MySensors.UpdateSensorDevice) UpdateSensors updated Master 2 type ZHATemperature To 71.17
10:26:12.3947039 -- (WebCommander.HandleWebQueue) Dequeue command: json {"e":"changed","id":"17","r":"sensors","state":{"humidity ":2 588,"lastupdated":"2021-02-04T18:26:12"},"t":"event","uniqueid":"00:15:8d:00:04:27:23:4 a-01-0405"} new queue size is 0 on 00212E054189
10:26:12.3947039 -- (MySensors.UpdateSensorDevice) UpdateSensors updated Master 2 type ZHAHumidity To 25.88
10:26:17.9733151 -- (WebCommander.HandleWebQueue) Dequeue command: json {"e":"changed","id":"12","r":"sensors","state":{"alarm":t rue ,"lastupdated":"2021-02-04T18:26:17","lowbattery":false,"tampered":false},"t":"event ","uniqueid":"00:0d:6f:00:05:75:ec:df-01-0500"} new queue size is 0 on 00212E054189
10:26:32.4341439 -- (WebCommander.HandleWebQueue) Dequeue command: json {"e":"changed","id":"19","r":"sensors","state":{"lastupda ted ":"2021-02-04T18:26:32","temperature":2181},"t":"event","uniqueid":"00: 15:8d:00:02:2f:d1:f0-01-0402"} new queue size is 0 on 00212E054189
10:26:32.4341439 -- (MySensors.UpdateSensorDevice) UpdateSensors updated Pilates type ZHATemperature To 71.26
10:26:32.4733444 -- (WebCommander.HandleWebQueue) Dequeue command: json {"e":"changed","id":"20","r":"sensors","state":{"humidity ":2 978,"lastupdated":"2021-02-04T18:26:32"},"t":"event","uniqueid":"00:15:8d:00:02:2f:d1:f 0-01-0405"} new queue size is 1 on 00212E054189
10:26:32.4733444 -- (MySensors.UpdateSensorDevice) UpdateSensors updated Pilates type ZHAHumidity To 29.78
10:26:32.4889445 -- (WebCommander.HandleWebQueue) Dequeue command: json {"e":"changed","id":"21","r":"sensors","state":{"lastupda ted ":"2021-02-04T18:26:32","pressure":825},"t":"event","uniqueid":"00:15:8 d:00:02:2f:d1:f0-01-0403"} new queue size is 0 on 00212E054189
10:26:54.2899047 -- (WebCommander.HandleWebQueue) Dequeue command: json {"e":"changed","id":"3","r":"sensors","state":{"lastupdat ed" :"2021-02-04T18:26:54","temperature":2640},"t":"event","uniqueid":"00: 0d:6f:00:05:75:ec:df-01-0402"} new queue size is 0 on 00212E054189
10:26:54.3149061 -- (MySensors.UpdateSensorDevice) UpdateSensors updated Temperature type ZHATemperature To 79.52
10:27:14.4750592 -- (BridgeApi.SendRequest) sendrequest total took 9
10:27:14.4750592 -- (BridgeApi.GetJsonCommand) Sendrequest took 9 millisconds Thread: 0
10:27:14.5540638 -- (DeviceCreation.CreateNewDevice) starting Sensors
10:27:14.5540638 -- (DeviceCreation.CreateNewDevice) Debug: CreateNewDevice:start creating sensor device for Temperature ID=15
10:27:14.7670759 -- (MySensors.UpdateSensor) Debug: Error: checking sensorconfig battery
System.NullReferenceException(0x80004003): Object reference not set to an instance of an object.
at HSPI_JowiHue.MySensors.UpdateSensor(String id, Sensorstate state, SensorConfig config, String uniqueid)

10:27:14.7670759 -- (MySensors.UpdateSensor)
**************************** Object info *****************************
{
"state": {
"lastupdated": "2021-02-04T17:55:30",
"vibration": false,
"orientation": [
18,
-1014,
12
]
},
"config": {
"on": true,
"battery": 62,
"reachable": true
},
"name": "Temperature",
"type": "ZHAVibration",
"modelid": "multi",
"manufacturername": "Samjin",
"uniqueid": "28:6d:97:00:01:0a:d1:66-01-fc02",
"ep": 1,
"etag": "d42a98dbc235d7639121b0a321a0a539"
}
************************* End Object info ***************************

10:27:14.7680760 -- (MySensors.UpdateSensor)
**************************** Object info *****************************
{
"lastupdated": "2021-02-04T17:55:30",
"vibration": false,
"orientation": [
18,
-1014,
12
]
}
************************* End Object info ***************************

[nunoary]

This means that the problem is even more complicated. I was still convinced that it was only with these vibration sensors.

I hope that Wim can understand what is going on, in my case I completely deleted the devices in the plugin and deconz and now I am re-adding one by one to see how they behave. I already added one of the sensors with problems and after 12h everything is ok. The strange thing is that I had already done this, it was one of my first attempts, and it didn't work ... I don't remember well but the only difference maybe was restarting the deconz after erasing the devices.

Maybe you can first try to delete only the battery feature to see what happens.

[w.vuyk]

Nuno

There is one extra difference here I think? You installed the new plugin version after you started seeing this issue. The new version was still showing the same error, but maybe the remove and recreation of the device has been changed? It might be a difference that counts?

Wim

[nunoary]

Wim,

It's true but I went back to the previous version, because of the error in group 0 that I told you about and that caused the plugin to restart when it commanded a light. So I decided to restore a previous backup with the version 4.0.3.9 and I still haven't updated to the new version 4.0.4... when the tests are finished, which so far are going well with this version 4.0.3.9, I will install the new one and deal with the group 0 error on another tread


By the way, you should edit the version description on the release page. You have Release 4.0.3.9 Februari, 2021 when i think it should be Release 4.0.4 Februari, 2021

[w.vuyk]

Yuch, that is that age thing again updated it

[nunoary]

Yuch, that is that age thing again updated it

Hahaha
I know the feeling, in Portugal we call it P.D.I.

Which means bitch of age or old bitch. In Portuguese it's much more funny, believe me lol...

[nunoary]

Wim,

I think I finished all the tests and the error didn't come back. The solution seems to have been to delete the devices with problems (in my case, vibration sensors) and re-include them.

I am still in version 3.0.3.9 of the plugin and despite having little time to use and this little setback, I have to say that this version seems to have greatly improved the reliability and reliability of my system. The need to change the update to feature battery also helped a lot in the use of the SDJ-Health plugin.

[w.vuyk]

Nuno,

Thanks for the confirmation. I guess this is something that developed in the past and has beeen resolved, as long you let the plugin re-add the device. Great!
Don't worry abot the 4.0.4.0 release, it is good too, but next week I will update again, which will be great for creativity functions in the plugin and some very big mean error we all missed so far