GivTCP 3.5 read ERRORS on GIV-AIO-AC-13.5-3.6. 'TypeError ' and 'UnboundLocalError' in 'read.py'

Hi Everyone
New post, newbie to HA and GivTCP!
Just installed HA on Pi and MQTT seems to be running OK but limited devices running (e.g. no “control” services visible).
I have simplified the GivTCP config so only the AIO was setup as a single inverter (inverter 1 Enabled) ; it has a static IP address and is discovered successfully as a device and has the correct serial no as far as I can see.
Extracts from Error Log (4 entries) :
TypeError: bad operand type for unary -: ‘NoneType’

Error processing Inverter data: (‘TypeError’, ‘read.py’, 1119)
inverter Update failed so using last known good data from cache: (Exception: Process Data Failure - 2000)Key Error getting Battery Data: Missing key ‘multi_output’

UnboundLocalError: cannot access local variable ‘multi_output’ where it is not associated with a value

Error in calling handler: (‘UnboundLocalError’, ‘read.py’, 261)

line 261 is:
handler(client.plant)
#so issue with “plant”?

line 1119 is:
if -inverterModel.invmaxrate <= inverter_power <=inverterModel.invmaxrate:

#so something is not being passed in terms of “inverterModel.invmaxrate” ?

I also noted that in the MQTT Devices dashboard that the activity logs for AIO 1 AIO Serial Number that it “Became unavailable” so this value it seems is not being read, and may be the cause or one or both of the errors… possibly…

Curiously the Gateway, which I did not setup in GivTCP, (I followed the Speak to the Geek video guidance) is recognised as a gateway by MQTT and has valid Activity entries including for the Serial Number!

I cannot see anyone else thus far with this issue so am reaching out . I hope I am following the correct protocols here in creating a new topic.

many thanks everyone,
iancval

1 Like

I’ve been getting loads of the same issues over the past week or two, and have not yet figured out what is failing. Data occasionally gets through to HA from GivTCP, but it’s mostly unusable for now

I downgraded to v3.4 and service has returned to normal.