MMM-NewPIR v3

[bdream]

Hi @Bugsounet just going to install your module with deep hope in it’s functionality.
I’m going to use it on an Pi0 and get (now two times) an Network error: Software caused connection aborton Putty while npm install

Here all I get in console:

pi@RasPiZeroW:~/MagicMirror/modules/MMM-NewPIR $ npm install
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported

> epoll@4.0.0 install /home/pi/MagicMirror/modules/MMM-NewPIR/node_modules/epoll
> node-gyp rebuild

make: Verzeichnis „/home/pi/MagicMirror/modules/MMM-NewPIR/node_modules/epoll/build“ wird betreten
  CXX(target) Release/obj.target/epoll/src/epoll.o

Any idea, or is it caused on the hardware of RPi0?

I tried to start again and deleted all MMM-NewPIR stuff and rebootet RPi.
New attempt git clone and npm install

Getting this in coonsole:

pi@RasPiZeroW:~/MagicMirror/modules/MMM-NewPIR $ npm install
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported

> epoll@4.0.0 install /home/pi/MagicMirror/modules/MMM-NewPIR/node_modules/epoll
> node-gyp rebuild

make: Verzeichnis „/home/pi/MagicMirror/modules/MMM-NewPIR/node_modules/epoll/build“ wird betreten
  CXX(target) Release/obj.target/epoll/src/epoll.o
  SOLINK_MODULE(target) Release/obj.target/epoll.node
  COPY Release/epoll.node
make: Verzeichnis „/home/pi/MagicMirror/modules/MMM-NewPIR/node_modules/epoll/build“ wird verlassen

> @bugsounet/pir@1.0.4 postinstall /home/pi/MagicMirror/modules/MMM-NewPIR/node_modules/@bugsounet/pir
> electron-rebuild

⠸ Building module: epoll, Completed: 0

and status ⠸ Building module: epoll, Completed: 0 is not changing colpetition even it run and run.

So I assume it’s really related to RPi0 installation and electron. But that is to deep for my small knowledge selfsolving if possible anyway.

[Fozi]

Thanks for this new PIR module! I replaced last night the MMM-PIR-sensor module with yours and it works perfectly, also with my microwave sensor.
Especially the behaviour after the first start is now as expected, as the display is switches off after the countdown, without initializing the sensor first. With MMM-PIR-sensor the display would have stayed on after the first start until the sensor catches once a motion and the start the coutdown. I tweaked the node_helper.js to correct that, but after each module update I had to reapply that tweek. That belongs now to the past. Great job!:clapping_hands_light_skin_tone:

I have a feature request:
I would like to have two configuration options available to adjust the colours of “displayStyle”, as currently it is hardcoded in green:

• One option to adjust the colour of the remaining time (wich is currently green).
• Another option to adjust the colour of the past time (currently dark grey or white).

something like this:

displayStyleRemaining: 'e2e2e2', //RGB value of the remaining time
displayStylePast: '454545', //RGB value of the past time
[...]

I’m using the “Bar” style on “bottom_bar” position, which shows a decent thin line over the hole width of the mirror, which slowly creeps down to the left. But it is hard to distinguish the remaining time (green) and the past time (white) of that bar. I would prefer to adjust the remaining time to white, and the past time to black, as an example.

What do you think?

Oh BTW: I might help other users, if you enhance a little bit the README on GitHub on how to make the display styles visible. It took me some trials until I found out to configure an empty string for the “text” option to make the other styles show up.

[A Former User]

@bdream :

> @bugsounet/pir@1.0.4 postinstall /home/pi/MagicMirror/modules/MMM-NewPIR/node_modules/@bugsounet/pir
> electron-rebuild

⠸ Building module: epoll, Completed: 0

it’s a very very long processing for a pi0 but needed …
I never try with it, i don’t know how time it can take (and if it’s works !)

@Fozi : thanks for you feedback !
NP v3 is result of a lot of works ;)
First it’s part of code from another module (Assistant2Display).
NP v3 is make for user who don’t want (don’t use or don’t know) to use GoogleAssistant/Assistant2Display
I port it to NP v3 with my own npm library (less code and sync all code for all my modules)
I have to code the new feature from Assistant2Display (Last Presence display) to NV v3

If you want you can do a Pull request do add your wanted feature ;)
if you want to do it, you can make it in dev branch (for temp code and developping) and not in master (only for releasing)
So Pull request is welcome :)

[Fozi]

Well, that means I‘ll have get much much deeper into coding and learn js. But hey, why not? Cold and dark autumn is coming and that’ll be a nice project 🤗

[A Former User]

the hardest part is to anticipate the slightest possible error so as not to crash everything (and even crash MM)

If you can’t do it, i will do it soon :)
I finish other new module before ;)

so planned to this module:

• Last presence
• color feature
• HDMI CEC support

[bdream]

@Bugsounet don’t know how time it can take (and if it’s works !)
After a couple of trys it run to end but in time including MMM-NewPIR into config (smallest example or within many configurations…) mirror give error as config not available.

I hang it up an the RPi0

Will try it soon on an RPi3B as I feel this is a great module. - thanks for providing!

[A Former User]

memory less in pi0, so it’s difficult to do complex think with it

[hweigel]

Hi Cedric,

I’ve received an update notification for this module, but something must have happened on Github:

pi@MagicMirror:~/MagicMirror/modules/MMM-NewPIR $ git pull
Username for 'https://github.com': XXX.YYY@gmail.com
Password for 'https://helmut.weigel@gmail.com@github.com':
remote: Repository not found.
fatal: repository 'https://github.com/bugsounet/MMM-NewPIR.git/' not found

Please advise.
.
.
.

[dvbit]

currently all modules developed by bougsounet are offline due to some issue with MM project founder.
If you want them to go back online please invite the MM project owner, michmich, to have a dialogue.

[dvbit]

that is go here and ask for open dialogue https://github.com/MichMich/MagicMirror/issues/2130

[rejas]

I do not think that this issue in github is the correct place to have a dialogue about this topic. Either have it here in the forum or create a new issue there, but dont put non-issue related discussions into tickets.

[dvbit]

Yes you are right. I would just like dialogue to start.

[A Former User]

@rejas : LOL ! :clapping_hands: :clapping_hands: :clapping_hands:

No dialogue possible, so I decide to BAN all my module when using original MagicMirror app

I will recode another MagicMirror (with change !)
After … it will be the user’s choice … follow me or not !

See : There

@rejas : make as you want … you can BAN me if you want :)
it’s not a problem for me !

I do ANY of my module for me in first ! so it’s not a problem ;)
as long as it works for me, I don’t care!
I just share my work

so :zipper-mouth_face: !!!

[rejas]

@dvbit as you can see there isn’t a dialogue possible with bugsounet. Even though @michmich made a step forward to him and had his PR merged he still wants to make his own version of MM with some secure stuff to not allow other users to run his modules on the original code. Not to mention his signature.

Tell me @dvbit, is that a person you want to work with or where you want to trust your your personal data that you put into the Google-Assistant module of his? I sure don’t and thats my choice in the OpenSource world. As is his choice to behave like that.

Don’t forget, it was @MichMich that did all the work before that, starting Magic@Miror, doing the forums, maintaining the code. He is still around and is open for discussion and ideas. That’s the kind of person I want to work with and where I want to put my efforts into that.

[Fozi]

I’ve been a few days of and ran through my timelines and found this dispute here and on GitHub and must say I feel kind of sad and disappointed. Since the day I joint this community nearly a year ago it always felt like home. Everybody was helpful and patient, I always felt mutual respect and appreciation. Not to mention all those fantastic contributors with their modules and programming skills and those with various other knowledge they happily share. While I can understand @Bugsounet for waiting for @MichMich response quite some time and his engagement, I also see MichMich point which he laid out on GitHub. I don’t know what both have exchanged on other, private, channels but I can’t understand why such a dispute leads to such a extreme reaction. In the end it is the community that gets punished, when great modules are withdrawn and support is ceased. That’s sad!
As @Bugsounet is insistently not willing to contribute any more and to support, I have no other choice than to drop this module here and return to the old one. It is really a pitty and I do this very heavy hearted but travelers shouldn’t be halted.
I wish you all the best and great success with your own fork -I say this absolutely honestly- but still hope to see you here around again one day.

[A Former User]

@Fozi No one know my problem with mich. (hein rejas, so stop tell bad things)

So, I will recode another MagicMirror system… After it will be user choice… Fallow me in the new adventure with all @bugsounet module or… Mich Migic mirror without Any of my modules

Actually I do a mix of npm library and my magic mirror app (personal… I have to replace all patch of MagicMirror corrected…)

[A Former User]

@Bugsounet said in MMM-NewPIR v3:

the hardest part is to anticipate the slightest possible error so as not to crash everything (and even crash MM)

If you can’t do it, i will do it soon :)
I finish other new module before ;)

so planned to this module:

• Last presence
• color feature
• HDMI CEC support

under coding :)

[A Former User]

V3.1.0 is out !

• added : HDMI CEC support and other mode for turn on/off your screen

mode: 1 - use vgencmd (RPI only)
mode: 2 - use dpms (version RPI)
mode: 3 - use tvservice (RPI only)
mode: 4 - use HDMI CEC
mode: 5 - use dpms (linux version for debian, ubuntu, …)
mode: 0 - disabled and turnOffDisplay too

see new configuration of the screen field

• added: display last presence time
• added: auto updater script (npm run update)
• added: notify if update of npm library is available
• added: compatibility with MMM-UpdateNotification for automatic update
• deleted: configMerge script and use MM version integred (configDeepMerge: true,)

[A Former User]

v3.1.2 is out !

I have coded TouchScreen feature

TouchScreen Feature

You can use this feature with a mouse or your touch screen

• One Click on the screen: Will wake up the screen or restart your shutdown timer
• Double Click on the screen: Will turn off your screen

Edit: see next release

[A Former User]

v3.1.3 is out !

Touch Screen feature change

TouchScreen Feature

You can use this feature with a mouse or your touch screen

• One Click on the NewPIR Area: will restart your shutdown timer
• Long Click on the screen: Will turn off your screen or Will turn on if needed (Toogle)

if you want to use it:

enable useTouch feature in screen: {} field

CSS value correct

Correct a bug if no other module in the same position is set (module not displayed)

Update of @bugsounet/screen npm library

Counter will send bad value on start (lost one sec.)