Thingsboard VS CefSharp

Until recently I was still using TB v3.2.1, now I've set about updating the installation to the latest version. I proceeded as described at https://github.com/thingsboard/thingsboard/tree/master/docker:

You might find something more attuned to that use case to be more helpful out of the box (like thingsboard.io) but if you're committed to django, set up an API endpoint to receive json updates ('events') sent from the arduino.

Introduction：As a 100% open source IoT platform that can be hosted as a SaaS or PaaS solution, Thingsboard can provide device management, data collection, processing and visualization for your IoT project. The standard protocols that provide device connectivity such as MQTT, CoAP, and HTTP are all available on ThingsBoard. In addition, it supports cloud and local deployment and provides more than 30 customizable components that allow you to build end-user custom dashboards for most IoT cases. GitHub: https://github.com/thingsboardThingsboard: http://thingsboard.io/ Features:

Then host a ThingsBoard server and use the HTTP API to push data from the device. You can send alerts with Pushover.

**Source** [thingsboard (a foreign iot platform)](https://thingsboard.io/)

ThingsBoard is an open-source IoT platform for data collection, processing, visualization and device management. It supports device connectivity via protocols, such as MQTT, CoAP and HTTP, and supports both cloud and private deployments. Deliver, monitor and control your IoT entities in a secure way using rich server-side APIs that define the relationships between your devices, assets, customers, or any other entities. Collect and store telemetry data in a scalable and fault-tolerant manner, visualize your data with built-in or custom widgets and flexible dashboards, and share the Dashboard interface with your customers.

The company I work for uses https://thingsboard.io and the team from Ukraine that built it are awesome and the company is still responding even though they are going through this hell of a war.

The Fullscreen Chromium (cefsharp) based Web-Browser ignores optionally user input like Mouse clicks, and is optionally always in the foreground (Force-Top-Most), so it can be used for any situation.

Just as a background: I'm working on a façade for the CefSharp utility. This utility requires the programmer to initialize and terminate it in the same thread, once-per-process. My current implementation uses a lazy initialization algorithm requiring inter-thread communication. But the possibility of AppDomains arising or passing away complicates the algorithm by requiring threads to potentially signal one another across AppDomain boundaries. It would be easier to just let the threads communicate without worrying about which AppDomain they belonged to.

I dont want to state the obvious but of course there is CefSharp .. But of course thats pretty heavy duty as you end shipping a headless version of Chrome in your app, but it can do anything a browser can do (of course it can, its Chrome), including exectuting a JavaScript string on the fly and getting a response. Because its Chrome you evenn have access the the dev tool and everything like that. But the other suggestions might be better suited as they might be more lightweight.

Two options: Either use an embedded browser you can control programmatically like CefSharp (https://cefsharp.github.io/) or spawn a real browser and use sendkeys() to control the browser by emulating user input.

Chrome Runtime discussion in CefSharp repository.

https://github.com/cefsharp/CefSharp/ if i spiked your intrigue

CefSharp

I always use https://cefsharp.github.io/