{"schema_version":1,"metadata":{"branch":"release","release":"7.9","architecture":"amd64","generated_at":"2026-09-09T04:04:02.361425+00:00","source_url":"https://cdn.openbsd.org/pub/OpenBSD/7.9/packages/amd64/sqlports-7.54.tgz","source_sha256":"2de00144847bf9da3a365be982f101dbb55d591ed7a915ea94984a16ab0e0404","package_count":12059,"source_kind":"sqlports"},"package":{"name":"thingsd-4.0.2p1","path":"net/thingsd","url":"/packages/release/net/thingsd/","comment":"things proxy daemon for OpenBSD","homepage":"https://github.com/basepr1me/thingsd","maintainer":"Tracey Emery <tracey@traceyemery.net>","description":"The thingsd OpenBSD proxy daemon provides a mechanism for clients and client\nprocesses to communicate with an array of serial and IoT things. At its core,\nthingsd is primarily a data aggregator and repeater, in that it waits for\npackets to swap between subscriber clients and things. However, thingsd also\nprovides password control over those connections, including client limits.\n\nOn the client side, thingsd sets up TCP/IP sockets to transmit packets to and\nfrom things. On the server side, thingsd can connect to any serial device which\nhas a viable file descriptor, create a persistent connection to the IP address\nof a device transmitting packets, or setup a UDP listener on the network to\nreceive broadcasted packets. Devices tested include: ESP8266/ESP32 modules, on\nboth the serial and network sides, XBee Series 2 coordinators connected in a\nmesh network, and NF24 devices. To transmit to an IP address, which does not\nallow persistence, thingsd will create an ad hoc connection, transmit a packet,\nand detach. The thingsd proxy daemon is agnostic about packet data.\n","package_architecture":"amd64","stem":"thingsd","readme":null,"dependencies":[],"reverse_dependencies":{"count":0,"url":null},"categories":["net"],"flavors":[],"only_for_architectures":[],"not_for_architectures":[]}}