Replies: 13 comments 7 replies
|
Jep, is running since weeks on my side with the new firmware (dtu: V01.00.01/ mi: V01.00.08). Without any "disturbance" for the dtuGateway. |
|
So I have updated my 2. inverter with DTU Firmware update, today. I don't know maybe in combination with also newer Firmware of inverter it's not working anymore. 
|
|
Yep, my inverter version is still the shipped one V01.00.08 at that time ... but the dtu sw is the same as yours V01.00.01. Your second inverter with dtu lite stick was running you said... until dtu firmware update to V01.00.01? Has anything changed with your Wi-Fi/DHCP connection, resulting in a changed IP address in your network? (Perhaps too simple or rudimentary, but worth checking here as well) But as I said, no problems with this dtu firmware and dtuGateway on my side ... except the tradeoff/ rare missing of data displayed in cloud. Can you please also try with hoymiles app on smartphone to connect directly with the dtu
This connection from app to dtu is the same as the dutGateway is using, from protocol perspective. |
|
I can not imagine that there is direct dependency with the inverter version... Your second inverter with dtu lite stick was running you said... until dtu firmware update to V01.00.01? What I was checking today : (unfortunatly no success or changes with connection of dtuGateway)
Can you please also try with hoymiles app on smartphone to connect directly with the dtu
only for info each of the inverter are placed on different locations with different dtugateways and router and internet This connection from app to dtu is the same as the dutGateway is using, from protocol perspective. Addtionally I tried also with older dtuGateway firmware 2.0.0013 2.10014 no success. |
|
Hi, that's strange... as mentioned, no problem on my side with this dtu firmware. Other check... why ever it is now maybe changed at your side - with your router(s) is there maybe traffic blocked for port 10081 from one client to another within your network...? |
|
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) Booting - with firmware version 2.2.0017UserConfigManager::loadConfig - config loaded from json: /userconfig.json wifi ssid: MASKEDFROMMYSIDE dtu openhab mqtt remoteDisplay: 0 remoteSummaryDisplay: 0 display init (wifiAPstart): 0
|
|
Other check... why ever it is now maybe changed at your side - with your router(s) is there maybe traffic blocked for port 10081 from one client to another within your network...? Nothing changed from my side and on that router not possible as I know to block. |
|
hmm... thanks for the log
{
...
"dtuConnection": {
...
"dtuRssi": 75, // wifi strength of dtu
...
},
"wifiConnection": {
...
"rssiGW": 100, // wifie strength of dtuGateway
...
}
}
|
|
HMS-800 with DTU Lite S dtuRSSI is always 0 as there is no connection to get this value from DTU I think the physical connection shouldn't be here the problem. Has maybe something changed on the data from Hoymile silently ? 
HMS-800W currently not availble as on another location |
|
jep, you're right - if there is no functional connection the dtu rssi is not given...
sounds very weak - at least for testing give it a try with a rssi % of > 80
as said - have the same FW on dtu and no problems... so, if there is no same named (version) firmware by hoymiles for dtu with different protocol versions - it have to be something with the connection as already found out the bottom layer connection is given, but the waiting for response of dtu runs in timeout (that could mean, that the try to send something (longer payload) via TCP runs in errors and will be based on TCP retried. Here maybe then so often, that the 15 sec will be overrun. So, for that let's try the idea with a more longer timeout and the reset of wifi connection if the signal is to weak. I will try to provide this special version today or tomorrow. |
|
there is a small dev update with increased timeout and weak wifi signal reconnect if in timeout https://github.com/ohAnd/dtuGateway/actions/runs/17343018194 you can also downloiad directly from here https://github.com/ohAnd/dtuGateway/actions/runs/17343018194/artifacts/3889162783 you can see the changes here -> 87f589f |
|
I also added the reading of dtu and mi version info and providing this via api and webinterface - will be merged soon with snapshot 
that is also the proof, that interface is still working with 01.00.01 ;-) last feature branch build -> https://github.com/ohAnd/dtuGateway/actions/runs/17382133827 |
|
Now after my vacation, I'm back ... Have switched on my dtugateway with my HMS-800W in my flat. (2. BKW) There was a wrong cloudpausetime configured from the last test before vacation. |
|
interim conclusion ( test with 2.2.0052_test_dtu_connect_weak_connection ) after 1day. But the data connection to the hoymile cloud is not so good. For more testing according cloud behavior I think I need a configurable time value for cloudpause. |
|
Update test with 2.2.0052_test_dtu_connect_weak_connection I will update to the latest release now. |
|
Hi @zigit780 , I've also now encountered this issue regarding the inverter firmware update and communication problems with dtu... With the new inverter firmware it looks like the dtu has some more internal communication, so the prot server on dtu has only very short session times or capacity for additional sessions ... It's including the 5 min cloudpause and a later starting for cloud pause at xx:xx:50 before every 5 min - the length you can still configure (I have currently 30 s - but will try to reduce more and more...) For that it will be helpful that we collect a lot of consecutive update timestamps at hoymiles cloud e.g. 11:59:58/ 12:04:56/ 12:10:02 and so on ... hint: during the process of finding the problems I've implemented also a (currently undocumented) connection error log - you can reach this via json at .../api/dtuEvents.json {
"events": [
{
"timestamp": 302084344,
"eventType": "RECOVERY",
"description": "DTU healthy state recovered",
"connectionDuration": 34961,
"dtuState": 1,
"bufferSpace": 5760,
"localTime": 302084344
},
...
],
"statistics": {
"totalConnections": 2,
"shortConnections": 0,
"longestConnection": 99789,
"averageConnectionTime": 99789,
"healthyState": true,
"eventCount": 50,
"currentTimestamp": 292086
},
"currentConnection": {
"duration": 126060,
"bufferSpace": 5760,
"state": "connected"
}
}Please let me know - how stable it will running with that... |
|
PS: prior to this (directly after inverter fw upgrade) I had mutliple longer run times - but then the dtu were "suddenly" unreachable anymore for the dtuGateway - a Reboot of dtu via hoymiles cloud brought the dtu back for dtuGateway communication until the next failure |
|
Hi @ohAnd, |
|
Unfortunately I don't get any data from the HMS-800 with DTU LiteS. 
|
|
FW-Update to 1.02 on DTULiteS done. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There was a FW-Update some weeks ago for the DTU. see below the changes
Also there was a WLAN-security-Fix included.
Has someone dtuGateway successfully in operation with this firmware ?
All reactions