Bit of a weird one. Have had 21Jul21 running for a while now following a clean install on a new SD card.
As always with my emonPi, I install Dataplicty and use the wormhole feature to view my solar app and manage the pi remotely. Has always worked fine across multiple builds but for whatever reason (maybe a power outage but really not sure) the remote session now throws up errors accessing the app page and will not load. Clicking OK to error just results in spinning wheel.
Note: accessing my emonPi from the IP/local web interface has absolutely zero issues.
I also get errors accessing the Inputs page advising “Device already in use” but other pages seem to have no issues including Admin, Emonhub, etc. I would love to post a screenshot of the Inputs error popup, however it seems accessing the Inputs page from the remote session starts creating new and random inputs.
This ended up breaking my setup and I had to recreate the device/feeds/inputs, and I also reinstalled Dataplictiy, checked for updates, rebooted, etc. but still the same errors.
Accessing my pi page from the IP/locally has absolutely zero issues. Has me a bit stumped.
I would clear the cache on your browser. Maybe try a different browser. I have build low-write 10.5.6, and have no problems using Dataplicity with Chrome and Firefox.
@glyn.hudson any ideas?
I found a previous thread about flushing redis keys however this only broke my feeds/inputs and I had to set them up again. It resulted in no change to there being errors trying to view the emonpi web interface for apps and feeds via dataplicity despite it working perfecly via internal IP.
Trying the input/feeds pages via the wormhole creates nodes 0 and 30 magically and provides an error stating “device already in use”. Seems to also indicate feeds/inputs come to a halt…
The config error seems to be something caused by dataplicity themselves blocking the JavaScript that emoncms is trying to load. I’ve messaged dataplicity about it but haven’t heard back yet, I need to follow it up
No response from dataplicity, so I’ve gone ahead and renamed the script that was being blocked from config.js to appconf.js and pushed this to master and stable. If you update the app module it will pull in the fix.
@TrystanLea - since fixing this issue, the remote/wormhole session of my pi has been incredibly slow and occassionally times out. Local version is snappy and normal.
Any thoughts before I backup and start a fresh SD card?
