Node Red Fragen

[multimedia]

I’m happy to see your discussion here

[PhilW]

Massimo,

I could give you a login (siteID&APIKey) tomorrow if we didn't solve it.
As I said there's a limit of 300 request on the solaredge monitor side and I did a lot today ;-), and the last 3 days I exeeded this.
If I stress the account to much they say tey'll close the account complete. In parallel I'll try to go via a modbusTCP node directly to the inverter, but this is a little bit more complicated (for me) yet.


Result of your node:
11.PNG
10.PNG

[TheMax74]

Phil,
i don't want you to be banned from solaredge.
The debug log shows that all objects are fine, all properties as well. The payload 0.57 is also fine.
On my end, i tried the full morning to reproduce the problem, but the node always sent the payload, never hat issues.
I suggest you to try to change the DPT to 14.056 (the correct DPT).

Is your Inverter having a webpage where you can view the power consumption etc? If yes, you can grab the data from here, like me.
Try to point your browser here http://userassword@192.168.0.40/v1/livedata (change the IP address with the IP of your inverter, and "user" and "password" with the username and password you use to login into the webpage of your inverter, if any).

PS: the "face" you see, are in reality the characters : followed by p

We'll try tomorrow.
If you wish, i can send you my enertex IP Interface to do some tests.

[PhilW]

Changed everything to 14.056 = same result
I couldn't really imagine it either, because the difference is only the byte size between 9.024 and 14.056 behind the comma (4- or 2- byte floating point). But both are power.
Also that it sometimes works would speak against a fundamental error

That is more or less the Info (more the metadata) off the Inverter sent to the solarEdge Monitoring Portal. I connect to this thru the API.
I found nothing in the web for a direct connect. The only direct way is ModBusTCP but as I said it costs a little bit more mental exercise for me.

So thx for your help so far, I'll test some more things, maybe I'll get the answer somehow...

[TheMax74]

Again, if you wish i can send you my ip interface. If it works, you can then return it to me.
Otherwise i’ll find a proServ to make some tests for you.

If able, please try with other knx node, for example knxjs or kneasy and let me know.

About solar, if your inverter has a web interface, you can grab the values from it. It’s only matter of working with some js code. Maybe can i help you darüber.

[PhilW]

'll try to change to a peaknx IP-Router tomorrow and keep you posted.

Thx for your offer to help. One after th other... I've a little brain-overflow and need a pause

[TheMax74]

I know the brain-overflow!
Bitte prüfen und sage mir. Das ist sehr wichtig, da ich absolut keine Probleme von diesem knxultimate node gehabt habe. Schoenes Wochenende. Danke.

[PhilW]

SOOOOOO!!!
It didn't leave me alone. I still had an ISE RemoteConnect that is capable of multicast and I connected it.
In the Ultimate node enter the multicast address 224.0.23.10 and !! there It goes directly without "write" interruption.
The values are all written correctly. So it is (as you said) somehow due to the router or the interface.
So Massimo, your KNX-Ultimate node is rehabilitated

multimedia your turn
Still strange that it is only with some values/adresses and somtimes it works...

[TheMax74]

Thanks Phil. You saved my day!
I was really concerned!
Good to hear!
My offer about solar inverter web page grab is still open!
Cheers!

[PhilW]

TheMax74 Good Morning Massimo,

because of the fact that I don't put the ise Remote IP-Router permanent in my system, I tested the whole morning a little bit.

Probably the communication speed for an IP interface is somehow too fast or the packets get stuck somewhere. Of course I don't know why. But I can always understand that two values work at the same time. As soon as a third value is added in any form, one command gets stuck in the "write". I can "provoke" this again and again. Would it be an idea for systems without a router to include a small "WaitState" in your node?

Thanks for your "grabing offer", as i said before, at solaredge there is no simple webpage you can grab something with http://user: pass... You get a SiteID and an APIKey to access the data: This is normally sufficient, but with the 300 pull limitation and of course the data is not realtime. That's why I'll try the ModbusTCP directly at the inverter later.

[TheMax74]

Hello Phil
the node already has 4 times the reccommended minimum delay between telegrams.
You can maybe install a knxjs node or the knxeasy node and do some tests.

I've the node in my system up and running for over a year, with many transmission per seconds. I've tested that with IP Router (i have 1 Eibmarkt IP Router + 1 Enertex secure IP Router) and two IP Interfaces (one old Siemens, dead, and one Enertex IP Interface).
As stated before, the IP Interface mimics the TCP stack, but in reality it does all in UDP. If you have some glitches in your LAN routing, or for example a multicast storm protection, or a ddos protection active on the router or on a switch, you can have communication issues.
If you can, you should connect your proServ interface, directly to your PC, or you can use a spare switch to do some tests.
Doing the "ip interfacing" between TP cable and Eth LAN is an hard work and i highly recommend to use a dedicated piece of hardware (IP Router or IP Interface).
Those are "setup and forget" devices. The reliability is way too important. Do it, now.
You can buy an IP router on Amazon and eventually return it, but i'm pretty sure, you wouldn't.

[TheMax74]

PS: Phil, you can use this delay, to delay each telegram

[{"id":"faaf24d6.0d58a8","type":"delay","z":"5635003e.2d70f","name":"Limit rate","pauseType":"rate","timeout":"1","timeoutUnits":"seconds","rate":"6","nbRateUnits":"1","rateUnits":"second","randomFirst":"1","randomLast":"5","randomUnits":"seconds","drop":false,"x":700,"y":160,"wires":[["98cf75d7.be4988"]]}]

My offer to login into your node-red flow is still valid. Eventually with teamviewer or chrome remote desktop, if you prefer to not give you user and passw.

PPS: have you tried to select "suppress ACK" in the KNXUltimate config node?

[PhilW]

The knxeasy has some troubles/issues with the tunnels thru the ip-interface, so no alternative.
Didn't try knxjs, and I like your node, so I stay with it ;-).

You are right I have enabled multicast storm protection etc. and some more in my switch,
Means connecting the realKNX (running node red) and the proServ with a simple switch direct and then go to the main switch could solve the issue?

With the next chance I'll add an IP Router, promise...

THX for the delay node. With at least 30ms between all values worked fine.
Supress ACK didn't help

I'll absolutely come back to your help offer when I sorted myself and find some time, thank you.

[PhilW]

maybe you can help me with one piece of code right now.
To calculate the feed (values) from/to the Grip I need always suptract it from my load which in one case or another always gives a minus number. What is the json code for not giving negative numbers or no numbers <0 as payload?

e.g. this is the feed to the grid. I don't need a value output if it's negative

msg.payload=(msg.payload.siteCurrentPowerFlow.PV.c urrentPower-msg.payload.siteCurrentPowerFlow.LOAD.currentPower )*1000;
return msg;

I'm near a bloody beginner

[TheMax74]

Means connecting the realKNX (running node red) and the proServ with a simple switch direct and then go to the main switch could solve the issue?

Yes, it helps because the simple switch does nothing on the traffic. That's a good idea.
Please keep in mind, that if it comes in your mind to add an IPS/IDS device in your network setup (like for example, Firewalla, Cojo, Bitdefender Box 2, Fingbox, etc.. etc..), this could affect UDP as well, irregards from where you physically connect these devices, because many of these acts as ARP spoofer/poisoner.
In case one day you decide to add one of those boxes, i suggest you to use a separate LAN or to do a VLAN trunk only for the KNX/ETH communications.