- This topic has 4 replies, 2 voices, and was last updated 7 years ago by Anonymous.
- April 28, 2015 at 1:24 am #3311MarcGuest
I am using the Example.py script as a basis without changing anything concerning the initialization or configuration since several days to log solar panels with a raspberry. When it is running it is stable. But I already had two occasions where the script only said “no mooshimeters found”. It didn’t help to reset the mooshimeter and raspberry, take out the batteries, load batteries or wait for a long time. The mooshimeter was blinking every 10s. The only way to get it running again was starting the android app to initialize and at least once I had to set current manually to 10A otherwise the python script said something like 2.3A when there was approx. 9-10A to be measured.
So is there a difference in the initialization between the Python API and the android app and is the current mode set properly?
- April 28, 2015 at 11:21 pm #3321adminKeymaster
That’s quite odd – I’ll dig in to it. Thanks for being specific.
- May 3, 2015 at 11:54 pm #3358AnonymousGuest
Hi James. today, after several days without problems, instead of “no mooshimeters found” the script stopped at “m.meter_settings.write()” which refers to line 43 in Example.py. After trying several times i gave up and had to use the android app again to make the python script work again. perhaps this helps to locate the problem.
- May 11, 2015 at 9:34 pm #3447adminKeymaster
Hi Marc –
Thank you for raising the issue! I think I found the problem. Please update your python API to the latest version from Github.
You were correct that it was an error in the initialization that would cause the meter to reboot if it had not previously been connected before. See this commit for the exact change:
- May 12, 2015 at 12:44 pm #3455AnonymousGuest
that’s great news, i installed the fix today.