In other words: Action is required on plugin implementors to check their device implementations. Related to this we’re currently discussing about adding a helper method to populate the attribute value updates in a consistent manner.
-
pimatic-dewpoint device doesn't update?
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Still not solved for mysensors multidevice 😕
-
Her you can see what happens:
Both graphs show the same sensor value. The blue one is from temperature sensor and the black one from MultiSensor. As you can see they the MultiSensor does not show every sample and in my opinion this is wrong. Anyway it is not consistent between the two sensor types.
-
@Heizelmann said in pimatic-dewpoint device doesn't update?:
not consistent between the two sensor types.
Which code-base are you using for pimatic-mysensors, i.e. latest npm or latest master?
I have contributed a couple of code changes to pimatic-mysensors back in June which have been accepted into master, but they have not been relased into a npm package yet, as far as I can see.
I have reviewed the pimatic-mysensors master and the pimatic-dewpoint code. Attribute handling is done as it should, as far as I can see. I my setup the graph lines match.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig Oh, sorry I didn’t see this here. I update the plugins usually via the Web GUI.
So I have to wait for an update. -
@Heizelmann Unfortunately, @Dheeraj has not assigned a co-maintainer and he has not been online in pimatic forum for 6 months. I have created another issue to ask for a new release and co-maintainership.
https://github.com/DheerajKhajuria/pimatic-mysensors/issues/85
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig Thanks. Btw your example is not clear to me. Please compare a basic
sensor and multi sensor including this basic sensor and show what happens when the value stays constant for more sampling intervalls.