@jhjang101 ok…
Read the statement by Michael Teeuw here.
Posts
-
RE: [MMM-SimpleCalendar] Calendar module optimized for an old tablet screen
@jhjang101 cool… can you articulate what you mean by old tablet?
MM uses the latest javascript idioms, Ecma6, which many older browsers do not support… on my old ipad, black screen
on my 2018 samsung tv, black screenok on latest android or iphone.
-
RE: Netatmo module will not shown
@kusselin so I had to use the mockdata: true option as I don’t have any server for this
I set the clientid… to garbage numbers . module fails if not set
and mockdata: true and after a while I see this on the lxc container MM instance
(MMM-Config generated config entry){ module: "netatmo", position: "bottom_left", order: "*", animateIn: "None", animateOut: "None", config: { clientId: '1234567', // your app id clientSecret: '1212123', // your app secret refresh_token: '3223232', // your generated refresh token mockData: true }, disabled: false, hiddenOnStartup: false, configDeepMerge: false },
the system service is setup without logging, so the MM app logging is lost…
for me lxc container looks and acts like a Virtual machine, (restricted to OS structure proxmox is running on)
-
RE: Netatmo module will not shown
@kusselin problem here was disk and memory too small… 10g disk and 2048g memory and install finished…
-
RE: I am using the default clock module in analog mode. Is there a way to enlarge the date up top, and change the thickness of the clock hands?
@briantogo said in I am using the default clock module in analog mode. Is there a way to enlarge the date up top, and change the thickness of the clock hands?:
I tried changing the clock hands in clock_styles.css
don’t change them there
copy that whole css entry to custom.css
for each hand
don’t change our files
-
RE: I am using the default clock module in analog mode. Is there a way to enlarge the date up top, and change the thickness of the clock hands?
@briantogo disable seconds for the debug then it will stay
you changed both values for both hands, right?
show your custom css for clock
-
RE: Netatmo module will not shown
@kusselin no network
the script says there is no network card for the container so it cannot talk to anything
from the script output see <---- below__ ___ _ __ ____ / |/ /___ _____ _(_)____/ |/ (_)_____________ _____ / /|_/ / __ `/ __ `/ / ___/ /|_/ / / ___/ ___/ __ \/ ___/ / / / / /_/ / /_/ / / /__/ / / / / / / / / /_/ / / /_/ /_/\__,_/\__, /_/\___/_/ /_/_/_/ /_/ \____/_/ /____/ 🧩 Using Advanced Settings on node pve 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 🔐 Root Password: ******** 🆔 Container ID: 101 🏠 Hostname: magicmirror 💾 Disk Size: 3 GB 🧠 CPU Cores: 1 🛠️ RAM Size: 512 MiB 🌉 Bridge: vmbr0 📡 IP Address: dhcp 🌐 Gateway IP Address: Default 📡 APT-Cacher IP Address: Default 🚫 Disable IPv6: yes ⚙️ Interface MTU Size: Default 🔍 DNS Search Domain: Host 📡 DNS Server IP Address: Host 🏷️ Vlan: Default 📡 Tags: community-script;magicmirror 🔑 Root SSH Access: yes Warning: No SSH key provided. 🔍 Verbose Mode: yes 🚀 Creating a MagicMirror LXC using the above advanced settings ✔️ Using local for Template Storage. ✔️ Using local-lvm for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✔️ LXC Container 101 was successfully created. ✔️ Started LXC Container net.ipv6.conf.all.disable_ipv6 = 1 ⠇ ✖️ No Network! ner OS <---- ✖️ No Network After 10 Tries <--- 📡 Check Network Settings /dev/fd/63: line 72: SPINNER_PID: unbound variable
-
RE: Netatmo module will not shown
@kusselin so with the script I get a container starting to be built, but it has no network
I see it in the list, can start/stop. but no network.this is proxmox in a VM, not native on the hardware…
I did get a vmware warning that proxmox was trying to set promiscuous mode, but that is not allowed
-
RE: Netatmo module will not shown
@kusselin no, just have to restart the container…
I am installing proxmox on a vmware VM now,
-
RE: Netatmo module will not shown
@kusselin netatmo is not in the module list
also the address already in use means the server is running already from whatever script is launched at container startup
in container you cannot run manual npm run server if the container does that
same as if pm2 autostarted on native os or virtual machine