I can, should I run that from the config file?
I will say though that it worked before the upgrade and I tried the config.js.sample file and it didnt work.
I can, should I run that from the config file?
I will say though that it worked before the upgrade and I tried the config.js.sample file and it didnt work.
I am having the same issue but doing npm install in all of the modules folders doesn’t resolve it. Any other thoughts?
Is this still working for you? I installed it and used the credentials that I use in the app but the module is stuck on loading.
Does this require the camera to be shared publicly?
What switch are you planning on using?
Any additional thoughts here? I am around if there is something that I can test.
The only thing I could find is the ability to change the encoding which doesn’t seem to be the problem.
This is the docker that works: https://github.com/nwootton/unRAID-Magic-Mirror-Docker
Looks like it’s based off this: https://github.com/bastilimbach/docker-MagicMirror
@jbishop129 said in Can’t view MM on LG TV WebOS browser - others fine:
I think what @potts-mike is implying is he got it to work with the prebuilt docker package, but not the newer version. If that’s correct, could you share your build version on the older docker image? Maybe we have an issue in the newer version preventing some browsers from working.
This is correct, the docker version works but is approx. 2000 commits behind the current version. I’ll grab some information about the Docker when I get a chance.
@bhepler said in Can’t view MM on LG TV WebOS browser - others fine:
My initial thought is that the WebOS browser that is included in your TV is probably locked down to within an inch of its life. It may not have Javascript enabled, which is used by the MM framework to load the modules. Possibly. Maybe. I’d have to do some research.
Intriguing idea though.
Could that be the case if an older version (docker) works?
I am trying to do this as well on a WebOS LED. What I have found is that the Docker server works fine but when connecting to a RPI as a server I see what your seeing. The docker server is out of date so something they have changed between the two versions broke it.
Please post back if you find a solution as this with pip would be perfect for mornings.
Maybe I can get a little help here.
The Todoist header is showing on my mirror but there are not any events. I made a test project with one event scheduled for tomorrow. The url is https://todoist.com/app?lang=en#project%2F2183902244 meaning that the project should be 2183902244. Meaning that the below code should be correct
maximumEntries: 60,
updateInterval: 90000,
projects: [ 2183902244 ],
fade: true,
orderBy: "todoist"
For the access token I am using the test token from the developer page on todoist. Should there be spaces between the quotations, brackets and token?
I am having a little trouble getting this module to work. I’ve tried multiple different projects and access tokens but neither have worked. Any help is appreciated.
{
module: 'MMM-Todoist',
position: 'middle_center', // This can be any of the regions. Best results in left or right regions.
header: 'To Do', // This is optional
config: { // See 'Configuration options' for more information.
accessToken: 'xxxxxxxxxxxxxxxx',
maximumEntries: 60,
updateInterval: 10*60*1000, // Update every 10 minutes
projects: [ xxxxxxxxx ],
fade: false
}
},
I have been playing with magic mirror for the last couple weeks. To start I loaded the docker to get a general feel for things. I decided I want to move forward and setup a raspberry pi to host magicmirror.
My problem is that the Docker version displayed fine in my LG TV browser, its great with the PIP in the mornings. The rpi version just shows a black screen. What are the difference between the two versions? Could it be something in the html?
Thanks,