Reporting back for the final time: I tried Qubes, but it runs rather slow on a 6th generation NUC, so it's a hassle to use. Not sure, but maybe on a super fast computer it would be more tolerable.
Anyhow, I think the idea has merit, but I'm not a fan of the Qubes distro. It's fine as a proof of concept, but its choice of apps really limits its fresh-out-of-the-box appeal. If there were something equivalent that ran under ProxMox, I'd probably like it better. From what I've read, ProxMox hypervisor can manage virtual TPMs (or, alternatively, pass through hardware TPMs to virtual machines), and I'd be interested in giving that a try (as it seems like a good idea in any case). So unless there's a reason to think that Xen is inherently more secure than ProxMox, maybe the same general idea (minus the color coding) could be approximated in ProxMox without much effort.
Anyhow, thank you everyone for your suggestions. Though everyone may have their own favorites and good reasons for them, it was useful to compare notes. Ultimately, it seems like
the sort of thing you just have to try for yourself to know whether you like a particular app or not, but starting with a solid list of candidates in the first place really helps a lot.
@NeverDie said in Advisory: put IOT devices on a separate LAN/vLAN for better security:
Lest I mislead anyone, I subsequently contacted to the seller and, despite the wording, it doesn't include an E3-1200 with the board. He just meant that as shorthand to refer to the processor family that's compatible with the board. That said, there are a ton of inexpensive used LGA1150 CPU's on ebay that could serve the purpose.
I still see this as a "controller" part, as it's mqtt you are totally free to subscribe to the messages from the gateway, transform it to something else, and then publish that onto mqtt as well.
That's the way I would do it, as it's much easier to edit config files etc on a computer (rpi etc).
as an "advanced hobbiest" i can tell why i am not getting really warm with mysensors.. I have a gateway and two nodes. One node (RFID garage opener) is working now but has range issues that i can not reach the gateway in the place i need it. And the other is a temperature sensor to play. So it works, but in real it does not, and to be honest the functionality is just nice to have for the moment
In my case i got stuck in details with my configuration. The one night a month i have to code is not enough to solve it. (and of course i am not a professional)
In the first view does mysensors look very cool. It wants to be an easy to use arduino library. A lot of examples for different gateways and nodes. Seems to be easy, "build = fun", no?
No, it is not that easy.
Mysensors is a framework. It hijacks already base functions of arduino.
As soon as you leave the application which is given in the example something does not work. And than you have to dick deep in the functionality of the mysensor framework and it is not easy to collect all necessary information in the documentation - at least for me.
Standard EEPROM functions are hijacked and can not be used as you are used to.
pin configuration is done in the framework. If your other things connected to the MCU need also a special treatment (RST-pin) you need to find out how
took me a while to release that there is a completely new version 2.0 of the radio-driver which worked for me instantly and i still no not know why the same code does not work with the standard version.. And you should use the newest development branch, not the released one
the examples are not consistent to each other and are not even compatible in all cases...
So i think it is difficult to catch the user or it is not clear which kind of user is addressed.
The normal arduino dummy user can use it for the very simple examples. As soon he wants to combine function and the issues come, he will get stucked. And of course you get the same function in the meanwhile out of the box from a lot of cheap commercial products. Maybe you have different systems running but for that money you can buy every two years new things. And most people use a Controller which can handle directly the different systems and the configration there is easier. The Controllers made big improvements in user friendly configuration!
The advanced user is getting rare. And honestly the mysensor framework is so big with all that #define-cases for the different platforms and configurations that it takes a while to go through and find your adaption. This users have already made their own private libraries which will not work directly on the mysesnors framework. They switch to a different system or maybe start extract the things they need from mysensors.
And than i also have the impression that the help in the forum is "superficial". Not because the forum does not want to help.
The problems occur in the system and it is not easily clear why something does not work without taking the time and go thorugh everything.
It is open source and the documentation is suffering. The contributors have limited time and nobody can expect to get a 24/7 full support.
Everything okay, please do not misunderstand me, i really appreciate the work behind mysensors and i can only imagine complicated it is to keep such a system administrated.
But to come back to the beginning it is the question which user should be addressed.
For the dummy user the documentation should be reduced but therefor everything should be consistent and straight. As the Controller software does, the work should focus on not technical functionality for easy configuration and usage.
For the advanced user the documentation should go more in detail in general in one place and the code should focus on a layer structure to make it easier to operate on different systems or exchange modules/versions (maybe without the arduino framework as base or an approach as FreeRTOS).
And i am not sure if it is just me, but i could imagine it would help to make it easier to get part of the active community and bring improved code or new functions back in the mysensors-core.
greeting from Germany
P.S.: i am sorry that i did not gender everything and always wrote "he" as "the user". Should of course also be a woman or girl or ...
@hek From what I've read, to better avoid browser fingerprinting, Brave apparently camouflages itself as Chrome: https://www.ctrl.blog/entry/brave-user-agent-detection.html That would make sense, since there would be less uniqueness if mixed into a larger pool, and Chrome has the largest pool by far. Perhaps that would mean you'd be getting tips from seemingly "out of the blue". Brave is pretty new, but there's a good chance the idea might catch on when people realize it works in their best interests.
It's actually at this link posted earlier in the thread: What did you build today (Pictures) ?:
I mostly use it with BME280 modules for temperature and humidity, but I have tried some other I2C modules in it.
I'm still experimenting with the motion detector. That will probably get it's own board at some point. It doesn't really fit the enclosure I designed this board for.
@NeverDie I have two of them and made some applications using PlatformIO IDE. I like the Wio Terminal. The only issue that I experienced until now is that I couldn't get one of my apps, which is repeatedly posting sensor data to Azure Storage Tables, running without hangs for longer time periods. If you can live with the watchdog it is useable.
I didn't try the bluetooth and sd-card functions.
A good thing is that you can easily enable debugging with a little bit soldering and a J-link debugger.