frodovdr/node-red-nodes
1
0
Fork 0
mirror of https://github.com/node-red/node-red-nodes.git synced 2023-10-10 13:36:58 +02:00
Code Issues Releases Wiki Activity
083d2841db
node-red-nodes/hardware/physical-web/README.md
Ben Hardill d9fb187cdd Pushing Physical-web node to node-red-nodes 
Hopefully fixing jslint errors

And once more

Getting closer

I think I've finally squashed all the jshint errors
2015-11-23 16:31:30 +00:00

1.5 KiB
Raw Blame History

node-red-node-physical-web

install with

npm install node-red-node-physical-web

Then on Linux follow these instrucations:

https://github.com/sandeepmistry/bleno#running-on-linux

Physical-Web out

A node to allow Node-RED to act as an Eddystone beacon broadcasting URLs

Config

The config window lets you set the inital URL, anouncement power and period for the Eddystone.

Any messages received will update the advertised URL from the msg.payload

Physical-Web in

A node to scan for local Eddystones and output information about discovered URLs and TLM data.

Two types of messages will be emitted:

  • URL -
    • type - Eddystone type
    • txPower - Received power at 0m in dBm
    • url - The URL the beacon is broadcasting
    • tlm - TLM data, if the device is interleaving broadcasts
    • rssi - RSSI of the beacon
    • distance - Estimated distance to the beacon
  • UID -
    • type - Eddystone type
    • txPower - Received power at 0m in dBm
    • namespace - 10-byte ID of namspace
    • instance - 6-byte ID insance
    • tlm - TLM data, if the device is interleaving broadcasts
    • rssi - RSSI of the beacon
    • distance - Estimated distance to the beacon

Where the tlm data will be in the following format

  • tlm -
    • version - TML version
    • vbatt - Battery Voltage
    • temp - Temperature
    • advCnt - Advertising PDU count
    • secCnt - Time since power on or reboot
    • rssi - RSSI of the beacon
    • distance - Estimated distance to the beacon