Skip to content
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

Input solarpower for the Solar²DHW function #170

Open
plutoarko opened this issue Sep 19, 2024 · 9 comments
Open

Input solarpower for the Solar²DHW function #170

plutoarko opened this issue Sep 19, 2024 · 9 comments

Comments

@plutoarko
Copy link

plutoarko commented Sep 19, 2024

Please, where can I find the input for the current solar power for the Solar²DHW function?
In which tab ?
What is the name of the node?

Thank you very much
Edit: I forgot i am using Flow version 24.03 Stable

@edterbak
Copy link
Owner

edterbak commented Sep 21, 2024

Hi, sorry for the late reply

Can you tell me if you have the P1 meter information comming in Node Red?
If so, you need to connect it in the tab WP Input:

image

When you have done this... very logicly (NOT!!) you need to go in the System > Sensor tab
Next you need to reset the sensor by clicking one the trashcan for both P1's once.
After that you need to wait until the first readings come in.
When the readings come in, y ou can select the correct topic / value in the dropdown on the left side.
See the below image:
image

After that you also need to check the tab: Solar2DHW > P1 Setup.
when sensor values come it, it can be that the values are not correct, like 1000x to large or small. You can correct it here.

It is not all that intuitive. It is the result of incremental development. But it should work in the end.

I am moving things arouund to make it easier.

@plutoarko
Copy link
Author

plutoarko commented Sep 22, 2024 via email

@edterbak
Copy link
Owner

can you put a debug node after your P1 sensor input? I want to see the data type which it is producing.
I would like to see the output of the debug node.

@plutoarko
Copy link
Author

plutoarko commented Sep 22, 2024 via email

@edterbak
Copy link
Owner

edterbak commented Sep 29, 2024

This part is kind of 'funny'

"Time": "2024-09-22T18:09:43", " ": { "vom_Netz": 5415.622, "zum_netz": 3095.9442, "mom_Leistung": 107 }}

The ," ": part seems to be breaking all logic.
if I replace the space between the quotes by something random, eg "test", then object gets a name and the values can be extracted.
"Time": "2024-09-22T18:09:43", "test": { "vom_Netz": 5415.622, "zum_netz": 3095.9442, "mom_Leistung": 107 }}

The below code works when I replace the space with 'test'.

[
    {
        "id": "9c1c469724a8c470",
        "type": "inject",
        "z": "d5fea67661261002",
        "name": "",
        "props": [
            {
                "p": "payload"
            },
            {
                "p": "topic",
                "vt": "str"
            }
        ],
        "repeat": "",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "topic": "",
        "payload": "",
        "payloadType": "date",
        "x": 1400,
        "y": 640,
        "wires": [
            [
                "8c0cb8a7de042ee3"
            ]
        ]
    },
    {
        "id": "8c0cb8a7de042ee3",
        "type": "function",
        "z": "d5fea67661261002",
        "name": "incoming message generation",
        "func": "var msg1={}\n//msg1={\"Time\": \"2024-09-22T18:09:43\", \" \": { \"vom_Netz\": 5415.622,  \"zum_netz\": 3095.9442, \"mom_Leistung\": 107 }}\nmsg1={\"Time\": \"2024-09-22T18:09:43\", \"test\": { \"vom_Netz\": 5415.622,  \"zum_netz\": 3095.9442, \"mom_Leistung\": 107 }}\nreturn msg1;\n",
        "outputs": 1,
        "timeout": 0,
        "noerr": 0,
        "initialize": "",
        "finalize": "",
        "libs": [],
        "x": 1630,
        "y": 640,
        "wires": [
            [
                "ca750540b7cb875b",
                "fb158560eb14e8e4"
            ]
        ]
    },
    {
        "id": "ca750540b7cb875b",
        "type": "debug",
        "z": "d5fea67661261002",
        "name": "debug 338",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "true",
        "targetType": "full",
        "statusVal": "",
        "statusType": "auto",
        "x": 1870,
        "y": 580,
        "wires": []
    },
    {
        "id": "fb158560eb14e8e4",
        "type": "function",
        "z": "d5fea67661261002",
        "name": "function 108",
        "func": "var msg1={};\nvar msg2={};\n\nmsg1.payload = msg.test.vom_Netz;\nmsg2.payload = msg.test.zum_netz;\n\nreturn [msg1,msg2];\n",
        "outputs": 2,
        "timeout": 0,
        "noerr": 0,
        "initialize": "",
        "finalize": "",
        "libs": [],
        "x": 1930,
        "y": 640,
        "wires": [
            [
                "a4cdcc9d04e043ce"
            ],
            [
                "245119d620efab47"
            ]
        ],
        "outputLabels": [
            "vom_Netz",
            "zum_netz"
        ]
    },
    {
        "id": "a4cdcc9d04e043ce",
        "type": "debug",
        "z": "d5fea67661261002",
        "name": "debug 339",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "false",
        "statusVal": "",
        "statusType": "auto",
        "x": 2170,
        "y": 600,
        "wires": []
    },
    {
        "id": "245119d620efab47",
        "type": "debug",
        "z": "d5fea67661261002",
        "name": "debug 340",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "false",
        "statusVal": "",
        "statusType": "auto",
        "x": 2170,
        "y": 680,
        "wires": []
    }
]

When changing back the 'test' value to the empty space " ", the same code fails.

If you can get your P sensor to produce the measurement in a proper format, I think that would help

@plutoarko
Copy link
Author

plutoarko commented Sep 29, 2024 via email

@plutoarko
Copy link
Author

plutoarko commented Sep 29, 2024 via email

@edterbak
Copy link
Owner

edterbak commented Oct 1, 2024

So the issue is now resolved?

@plutoarko
Copy link
Author

plutoarko commented Oct 3, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants