A new installation on RPi 3B+ was performed. Omniot service was registered and is active. BLE packets from Thingy:52 received as expected (gatttool, Bluepy and Bluez, all reports correct reception). Netstat verifies connection with mqtt broker BUT no packets forwarded to mqtt broker. Log and RuleEngine attached below.
What do i miss?
regards
George
---------------------------------------------------
SysLog.log
-------------------------------------------
12/14/19 08:09:23 - System Starting...
12/14/19 08:09:23 - Creating <MqttCommsManager> component.
12/14/19 08:09:23 - Component <MqttCommsManager> created successfully.
12/14/19 08:09:23 - Starting <BleCommsManager> component.
12/14/19 08:09:23 - Component <BleCommsManager> started successfully.
12/14/19 08:09:23 - Starting <HubRuleEngine> component.
12/14/19 08:09:23 - MQT COMMSMGR: INFO, Initiating client connection to remote server at test.mosquitto.org:1883.
12/14/19 08:09:23 - Component <HubRuleEngine> started successfully.
12/14/19 08:09:23 - SYSMON: ****** SYSTEM STARTUP STATUS ******
12/14/19 08:09:23 - SYSMON: BLE Subsystem is READY AND AVAILABLE
12/14/19 08:09:23 - SYSMON: Rule Engine is READY AND AVAILABLE
12/14/19 08:09:23 - SYSMON: DeviceId is 555
12/14/19 08:09:23 - SYSMON: Command listener port IS NOT enabled
12/14/19 08:09:23 - SYSMON: Autostart Sensors IS enabled
12/14/19 08:09:23 - SYSMON: SSL Certificate Validation IS NOT enabled
12/14/19 08:09:23 - SYSMON: Disk Caching IS enabled
12/14/19 08:09:23 - SYSMON: Log Files dir is: "/var/log/omniotshd/"
12/14/19 08:09:23 - SYSMON: Ethernet Cache dir is: "/var/cache/omniotshd/"
12/14/19 08:09:23 - SYSMON: ****** ********************* ******
12/14/19 08:09:23 - BLE COMMSMGR: Ble Sensor Type=Thingy, Id=Any, connection request queued.
12/14/19 08:09:24 - MQT COMMSMGR: INFO, Client connection successfully established to remote server at test.mosquitto.org:1883.
12/14/19 08:10:23 - BLE COMMSMGR: INFO, Connection reset for sensor (Type=Thingy).
12/14/19 08:11:24 - BLE COMMSMGR: INFO, Connection reset for sensor (Type=Thingy).
12/14/19 08:12:24 - BLE COMMSMGR: INFO, Connection reset for sensor (Type=Thingy).
12/14/19 08:13:25 - BLE COMMSMGR: INFO, Connection reset for sensor (Type=Thingy).
12/14/19 08:14:25 - BLE COMMSMGR: INFO, Connection reset for sensor (Type=Thingy).
12/14/19 08:15:25 - BLE COMMSMGR: INFO, Connection reset for sensor (Type=Thingy).
12/14/19 08:16:26 - BLE COMMSMGR: INFO, Connection reset for sensor (Type=Thingy).
12/14/19 08:17:26 - BLE COMMSMGR: INFO, Connection reset for sensor (Type=Thingy).
---------------------------------
RuleEngine.xml
-------------------------------
<?xml version="1.0" encoding="utf-8"?>
<?TargetDevInfo TargetHwId="RPi.Deb.1.0" TargetSwId="OmnIotCore.08.00"?>
<HubConfigurationDirectives>
<HubRuntimeOptions>
<HubDeviceId>555</HubDeviceId>
<HubRmtLoginEnabled>N</HubRmtLoginEnabled>
<NetworkCacheEnabled>Y</NetworkCacheEnabled>
<SSLCertValidation>N</SSLCertValidation>
<AutoStartSensors>Y</AutoStartSensors>
<EnableEmail>N</EnableEmail>
<EmailCacheSize>100</EmailCacheSize>
<PrimaryIpServer>api.ipify.org</PrimaryIpServer>
<SecondaryIpServer>bot.whatismyipaddress.com</SecondaryIpServer>
<MaxBadSvrPkts>10</MaxBadSvrPkts>
<MaxSrvrIdle0>1000</MaxSrvrIdle0>
<MaxSrvrIdle1>300</MaxSrvrIdle1>
<MaxSrvrIdle2>250</MaxSrvrIdle2>
<SysCmdBufSize>1024</SysCmdBufSize>
<SysEventBufSize>2048</SysEventBufSize>
<SysRespBufSize>4096</SysRespBufSize>
<SysLogBufSize>8192</SysLogBufSize>
<ThreadPriAntCommsMgr>60</ThreadPriAntCommsMgr>
<ThreadPriBleCommsMgr>60</ThreadPriBleCommsMgr>
<ThreadPriSysCommandMgr>50</ThreadPriSysCommandMgr>
<ThreadPriEthCommsMgr>50</ThreadPriEthCommsMgr>
<ThreadPriEthListener>60</ThreadPriEthListener>
<ThreadPriGpioDataMgr>75</ThreadPriGpioDataMgr>
<ThreadPriHubMain>50</ThreadPriHubMain>
<ThreadPriHubRuleEngine>60</ThreadPriHubRuleEngine>
<ThreadPriLogFileMgr>35</ThreadPriLogFileMgr>
<ThreadPriEmailCommsMgr>40</ThreadPriEmailCommsMgr>
<ThreadPriSchedEventsMgr>85</ThreadPriSchedEventsMgr>
<HubGpio></HubGpio>
</HubRuntimeOptions>
<HubEngineObjectDescriptors>
<HubSensorStream>
<BleSensorStream Name="bleSensorThingy">
<SensorType>Thingy</SensorType>
<SensorId></SensorId>
<SensorPin></SensorPin>
<SensorConnectEventName></SensorConnectEventName>
<SensorDisconnectEventName></SensorDisconnectEventName>
<NewPacketEventName>00-onNewBlePacket</NewPacketEventName>
<SensorActivationList>
<SelectedSensor>Barometric Pressure hPa</SelectedSensor>
</SensorActivationList>
</BleSensorStream>
</HubSensorStream>
<HubEvent>
<NewSensorPacket Name="00-onNewBlePacket">
<SourceStreamName>bleSensorThingy</SourceStreamName>
</NewSensorPacket>
</HubEvent>
<HubState></HubState>
<HubAction>
<PublishData Name="doPublishT52data">
<SourceStreamName>bleSensorThingy</SourceStreamName>
<MessageFormat>JSON</MessageFormat>
<MessageTopic>omniot/test</MessageTopic>
<DevCtrlTopic></DevCtrlTopic>
<ServerUserName></ServerUserName>
<ServerPassword></ServerPassword>
<ServerClientId></ServerClientId>
<ServerAddress>test.mosquitto.org:1883</ServerAddress>
<TrustedStoreFile></TrustedStoreFile>
<KeyStoreFile></KeyStoreFile>
<ExtOptionsFile></ExtOptionsFile>
</PublishData>
</HubAction>
<HubReport></HubReport>
<HubRule>
<UserRuleSpec Name="00-onNewNtPacket">
<TriggerEvent>00-onNewBlePacket</TriggerEvent>
<TriggeredAction>doPublishT52data</TriggeredAction>
</UserRuleSpec>
</HubRule>
</HubEngineObjectDescriptors>
</HubConfigurationDirectives>
Thingy52 renamed to "Thingy" and voila: Problem SOLVED
for the records, the problem arised because i have two Thingy52 and i was initially renamed the 1st as Thingy1 and the 2nd as Thingy2 :-)). This caused the problem.
Thanks for feedback
Another possibility would be if the sensor was already connected to another device...
Hi, Not sure if you received the emails I sent last night but judging by the log you posted (thanks for that!) the first thing to check would probably be to ensure that the sensor name (the sensor name you see when scanning with a phone for instance) is "Thingy". I saw last night that newer versions of the firmware allow you to change the name. That would explain the messages in the log file (can't find the sensor). Can you check that for me and let me know.? Thanks...