binaryInput: Why does point.lastValue change upon first update?

[carsten-AEI]

Hi,

I am not sure if I can phrase my question correctly, but I just stumbled upon.

I'm querying a industrial control system, the DEBUG output for one point looks like

grep -A5 "'binaryInput' : 235025" ~/.BAC0/BAC0.log
2025-04-02 13:16:15,643 - DEBUG   | 'binaryInput' : 235025
2025-04-02 13:16:15,643 - DEBUG   | ==================================================================================================================
2025-04-02 13:16:15,643 - DEBUG   | propertyIdentifier   propertyArrayIndex   value                          datatype
2025-04-02 13:16:15,643 - DEBUG   | ------------------------------------------------------------------------------------------------------------------
2025-04-02 13:16:15,643 - DEBUG   | 'objectName'         None                 '/02/002/00/00/P.02/CDI/k'     <class 'bacpypes.primitivedata.CharacterString'>
2025-04-02 13:16:15,643 - DEBUG   | 'presentValue'       None                 'active'                       <class 'bacpypes.basetypes.BinaryPV'>
--
2025-04-02 13:16:24,562 - DEBUG   | 'binaryInput' : 235025
2025-04-02 13:16:24,563 - DEBUG   | ==================================================================================================================
2025-04-02 13:16:24,563 - DEBUG   | propertyIdentifier   propertyArrayIndex   value                          datatype
2025-04-02 13:16:24,563 - DEBUG   | ------------------------------------------------------------------------------------------------------------------
2025-04-02 13:16:24,563 - DEBUG   | 'presentValue'       None                 'active'                       <class 'bacpypes.basetypes.BinaryPV'>
2025-04-02 13:16:24,563 - DEBUG   |

but the output (once a second) of print(f"{datetime.now()}: {type(point)} {type(point.lastValue)} '{point.lastValue}' {getattr(point.properties, 'address')}") looks like

2025-04-02 13:16:18.677166: <class 'BAC0.core.devices.Points.BooleanPoint'> <class 'str'> 'active' 235025
2025-04-02 13:16:19.691083: <class 'BAC0.core.devices.Points.BooleanPoint'> <class 'str'> 'active' 235025
2025-04-02 13:16:20.705026: <class 'BAC0.core.devices.Points.BooleanPoint'> <class 'str'> 'active' 235025
2025-04-02 13:16:21.718947: <class 'BAC0.core.devices.Points.BooleanPoint'> <class 'str'> 'active' 235025
2025-04-02 13:16:22.732763: <class 'BAC0.core.devices.Points.BooleanPoint'> <class 'str'> 'active' 235025
2025-04-02 13:16:23.746609: <class 'BAC0.core.devices.Points.BooleanPoint'> <class 'str'> 'active' 235025
2025-04-02 13:16:24.766135: <class 'BAC0.core.devices.Points.BooleanPoint'> <class 'str'> '1: active' 235025
2025-04-02 13:16:25.779996: <class 'BAC0.core.devices.Points.BooleanPoint'> <class 'str'> '1: active' 235025
2025-04-02 13:16:26.793825: <class 'BAC0.core.devices.Points.BooleanPoint'> <class 'str'> '1: active' 235025
2025-04-02 13:16:27.807832: <class 'BAC0.core.devices.Points.BooleanPoint'> <class 'str'> '1: active' 235025

To my surprise, the value changed from the initial active to 1: active upon first update!

My current assumption is that the enumeration value was not known right form the start but this really caught me off-guards and took way too long for me to debug/land at.

Anyone who could shed light on this for me?

Thanks a bunch in advance!

[ChristianTremblay]

Damn, you discovered that I'm not a good programmer :)
This issue dates from a long time and I haven'T figure out a good way to fix it.