Hi there.
I have following (but growing, I hope) setup:
- several Sonoff 230V modules (Basic, Basic RF, 4CH Pro, Mini, Zigbee Mini, RF Bridge, Zigbee USB stick - CC2531),
2 Orange Pi’s for hosting OH and companions: - OPi3 (4 cores at 1.8GHz, 2GB RAM, ARM) with OH2, and
- OPi4 (6 cores at 1.8GHz, 4GB RAM, ARM) with OH3.
Both with Armbian Buster with OH installed using system tools (apt, synaptic, NO compiling etc). - mosquitto MQTT broker on OH2 host → OPi3. Simple user / pass security, no SSL (yet).
Connected with Eth and 802.11n WiFi.
Now the experience:
- managed on both OH to make “things”, “channels” and “items” for Sonoff (and WeMos D1 mini) real world devices. CC2531 stick connected only to OPi4.
- did not bother for now with “presentation level”, ie use Paper UI on OH2, and basic “overview” page on OH3.
Now the problem:
-
OH2 works relatively fast (giving user experience of “less than 3 secs response”) despite slower hardware. Items / things got updated in realtime if switched / changed by real world device / sensor. (use DS18B20’s, INA226, RF remotes). Gives reliable “look and feel”.
But it lacks SECURITY by design!! So not to use in real world application! (imo), (do You want “anyone” switching off heating during Eastern Europe winter? -20*C outside ). -
OH3 it designed with (some?) security in mind, BUT gives UNRELIABLE “look and feel”:
- readings, “items” (DS18B20, switches etc) stop to get updated quite short after OH3 startup (not all, ex I can get time reading from Tasmotized Sonoff but no switch state updated, if I change state from OH, it updates),
- ZigBee got “on/off line” at random (from user point of view).
- need to hit browser (Firefox, as my favourite SeaMonkey does not work with OH3, works with OH2!!!) “refresh” key on regular basis,
- “big fat and heavy” look and feel.
Now how to:
- pinpoint OH3 problems with responsivity (which config files shoud I attach?, what log info?),
- change config.
- what should I read about “how to make Your OH3 presentation layer appealing” :),
- same question for security (granular), ie “Tom can only view AC temperature”, but “Alice can change them”.
?
As robustness is key for me, so I plan to use as much of intelligence on MQTT / Tasmota level as possible, using OH for “nice interface”.