Small Web-UI, dockerized

[Matthias Kallenbach]

Hi dudes and duderinas,

have done a little Web-UI for my needs:

- simply map a value from a device to a mqtt topic

- exclude models or a specific device

- forget unmapped devices after a given time

- translateable

Works well on a raspberry pi 4, dockerized.

https://github.com/seekwhencer/node-rtl433-ui

greets from germany.

[Christian Z.]

Very nice. Be sure to list this on the https://github.com/merbanan/rtl_433/wiki page.

[Matthias Kallenbach]

ok. done.

[Matthias Kallenbach]

Now you can order by time or signal count.

 

[Matthias Kallenbach]

Now you can enable or disable dropping unmapped devices from list by a given livetime in seconds. Define the livetime in the config file or with an environment variable.

 

[Christian Z.]

This is making leaps forward, very nice. I was hoping for some kind of elegant Web UI to come along, thanks!

[Matthias Kallenbach]

Thanks. joah... have time at the moment ;)

Here a video:
https://www.youtube.com/watch?v=uaaDtUsMjKc

[David Powell]

Very nice, I like it. 

Is this going to replace the one that you get at http://localhost:8433 when you use the -F http flag?

--
You received this message because you are subscribed to the Google Groups "rtl_433" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtl_433+u...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rtl_433/ac4f006d-2f5f-4681-a531-af18bc34b916n%40googlegroups.com.

[Christian Z.]

Is this going to replace the one that you get at http://localhost:8433 when you use the -F http flag?

The built-in Web UI is meant to control the rtl_433 instance and tune settings. It will focus on that.

 

[Matthias Kallenbach]

i saw it the first time: now ;) looks good. but, i didn't saw it in the documentation. have you some api documentation?

[Christian Z.]

It's still incomplete and the only docs so far is the doc-comment here: https://github.com/merbanan/rtl_433/blob/master/src/http_server.c

[Matthias Kallenbach]

ahh. your dark theme is also green... haha. nice.

Just add the mapping feature to map a value to a mqtt topic.

That was the only reason why i build that piece of code.

I want to do it user guided at runtime. Not per config-file or scripting.

[David Powell]

It's a great feature. Seems pretty complete to me,  I use it all of the time and have never seen a problem.  I think it should be deemed complete and added to the documentation. 

On April 15, 2023 7:20:02 AM "Christian Z." <chri...@zuckschwerdt.org> wrote:

It's still incomplete and the only docs so far is the doc-comment here: https://github.com/merbanan/rtl_433/blob/master/src/http_server.c

--

You received this message because you are subscribed to the Google Groups "rtl_433" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtl_433+u...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/rtl_433/210f19e2-3391-4ee1-9c86-02ffa5b347f4n%40googlegroups.com.

[Christian Z.]

Thanks, now that #1978 is merged we can really move forward with a web API.

[Matthias Kallenbach]

Hm. There are two things with the "official" web ui

- the web statics are not embedded in the binary. they are distributed by a web-server. this means: no offline use
- and please: no tracking ;) saw it here: https://triq.org/rxui/

For the web statics a suggestion: place the production frontend-build inside the binary. and make it possible, that you can use a newer frontend-bundle in a configurable folder.
If the consideration was, that the user can use the newest frontend build: this is possibe. but the user must use the newest frontend bundle. if the binary where not updated, the versions runs out of date and the frontend can not be used.

you have to establish a workflow, before continuing.

Maybe a github action for the frontend production bundle. or other ci things like travis...

[Matthias Kallenbach]

use a github action like that:

https://github.com/seekwhencer/node-rtl433-ui/blob/master/.github/workflows/build_and_deploy.yml

This does:

- create a new frontend production build on a push

- publish only the bundle on a second branch

And with github pages you can distribute the production bundle from github.io

https://seekwhencer.github.io/node-rtl433-ui/

This could be the alternative for your selfhosted solution... with an actual frontend production bundle ...

[Christian Z.]

Thanks for the good examples. This should be inspiration or even a template once things settle with the API and UI.

The bundled UI was present earlier (see the doc-comment about included files, currently not true though), but moved out to allow development at a different pace. I think the bundle-at-build rules are still in some branch. Worth looking into, maybe later this year.

[Matthias Kallenbach]

https://github.com/seekwhencer/node-rtl433-ui/blob/master/.github/workflows/build_and_deploy.yml

add something when a pull_request happens ;) this is only for a push

[Matthias Kallenbach]

Hi Volks,

have done a public docker image. Just use it like:

https://github.com/seekwhencer/node-rtl433-ui/blob/master/docker-compose.yml

It's a multi-arch build and runs on a raspberry pi 4.

https://github.com/seekwhencer/node-rtl433-ui/pkgs/container/node-rtl433-ui