Hi Klaus,

I replied to your comment on facebook, I hope it’s useful to you. Sorry again for the trouble, best

~James

I had same kind of problem yesterday, as i tried logging with newest android beta (29).. I did not (remember/know to) disconnect from mooshimeter and logging stopped as i went out of bluetooth range.. Not sure how that would be reasonable way to behave, but after that i tried again and logging worked fine, as i remembered to disconnect.

no wait/1 sec log intervals are easy to check, as led is blinking constantly, but nothing tells us to disconnect.. So it would seem that everything is fine, but after walking away it stops.. So JAMES, THIS IS A BUG.

For excel (and in my case, libreoffice calc), i would first add “=(A9/86400)+25569+(1/24)” (which seems to give your timezone) in G9 and format G-column as date/time (like: 30.07.2016 10:08:10) and then expand those values to the end.

For actual data (which should be in B and C columns), formatting those columns to basic numbers should do the trick. If not, there is always that locale difference possibility with wrong decimal separator, so you should somehow tell excel that you are importing that csv in american english. Libreoffice does ask for that as you are opening csv:s.

@James

Just remembered what i thought when screwing with test logs yesterday.. Would it be possible to add human readable starting date+time to log headers? And to end also, when done the right way by stopping from app before ripping memorycard out..

And for added bonus, that formula with correct timezone for quick starts and less hussle for new users..

BRA-KB, Sorry I probably cant help since I don’t have a IOS device. In android, there is a setting (top right gear symbol) which allows a setting of Auto-connect if the meter and phone get disconnected. This seems to help.

James, ville sparked an interesting question in my mind. How do you [gracefully] stop the app? For example. if sound is on (speaking meter readings), then none of the exit buttons will stop the app nor stop the BLE connection. This is not necessarily a bad thing, maybe even desirable in many situations, how is the app stopped if desired? And should there be a way to BLE disconnect separate from app stop? Not a big issue for me since I can use android force stop or android turn bluetooth off, but I thought it might be related to the posts here. – — Duane

I have “autoconnect” switched off and i manually connect and disconnect in meter selection screen by pushing plug-symbols. It does disconnect while speaking values etc.. Only times i had to really kill the app, is after updates, if i cant connect. Then (on my oneplus two) it is enough to swipe mooshi-app off from “multitasking” menu (not sure what to call it in english, but there is home, back and that multitask-button in android phones)

I somehow knew that i should be disconnecting from mooshimeter while logging, if i remember right, at some point every sample got written to memorycard when app was connected and only after disconnection was set intervals applied. Now user selected interval is used from the start, but now the problem seems to be that we all forget to disconnect and that, in my opinion, should happen automatically, not matter what we do..

Finnish and english, sorry.. I thought at 90’s that i understand german as i watched so much viva music channels, but for real, i do not understand a thing :D

Sorry I didn’t get to this thread sooner – there are a lot of questions in the last 24 hours.

ville: no wait/1 sec log intervals are easy to check, as led is blinking constantly, but nothing tells us to disconnect.. So it would seem that everything is fine, but after walking away it stops.. So JAMES, THIS IS A BUG.

Can you confirm what firmware version you’re running? If the LED is blinking constantly, I suspect you are a few firmware versions behind, as the LED has become more sensible in later versions. The latest firmware version (available to the beta) is 1469410939. I’ve been working on logging reliability specifically in the last few firmware updates. Log settings are now saved to non-volatile memory so that even if the device is rebooted, logging will resume.

ville: Would it be possible to add human readable starting date+time to log headers? And to end also, when done the right way by stopping from app before ripping memorycard out..

Yes, I will add this to the feature list. Epoch timestamps are so second nature to me now I forget the perspective of users who have not worked with them before. It should not be hard to add a human readable stamp at the beginning of the file because the Mooshimeter already does this calculation (year, month, date, hour, etc.) for the filesystem timestamp, which is in a human readable format.

Duane: How do you [gracefully] stop the app? For example. if sound is on (speaking meter readings), then none of the exit buttons will stop the app nor stop the BLE connection. This is not necessarily a bad thing, maybe even desirable in many situations, how is the app stopped if desired? And should there be a way to BLE disconnect separate from app stop?

If I need to manually close the app I use the native iOS/Android method of doing so. It’s a double press of the home button or something like that… it brings up the task switcher. I very rarely have to do this though… never in iOS, sometimes in Android when the bluetooth stack crashes. Maybe I will add this as a button in the global settings menu, it’s a single system call to close the app so not too hard.

99% of the time, I just press the home button and let the app fall in to the background. Leaving the sound on in that state is deliberate to make multitasking easier. I think this is closer to the accepted idiom for smartphone app lifecycle. You can manually disconnect the BLE connection by pressing the connection icon of the connected meter in the scan screen. If you let the connection fail naturally (leave it connected and walk away from the meter) that’s fine too*

*ville I did not forget your report above about walking away and finding it caused logging to fail. I will wait for confirmation on your firmware version so I know where to look though.

Regarding autoconnect feature: When active, this causes the app to automatically connect to the meter if it’s detected in a scan. The idea is that almost all users have only a single meter, and will close the app by just pressing the home button and putting the phone in their pocket. With auto-connect on, it means all they have to do is open the app again and the device will start scanning, then connect to their meter

Regarding documentation in general: I’m transitioning to a wiki for documentation, as it’s much easier to maintain than a collection of PDFs and wordpress pages. I am working on it now, it’s here: moosh.im/wiki . It’s still a skeleton but if you have thoughts on the evolving structure, I welcome your feedback and contributions.

Thank you again, let me know if I missed anything. Best
~James

James,
Wow. Looks like the wiki will be very nice once populated. Thanks for sharing with us.
— Duane

“walking away stopped logging”

build: 1469410939
app: 29 (android beta)

I set up logging, just ac voltage with 1 sec intervals for test, left meter alone and went to eat for half an hour or so. When i got back to mooshimeter, realized that led is not blinking like it did when i left* –> open app –> (if it had been on at this time) “stop” logging –> card out –> only couple minutes from start had been saved.

* – Might be my mistake, your former blink-rate help-page says that led triple blinks when data is recorded, is that when sample is taken or when few of those values are written to a card. Or is there any difference? After all, most of us are not native english speakers, so we get very easily of the track ;)

And i should be going to work by now..

I agree with ville. Set up same configuration build: 1469410939, app: 29. I used two meters and two android phones, both android 5. Android displays set to never turn off. Used two different brand of SD cards and in fact the same cards I have used in the meter in the past. Did not move the meters or the phones.

Started logging at 1s rate, metering page active. One app went back to scan page after 4 minutes and the other app after about an hour. Both meters blink changed to double blink every 10s.

Restarted one meter (4s meter) again same configuration. A few hours later when I checked, I found logging turned off. The SD card log shows it stopped logging after 1.5 hours.

I have restarted the other meter (the 1 hour one), but this time I set logging interval at 10s. It appears to still be logging after close to 4 hours.
—- Duane

@Duane

There is one big difference in our logging setups.. I use my primary phone for setting up mooshimeter and (if i remember ;) ) disconnect from mooshimeter and took my phone with me when leaving my meter to do its thing.

That is why i thought that logging stopped as i got out of bluetooth range.

Still, these symptoms might be related. And my next attempt just after that failed one went fine.. But that time i disconnected and logged only for an hour or something.

ville, thanks for the clarification. I misunderstood your previous post. Yes as you probably know, here in the USA we can get pre-paid phones real cheap $10 or less (the carrier doesn’t matter since I don’t activate the cell coverage), so it is very easy for me to dedicate a phone to a meter and not use my main phone. I’m glad I ran the tests because it shows the logging stops even when the phone/meters are not separated. I don’t understand since it was pretty stable in previous versions. It is very good that folks from all over the world can all compare our experience here to hopefully make this better. Thanks to BRA-KB for starting us out on this thread.

Additionally, the meter I restarted with logging set at 10s finally stopped logging after about 5 hours, went back to scan page, and blink is 2 blinks every 10s.

I restarted the original 4s meter with logging every 10s. After 1.5 hours, I found the app metering page changed to logging off, and the meter was blinking at 1 per second.
– – – Duane

Thanks for the details guys. Good news is that I can reproduce the issue I think you’re seeing – staying connected while streaming AC, while logging at 1s intervals, seems to cause a failure after X minutes where X is variable.

I haven’t figured it out yet though. This one is very tough…

Hi BRA-KB,

I had not seen Ingo’s CSV viewer before, thank you. I added it as another useful tool to the wiki.

Before I left my office to work on the next Mooshimeter manufacturing run (Aug. 8), I spent a few days reproducing the bugs outlined in this thread and trying to fix them. I think I accomplished that with firmware release 1470628829. Thank you for the detailed reports, they really helped.

Regarding the list of features:
I’ve added most of these to the feature list. I’ll be working on documentation improvement and hunting the last few bugs in the last release before moving on to new content, but I just wanted to let you know I heard you.

Thanks!
~James