curVal kind mismatch


#1

We periodically see a curVal kind mismatch.

haystack::FaultErr: curVal kind != configured kind: Bool != Number

As soon as this occurs, the hisCollect will stop working, If I run a haystackSyncCur, it typically resolves its self.

This was previously reported on SkyFoundry’s forum. The belief is that Niagara is serving up the wrong curVal some how.

https://skyfoundry.com/forum/topic/3354


#2

There is a chance that the watch may be encoding some data in a non-predictable order which could be causing some ID’s and values to be swapped. I will send you a patch to test which should account for this scenario.