Tube_gateways - Information and Documentation on Tube's Zigbee Gateways

Overview

Tube's Zigbee Gateways

Information and documentation on Tube's Zigbee Gateways. Pre-assembed hardware devices can be purchased from https://www.tubeszb.com

Tube's Zigbee Gateways are serial over Ethernet zigbee gateways for use with any project that can access and interface with a remote Serial to IP bridge/proxy server device.

This can today be used by home automation applications such as example; Home Assistant (ZHA integration) and Zigbee2MQTT.

The gateway hardware itself is made up of a WT32-ETH01 module which is an ESP32 with Ethernet in combination with either a Texas Instruments CC2652P or a Silicon Labs EFR32 based Zigbee module.

Getting up and Running

For EFR32 Gateways see specific insturctions for config file https://github.com/tube0013/tube_gateways/tree/main/tube_zb_gw_efr32

Auto Discovery for EFR32 Gatways is currently broken in HA, Please ignore the discovered device and set up manually

  1. Connect the gateway to a ethernet cable which has access you your local network.

  2. Power on the gateway with a micro usb cable and power supply. The link lights on the ethernet port will start blinking as it tries to negotiate a connection with your home network router.

  3. Determine the device's ip address If your local network supports .local mdns addresses, the devices can be reached that way:

    -for CC2652p based microUSB powered coordinators: tube_zb_gw_cc2652p2.local

    -for CC2652p based PoE coordinators: tube_zb_gw_cc2652p2_poe.local

    -for EFR32 based coordinators: tube_zb_gw_efr32.local

    Using a Reserved or static IP Address is strongly advised. Reserve the address in the router or use a static ESPHome build with static ip

  4. Configure your software to access the device.

    For HomeAssistant's Built in ZHA implementation:

    Add the ZHA Integration via the Add Integrations option:

    In the next window use the dropdown to select Manual:

    Select the Radio type:

    For CC2652p based gateways select ZNP
    For EFR32 based gateways select EZSP

    For the Specifying the Port Specific Settings: Enter socket://ip_or_localdns_name:6638 and Port Speed of 115200 and Software Flow Control.

    CC2652p Based example:

    EFR32 Based example:

    For Zigbee2mqtt - Only the CC2652p based gateway is supported at this time:

    in the Zigbee2MQTT configuration.yaml

    serial:
      port: 'tcp://tube_zb_gw_cc2652p2.local:6638'
    
    

    No need to pass any devices through to Zigbee2MQTT docker container setups. Also the docker containers for Zigbee2MQTT do not seem to work well with mdns, so best to use the ip address of the coordinator here:

    serial:
      port: 'tcp://IPADDRESS:6638'
    
    

ESPHome

The ESP32 in the gateway runs ESPHome. Configured in ESPHome are switches in order to prep the zigbee modules for firmware updates if needed. It is Highly Advised to Ignore these entities in HomeAssistant as accidential toggling could rest the zigbee modules.

To access the ESPHome Web Interface on the gateway connect to it in your Browser:

CC2652p based gateways: http://tube_zb_gw_cc2652p2.local EFR32 based gateways: http://tube_zb_gw_efr32.local

Zigbee Module Firmware Updates:

CC2652p based Gateways:
Firmware - use the CC1352P2_CC2652P_launchpad_*.zip based firmware available here:
https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/Z-Stack_3.x.0/bin

Be Sure to backup your device before updgrading as the update will erase the zigbee module completely https://github.com/zigpy/zigpy-znp/blob/dev/TOOLS.md#backup-and-restore

Use the cc2538-bsl programmer available here: https://github.com/JelmerT/cc2538-bsl

  1. Prep the Module for firmware update:

Click the button to intiate the bootloader mode for the module:

Watch the Debug output and when pompted go to step 2.

  1. Run the cc2538-bsl programmer:
cc2538-bsl.py -p socket://tube_zb_gw_cc2652p2.local:6638  -evw ../CC1352P2_CC2652P_launchpad_20210120.hex
Opening port socket://tube_zb_gw_cc2652p2.local:6638, baud 500000
Reading data from ../CC1352P2_CC2652P_launchpad_20210120.hex
Your firmware looks like an Intel Hex file
Connecting to target...
CC1350 PG2.0 (7x7mm): 352KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x00057FD8
Primary IEEE Address: 00:12:4B:00:21:B4:97:D8
    Performing mass erase
Erasing all main bank flash sectors
    Erase done
Writing 360448 bytes starting at address 0x00000000
Write 104 bytes at 0x00057F980
    Write done
Verifying by comparing CRC32 calculations.
    Verified (match: 0xdb4192ef)

EFR32 based Gateways

https://www.youtube.com/watch?v=zKrISuWEzL4tube-

Issues
  • Updated ESPHome on my tube-zb-gw-cc2652p2-v2 and now it doesn't work :)

    Updated ESPHome on my tube-zb-gw-cc2652p2-v2 and now it doesn't work :)

    I did exactly the same as:

    So I think I messed up my coordinator, but not really sure how. It is the tube-zb-gw-cc2652p2-v2 model :)

    I updated ESPHome to the tube-zb-gw-cc2652p2-v2_2022_01_15.bin that was posted on GitHub, that worked fine, but then I could not connect to the serial port on 6638. I rolled it back to tube-zb-gw-cc2652p2-v2_2021_09_17.bin which was what I wasn on previously, but it still did not work. I attempted to flash new zstack code onto it, but that just fails - I was able to update it to this version of zstack a few days ago without problems.

    But I am unable to get the device into boot mode.

    I have the jumpers in this postion

    image

    I hold down boot, plug in the device, but my windows PC does not see it.

    Any suggestions?

    opened by hvddrift 37
  • Unable to update or connect to zigbee2mqtt with cc2652p2_poe.

    Unable to update or connect to zigbee2mqtt with cc2652p2_poe.

    Trying to get the cc2652p2_poe working, however I keep getting this error in zigbee2mqtt:

    Zigbee2MQTT:error 2021-11-01 17:39:16: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
        at ZStackAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:102:27)
        at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:123:29)
        at Zigbee.start (/app/lib/zigbee.ts:63:27)
        at Controller.start (/app/lib/controller.js:116:27)
        at start (/app/index.js:95:5)
    

    So I decided to install firmware to see if this resolves the issue. However when I click Prep the cc2652p2 for firmware update nothing happens in the debug log. This is after waiting 2 minutes: image Switching browsers or incognito also doesnt work. The only button that seems to do something is restart, which it then does.

    Anything I can do to resolve this?

    opened by Eagleman7 34
  • Trying to update firmware OTA but getting Update Failed: Wrong Magic Byte

    Trying to update firmware OTA but getting Update Failed: Wrong Magic Byte

    I have the Tubes ZB CC2652P2 ethernet cordinator and im trying to update it OTA but im getting 'Update Failed: Wrong Magic Byte'

    I got the firmware from here: https://github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_coordinator_20220219.zip

    image

    opened by Ming-A 25
  • PoE Coordinator unresponsive

    PoE Coordinator unresponsive

    Hi there! I bought one of your PoE Zigbee Coordinators recently (Order No. 729000642), and I'm (somewhat belatedly) trying to get it up and running.

    I'm a fairly competent Linux admin, but completely new to Zigbee and home automation, so it's entirely possible I'm missing something really basic here, but I can't seem to get past step 0 with this device. I don't have mDNS, but I have dnsmasq all set up on my router and I'm very familiar with setting up static DHCP leases. I was expecting the coordinator to request a DHCP lease from the router as soon as it was plugged in to PoE, so I could grab the MAC address from the router's logs and give it a static entry in my dhcp-hosts file just like any other client on the LAN.

    What's actually happening is nothing. I've tried connecting it directly to an Ethernet port on my Edgerouter and turning on PoE to that port, and I see the PoE indicator light come on, but the link indicator just stays dark. I've also tried connecting it to an Ethernet switch elsewhere in the house via a PoE injector, with similar results: the PoE injector's power LED comes on, but the link indicator LED on the switch stays dark. In the name of thoroughness, I've tried three different Ethernet cables. Looking at the logs for dnsmasq, no activity at all shows up when I plug in the co-ordinator. I've tried leaving it plugged in for ~30 minutes and nothing changes.

    Is there something I'm missing, or some obvious troubleshooting I should try? For reference, I have near zero expertise on the hardware side of things.

    opened by scruloose 21
  • Not able to connect to zigbee2mqtt with cc2652p2_poe

    Not able to connect to zigbee2mqtt with cc2652p2_poe

    the zigbee2mqtt keep running in circle

    [19:02:06] INFO: Socat not enabled, marking service as down [19:02:06] INFO: MQTT available, fetching server detail ... [19:02:06] INFO: MQTT server settings not configured, trying to auto-discovering ... [19:02:07] INFO: Configuring 'mqtt://core-mosquitto:1883' mqtt server [19:02:07] INFO: Previous config file found, checking backup [19:02:07] INFO: Creating backup config in '/config/zigbee2mqtt/.configuration.yaml.bk' [19:02:07] INFO: Adjusting Zigbee2mqtt core yaml config with add-on quirks ... [19:02:07] INFO: Handing over control to Zigbee2mqtt Core ... [19:03:16] INFO: Handing over control to Zigbee2mqtt Core ...

    I get the "502: Bad Gateway" on the UI

    i have got the zigbee2mqtt running with a Conbee before this so the plugin is working.

    i have followed the instructions and use tcp://xxx.xxx.xxx.xxx:6638 ip address instead of mDNS

    after a while the log is updated with this:

    [19:04:24] INFO: Handing over control to Zigbee2mqtt Core ... Zigbee2MQTT:error 2021-10-01 19:05:33: Error while starting zigbee-herdsman Zigbee2MQTT:error 2021-10-01 19:05:33: Failed to start zigbee Zigbee2MQTT:error 2021-10-01 19:05:33: Check https://www.zigbee2mqtt.io/information/FAQ.html#help-zigbee2mqtt-fails-to-start for possible solutions Zigbee2MQTT:error 2021-10-01 19:05:33: Exiting... Zigbee2MQTT:error 2021-10-01 19:05:33: Error: network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby at ZnpAdapterManager.beginCommissioning (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:347:23) at ZnpAdapterManager.start (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:92:17) at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:123:29) at Zigbee.start (/app/lib/zigbee.js:66:27) at Controller.start (/app/lib/controller.js:110:27) at start (/app/index.js:95:5) [19:05:34] INFO: Handing over control to Zigbee2mqtt Core ... [email protected] start node index.js [19:06:42] INFO: Handing over control to Zigbee2mqtt Core ...

    opened by koburg 19
  • Connect to Philips Hue Bulb

    Connect to Philips Hue Bulb

    Just wondering how can I link my old philips hue bulb to my new cc2652p2. I cant seems to find the bulbs on HA scan ZHA. I cant also find a way to make the bulb go into discovery mode. Anyone have any idea?

    opened by ranrinc 16
  • CC2652p2 POE Coordinator ZHA connection issue

    CC2652p2 POE Coordinator ZHA connection issue

    Hi,

    I just purchased a CC2652P2 Based Zigbee to Power Over Ethernet Serial Coordinator V2 to replace a ConBeeII for my Profalux covers.

    I deleted all zigbee devices via zha.remove and the ZHA integration itself. I then re set the ZHA integration according to the instructions (ZNP, socket://ip:6638, 115200, software flow control) and joined my devices to this new gateway.

    All went fine except I'm having connection issues between my HA Virtual Machine (hypervised by VMM on a Synology RS1221+) & the gateway, resulting il osme lines in the Debug Log but more embarassing : my covers are slightly moving up and down on each reconnection as I guess the gateway enter permit join after a connection?

    Gateway Log Capture d’écran 2021-09-04 100453

    HA Log Capture d’écran 2021-09-04 100722

    The coordinator is powered by a Unifi 8 POE switch and is set on the same VLAN as HA (so firewall shouldn't be cocnerned). I forced the switch port to 100mbits FDX as recommended but this didn't helped.

    • Can you confirm that the coordinator should permit join after a connection (is it on the coordinator or ZHA side?), and why?
    • Is it possible to disable it?
    • Do you have any suggestion to improve the connection stability?

    Disconnections happens variably from every minute to every half hour. This is quite annoying and can't stay as it. Any help is very welcome! :) Thanks!

    opened by glamirand 14
  • Lower LQI Performance

    Lower LQI Performance

    Using one of the POE coordinators and finding significantly lower LQI results when using this over my previous Sonoff ZHA bridge

    For example with both devices next to each other, the poe coordinator on channel 11 (which I moved from 15 to test if it would improve, it made no change), and the Sonoff on 15

    Sonoff Device info TS0014 by _TYZB01_bagt1e4o Zigbee Coordinator Zigbee info IEEE: 5c:02:72:ff:fe:cf:53:e0 Nwk: 0x579f Device Type: EndDevice LQI: 188 RSSI: -53 Last Seen: 2021-10-02T20:29:53 Power Source: Battery or Unknown

    Tubesz Device info TS0014 by _TYZB01_bagt1e4o Zigbee Coordinator Zigbee info IEEE: 5c:02:72:ff:fe:cf:53:e0 Nwk: 0x101c Device Type: EndDevice LQI: 81 RSSI: Unknown Last Seen: 2021-10-02T20:32:43 Power Source: Battery or Unknown

    Seems really odd, I am also seeing a lot of strange issues recently with this device with the latest ZStack firmware, going to downgrade shortly and see if this resolves it, but since updating the switch doesn't even work at all on the tubesz coordinator.

    Has anyone else come across this?

    opened by claymen 13
  • Setting up zha integration in home assistant fails

    Setting up zha integration in home assistant fails

    I recently received the CC2652P2 based Zigbee to Ethernet/USB Serial Coordinator.

    Whenever the zha integration in homeassistant tries to load (after the integration successfully connects which is a bit sporadic), I get the following error:

    Error setting up entry socket://192.168.0.172:6638 for zha
    Traceback (most recent call last):
      File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 888, in request_callback_rsp
        return await callback_rsp
    asyncio.exceptions.CancelledError
    
    During handling of the above exception, another exception occurred:
    
    Traceback (most recent call last):
      File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 282, in write_network_info
        commissioning_rsp = await self.request_callback_rsp(
      File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 888, in request_callback_rsp
        return await callback_rsp
      File "/usr/local/lib/python3.9/site-packages/async_timeout/__init__.py", line 129, in __aexit__
        self._do_exit(exc_type)
      File "/usr/local/lib/python3.9/site-packages/async_timeout/__init__.py", line 212, in _do_exit
        raise asyncio.TimeoutError
    asyncio.exceptions.TimeoutError
    
    The above exception was the direct cause of the following exception:
    
    Traceback (most recent call last):
      File "/usr/src/homeassistant/homeassistant/config_entries.py", line 339, in async_setup
        result = await component.async_setup_entry(hass, self)
      File "/usr/src/homeassistant/homeassistant/components/zha/__init__.py", line 102, in async_setup_entry
        await zha_gateway.async_initialize()
      File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 173, in async_initialize
        self.application_controller = await app_controller_cls.new(
      File "/usr/local/lib/python3.9/site-packages/zigpy/application.py", line 69, in new
        await app.startup(auto_form)
      File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 152, in startup
        return await self._startup(
      File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 207, in _startup
        await self.form_network()
      File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 393, in form_network
        await self.write_network_info(network_info=network_info, node_info=node_info)
      File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 1149, in write_network_info
        return await self._znp.write_network_info(
      File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 311, in write_network_info
        raise RuntimeError(
    RuntimeError: Network formation refused, RF environment is likely too noisy. Temporarily unscrew the antenna or shield the coordinator with metal until a network is formed.
    
    

    I tried looking up this error in the home assistant community forums and elsewhere but the proposed solutions do not work.

    Things I have tried:

    1. removing the zha integration, deleting zigbee.db, restarting home assistant
    2. removing the antenna temporarily and trying to re-setup
    3. with the antenna removed covering the controller with cast iron and cast steel pans
    4. rebooting the controller

    Any advice on how I can get this integration to successfully be set up?

    opened by drewthor 11
  • Issue setting up a new EFR32 coordinator with HASS

    Issue setting up a new EFR32 coordinator with HASS

    I am running my new EFR32 coordinator via serial/USB and so have put the jumpers in the middle per the GitHub instructions. However, the instructions here seem to focus on Ethernet, and I am having issues with USB.

    Here is what I am doing:

    1. I go into integrations and add ZHA and Hass sees a device at /dev/ttyAMA0.
    2. I choose that and EZSP radio type.
    3. This brings me to the screen where it shows the path, asks for port speed and data flow. The default port speed is 57200 and I choose 115200 per GitHub. Once, I click “Submit”, I get “failed to connect.”
    4. I have tried playing with data control and port speed and always seem to get failed to connect.

    Any advice on what I should do?

    Oh and I added those lines to configuration.yaml. TIA for any ideas!

    opened by jl-678 10
  • compile failed in latest esphome

    compile failed in latest esphome

    while doing some house keeping i saw that esphome was updated in my home assistant and tried to update my poe board. however it failed to compile.

    i am on currently 2021.9.2, all working fine, was trying to compile 2021.11.1.

    INFO Reading configuration /config/esphome/tube_zb_gw_cc2652p2_olimex_POE.yaml...
    WARNING 'tube_zb_gw_cc2652p2_poe': Using the '_' (underscore) character in the hostname is discouraged as it can cause problems with some DHCP and local name services. For more information, see https://esphome.io/guides/faq.html#why-shouldn-t-i-use-underscores-in-my-device-name
    INFO Generating C++ source...
    INFO Compiling app...
    Processing tube_zb_gw_cc2652p2_poe (board: esp-wrover-kit; framework: arduino; platform: platformio/espressif32 @ 3.3.2)
    --------------------------------------------------------------------------------
    HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
    Dependency Graph
    |-- <AsyncTCP-esphome> 1.2.2
    |-- <WiFi> 1.0
    |-- <FS> 1.0
    |-- <Update> 1.0
    |-- <ESPAsyncWebServer-esphome> 2.1.0
    |   |-- <AsyncTCP-esphome> 1.2.2
    |-- <ArduinoJson-esphomelib> 5.13.3
    |-- <ESPmDNS> 1.0
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/api/api_connection.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/api/api_frame_helper.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/api/api_pb2.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/api/api_pb2_service.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/api/api_server.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/api/list_entities.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/api/proto.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/api/subscribe_state.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/api/user_services.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/api/util.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/esp32/core.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/esp32/gpio_arduino.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/esp32/gpio_idf.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/esp32/preferences.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/ethernet/ethernet_component.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/gpio/switch/gpio_switch.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/json/json_util.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/logger/logger.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/md5/md5.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/mdns/mdns_component.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/mdns/mdns_esp32_arduino.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/mdns/mdns_esp8266.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/mdns/mdns_esp_idf.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/network/util.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/ota/ota_backend_arduino_esp32.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/ota/ota_backend_arduino_esp8266.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/ota/ota_backend_esp_idf.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/ota/ota_component.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/restart/restart_switch.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/script/script.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/socket/bsd_sockets_impl.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/socket/lwip_raw_tcp_impl.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/switch/automation.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/switch/switch.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/template/switch/template_switch.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/uart/uart.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/uart/uart_component.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/uart/uart_component_esp32_arduino.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/uart/uart_component_esp8266.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/uart/uart_component_esp_idf.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/uart/uart_debugger.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/web_server/web_server.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/components/web_server_base/web_server_base.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/core/application.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/core/color.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/core/component.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/core/controller.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/core/entity_base.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/core/helpers.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/core/log.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/core/scheduler.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/esphome/core/util.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/main.cpp.o
    Compiling /data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/stream_server.cpp.o
    src/stream_server.cpp: In member function 'void StreamServerComponent::read()':
    src/stream_server.cpp:59:65: error: 'min' was not declared in this scope
             size_t read = this->stream_->readBytes(buf, min(len, 128));
                                                                     ^
    src/stream_server.cpp:59:65: note: suggested alternative:
    In file included from /data/cache/platformio/packages/toolchain-xtensa32/xtensa-esp32-elf/include/c++/5.2.0/algorithm:62:0,
                     from src/esphome/core/optional.h:19,
                     from src/esphome/core/component.h:7,
                     from src/stream_server.h:19,
                     from src/stream_server.cpp:17:
    /data/cache/platformio/packages/toolchain-xtensa32/xtensa-esp32-elf/include/c++/5.2.0/bits/stl_algo.h:3451:5: note:   'std::min'
         min(initializer_list<_Tp> __l, _Compare __comp)
         ^
    In file included from src/stream_server.cpp:19:0:
    src/stream_server.cpp: In member function 'virtual void StreamServerComponent::dump_config()':
    src/stream_server.cpp:75:64: error: 'network_get_address' was not declared in this scope
         ESP_LOGCONFIG(TAG, "  Address: %s:%u", network_get_address().c_str(), this->port_);
                                                                    ^
    src/esphome/core/log.h:97:90: note: in definition of macro 'esph_log_config'
       esp_log_printf_(ESPHOME_LOG_LEVEL_CONFIG, tag, __LINE__, ESPHOME_LOG_FORMAT(format), ##__VA_ARGS__)
                                                                                              ^
    src/stream_server.cpp:75:5: note: in expansion of macro 'ESP_LOGCONFIG'
         ESP_LOGCONFIG(TAG, "  Address: %s:%u", network_get_address().c_str(), this->port_);
         ^
    *** [/data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/stream_server.cpp.o] Error 1
    /config/esphome/tube_zb_gw_cc2652p2_olimex_POE.yaml: In lambda function:
    /config/esphome/tube_zb_gw_cc2652p2_olimex_POE.yaml:86:62: error: no matching function for call to 'StreamServerComponent::StreamServerComponent(esphome::uart::ESP32ArduinoUARTComponent*&)'
           auto stream_server = new StreamServerComponent(id(uart_bus));
                                                                  ^
    In file included from src/main.cpp:56:0:
    src/stream_server.h:35:14: note: candidate: StreamServerComponent::StreamServerComponent(Stream*)
         explicit StreamServerComponent(Stream *stream) : stream_{stream} {}
                  ^
    src/stream_server.h:35:14: note:   no known conversion for argument 1 from 'esphome::uart::ESP32ArduinoUARTComponent*' to 'Stream*'
    src/stream_server.h:33:7: note: candidate: StreamServerComponent::StreamServerComponent(const StreamServerComponent&)
     class StreamServerComponent : public esphome::Component {
           ^
    src/stream_server.h:33:7: note:   no known conversion for argument 1 from 'esphome::uart::ESP32ArduinoUARTComponent*' to 'const StreamServerComponent&'
    src/stream_server.h:33:7: note: candidate: StreamServerComponent::StreamServerComponent(StreamServerComponent&&)
    src/stream_server.h:33:7: note:   no known conversion for argument 1 from 'esphome::uart::ESP32ArduinoUARTComponent*' to 'StreamServerComponent&&'
    /config/esphome/tube_zb_gw_cc2652p2_olimex_POE.yaml:87:28: error: could not convert '{stream_server}' from '<brace-enclosed initializer list>' to 'std::vector<esphome::Component*>'
           return {stream_server};
                                ^
    *** [/data/tube_zb_gw_cc2652p2_poe/.pioenvs/tube_zb_gw_cc2652p2_poe/src/main.cpp.o] Error 1
    ========================= [FAILED] Took 29.45 seconds =========================
    
    
    opened by tmottabr 8
  • Converting Zigbee to IP

    Converting Zigbee to IP

    Not related to anything necessarily here, but maybe something that can be built by Tube? I have a need for connecting Zigbee devices to a remote site through a VPN (Wireguard/OpenVPN), while keeping only one coordinator locally. My thought is a zibee transceiver which converts and carries zigbee signals over TCP/IP, then once it transcends to the other side, it's converted back to zigbee radio waves. Has something like this been done, or can it even be done for that matter?

    opened by lacojim 2
  • ZHA not recognizing Tubes Zigbee Router

    ZHA not recognizing Tubes Zigbee Router

    Hi. I just received the Zigbee router today that I purchased from you last week. However, My HA ZHA does not find it. I have tried pairing just a few feet away, to about 20' away. Nothing. My Zigbee controller is the GoControl Nortek Zigbee and Zwave USB adaptor on a RPi4 running HA. Any suggestions would be appreciated.

    EDIT: I should probably mention that the LED is lighted, and pressing the reset button does not turn it off momentarily, as I would expect. Also, plugging this into the USB on my Fedora 34 computer shows nothing in the logs. I would have expected something, unless the USB port is power only.

    opened by lacojim 2
  • [REQUEST] OpenThread Border Router (OTBR) RCP and NCP firmware images for CC2652P based Tube's Zigbee Gateways/Adapters?

    [REQUEST] OpenThread Border Router (OTBR) RCP and NCP firmware images for CC2652P based Tube's Zigbee Gateways/Adapters?

    Please consider providing OpenThread Border Router (OTBR) "RCP mode" firmware images well as "NCP mode" firmware images (with support for the OpenThread spinel+hdlc+uart protocol) and preferably using the latest SDK for this Texas Instruments CC2652 based gateways/adapters so that it will be compatible with the "OpenThread Border Router Add-on" that Home Assistant developer agners (Nabu Casa employee Stefan Agner) is currently developing? Check out:

    https://github.com/home-assistant/addons-development/tree/master/openthread_border_router

    https://github.com/openthread/ot-br-posix/

    https://github.com/agners

    https://community.home-assistant.io/u/agners/summary

    Thread Spinal RCP mode vs Thread Spinal NCP mode is summarized here:

    https://openthread.io/platforms/co-processor

    https://groups.google.com/g/openthread-users/

    OTBR should be a "Thread Certified Component" Texas Instruments CC2652 based chips:

    https://github.com/openthread/ot-cc13x2-cc26x2/blob/main/src/cc2652/README.md

    https://github.com/openthread/ot-cc13x2-cc26x2

    https://github.com/openthread/openthread/tree/main/examples/platforms

    https://dev.ti.com/tirex/explore/node?node=APzU0zOtgnQIe0sFnHCfxg__BSEc4rl__LATEST

    https://openthread.io/vendors/texas-instruments

    https://www.threadgroup.org/What-is-Thread/Thread-Benefits#certifiedproducts

    https://training.ti.com/thread-cc2652-cc1352

    The main reason for this request is that an "RPC" firmware with OTBR (OpenThread Border Router) support will make your adapter will be compatible with upcoming Thread based "Matter" (Project CHIP / Connected Home over IP) devices if used in Home Assistant with their other add-ons for the that is also in development. This addon by agners requires that the radio hard a firmware in "RPC" mode instead of the no traditional "NCP" mode:

    https://github.com/home-assistant/addons-development/tree/master/chip_controller_repl

    https://github.com/home-assistant/addons-development/tree/master/chip_tool

    https://github.com/project-chip/connectedhomeip

    https://buildwithmatter.com

    https://csa-iot.org/all-solutions/matter/

    Also having optional OpenThread "NCP" border router firmware would allow users to alternatively use other existing OpenThread applications that use "NCP" mode instead of the newer "RPC" mode which require additional component running on the host. Ex:

    https://github.com/openthread/wpantund

    Note that so far agners has only worked with Silicon Labs based adapter with OpenThread "RPC" firmware for Thread based Matter (as well as ESP32-C3 based devkit for Matter over WiFi) and that is only because it is a Silabs EFR32MG21 chip based adapter that will ship inside the official Home Assistant Yellow (formerly Home Assistant Amber) hardware:

    https://github.com/zigpy/zigpy/discussions/894

    https://github.com/home-assistant/addons-development/tree/master/silabs-multiprotocol

    https://www.home-assistant.io/blog/2021/09/13/home-assistant-yellow/

    https://www.crowdsupply.com/nabu-casa/home-assistant-yellow

    Off-topic but FYI; Elelabs now provide OpenThread RCP firmware with Spinel API for their upcoming EFR32MG21 based USB adapter:

    https://github.com/Elelabs/elelabs-zigbee-ezsp-utility

    PS: By the way, you might be interested in the the "Matter" workshop that Home Assistant is holding on the 15th of June even if they are in that specific workshop will not use a Thread based controller or devices and instead use a WiFi (+ Bluetooth) based "Matter" devices:

    https://www.home-assistant.io/blog/2022/05/29/matter-in-home-assistant-workshop-announcement/

    https://www.youtube.com/watch?v=9fOHBl5w0_k

    https://community.home-assistant.io/t/matter-in-home-assistant-workshop-announcement/426129/

    opened by Hedda 1
  • PoE Gateway failing with 'MAC channel access failure' (225) & 'No network route' (205)

    PoE Gateway failing with 'MAC channel access failure' (225) & 'No network route' (205)

    I bought 2 of the last of the round "CC2652P2 Based Zigbee to PoE Coordinator V2". One of them has been in use and working up till today with HomeAssistant ver 2022.4.1

    Logs are showing that Zigbee2MQTT is still receiving reports from Zigbee devices, but when sending requests to change device state it is erroring with:

    • 'MAC channel access failure' (225)
      then
    • 'No network route' (205)

    The PoE gateway was first Restarted through the web interface. Then it was power cycled. Zigbee2mqtt was restarted, then Home Assistant restarted.

    The PoE Debug Log is also showing multiple entries with:

    [D][streamserver:050]: Client 192.168.1.84 disconnected [D][streamserver:085]: New client connected from 192.168.1.84

    (where 192.168.1.84 is Home Assistant/MQTT)

    What next steps should I take to rectify this?

    Thanks, Paul


    Received status messages - working:

    Zigbee2MQTT:debug 2022-04-24 23:02:35: Received MQTT message on 'homeassistant/sensor/0xec1bbdfffecd5b8f/power_on_behavior/config' with data '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"device":{"identifiers":["zigbee2mqtt_0xec1bbdfffecd5b8f"],"manufacturer":"TuYa","model":"Multiprise with 4 AC outlets and 2 USB super charging ports (10A or 16A) (TS0115)","name":"Bedroom Strip"},"enabled_by_default":false,"entity_category":"config","icon":"mdi:power-settings","name":"Bedroom Strip power on behavior","state_topic":"zigbee2mqtt/Bedroom Strip","unique_id":"0xec1bbdfffecd5b8f_power_on_behavior_zigbee2mqtt","value_template":"{{ value_json.power_on_behavior }}"}'
    

    Changing device state - failing:

    Zigbee2MQTT:debug 2022-04-24 23:02:48: Received MQTT message on 'zigbee2mqtt/Bedroom Light 1/set' with data '{"state":"OFF"}'
    Zigbee2MQTT:debug 2022-04-24 23:02:48: Publishing 'set' 'state' to 'Bedroom Light 1'
    Zigbee2MQTT:debug 2022-04-24 23:02:53: Received MQTT message on 'zigbee2mqtt/Bedroom Light 1/set' with data '{"state":"OFF"}'
    Zigbee2MQTT:debug 2022-04-24 23:02:53: Publishing 'set' 'state' to 'Bedroom Light 1'
    Zigbee2MQTT:error 2022-04-24 23:02:57: Publish 'set' 'state' to 'Bedroom Light 1' failed: 'Error: Command 0x00124b0013eda6bd/11 genOnOff.off({}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC channel access failure' (225))'
    Zigbee2MQTT:debug 2022-04-24 23:02:57: Error: Command 0x00124b0013eda6bd/11 genOnOff.off({}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'MAC channel access failure' (225))
        at ZStackAdapter.sendZclFrameToEndpointInternal (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:414:23)
        at runMicrotasks (<anonymous>)
        at processTicksAndRejections (internal/process/task_queues.js:95:5)
        at Queue.executeNext (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
    Zigbee2MQTT:error 2022-04-24 23:03:18: Publish 'set' 'state' to 'Bedroom Light 1' failed: 'Error: Command 0x00124b0013eda6bd/11 genOnOff.off({}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))'
    Zigbee2MQTT:debug 2022-04-24 23:03:18: Error: Command 0x00124b0013eda6bd/11 genOnOff.off({}, {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Data request failed with error: 'No network route' (205))
        at ZStackAdapter.sendZclFrameToEndpointInternal (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:414:23)
        at runMicrotasks (<anonymous>)
        at processTicksAndRejections (internal/process/task_queues.js:95:5)
        at Queue.executeNext (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)
    
    opened by paulhaddon 1
  • Motion sensors vanished

    Motion sensors vanished

    Hi there

    I'm using a cc2652p2 poe gateway with zigbee2mqtt and last night all of my aqara motion sensors vanished, I have two versions of the motion sensors and they are both gone.

    I have around 10 other aqara devices still functioning perfectly, I'm just a bit miffed as to how only the motion sensors vanished.

    Wondering if you've come across anything like this before?

    Any input is greatly appreciated!

    Thanks

    opened by hammondses 1
  • Connectivity issue with CC2652P2 Ethernet/USB Coordinator after some minutes

    Connectivity issue with CC2652P2 Ethernet/USB Coordinator after some minutes

    Hello,

    I ordered a CC2652P2 based Zigbee to Ethernet/USB Serial Coordinator beginning of Feb 2022. It was working fine until last week when I lost ethernet connection regularly. Need a power on/off to have it up again during a few hours or minutes. Then I removed the WT32_ETH01 board. Without this board, the zigbee part is working fine connected via USB (several days without issues).

    If I power the WT32_ETH01 separately and connect to ethernet, then pinging stops after some minutes.

    So seems an issue with either the WT32_ETH01 board or with the ESP software.

    Any idea to investigate more this issue ?

    Regards

    Didier

    opened by didles 7
This repository contains a set of InternalBlue patches for the BCM4375B1 Bluetooth controller, allowing to sniff and inject Zigbee, Mosart and Enhanced ShockBurst packets from a Samsung Galaxy S20 smartphone.

RadioSploit 1.0 - Patches This repository contains a set of InternalBlue patches for the BCM4375B1 Bluetooth controller, allowing to sniff and inject

Romain Cayre 11 Aug 29, 2021
It is a wireless temperature, pressure and humidity sensor, supports working in Zigbee networks.

It is a wireless temperature, pressure and humidity sensor, supports working in Zigbee networks. (Zigbee2mqtt open source project). Built on CC2530 chip (Zigbee), two modications: Ebyte E18-MS1PA2-PCB radio module with amplifier and Ebyte E18-MS1-PCB. Powered by the most common AAA batteries.

Andrew Lamchenko 23 Jun 10, 2022
A tiny example how to work with ZigBee stack using JN5169 microcontroller

Hello NXP JN5169 ZigBee World This is a tiny example how to work with ZigBee stack using JN5169 microcontroller. The example implements a smart switch

Oleksandr Masliuchenko 19 Jun 23, 2022
GCFFlasher is the tool to program the firmware of dresden elektronik's Zigbee products.

GCFFlasher 4 GCFFlasher is the tool to program the firmware of dresden elektronik's Zigbee products. Supported Hardware ConBee I ConBee II RaspBee I R

dresden elektronik ingenieurtechnik gmbh 20 Jun 12, 2022
Plant Watering Sensor Project for Zigbee Network

Plant Watering Sensor Project for Zigbee Network (based on the Source Code of the DIYRUZ Flower Project).

Andrew Lamchenko 64 Jun 20, 2022
WiFi scanner with visual persistence, intended to find the idlest channel e.g. to assign to a ZigBee device

WiFiChanViz Motivation This tool was initially coded to help find the idlest 2.4GHz channel in order to connect a ZigBee device to HomeAssistant in id

tobozo 12 May 3, 2022
ASN intelligence information (IP to ASN mapping) collected and distributed in open source and transparent way

ASN Intelligence The main goal of this project to retrieve information required to map IP address to ASN number in open source and transparent way. Wh

Pavel Odintsov 60 Jun 27, 2021
Information Panel for DayZ SA

Server_Information_Panel Usage Installation: Make sure that you have installed Community Framework by Jacob_Mango, Arkensor and Kegan Hollern Download

LaGTeK 11 May 5, 2022
Triton Python and C++ client libraries and example, and client examples for go, java and scala.

Triton Client Libraries and Examples To simplify communication with Triton, the Triton project provides several client libraries and examples of how t

Triton Inference Server 141 Jun 24, 2022
Encapsulates the two protocols of OpenVpn and Ikev2, you only need to enter the server IP and port number to realize the connection and status display, and the specific situation of the connection can be displayed at the same time。

NewVpnCore 封装了OpenVpn和Ikev2两种协议,只需要输入服务器IP和端口号即可实现连接和状态显示,同时可以显示连接的具体情况。 UniteVpn Core(第一版) 1. 模块说明 unitevpn:封装了vpn的操作和统一不同协议信息的模块 ikev2:IKEV2协议的源码 op

ZFashion 3 Jun 8, 2022
Like libevent and libuv, libhv provides event-loop with non-blocking IO and timer, but simpler api and richer protocols.

中文版 Intro Like libevent, libev, and libuv, libhv provides event-loop with non-blocking IO and timer, but simpler api and richer protocols. Features cr

ithewei 4.3k Jun 24, 2022
🌱Light and powerful C++ web framework for highly scalable and resource-efficient web application. It's zero-dependency and easy-portable.

Oat++ News Hey, meet the new oatpp version 1.2.5! See the changelog for details. Check out the new oatpp ORM - read more here. Oat++ is a modern Web F

Oat++ 5.5k Jun 27, 2022
Ole Christian Eidheim 735 Jun 24, 2022
A very simple, fast, multithreaded, platform independent HTTP and HTTPS server and client library implemented using C++11 and Boost.Asio.

A very simple, fast, multithreaded, platform independent HTTP and HTTPS server and client library implemented using C++11 and Boost.Asio. Created to be an easy way to make REST resources available from C++ applications.

Ole Christian Eidheim 2.3k Jul 2, 2022
Cross-platform, efficient, customizable, and robust asynchronous HTTP/WebSocket server C++14 library with the right balance between performance and ease of use

What Is RESTinio? RESTinio is a header-only C++14 library that gives you an embedded HTTP/Websocket server. It is based on standalone version of ASIO

Stiffstream 863 Jun 23, 2022
Ultra fast and low latency asynchronous socket server & client C++ library with support TCP, SSL, UDP, HTTP, HTTPS, WebSocket protocols and 10K connections problem solution

CppServer Ultra fast and low latency asynchronous socket server & client C++ library with support TCP, SSL, UDP, HTTP, HTTPS, WebSocket protocols and

Ivan Shynkarenka 848 Jun 26, 2022
DNS and Target HTTP History Local Storage and Search

dooked DNS and Target HTTP History Local Storage and Search Installation Download Boost Library from the official website Extract the library into any

Michael Skelton 58 Jun 16, 2022
This repo contains Direct3D 9, Direct3D 10, a few Direct3D 11, and DirectSound C++ samples from the legacy DirectX SDK updated to build using the Windows 10 SDK and the Microsoft.DXSDK.D3DX NuGet package

DirectX SDK Legacy Samples This repo contains Direct3D 9, Direct3D 10, a few Direct3D 11, and DirectSound samples that originally shipped in the legac

Chuck Walbourn 33 Jun 21, 2022