Read the statement by Michael Teeuw here.
How difficult would it be to change the data an existing module receives?
- 
 @Tippon so, summary you use the app to push data to fitbit, where the existing Fitbit2 module can get the data from the existing fitbit api… 
- 
 @sdetweil That’s right, yes :) It’s ideal for me, and I have suspected ADHD, and don’t always remember to do things. I can just put the shortcut to this app next to my other health apps, and it acts as a reminder. I’ve decided to remove one of the MMM-fitbit2 default categories and replace it with a modified copy of the calorie goal category instead. The default shows the calories remaining until your calorie goal, but I also want to see how many calories I’ve consumed. I just had a quick play and it seems easy enough, but I need to make sure that it doesn’t break the existing categories too. Time for a break though, my kid’s about to get home from school, so any chance of peace and quiet is gone for the next few hours :D 
- 
 Just to double check before I break anything, if I forked the repo and replaced the installed version of MMM-Fitbit2 with my own, would I need to change anything in my config.js? I’m assuming that if I kept the same repo name it would just work, but I want to make sure. 
- 
 @Tippon no changes to config unless you added something 
- 
 @sdetweil Brilliant, thank you :) 
- 
 @sdetweil said in How difficult would it be to change the data an existing module receives?: and then cvt().fromFile(payload.tmpfile) // input xls // changed to tmpfile .subscribe((jsonObj, index) => { // handle each row })Sorry, I forgot to ask, where does this go? Does it go into the node_helper.js with the other line? 
- 
 @Tippon it goes in the node_helper. this is one way to process the csv file 
- 
 @sdetweil Thank you :) 

