Skip to content

Instantly share code, notes, and snippets.

View Ell's full-sized avatar
😝
coding? more like living! haha i love coding so much :)

Ell Ell

😝
coding? more like living! haha i love coding so much :)
View GitHub Profile

BTLE Protocol

Notes

  • All command values end with 0xff
  • All commands use the same handle address of 0x0025
  • Different commands are signified by the first 2 bytes

Keepalive

  • Value: aa:02:ff

Output Amount Control

DescValue

BTLE Protocol

Notes

  • All command values end with 0xff
  • All commands use the same handle address of 0x0025
  • Different commands are signified by the first 2 bytes

Keepalive

  • Value: aa:02:ff

Output Amount Control

DescValue

Device Info

  • BT Address: 20:91:48:2f:f0:4c

BTLE Protocol

Notes

  • All command values end with `ff`
  • All commands use the same handle address of 0x0025
  • Different commands are signified by the first byte

Output Amount Control

Device Info

BT Address

20:91:48:2f:f0:4c

BTLE Protocol

Notes

  • All command values end with `ff`
  • All commands use the same handle address of 0x0025
  • Different commands are signified by the first byte

Output Amount Control

package main
import (
"bytes"
"encoding/binary"
"errors"
log "github.com/Sirupsen/logrus"
"net"
)
FROM golang:alpine
EXPOSE 7070
RUN apk update
RUN apk --no-cache add git
RUN mkdir /app/
COPY ./config.toml /app/
version: '2'
services:
data:
container_name: tracker-redis-data
image: alpine
entrypoint: /bin/true
redis:
container_name: tracker-redis
image: redis:alpine
command: redis-server --appendonly yes
package main
import (
"bytes"
"encoding/binary"
"errors"
log "github.com/Sirupsen/logrus"
"net"
)
Hello!
You've published a series of packages that depend on all packages in the npm registry, probably using this program: https://github.com/Ell/npm-gen-all
We’re not entirely sure what your motivations are for creating this series of packages, but we have some concerns.
First, these packages violate npm's Terms of Use. Much like a squatter package, these have no individual functionality beyond depending on other packages. As a result, we intend to remove them from the registry this afternoon.
It seems that these series of packages might be a response to the events of last week and recent changes to our unpublish policy. A few community members are concerned that series of packages like the ones you’ve created will make unpublishing packages completely impossible after the 24 hour window. This is not the case. These series of packages are not valid package dependents because they violate the npm terms of use. If your goal with these series of packages was to make unpublish impossible, know that it is not
print "hello gist"