@ElectronicFur Not sure what the issue is with Heroku, but once I managed to get the ES server running on Pi It retrieved the cookie on the third login attempt.
As per the above back and forth I installed it using
git clone GitHub - tonesto7/echo-speaks-server
then CD into that directory
sudo NPM install
At first I ran it with NPM start but was struggling to work out how to make it autorun on reboot and be Daemonized.
as per @Evilborg 's advice I am using PM2 to run ES as a service that persists on reboot.
sudo npm install -g pm2
when in the echo-speaks-folder run
sudo pm2 start index.js
sudo pm2 save
Then run
Sudo PM2 list
to check it's running, then run
PM2 startup
to make it run after network connection on boot.
then run:
sudo pm2 save
This should have daemonised the server as a service, and bind it to systemd startup services.
Once running you go to you PI's ip i.e 192.168.1.2:8091 , fill in the server port and callback URL from the echospeaks hubitat app config page, make sure to turn off deploy to heroku in the ES app on Hubitat and give it your local server IP (Pi IP)
