V2 - Raspberry Pi 3B IoT Edge Device doesn't respond on a desired properties update

[HenrikBach1]

Hi @dariuszparys or @varunpuranik,

I have issues with receiving desired properties updates from Azure IoT Hub to my Raspberry Pi 3B running Rasbian Stretch.

I have checked that the issue exists both in the image from microsoft/azureiotedge-simulated-temperature-sensor:1.0-preview and a build from the latest source code from https://github.com/Azure/iot-edge/tree/master/v2/samples/azureiotedge-simulated-temperature-sensor to my repo hebhddauazureiotedgetest1.azurecr.io/azureiotedge-simulated-temperature-sensor-linux-arm:0.2:

"properties": {
    "desired": {
      "SendData": true,
      "SendInterval": 65,
      "$metadata": {
        "$lastUpdated": "2018-05-09T09:23:36.2694807Z",
        "$lastUpdatedVersion": 2,
        "SendData": {
          "$lastUpdated": "2018-05-09T09:23:36.2694807Z",
          "$lastUpdatedVersion": 2
        },
        "SendInterval": {
          "$lastUpdated": "2018-05-09T09:23:36.2694807Z",
          "$lastUpdatedVersion": 2
        }
      },
      "$version": 2
    },

Moreover, the above issue doesn't exists at your "reference" platform (Docker-on-Windows using the linux-x64 cpu architecture). So, in that respect, it seems to be a specific Raspbian (linux-arm) issue.

OS: Raspbian GNU/Linux 9 (stretch) @ Raspberry Pi 3B
Docker: Docker version 18.04.0-ce, build 3d479c0
IoT Edge Ctl: iotedgectl 1.0.0rc22

$ docker ps -a
CONTAINER ID        IMAGE                                                                                          COMMAND                  CREATED             STATUS              PORTS                                          NAMES
5b4c5fdebbc6        hebhddauazureiotedgetest1.azurecr.io/azureiotedge-simulated-temperature-sensor-linux-arm:0.2   "dotnet azureiotedge…"   About an hour ago   Up About an hour                                                   tempSensor-2
b9fd9e0686e8        microsoft/azureiotedge-hub:1.0-preview                                                         "scripts/linux/start…"   3 hours ago         Up 3 hours          0.0.0.0:443->443/tcp, 0.0.0.0:8883->8883/tcp   edgeHub
c29b17426350        microsoft/azureiotedge-agent:1.0-preview                                                       "/usr/bin/dotnet Mic…"   3 hours ago         Up 3 hours                                                         edgeAgent

To read from my repo, use: hebhddauazureiotedgetest1/wNf79YKKRZtEP9jVAIcbWRDu12/jwrNG

Thank you.

/Henrik

[varunpuranik]

Hi Henrik,

Can you provide some more details on what kind of problems you are running into? Are you not getting the Desired properties updated callback at all? Or is there some other problem?
Also, if you run your code (the same module code) on your dev box, does it work?

The reason I ask is because desired property update callbacks are that way not platform specific, so I am trying to understand your scenario and why you might be seeing this.

[HenrikBach1]

Hi @varunpuranik or @dariuszparys ,

I don't get the desired properties updated callback on Raspbian, but only on (Docker-on-)Windows. So, in that sense it works only on one platform and in that sense the Windows box has become my dev box, at the moment.

Moreover, I have also observed, that the updated desired properties eventually reaches the Edge, but it is not pickup up by the desired properties updated callback run-time. This is observed when I delete and re-add the module (given the same module name).

I would like to provide you with more details. However, I don't exactly know, where to look in this case. Can you suggest which logs I should provide you?

Thank you.

/Henrik

[henriksen]

I'm having the same problem, but both on a RPi 2 and on my Windows 10 PC. I've tried running my own code and I've tried running the tempSensor sample module.

Desired properties are picked up if I do an explicit read

var moduleTwin = await ioTHubModuleClient.GetTwinAsync ();
var moduleTwinCollection = moduleTwin.Properties.Desired;

but any callbacks registered are never called.
await ioTHubModuleClient.SetDesiredPropertyUpdateCallbackAsync (OnDesiredPropertiesUpdate, null);

Similarly, a registered method handler is also never called.
await ioTHubModuleClient.SetMethodHandlerAsync ("setState", SetStateMethod, null);

Trying to invoke the direct method just gives me a timeout message:

{"message":"Device {\"Message\":\"{\\\"errorCode\\\":404103,\\\"trackingId\\\":\\\"632f10b976a44866a3d177c28b715f53-G:11-TimeStamp:05/16/2018 13:18:33\\\",\\\"message\\\":\\\"Timed out waiting for device to connect.\\\",\\\"info\\\":{\\\"timeout\\\":\\\"00:00:10\\\"},\\\"timestampUtc\\\":\\\"2018-05-16T13:18:33.894092Z\\\"}\",\"ExceptionMessage\":\"\"} not registered"}

Windows 10

> [System.Environment]::OSVersion.Version
Major  Minor  Build  Revision
-----  -----  -----  --------
6      2      9200   0

> iotedgectl.exe --version
iotedgectl 1.0.0rc22

> docker --version
Docker version 18.05.0-ce-rc1, build 33f00ce

> docker ps -a --format "table {{.ID}}\t{{.Names}}\t{{.Image}}"
CONTAINER ID        NAMES               IMAGE
fb0160795699        edgeHub             microsoft/azureiotedge-hub:1.0-preview
e76421cc4122        tempSensor          microsoft/azureiotedge-simulated-temperature-sensor:1.0-preview
5db2e09676f2        edgeAgent           microsoft/azureiotedge-agent:1.0-preview

Raspberry 2

pi@pidev:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 9.4 (stretch)
Release:        9.4
Codename:       stretch

pi@pidev:~ $ docker --version              
Docker version 18.04.0-ce, build 3d479c0    
pi@pidev:~ $ iotedgectl --version          
iotedgectl 1.0.0rc22

pi@pidev:~ $ docker ps -a                  
CONTAINER ID        IMAGE                                              COMMAND                   NAMES        
501d801428fe        privateacr.azurecr.io/custommodule:0.1.9-arm32v7   "dotnet CustomModule.…"   customModule  
9ba60a2ee487        microsoft/azureiotedge-agent:1.0-preview           "/usr/bin/dotnet Mic…"    edgeAgent    
d692e148cf6d        microsoft/azureiotedge-hub:1.0-preview             "scripts/linux/start…"    edgeHub

Docker base images are microsoft/dotnet:2.0-runtime-stretch and microsoft/dotnet:2.0-runtime-stretch-arm32v7

I've attached log files from the Windows machine with IoTEdgeCtrl log level debug. I see no sign in the logs when trying to update desired properties or invoking a direct method.
edgeAgent.log.txt
edgeHub.log.txt
tempSensor.log.txt

[dariuszparys]

Thanks for the logs I'll have a look later today. /cc @varunpuranik

[henriksen]

Strangest thing, today desired properties updates just decided to work. Update desired updates in the Module Twin and boom, the update triggered on the PI. No change in the Direct Method though...

[henriksen]

Well, turns out I've been doing the wrong thing. Doh! I expected the Direct Method button in the IoT Edge Device page to be able to work with modules, but it doesn't.

Also, I tried with the ServiceClient.InvokeDeviceMethodAsync method but there was no way to specify the module there either. However, if I use the 1.16.0-preview-004 version of Microsoft.Azure.Devices instead of the 1.6 version, there is a new parameter moduleId. That worked.

var response = await serviceClient.InvokeDeviceMethodAsync ("myDevice", "myModule", methodInvocation); works like a charm now. All good!

[dariuszparys]

@HenrikBach1 can you please submit your logs of edgeHub, edgeAgent and the Temperature Sensor you're using?

[HenrikBach1]

Hi @dariuszparys,

All referenced files can found here.

• I upgraded my system (Raspberry Pi 3B/Raspbian 9 (Stretch) to the latest runtimes,
• I re-installed and setup your azure iot edge runtime, etc.,
• I deployed your tempSensor module (deployment.json-1),
• I updated the desired properties in the module (module-twin.json-1) at about 07:56,
• I've attached your requested logs (tempSensor.log-1, edgeAgent.log-1, and edgeHub.log-1).

Thank you.

/Henrik

[dariuszparys]

@HenrikBach1 I just tried to repro the problem. I can't. I can successfully update the module twin properties to the temperature simulator running on my Raspberry PI 3B. The question I have is how do you update the properties? I ran into problems using the portal what I did then was to leverage the Azure CLI IoT Hub extensions to update them.

My command I used was

az iot hub module-twin update --module-id tempSensor --device-id thepi --hub-name codin --set properties.desired='{\"SendInterval\": 7}'

from Powershell. From Bash you need different JSON encoding.

[HenrikBach1]

@dariuszparys ,

I haven't not tried to do a twin-module update from the CLI, yet. I have only done that from the Portal.

If I now change the SendInterval to 30 from Portal, then, if I use your command excluding the --set option:

$ az.cmd iot hub module-twin update --module-id tempSensor --device-id hebh-IoT-Edge-Rpi3B --hub-name hebh-IoT-Hub-Test
{
  "authenticationType": "sas",
  "cloudToDeviceMessageCount": 0,
  "connectionState": "Connected",
  "deviceEtag": "NDUyOTc5MDgw",
  "deviceId": "hebh-IoT-Edge-Rpi3B",
  "etag": "AAAAAAAAAAY=",
  "lastActivityTime": "0001-01-01T00:00:00",
  "moduleId": "tempSensor",
  "properties": {
    "desired": {
      "$metadata": {
        "$lastUpdated": "2018-06-06T07:50:36.6522808Z",
        "$lastUpdatedVersion": 6,
        "SendData": {
          "$lastUpdated": "2018-06-06T07:50:36.6522808Z",
          "$lastUpdatedVersion": 6
        },
        "SendInterval": {
          "$lastUpdated": "2018-06-06T07:50:36.6522808Z",
          "$lastUpdatedVersion": 6
        }
      },
      "$version": 6,
      "SendData": true,
      "SendInterval": 30
    },
    "reported": {
      "$metadata": {
        "$lastUpdated": "0001-01-01T00:00:00Z"
      },
      "$version": 1
    }
  },
  "status": "enabled",
  "statusUpdateTime": "0001-01-01T00:00:00",
  "version": 7,
  "x509Thumbprint": {
    "primaryThumbprint": null,
    "secondaryThumbprint": null
  }
}

But, the tempSensor module doesn't react on that, too...

If I issue:

$ az.cmd iot hub module-twin update --module-id tempSensor --device-id hebh-IoT-Edge-Rpi3B --hub-name hebh-IoT-Hub-Test --set properties.desired='{\"SendInterval\": 7}'
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

hebh@COP382 ~/projects/ddau-azure-iot-edge/logs
$ az.cmd --version
azure-cli (2.0.32)

Is there a way to see, which desired properties my pi has received?...

Thank you.

[HenrikBach1]

Hi @dariuszparys ,

If I move the sd-card to another pi2b, then the result is the same:

$ az.cmd iot hub module-twin update --module-id tempSensor --device-id hebh-IoT-Edge-Rpi3B --hub-name hebh-IoT-Hub-Test
{
  "authenticationType": "sas",
  "cloudToDeviceMessageCount": 0,
  "connectionState": "Connected",
  "deviceEtag": "NDUyOTc5MDgw",
  "deviceId": "hebh-IoT-Edge-Rpi3B",
  "etag": "AAAAAAAAAAc=",
  "lastActivityTime": "0001-01-01T00:00:00",
  "moduleId": "tempSensor",
  "properties": {
    "desired": {
      "$metadata": {
        "$lastUpdated": "2018-06-06T08:16:54.5749582Z",
        "$lastUpdatedVersion": 7,
        "SendData": {
          "$lastUpdated": "2018-06-06T08:16:54.5749582Z",
          "$lastUpdatedVersion": 7
        },
        "SendInterval": {
          "$lastUpdated": "2018-06-06T08:16:54.5749582Z",
          "$lastUpdatedVersion": 7
        }
      },
      "$version": 7,
      "SendData": true,
      "SendInterval": 30
    },
    "reported": {
      "$metadata": {
        "$lastUpdated": "0001-01-01T00:00:00Z"
      },
      "$version": 1
    }
  },
  "status": "enabled",
  "statusUpdateTime": "0001-01-01T00:00:00",
  "version": 8,
  "x509Thumbprint": {
    "primaryThumbprint": null,
    "secondaryThumbprint": null
  }
}

I have added a tempSensor.log-2 to here.

[HenrikBach1]

Hi @dariuszparys ,

PowerShell doesn't seem to work with azure-cli, even though, I've logged in to the portal:

PS C:\Users\hebh> az.cmd iot hub module-twin update --module-id tempSensor --device-id hebh-IoT-Edge-Rpi3B --hub-name he
bh-IoT-Hub-Test --set properties.desired='{\"SendInterval\": 7}'
az iot hub: 'module-twin' is not an az iot hub command. See 'az iot hub --help'.

PS C:\Users\hebh> az.cmd --version
azure-cli (2.0.32)

The Bash I'm using is:

$ bash --version
GNU bash, version 4.4.12(3)-release (x86_64-unknown-cygwin)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

And, as far as I can remember, I've installed the azure-cli with chocolatey:

$ choco upgrade azure-cli -y
Chocolatey v0.10.11
Upgrading the following packages:
azure-cli
By upgrading you accept licenses for the packages.
azure-cli v2.0.32 is the latest version available based on your source(s).

Thank you.

[dariuszparys]

@HenrikBach1 you have to install the iot hub extension prior to using it.

az extension add --name azure-cli-iot-ext

You can read the details here.
https://docs.microsoft.com/en-us/azure/iot-dps/how-to-manage-dps-with-cli

Further the logs you specified are referencing the microsoft/azureiotedge-simulated-temperature-sensor:1.0-preview container. This one doesn't implement the update properties behavior as described here https://github.com/Azure/iot-edge/blob/master/v2/samples/azureiotedge-simulated-temperature-sensor/README.md

[HenrikBach1]

@dariuszparys Ok, then I'll (try to) show that the update properties behavior doesn't do what is expected in the v2/samples tomorrow , because, it was that code I've made module tests from...

I thought that the microsoft/azureiotedge-simulated-temperature-sensor:1.0-preview was made from that code, too.

Thank you.

[HenrikBach1]

Hi @dariuszparys ,

Today, I've updated and build a new version of the tempSensor module from https://github.com/Azure/iot-edge/tree/master/v2/samples/azureiotedge-simulated-temperature-sensor.

I updated the desired properties at 2018-06-07T12:01:59.5952151Z with no effect to its internal values in the module. I waited to about 06/07/2018 12:10:10 before I stopped monitoring the module.

I've updated the logs as requested here.

You can reach my version of the module with these preliminary credentials: hebhddauazureiotedgetest1/wNf79YKKRZtEP9jVAIcbWRDu12/jwrNG.

I'm doing my tests on a Rpi2B device.

Thank you.