Android app for the Classic

[Resthome]

With 2.4.2 I am not getting data uploaded to PVOutput.org  Had been working previously. Have System View unchecked. Have tried the Reset button also but no luck. 5/18/16 is last data.

Do you have more than one classic on your network?

No only one.

[grgdgreek]

I have 2*cl150 in follow me if it helps
George

[Westbranch]

John, in the "ABOUT" , last screen, it says

'' The daily energy recorded can be sent ...  by supplying an API Key and SID# in the settings for each controller"... 

Is that sent and what did you use?

[Graham]

With 2.4.2 I am not getting data uploaded to PVOutput.org  Had been working previously. Have System View unchecked. Have tried the Reset button also but no luck. 5/18/16 is last data.

Do you have more than one classic on your network?

No only one.

Could you try it with System View Checked, + make sure the SID is still there,

I modified the PVOutput uploader to support multiple independent classics to support Andy's setup when the System View is unchecked
this new uploader should not be used when you have one classic, I'll have to add that condition in the code

Normally you would enable System View when you have more than one classic in follow me mode supplying one battery bank
you would disable it if you have multiple classics supplying different battery banks (Andy's setup)

If you have one classic, then the System View should be a no-op and probably hidden, which I shall fix.

[Resthome]

John, in the "ABOUT" , last screen, it says

'' The daily energy recorded can be sent ...  by supplying an API Key and SID# in the settings for each controller"... 

Is that sent and what did you use?

Yep have my own API Key and SID# from my PVout.org account. It worked with older versions, but I usually don't use it because I normally have no internet access. This weekend i'm pickin up one of the homeowners Wi-Fi for internet.

[Resthome]

With 2.4.2 I am not getting data uploaded to PVOutput.org  Had been working previously. Have System View unchecked. Have tried the Reset button also but no luck. 5/18/16 is last data.

Do you have more than one classic on your network?

No only one.

Could you try it with System View Checked, + make sure the SID is still there,

I modified the PVOutput uploader to support multiple independent classics to support Andy's setup when the System View is unchecked
this new uploader should not be used when you have one classic, I'll have to add that condition in the code

Normally you would enable System View when you have more than one classic in follow me mode supplying one battery bank
you would disable it if you have multiple classics supplying different battery banks (Andy's setup)

If you have one classic, then the System View should be a no-op and probably hidden, which I shall fix.

Yep that worked, Thanks Graham. BTW Love your app

[Graham]

Yep have my own API Key and SID# from my PVout.org account. It worked with older versions, but I usually don't use it because I normally have no internet access. This weekend i'm pickin up one of the homeowners Wi-Fi for internet.

The app has a 'Store and Forward' feature for PVOutput, when it connects to your classic it will save the day logs in a file on your device if it can't access PVOUtput.org, later, when you get home to wifi with internet access, if you let the app run for a few minutes, it will upload the day log data to PVOutput.org

[Graham]

Graham,

sorry don't work like expected

If one Tab has both found, the other finds both but can nothing do with themm.
If one has only one Classic, the other can sometimes connect to the other, but displays no alias. Then like it is now, the other show the IP in the headline and "blinks" "- (RUHEND" (what was it in english, ehm "resting") and in the gauges in the same rhythm the needles come up for a flash of a second

This could be due to the fact that the classic can only support one TCP connection at a time, if you have two devices with 'Auto Detect Classic' turned on, it might cause the problem you're experiencing since they are both trying to establish a connection the each classic.

Could you try just using one android device

just to make sure it's in the correct mode, start the app then uncheck the 'Enable System View' and check the 'Auto Detect Classics', save/apply the settings
clear out any existing entries in the nav bar by sliding them to the right
then shut down the app to make sure that setting is saved.
Then start the app again and wait a couple of minutes for the classics to be auto detected.

Let me know if this basic test works and we'll go from there.

Background Info:

The classics broadcasts a UDP packet on your local network every minute or so, this packet contains the classics IP Address and the Modbus port number
When the app has Auto Detect turned on, it will listen for this broadcast, when it gets one that is not already configured, it will display the IP address on the Nav bar and will attempt to connect to the classic, once connected, it will request the unit name by reading the modbus address 4209 ( the unit name can be set with the local app, 'Classic' by default) and replace the IP address with the unit name in the Nav bar.
When Auto Detect Classic is unchecked, you have to manually enter the classics IP address and port by pressing the +Add when the Nav Bar is in view. When the app connects to the given IPAddress, it will replace the IPAddress in the NAv Bar with the unit name as it did with Auto Detect mode.

You can also enter a Domain name instead of an IP Address, the app will then perform a DNS lookup to convert the DN to an IP Address. This is normally used when you have port forwarded your classic and have purchase a DDNS service and Domain Name registration that will resolve to your routers WAN IP address.

[binkino]

Hi Graham,

today the tab wanted to ... me.
I took the tab that displays the 48v System.

Had installed the old version version again, now updated again to the 2.4.2 version
https://youtu.be/kDkSh1J_dok
now it crashed again and again

Also rebooted the device, crashed.


It worked now, after I set:
"System view enabled" on and deactivate it after it has found the two classics.
Than remove the 2nd classic that will be displayed on the other device, so it can be displayed on the 2nd device

https://youtu.be/prB4kCKpvOg
On the 2nd device is installed the old version


(sorry cam has problem with focusing because the protective foil on the display)

[Graham]

Hi Graham,

today the tab wanted to ... me.
I took the tab that displays the 48v System.

Had installed the old version version again, now updated again to the 2.4.2 version
https://youtu.be/kDkSh1J_dok
now it crashed again and again

Also rebooted the device, crashed.


It worked now, after I set:
"System view enabled" on and deactivate it after it has found the two classics.
Than remove the 2nd classic that will be displayed on the other device, so it can be displayed on the 2nd device

https://youtu.be/prB4kCKpvOg
On the 2nd device is installed the old version


(sorry cam has problem with focusing because the protective foil on the display)

hmm, I have some work to do!

can you confirm that you didn't have PVOutput setup/enabled during the test? couldn't see the setting in the video

[binkino]

hmm, I have some work to do!

can you confirm that you didn't have PVOutput setup/enabled during the test? couldn't see the setting in the video

PVOutput was not set and not active

[Graham]

hmm, I have some work to do!

can you confirm that you didn't have PVOutput setup/enabled during the test? couldn't see the setting in the video

PVOutput was not set and not active

I fixed one issue, but I'm sure there's more...
let me know if you can connect with System View unchecked

https://www.dropbox.com/sh/z04q8hpw5ibpwfd/AACbRXpllos-IuLR6Z4pGWska?dl=0

[binkino]

Thanks, Graham

Have uninstall 2.4.2beta and install the new version
Did not crash after start,
it found both classic after start, I removed them, then go to settings and set "System View" unchecked, no problem
also testing "detect classic" un/checked = no crash
I let it find both classic, switch between them, no problem
I let the 48v classic on this device open,
and open the old version on the other device with 24v system displaying,
it works, no interferences
PVOutput is unchecked.

[Graham]

Thanks, Graham

Have uninstall 2.4.2beta and install the new version
Did not crash after start,
it found both classic after start, I removed them, then go to settings and set "System View" unchecked, no problem
also testing "detect classic" un/checked = no crash
I let it find both classic, switch between them, no problem
I let the 48v classic on this device open,
and open the old version on the other device with 24v system displaying,
it works, no interferences
PVOutput is unchecked.

Thanks Andy,

The PVOutput now has two modes,
when SystemView is checked, PVOutput is like is was before, the system energy is uploaded to one PVOutput SID/account.
when SystemView is unchecked, you can now enter a separate SID for each classic, (enter the SID while connected to a classic). The PVOutput uploader should upload the day logs for each classic to each SID/PVOutput account.
When you have one classic, the pvOutput code should default to the first mode. (still need to hide the SystemView setting when one classic is detected)

I haven't had a chance to test the second mode, hopefully I'll be able to test it this weekend when I get up to the lake with me second classic.

[ClassicCrazy]

I just loaded the newest version of app from Dropbox.
It found both of my systems and all seems to work okay - except  I don't have any loads on one of my systems and it shows Consumption 232 W which is the same as the other system which is the one that has the loads on it .

These two classics are independent of each other with their own batteries and don't share anything - both have their own Whizbang etc.

Larry