There can be many reasons why Bluetooth sensors do not report on ModuSense .

1. Sensors are not powered on / battery flat

Bluetooth sensors require batteries to operate and batteries can run out of course. Secondly, some Freewave Bluetooth sensors have an on/off switch and must be powered on to work. Devices like the Brood and Environment Monitors have a switch whereas devices like HiveScales (HM4 and HRF models) and BluTilt sensors auto-power on once batteries are installed.

2. I think they're on. I'm on site. How do I find out?

All Freewave Bluetooth devices will appear in the list on the Freewave App. Once you log in, the app will automatically scan for Freewave Bluetooth devices.

Any MS device that is in the scanning range will appear at the top of the list with an orange question mark.

This can also be achieved using a Bluetooth app like NRF Connect especially if you don't know the login details.

This will show any Bluetooth devices in range and Freewave devices will appear starting with MS-.

3. They're all on but I'm still not seeing anything

Make sure the ModuSense is on and the antennas are screwed into the correct sockets and are finger-tight. 

Any blockages to the sky above will impede the ModuSense 's effectiveness to get a GPS lock and transmit.

4. The ModuSense is transmitting but I'm not getting any Bluetooth devices

If you have measurements like ModuSense battery health, it is possible the Bluetooth functionality on the ModuSense is not working as expected. Please contact support@freewave.com

5. I'm seeing some Bluetooth devices but not all

With the introduction of the V2 Portal, some architectural changes were made to make the portal easier to use and require less configuration.

However, there can be an issue where new BT sensors talking to legacy ModuSense may not appear.

This comes down to the concept of Device Groups. 

In the original V1 portal, ModuSense , and sensors needed to be in a Device Group to show sensor data. In the V2 portal, we've designed the portal so you don't specifically need a Device Group. Now the V2 portal will show any MS-BT device that is communicating via a Fusion Mini.

An issue arises when a customer tries to use new sensors on an older ModuSense . The original Device Group is still configured for that ModuSense which has specific sensors included in it but it doesn't have the new sensor. As a result, the new sensor data will not appear.

The solution is to either add the sensor to the Device Group or remove the Device Group.