npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@0x77/iqos.parser

v0.0.11

Published

A parser library for holder charge status.

Downloads

5

Readme

iQOS.parser

A parser library for holder charge status parsing.

Tested on iQOS 2.4+ and Chrome 76

iQOS commmunity npm GitHub code size in bytes GitHub issues Edit iQOS.parser demo

Q&A

TODO

  • Add charger support
  • Test on iQOS 3.0
  • Write connection library
  • etc... (P.S.: purpose your features on issues)

Where I can ask the question or bug report?

What is this?

  • This library contains simple function that parse the iQOS holder charge status

How to know that holder is not inside charger?

  • It will return -1

What i need to test it out?

  • Chrome that supports BLE.
  • Bluetooth-enabled iQOS (not tested on iQOS 3)
  • A simple code for access ble and display the status:
import HolderChargeEventHandler from '@0x77/iqos.parser';
let optionalServices = ["daebb240-b041-11e4-9e45-0002a5d5c51b"];
//f8a54120-b041-11e4-9be7-0002a5d5c51b battery status characteristic

console.log('Requesting any Bluetooth Device...');
navigator.bluetooth.requestDevice({
    acceptAllDevices: true,
    optionalServices: optionalServices
})
    .then(device => {
        console.log('Connecting to GATT Server...');
        return device.gatt.connect();
    })
    .then(server => {
        console.log('Getting Services...');
        return server.getPrimaryServices();
    })
    .then(services => {
        console.log('Getting Characteristics...');
        let queue = Promise.resolve();
        services.forEach(service => {
            queue = queue.then(_ => service.getCharacteristics().then(characteristics => {
                console.log('> Service: ' + service.uuid);
                characteristics.forEach(characteristic => {
                    // log('> C: ', characteristic.uuid.uuid);
                    console.log(characteristic.uuid);
                    if (characteristic.uuid == "f8a54120-b041-11e4-9be7-0002a5d5c51b") {
                        console.log("characteristic of battery found");
                        characteristic.startNotifications().then(characteristic => {
                            characteristic.addEventListener(
                                'characteristicvaluechanged', handleCharacteristicValueChanged
                            );

                        })
                            .catch(error => { console.log(error); });

                    }
                    console.log("Reinsert holder to begin...");
                });
            }));
        });
        return queue;
    })
    .catch(error => {
        console.log('Argh! ' + error);
    });

const handleCharacteristicValueChanged = (event) => {
    console.log(HolderChargeEventHandler(event));
}