Don’t worry about that at this stage; Modbus incorporates retries. Many slaves are sometimes just too busy to service a poll. When you get "Try 3 out of 3 failed ..."
is the time to look into it.
I’m sure it’s just down to data Thing configuration. This requires knowledge of the target device registers - their format, if you will, as well as address and type.
I’m handicapped because I cannot see this spreadsheet, maybe my Excel is too ancient to deal with it.
Let’s concentrate on device type. You said you had that working at one time, reporting 9302. We don’t know what settings you used for that, I doubt you’ll remember!
You’re reading that using
// SMA SunnyBoy Device Type 30053 Device Type
Bridge poller sma30053 [ start=30053, length=4, refresh=5000, type="input" ] {
Thing data DevType [ readStart="30053", readValueType="int32" ]
}
I think - please confirm, since your last changes.
So, what can be wrong with that? Maybe the address of course, maybe it should be holding not input - but maybe the type - is it really 32-bit?
It doesn’t need to be for 9032. If it is 32-bit, it is two 16-bit registers stuck together. Whch way round should they be stuck? A + B is nothing like B + A in this case, and will give hugely different results.
Let’s get the raw 16-bit data so that we can see more easily.
// SMA SunnyBoy Device Type 30053 Device Type
Bridge poller sma30053 [ start=30053, length=4, refresh=5000, type="input" ] {
Thing data DevType [ readStart="30053", readValueType="int32" ]
Thing data DevTypeA [ readStart="30053", readValueType="uint16" ]
Thing data DevTypeB [ readStart="30054", readValueType="uint16" ]
}
We can interpret the same data different ways at the same time.
Make two temporary test Items
Number DevTypeA { channel="modbus:data:SMAinverter:sma30053:DevTypeA:number" }
Number DevTypeB { channel="modbus:data:SMAinverter:sma30053:DevTypeB:number" }
You don’t even need to put these on your sitemap if you watch for the update in your events.log
after the first poll.
I’m expecting to find one of them is 9302?