@csdj92 This is a screenshot of a calendar…
Read the statement by Michael Teeuw here.
Posts made by lavolp3
-
Several issues when using pages
I am trying to build a dashboard with several pages and I recognize general issues with several modules when e.g. MMM-pages is activated.
For one of my modules I have heard of the same issues using MMM-page-selector, so I think it is not a module-specific issue but rather issues originating from theshow()
andhide()
-methods
Examples:-
Some modules do not show at all. (MMM-Keyboard, MMM-WeatherBoy). They are suspended but for some reason not resumed. The region does not seem to make a difference.
-
MMM-Bring, which has a touch function, does not work properly within a page. The implemented
.onclick
-method of the divs only seems to work once, then not anymore wherever I click.
The module works as intended when I deactivate MMM-pages.
Can anyone confirm this odd behaviour or does anyone know a reason for that?
-
-
RE: Night sky: planets, constellations, satellites
@Mykle1 No time to answer. Must find API first
-
Night sky: planets, constellations, satellites
So I have this idea about a module in mind but I’m missing the api for it.
I’d like to have it show the following- a random picture of a star constellation including its current position on the sky (direction and angle)
- the position of planets and remarkable stars on the sky (direction and angle)
- next passing of any starlink group. (Here I have tried to use n2yo.com but they can only filter by one satellite number and there are many starlink numbers available already)
Can anyone help me, at least with a source? Especially looking at you @Mykle1 :-)
-
RE: Display temperature over network
EDIT: Sorry, didn’t read everything.
tl;dr: what @stampeder said…@linuxdxs I personally would use MQTT for that purpose. It’s a very lightweight way of regularly publishing data through your network and fetching it with any device you want to. It’s also cross platform. You could use your android mobile as well.
I use MQTT to fetch data from and send controls to my tasmota plugs and it works very well.
There’s a module called MMM-MQTT-Bridge already published that could be used and my soon-to-be-published MMM-Tasmota would work as well as a basis.
On the Raspi’s you would need an MQTT server like mosquitto.
May not sound like the easiest way but on the publisher side it’s not more than a few lines of code. -
RE: Remove Modules
@StewartBaird86 Or you can include the property
disabled: true
to the module entry.{ module: "MMM-Module", disabled: true, position: "top_right", config: { } },
Using this moethod, you can quite easily enable it again by just commenting the entry out.
{ module: "MMM-Module", //disabled: true, position: "top_right", config: { } },
-
RE: MMM-OralB / Bluetooth equipped toothbrush integration
@timodejong95 OK I have identified the source of the error.
It originated from the connectDevice function on Dongle.js
I had a wrong mac address for the brush which leads to an unresolved promise.
Good luck finding the promise :smiling_face_with_open_mouth_smiling_eyes:
(I love/hate promises…)Correcting the mac address I get new unresolved rejection errors.
[11:54:35.940] [LOG] 11:54:35 <log> Retrying Dirks OralB 2/3 (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Device.js:42 Promise) [11:54:35.964] [ERROR] 11:54:35 <error> (node:23373) UnhandledPromiseRejectionWarning: Software caused connection abort (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:54:35.970] [ERROR] 11:54:35 <error> (node:23373) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:54:35.975] [ERROR] 11:54:35 <error> (node:23373) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:55:16.260] [LOG] 11:55:16 <log> Retrying Dirks OralB 3/3 (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Device.js:42 Promise) [11:55:16.275] [ERROR] 11:55:16 <error> (node:23373) UnhandledPromiseRejectionWarning: Software caused connection abort (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:55:16.279] [ERROR] 11:55:16 <error> (node:23373) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2) (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:55:56.582] [ERROR] 11:55:56 <error> (node:23373) UnhandledPromiseRejectionWarning: Error: Couldn't connect to Dirks OralB after 4 tries. at Promise (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Device.js:46:16) at new Promise (<anonymous>) at tryConnect (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Device.js:40:14) at Object.iFace.Connect (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Device.js:56:13) at EventEmitter.<anonymous> (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/dbus-native/lib/bus.js:140:19) at EventEmitter.emit (events.js:187:15) at /home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/dbus-native/index.js:106:14 at Socket.<anonymous> (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/dbus-native/lib/message.js:55:9) at Socket.emit (events.js:182:13) at emitReadable_ (_stream_readable.js:540:12) (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:55:56.588] [ERROR] 11:55:56 <error> (node:23373) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3) (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:55:56.593] [ERROR] 11:55:56 <error> (node:23373) UnhandledPromiseRejectionWarning: Software caused connection abort (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:55:56.599] [ERROR] 11:55:56 <error> (node:23373) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4) (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)
So… Software caused connection abort. Don’t know what that means unfortunately. Guess I need to learn a bit more about the connection process. But I get the feeling that this module is a bit too complex for just using with my toothbrush.
Let me know if you know my problem. -
RE: MMM-OralB / Bluetooth equipped toothbrush integration
@timodejong95 that’s rather difficult for me juggling with family, (home) office and several other things I have to say. Will think about this and let you know.
I have worked successfully with bluetoothctl and noble (npm).
Both were able to connect to the brush.
With bluetoothctl I got a constant stream of the manufacturer data that contains some info. (see above)
I used that straight from the console. -
RE: MMM-OralB / Bluetooth equipped toothbrush integration
OK I have a first error message
[15:04:46.174] [ERROR] 15:04:46 <error> (node:1454) UnhandledPromiseRejectionWarning: Error: No such interface found at /home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/dbus-native/lib/introspect.js:31:23 at Parser.<anonymous> (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/xml2js/lib/parser.js:304:18) at Parser.emit (events.js:182:13) at SAXParser.onclosetag (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/xml2js/lib/parser.js:262:26) at emit (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/sax/lib/sax.js:624:35) at emitNode (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/sax/lib/sax.js:629:5) at closeTag (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/sax/lib/sax.js:889:7) at SAXParser.write (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/sax/lib/sax.js:1436:13) at Parser.exports.Parser.Parser.parseString (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/xml2js/lib/parser.js:323:31) at Parser.parseString (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/xml2js/lib/parser.js:5:59) (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)
no Toothbrush activated yet. Only started the mirror with npm start dev.
Running on a RasPi 3b w/ on-board bluetooth -
RE: MMM-OralB / Bluetooth equipped toothbrush integration
@lavolp3 Also mentioning in the Readme that
npm install
is necessary would be helpful