even my RP3 works great I have also tested it with RP4 8GB ram. Blazing fast.
Did the 3 only have 1GB ram? That's all I can find on their site...guessing if I went with the RP4 4gb that should cover me for other projects too if I want to repurpose it or give docker a shot 
I will probably toss it into a VM tonight and give it a spin!
I've been watching to see how it goes, only holdup has been not having a pi to run it on but I've been debating getting one for a while anyway. Are you thinking of pulling the plug or just wondering how much interest is out there?
@good.looking.blues you probably want npm installed first here:
sudo npm install -g node-gyp
echo -e "\e[1;45m Installing NPM \e[0m"
sudo apt install npm -y
echo -e "\e[1;45m Installing pm2 \e[0m"
sudo npm install pm2 -gNot pulling the plug. Just interested what people think of it. It's kinda inspiring to see how a hobby project becomes useful to smbdy else.
2 Likes
I actually should remove npm at all. It's a leftover from the dev process. At that point it's installed anyway. I will tweak it later down the line, thanks for noticing 
Ok cool, I just ordered the Pi and assuming time works out should have this set up next week at some point At least based on screenshots etc, I'm very interested to see it myself.
When did it get installed? I didn't see it elsewhere in the script .... unless nvm installs it now (it never used to).
(Just getting my head round what's required for a Dockerfile)
Probably node installs it. In any case up to the point it reaches this line - npm is already installed.
I am - but just playing / learning at the moment.
1 Like
Saw someone with the same error earlier Screen Shot 2021-03-16 at 8.48.08 PM|690x439 but I ran into the same issue using the latest build (1.2.1) ...any ideas on how to get around this?
Also, thanks for putting this together - Excited to get it working
My RPi will be delivered tomorrow and then I will be loading it with Hubidash. I can't wait to try it out and see what it can do. Thank you very much for making this available and I look forward to see what comes next. I would like to see Hubitat Safety Monitor tiles become available.
Most probably instructions where poorly followed at the stage of modifying two key files - .env and monogDB-setup.js.
Tried it again following instructions modifying both .env and mongoDB-setup.js.
Two errors i noticed during the install
- This command 'sudo cp -f mongod.conf ../../etc/mongod.conf' generated the following response
"cp: cannot create regular file '../../etc/mongod.conf': No such file or directory"
I tweaked the command to 'sudo cp -f mongod.conf ../../../etc/mongod.conf' and i believe it worked
- During the Hubidash package install I got the following error:
node-pre-gyp ERR! install response status 404 Not Found on https://github.com/kelektiv/node.bcrypt.js/releases/download/v5.0.1/bcrypt_lib-v5.0.1-napi-v3-linux-arm64-glibc.tar.gz
I ran the following command
"sudo apt-get install -y build-essential python"
and then re-ran
"
(cd ./server/ ; npm install)
"
and it seemed to clear
Anyway not sure if these are related but I figured it might be worth mentioning.
My set up is an RPi3 Model B with no WiFi
Weird, since I have tested the script on fresh RPis 3 and 4 and none of them had the issues you mention. But I will add that line to the script. Will not hurt.
And regarding the mongod - it might mean that you have tried to change the structure of folders to something other than in Installation Tutorial.
I have this dockerised in a container with just node.js (I already had mongo running, also dockerised).
It's really nice looking and very fast!
I appreciate docker isn't the intended platform, so are there any debug / verbose logging files that I can view so I can troubleshoot any issues from that side?
For example I assume it should real-time update device status but it doesn't so far, could be some ports need mapping or something I missed in creating the container. Does Hubidash use the Hubitat eventsocket or Maker API post for status updates?
I accidentally deleted the part where I have explained how to tweak the Hubitat to work with Hubidash. I'll bring it back soon. But generally - you need to point your Maker API to send post events to Hubidash server (don't forget the port)
the section is now back online at the bottom of the page:
http://www.hubidash.com/installation#hubitat
That's great, all seems to be working now.
Currently pointing it at my development Hubitat, if I point it at one of my other Hubitats in the future do I need to clear the current hubidash database first?
From a docker perspective, other than the .env file, is everything in the hubidash folder expendable? So to update to a new version, I can just rebuild my docker image with the latest hubidash .zip file?
