-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Description
In the EDC kit when (following the manual) I create a new rule for turn on a LED on the demo board by pressing a button through MQTT control request, the device rejects the message for "Not valid signature or message not signed."
The rule is:
Statement:
select * from EdcMessageEvent where semanticTopic.startsWith("ModbusManager/devkit") and boolMetric('t4')=true
Action:
MQTT
Topic: $EDC/$account/$asset/ModbusManager/POST/devkit/led/1
Metric: Light | String | True
In kura.log
when I press the button:
2016-06-17 09:08:03,020 [] INFO c.e.f.e.ModbusManager - t4=true
2016-06-17 09:08:03,105 [] INFO c.e.f.e.ModbusManager - One of the metrics changed
2016-06-17 09:08:03,106 [] INFO c.e.f.e.ModbusManager - Publishing on topic: devkit
2016-06-17 09:08:03,115 [] INFO o.e.k.c.d.DataServiceImpl - Storing message on topic :#account-name/#client-id/ModbusManager/devkit, priority: 5
2016-06-17 09:08:03,132 [] INFO o.e.k.c.d.DataServiceImpl - Stored message on topic :#account-name/#client-id/ModbusManager/devkit, priority: 5
2016-06-17 09:08:03,139 [DataServiceImpl:Submit] INFO o.e.k.c.d.t.m.MqttDataTransport - Publishing message on topic: luca-tests/00600C83B323/ModbusManager/devkit with QoS: 0
and then the message from the rule:
2016-06-17 09:08:03,262 [MQTT Call: 00600C83B323] INFO o.e.k.c.c.CloudServiceImpl - Message arrived on topic: $EDC/luca-tests/00600C83B323/ModbusManager/POST/devkit/led/1
2016-06-17 09:08:03,295 [MQTT Call: 00600C83B323] WARN o.e.k.c.c.CloudServiceImpl - Message verification failed! Not valid signature or message not signed.
Metadata
Metadata
Assignees
Labels
No labels