MagicMirror Pimatic (Home Automation) Dashboard

[Mr.Sponti]

@binderth
as @sero mentioned, the Advantage over the socket-API is that you get live events, if something in pimatic changes.
In addition I use the “MMM-REST” (push) module for displaying selected status messages in case a specific pimatic rule is fullfilled.

[binderth]

@sero said in MagicMirror Pimatic (Home Automation) Dashboard:

@binderth
When using REST you need to poll / ask pimatic for updated values in a regular interval. With WebSockets pimatic can push changed values. This is less overhead and minimizes delays.

@Mr.Sponti said in MagicMirror Pimatic (Home Automation) Dashboard:

@binderth
as @sero mentioned, the Advantage over the socket-API is that you get live events, if something in pimatic changes.
In addition I use the “MMM-REST” (push) module for displaying selected status messages in case a specific pimatic rule is fullfilled.

Thanks for the update. So, I think, I’ll do the same for my openHAB items, as openHAB can also push item changes through an API to MM. oh, I love challenges, since I never had done something in node.js! ;)

[shgmongohh]

Hi,

Nice mirror. Could you please provide your Module? I want to use it for my own pimatic controller.

Thank you in advance.

Sebastian.

[Mr.Sponti]

@shgmongohh - Unfortunately I’m neither familiar with git nor with javascript or web style sheets. Based on my old school programming skills from the early eighties I studied several moduls and created 2 new moduls.

The first one connect to pimatic via the WebSocket API and receives on device attribute changes all new values which I compare to device attribute definitions placed in the magic mirror config.js. If a device mach the new attribute, it is shown in the notification board (similar and based on modul MMM-DWD-WarnWeather by LukeSkywalker92). My modul also consist on 3 files:

Pimatic Notification Borad:

• MMM-Pimatic.js
• node_helper.js
• MMM-Pimatic.css
• icons/icons-pimatic.png

The second modul displays temperature devices and consists of 2 files and requires that the first modul is running, as it receives the pimatic attribute changes from the node-helper of the first modul by waiting on “notificationReceived”.

Pimatic Temperature Devices:

• MMM-M2-Pimatic.css
• MMM-M2-Pimatic.js

If someone could create the git repository and crosscheck the code I can provide the files by sending a zip.archiv.

I would be glad to see additional ideas/moduls dealing with pimatic.

[Zinkeler]

Hello,
please can someone tell me how i can install MagicMirror and Pimatic together.
If i install MagicMirror then i can´t install pimatic (needs a lower version of node).
If i install pimatic then i cant´t install MagicMirror (needs a higher version of node).
:-(
For MagicMirror i used the latest version.
For Pimatic is used the latest version.
For Raspberry i installed Raspberry stretch

[Mr.Sponti]

@Zinkeler - Sorry, but I can’t help here. I’m running 2 pi’s with separate installations of pimatic and MagicMirror. The first Raspberry hosts pimatic including several interfaces (Homeduino, MySensors, arexx temperature logger) and the second is mounted behind a HDMI Monitor hanging at the wall of my diningroom.

[Zinkeler]

@Mr.Sponti - thank you for your answer.
I now setup a second PI and installed Pimatic.
On both PI´s i installd socket.io and socket.io-Client.
My second pi works fine with pimatic and my first Pi works with MagicMirror.
I installed your modul as you described.

If i run a test on my MagicMirror-PI:

pi@raspberrypi3:~ $ node testpim.js
connected
[ { id: 'temperatur',
    name: 'Temperatur',
    template: 'device',
    attributes: [ [Object], [Object] ],
    actions: [],
    config:
     { class: 'HomeduinoRFWeatherStation',
       protocols: [Object],
       values: [Object],
       processingTemp: '$value',
       processingHum: '$value',
       xAttributeOptions: [],
       id: 'temperatur',
       name: 'Temperatur' },
...```
i see, that socket works too.
But on my MagicMirror is only get the message "Connecting to pimatic ..." 
 config.js:
*{
            module: 'MMM-M1-Pimatic',
            position: 'bottom_center',
            header: 'PIMATIC',
            host : 'xxx.xxx.xxx.xx',
            port : 80,
            user : 'user',
            passwd : 'passwort',
            config: {
                device: [
                    { 
                        name: 'Schrankschalter',
                        icon: 'icon-Default',
                        attributeName: 'schrankschalter.state',
                        defaultValue: false,
                        notification : 'Eingeschaltet'
                    },
                ],
            },
        },*
What am i doing wrong??
Thanks
P.S. are you german, because than it´s easier to talk about :-)

[yawns]

Ich weiß, dass github in der Readme genau das zeigt, was du probierst, aber meiner Meinung nach ist das falsch.

{
            module: 'MMM-M1-Pimatic',
            position: 'bottom_center',
            header: 'PIMATIC',
            config: {
                host : 'xxx.xxx.xxx.xx',
                port : 80,
                user : 'user',
                passwd : 'passwort',
                device: [
                    { 
                        name: 'Schrankschalter',
                        icon: 'icon-Default',
                        attributeName: 'schrankschalter.state',
                        defaultValue: false,
                        notification : 'Eingeschaltet'
                    },
                ],
            },
        }

Meiner Meinung nach müssen host, port, user und passwd in den config Bereich.

[Zinkeler]

@yawns
Vielen Dank !!
Genau das war das Problem, jetzt klappte es :-)

[Peter]

Who can help me with this?
I am running MM on one RPI and Pimatic on another one.
But I have no idea how to get the information of Pimatic on the MM screen.
If somebody can tell me what to install where …
Thanks in advance!
Peter