📢 WebThings Gateway 2.1 Beta available for testing

Dear WebThings community,

Happy Things Thursday!

I’m writing to let you know that early builds of WebThings Gateway 2.1 Beta are now available for testing. So far the release includes:

You can run the latest WebThings Gateway 2.1.0-beta.2 Docker image using a command like:

docker run \
    -d \
    -e TZ=Europe/London \
    -v /path/to/shared/data:/home/node/.webthings \
    --network="host" \
    --log-opt max-size=1m \
    --log-opt max-file=10 \
    --name webthings-gateway \
    webthingsio/gateway:2.1.0-beta.2

(replacing /path/to/shared/data with a directory in which you would like to store the .webthings data directory)

As ever your feedback, ideas and contributions are most welcome - here and on GitHub.

–

Meanwhile work also continues on the WebThings App and WebThings Framework and there are some exciting developments on the standardisation front as the W3C WoT Working Group have expressed an interest in turning the Web Thing Protocol into a formal W3C standard. See my recent blog post on why I think there is a need for this universal web-based application layer protocol for the Web of Things, and how this has been a long term ambition of the WebThings project.

Kind regards

Ben

Is there no update/s for the Snap package?

Not yet. Are you using the snap package? If people are interested in that then we can release 2.1 Beta as a snap package too.

Now that we’re no longer targeting Ubuntu Core as a replacement base operating system I’m less motivated to work on it, but I do think it’s useful and arguably more user friendly to install than the Docker image so if people are interested in using/contributing to that then we can keep maintaining it.

Ben

Yes I’m using the snap again.

I did go back to using version 1.1 because the Telegram addon doesn’t work in version 2.0 and I really needed notifications but then I discovered the Pushover addon and it works in version 2.0 so I’m back using version 2.0 again using the snap.

Pushover is really good by the way.

1 Like

Hi Lenno.

I’ve just been donated a Dell Optiplex 9020 SFF PC with Kubuntu already installed. After a bit of a system tidy-up and update to Kubuntu 26.04 LTS I’ve installed the SNAP option but am unable to get anything happening to be able to appear on https://localhost:8080 in Firefox.

Do you have any suggestions? Or should I just wipe the system and install the base version of Ubuntu.

When I run “ss -nltp”, all I get back is;

State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 4096 127.0.0.1:631 0.0.0.0:*
LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:*
LISTEN 0 4096 127.0.0.54:53 0.0.0.0:*
LISTEN 0 32 192.168.122.1:53 0.0.0.0:*
LISTEN 0 50 :1716 : users:(("kdeconnectd",pid=1809,fd=20))
LISTEN 0 4096 [::1]:631 [::]:

With no port 8080 evident.

Sorry for just poking into this conversation, I’m fairly fresh to Linux so still learning.

Regards, Antonio Benci

Or should I just go the Docker option?

Hi Antonio,

If the Firewall is enabled you would need to open port 8080.

Also try http instead of https and try using the local IP address. eg. http://192.168.122.1:8080 (or whatever your IP address is)

Also another thing to check would be the Firefox setting that only allows https connections- change to “Don’t enable HTTPS-Only Mode”

Hi Lenno.

Thanks for the advice. Unfortunately nothing thus far has worked.

Firewall is off, Firefox is set to “Don’t enable HTTPS-Only Mode”.

I’ll dive headfirst into Docker (:grimacing: ) and see how I go.

I had the same issue you’re having when I tried installing the snap on Raspberry Pi OS so the only other thing I’d suggest is installing Ubuntu instead of Kubuntu.

Hi Lenno.

Was hoping you’d not suggest that.

Oh well, next thing to try. Cheers.

Some success…

The hardware: Dell OptiPlex 9020M Micro-Form-Factor PC [AU$90.00]

Operating System: Kubuntu 26.04 LTS
KDE Plasma Version: 6.6.4, KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2, Kernel Version: 7.0.0-27-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-4590T CPU @ 2.00GHz
Memory: 8 GiB of RAM (7.7 GiB usable)
Graphics Processor: IntelÂŽ HD Graphics 4600

webthingsio/gateway:2.1.0-beta.2

After a whole lot of reading, failure, reading some more. The following Docker script, saved as a bash script works…

#!/bin/bash
docker run
-d
--name webthingsio-gateway
-e TZ=Australia/Melbourne
-v /home/node/.webthings
-p 8080:8080
-p 4443:4443
--log-opt max-size=1m
--log-opt max-file=10
webthingsio/gateway:2.1.0-beta.2

Accessible at: http://localhost:8080

Some Bugs: Localisation:Unable to change country.

Web Thing and Tasmota are not working, probably network related.

And others. More testing to do.

Hi @Antonio_Benci, I’m glad you got this working using the Docker image.

FYI switching the country is not currently supported in the Docker image. All it actually does is set the regulatory country for the Wi-Fi adapter, which was important for the old Raspberry Pi image but likely unnecessarily when running the Docker image on your own OS. I realise it looks broken though so I’ve filed an issue to fix that. You should still be able to choose the localisation language and units.

Please let us know how you get on and whether you are able to resolve the issues with the web thing and Tasmota adapters.

Please note that a Docker image of 2.1.0-beta.3 is now available on Docker Hub, which includes:

  • An upgrade to Node.js 24
  • And consequently a fix for security bug CVE-2026-111497 (thank you Mahfuzur Rahman for their help with this)

A snap package is also available for testing via the edge channel, but I haven’t yet tagged a new release of that.

Known issues:

Please also note that version 2.1.0-beta.3 deprecates armv7 support for the Docker image (which includes older Raspberry Pis and 32-bit operating systems running on newer Raspberry Pis) because Node.js is no longer supported on that architecture as of version 24. It should still be possible to build the gateway yourself on older Raspberry Pis or 32-bit operating systems using Node.js 22. 64-bit operating systems on Raspberry Pi are unaffected.

Given the security patch above I would like to get this released as a stable release as soon as possible, so any help with testing is appreciated.

Have a great weekend!

Running this since Sunday, but have no coherent feedback as of now. However: My two non-docker RPI4 1.1.0 installations both says new version available. This cannot be right ?? Both have automatic update off, so nothing has been disturbed.

Regards GHo

Hi @GHoGit,

Running this since Sunday, but have no coherent feedback as of now.

Great, let me know if you spot any add-ons that break.

My two non-docker RPI4 1.1.0 installations both says new version available. This cannot be right ??

Interesting. I note that the addon-proxy is still adding new GitHub releases to https://api.webthings.io:8443/releases even though those releases don’t have a gateway-*.img.zip so there’s no way for the Raspberry Pi OS based images to actually update, so that may be why. Even if you tried to update it would fail so I’m sure it’s safe, but we should probably fix that. I have filed an issue.

Thanks for reporting back

Ben

OK, I have updated the Zigbee add-on to support Node.js 24 (it needs separate packages for each Node version due to the native serialport dependency), and updated the add-on list so the Zigbee add-on is now working in WebThings Gateway 2.1.0-beta.3.

This also involved publishing new addon-builder toolchain images to DockerHub in case anyone needs those to update their add-ons.

Other add-ons which specify a particular gateway version or Node.js version may need updating and/or updating in the add-ons directory but otherwise I’ve not come across any bugs with the new Docker image.

Please keep testing and report back any issues (particularly with broken add-ons you care about), but hopefully we should be able to push a stable release WebThings Gateway 2.1.0 soon.

Kind regards

Ben

FYI: zigbee addon 2.2.0 brought back my lost sensors. Reading remote mosquitto fed by zigbee2mqtt.

Regards GHo

1 Like

Hi Ben,

When a stable release of 2.1.0 is available what will be the benefits of upgrading from 2.0?

Also will there come a time when the gateway can be updated in the updates section of the gateway itself instead of having re-install the snap or docker image?

Having to re-install the snap when a new version comes out and then setup the gateway again with all the zigbee sensors and then the 50 or so rules and everything else is super time consuming.

Hi @lenno,

My goal is for us to release 2.1 this week. Currently just working on another bug fix.

The main changes in 2.1 are support for occupancy sensors, some UI bugfixes, an upgrade to Node.js 24, and some important security patches. There will be release notes and an announcement blog post.

You shouldn’t need to re-install the snap package when upgrading to a new version, it should automatically update itself once a new version lands on the channel you are using. Similarly when upgrading the Docker image it shouldn’t be necessary to re-install anything, it will mount the same .webthings data directory with all of your settings and data.

Regards

Ben

Hi,

I wrote this up last week. A little long probably, but posting anyway.

A quick run through of addons that I normally use, or installed just for this test.
Other addons supporting particular services or hardware not used or owned by me are not tested.

Calendar
Displays Today’s state with day name ‘Wednesday’ marked as ‘Working Day’ and ‘Holiday’ unchecked.
Not tested as part of rule.
2026-11-11 17:44:16.238 WARN : The type member of event descriptions is deprecated, please use data.type

Counter: As before

Cron adapter
Added an extra group with job and made it increment a counter.
Appears to work as before.

2026-11-11 17:13:14.129 ERROR : cron-adapter: The manifest object is deprecated and will be removed soon. Instead of using manifest.name, please read the id field from your manifest.json instead.

DateTimeAdapter
Reset a counter on a specific hour → OK
2026-11-11 18:00:00.135 INFO : DeviceProxy: requestAction: reset for: counter-170f4af101c900ec9f6612d546611cf4

Excessive log printouts when activated. Appears to be the full set of Things w/Properties ??

026-11-11 17:47:00.299 INFO : date-time-adapter: Invalid message received: {‘messageType’: 8207, ‘data’: {‘deviceId’: ‘0x00158d0008746989’, ‘device’: {‘title’: ‘TiltVib-1’, ‘@context’: [‘https://www.w3.org/2022/wot/td/v1.1’, ‘WoT Capability Schemas - WebThings’], ‘@type’: , ‘profile’: [‘https://www.w3.org/2022/wot/profile/http-basic/v1’, ‘https://www.w3.org/2022/wot/profile/http-sse/v1’], ‘description’: ‘’, ‘href’: ‘/things/0x00158d0008746989’, ‘properties’: {‘battery’: {‘name’: ‘battery’, ‘title’: ‘Battery’, ‘type’: ‘number’, ‘@type’: ‘LevelProperty’, ‘unit’: ‘%’, ‘description’: ‘Remaining battery in %, can take up to 24 hours before reported’, ‘minimum’: 0, ‘maximum’: 100, ‘readOnly’: True, ‘forms’: [{‘href’: ‘/things/0x00158d0008746989/properties/battery’}, {‘href’: '/things/0x00158d
..
..

MQTT Bridge
Not used this actively before. Observing using mosquitto_sub. Messages print when enabled. Stop when disabled.
Interestingly, when adding also for my two WT1.1.0 no data comes through.

ONVIF
As before.
Installs, but fails when parsing Tapo C520WS.
Camera supports RTSP, can view using VLC.
No idea whether ONVIF requires something extra from unit.

026-11-11 18:24:28.731 INFO : Loading add-on: onvif-adapter
2026-11-11 18:24:28.886 INFO : onvif-adapter: Opening database: /home/node/.webthings/config/db.sqlite3
2026-11-11 18:24:29.805 INFO : onvif-adapter: Loading add-on onvif-adapter from /home/node/.webthings/addons/onvif-adapter
2026-11-11 18:24:35.393 ERROR : onvif-adapter: <ref *1> IncomingMessage {
2026-11-11 18:24:35.393 ERROR : onvif-adapter: _events: {
2026-11-11 18:24:35.393 ERROR : onvif-adapter: close: [
2026-11-11 18:24:35.394 ERROR : onvif-adapter: [Function (anonymous)],
2026-11-11 18:24:35.394 ERROR : onvif-adapter: [Function (anonymous)],
2026-11-11 18:24:35.394 ERROR : onvif-adapter: Symbol(events.emitting): 0
2026-11-11 18:24:35.394 ERROR : onvif-adapter: ],
2026-11-11 18:24:35.394 ERROR : onvif-adapter: error: [Function (anonymous)],
2026-11-11 18:24:35.394 ERROR : onvif-adapter: data: [Function (anonymous)],
..
..
2026-11-11 18:24:37.228 INFO : onvif-adapter: {
2026-11-11 18:24:37.228 INFO : onvif-adapter: Manufacturer: ‘tp-link’,
2026-11-11 18:24:37.228 INFO : onvif-adapter: Model: ‘Tapo C520WS’,
2026-11-11 18:24:37.228 INFO : onvif-adapter: FirmwareVersion: ‘1.2.7 Build 260716 Rel.35957n’,
2026-11-11 18:24:37.228 INFO : onvif-adapter: SerialNumber: ‘7461dc94’,
2026-11-11 18:24:37.228 INFO : onvif-adapter: HardwareId: ‘2.0’,
2026-11-11 18:24:37.229 INFO : onvif-adapter: Ptz: false,
2026-11-11 18:24:37.229 INFO : onvif-adapter: Name: ‘C520WS’,
2026-11-11 18:24:37.229 INFO : onvif-adapter: Hardware: ‘C520WS’,
2026-11-11 18:24:37.229 INFO : onvif-adapter: ProfileS: true
2026-11-11 18:24:37.229 INFO : onvif-adapter: }
2026-11-11 18:24:37.320 ERROR : onvif-adapter: Failed to initialize device at undefined: TypeError: Cannot read properties of undefined (reading ‘Uri’)

Philips Hue : As before

Pulse : As before. Single pulse trigged by DateTimeAdapter → OK

RunProgram
I have some unresolved issues with reduced functionality when used from within the container.
Essentially, I could not find out how to call ssh on an other machine for executing a command.

Scheduler
Defined a time period. Set lamp on inside period, off outside. → OK

026-11-11 18:46:41.485 ERROR : scheduler-adapter: The manifest object is deprecated and will be removed soon. Instead of using manifest.name, please read the id field from your manifest.json instead.

Zigbee adapter
Now appears to work as before. All is not well though.

Never managed to display other contents than zigbee2mqtt topics.
Specifically, this apply to a leaksensor handled by zwave-js-ui->mosquitto and ams (power meter) posting directly to mosquitto.
For these two I’ve made workarounds reading mosquitto_sub output and posting the corresponding data as ‘WebThings’.
Sort of have it working, but would prefer something more straight forward.

Minor display issue - my door sensors show with reversed icons. ‘Open’ when ‘Closed’ and vice versa.
Tuya TS0203 or eqivalent.

OPEN (no contact):
zigbee2mqtt/bridge/logging {“level”:“info”,“message”:“z2m:mqtt: MQTT publish: topic ‘zigbee2mqtt/No2-Terasse’, payload ‘{"battery_low":false,"contact":false,"linkquality":255,"tamper":false}’”}

zigbee2mqtt/No2-Terasse {“battery_low”:false,“contact”:false,“linkquality”:255,“tamper”:false}

CLOSED (contact):
zigbee2mqtt/bridge/logging {“level”:“info”,“message”:“z2m:mqtt: MQTT publish: topic ‘zigbee2mqtt/No2-Terasse’, payload ‘{"battery_low":false,"contact":true,"linkquality":255,"tamper":false}’”}

zigbee2mqtt/No2-Terasse {“battery_low”:false,“contact”:true,“linkquality”:255,“tamper”:false}


Webhook adapter.
Partial success only. Fingertrouble ?
Never used this before since I found the readme a little lacking. So did not know what it could do.
Had a go and managed to set a string variable from a separate pi using curl.
Later however, nothing happens from the same command. No debug output seen.
Several reboots, stop-rm-start docker image etc to no avail.

Regards
GHo