Closed Telemachus1977 closed 3 years ago
I added some code in the UI to default the setpoint to the current temp if it isn't set. Additionally, I added some code so njsPC would not try to send packets with null values.
However, I'm not clear how you got into this pickle. Can you do a Packet Capture (with reset - it will give you a clean set of configuration files and back up your existing ones to the logs dir)? If it happens again, I'll be able to track it down but otherwise you seem to be getting all the right packets from the OCP.
I think what happened is instead of using the arrows to change the temp I tried typing in the desired temp. Hasn't worked well since.
Type in values are fine and we validate they are numeric in the back end.
Let us know of it is working now and if you happen to recreate this it would be interesting to see but hopefully it's okay now.
What do I need to update? The web UI or the controller?
Sorry should I delete the whole ui and reinstall it?
Do a 'git pull' on both njsPC and dashPanel. Then in your browser do a hard refresh (ctrl–f5) to ensure you have the latest dashPanel version in your browser.
Do I need to "npm i" after git pull?
Attached is a log with a reload and then attempts to change temp with heater which gives me this error screen.
EDIT:
It works fine with incognito mode or another browser. I need to find the equivalent of control- F5 for mobile chrome. Erasing cookies didn't work.
There were no new modules added so you don't need to run npm i
although it never hurts.
Clearing browser cache on mobile devices is awful. For Safari (iOS) you need to go to settings and literally erase your life. For Chrome, you have a little bit more flexibility. See link. You might want to try the cached images and files
; it should be there.
When I try to change the temperature on the heater its not working.
Log attached.
replay (1).zip
Pentair Easytouch 8 with raspberry pi zero w.
Gas heater.
I would expect changing the temp on my phone to work but it times out.