-
Notifications
You must be signed in to change notification settings - Fork 394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
False Not Enacted in Nightscout with Dev 0.6.0-dev #637
Comments
What does the pump-loop.log run look like? |
We experience the same error on the 0.6.0-dev and cob-aware-autosens branches. Nightscout works fine with all other branches. Boluses and basal rates are uploaded without any issues. |
I think I may have found a possible cause. In the mlab devicestatus entries the word "received" is spelt differently in the enacted-section. |
There is a dependency on a new version of openaps that fixes the spelling. Did you reinstall and re-run oref0-setup? I believe it will upgrade |
I reflashed the rig to jubilinux 0.2.0, installed the current master, switched to 0.6.0-dev and did npm run global-install and then re-ran oref0-setup. 0.5.3-entries containing the wrong spelling "recieved" work fine. Could the correct spelling "received" be the problem because Nightscout does not parse it? |
Can also confirm this bug, on a fresly installed jubilinux 0.1.1 with 0.6.0-dev rig (installed with oref0-setup and
|
Changing the spelling back to "recieved" in enacted.json leads to a correct "Enacted" display on Nightscout. |
Found the problem in Nightscout: I can make a PR to Nightscout later this week or this weekend (including adding a test to |
The fix has now been merged into the Nightscout dev branch. I think this issue can be closed. |
It is not fixed in Dev for me. The issue is still there. |
You are running OpenAPS 0.6.0-dev and updated your Nightscout to the latest dev version less than 7 days ago and still get the "Not enacted" message in the OpenAPS pill in Nightscout although the rig is looping without any problems? |
Could you post an mLab devicestatus entry that should display as enacted but does not? |
@ELUTE It's fixed in Nightscout, not in oref0. Did you upgrade your Nightscout to the dev branch? |
If you could copy and paste the text I could paste it into my database and see what happens. |
@PieterGit I have always used Dev. I am running the latest commit |
Apologies. My computer was caching. I will close now as it is resolved. |
Nightscout reporting not enacted but rig is working. Only started when updated to 0.6.0-dev
The text was updated successfully, but these errors were encountered: