Frequently Asked Questions

  1. Which Wi-Fi routers are compatible with Cricket?
    Cricket works with all standard Wi-Fi routers


  2. Does Cricket require any IoT HUB e.g. ZigBee or Z-Wave?
    No, it does not. Cricket works with all standard Wi-Fi routers


  3. What is a distance range / network coverage of Cricket?
    Up to 100 meters


  4. Is there any Cloud service cost?
    No, there is none. Cloud services are OPTIONAL and FREE of charge!


  5. Can Cricket send payloads directly to my service?
    Yes, Cricket is fully configurable to send payloads directly to your services:
    - local network or internet services
    - 3rdparty MQTT brokers
    - Webhooks (HTTP(s) POST / GET) e.g. Blynk, IFTTT, ...


  6. Does Cricket support smart-home integrations i.e. HA, IFTTT, NodeRed, ... ?
    Yes, via HTTP(S) POST / GET or MQTT api


  7. Do I need to program the device?
    No, you do not need! Configuring devices is done over Cricket's local Wi-Fi hotspot or remote micro-service (


  8. How long the device can run on a battery?
    It depends on a use case. Cricket can last many years on a single battery as it supports true 0A. The longevity should be measured by number of events sent.
    Cricket can send ~
    15000 events to the internet on 2x 
    AAA batteries on average.
    For example: a temperature sensor which reports data every 
    1 hour runs 625 days on a single AAA battery


  9. Which batteries can power up Cricket?
    Practically almost any battery i.e.: 3LR12 (4.5-volt), D, C, AA, AAA, AAAA, A23 (12-volt) and PP3 (9-volt)
    below 3.5V can be connected directly
    above 3.5V must be connected via a step-down DC-DC regulator


  10. Can Cricket be powered from a power adaptor?
    Yes, it can


  11. What mobile app can be used?
    There is a huge ecosystem of mobile apps (both FREE and commercial) that users can choose.
    Cricket supports HTTP(s) and MQTT apis  which allow users to integrate their devices to services & apps such as Blynk, IFTTT, Pushsafe, and the like