David Jones
Nb: Don't want to use it inline. Want it as a popup.
Further, its just the Sunday column that isn't opaque. There is a box around Mo to Sa columns. It appears that the Su column doesn't fit in Clear button overhangs...
Drilling into the Arduino Sample I can see that: CbSampleRate() is not called at startup in the Arduino code, although I can see the property set reaches **PnP_ProcessTwinData()** The json...
Current Bridge output: Nb: Some debug messages have been added in PnP_ProcessTwinData() code. ``` Info: -- Press Ctrl+C to stop PnpBridge Info: Using configuration from specified file path: C:\Users\DavidJones\source\repos\ArduinoSerailPnPExample\Config\config.json Info:...
Drilling in further, I can see that the Callback is reached in Bridge code: In **VisitDesiredObject( )** in **pnp_protocol.c** ``` pnpPropertyCallback(NULL, name, value, version, userContextCallback); ``` ... but the function...
In deeper: The correct value is being discerned by the Bridge and passed to the Callback LOC above. Both at start and when a Property update is action by IoT...
The Description request gets to the Arduino device at the start but subsequent property set and conmand packets do not.
_Drilling in deeper to where the Property Update is to be actioned in the Bridge Console app ..._ The following call in **PnpAdapterManager_RoutePropertyCallback( )** in ```pnpadapter_manager.c ``` gets called: ```...
Questions form the previous post are: - is the code ```pnpPropertyCallback(NULL ,``` correct to use NULL or is my determination of the CompnentName correct? - If the former is correct...
### Plugging away at this some more. Re: _processPropertyUpdate()_ **SETTING The Callback Info:** ``` void PnpComponentHandleSetPropertyUpdateCallback (PNPBRIDGE_COMPONENT_HANDLE ComponentHandle, PNPBRIDGE_COMPONENT_PROPERTY_CALLBACK PropertyUpdateCallback) { PPNPADAPTER_COMPONENT_TAG componentContextTag = (PPNPADAPTER_COMPONENT_TAG)ComponentHandle; componentContextTag->processPropertyUpdate = PropertyUpdateCallback; } ```...