Error: Please make sure mqtt.py exists in the exports folder

[kiripparam-create]

I'm having an issue with this code at the moment:
current configration.yaml for sungather:

host: winet-s IP
timeout: 10
scan_interval: 30
connection: modbus
smart_meter: true
custom_mqtt_server: false
log_console: INFO
mqtt:
enabled: true
host: home assisant ip
port: 1883
username: user
password: generic password
client_id: SunGather1
homeassistant: true

logs:
25-09-27 20:28:06 INFO Loading Export: exports webserver
2025-09-27 20:28:06 INFO Webserver: Configured
2025-09-27 20:28:06 INFO Loading Export: exports mqtt
2025-09-27 20:28:06 ERROR Failed loading export: 'NoneType' object has no attribute 'replace'
Please make sure mqtt.py exists in the exports folder
Failed loading export: 'NoneType' object has no attribute 'replace'
Please make sure mqtt.py exists in the exports folder
2025-09-27 20:28:06 INFO Modbus, Connecting new session
2025-09-27 20:28:06 INFO Setting Initial Daily registers; daily_export_to_grid, daily_import_from_grid, last_reset
2025-09-27 20:28:06 INFO Inverter: Successfully scraped in 0.192058 secs
2025-09-27 20:28:06 WARNING MQTT: Server Error; Server not configured
MQTT: Server Error; Server not configured
2025-09-27 20:28:06 INFO Closing Session:

My core mosq yaml file:
logins:

• username: user
  password: password
  require_certificate: false
  certfile: fullchain.pem
  keyfile: privkey.pem
  customize:
  active: false
  folder: mosquitto

Logs:
2025-09-27 20:23:36: Opening ipv4 listen socket on port 1883.
2025-09-27 20:23:36: Opening ipv6 listen socket on port 1883.
2025-09-27 20:23:36: Opening websockets listen socket on port 1884.
2025-09-27 20:23:36: mosquitto version 2.0.22 running
2025-09-27 20:23:36: New connection from ::1:40934 on port 1883.
2025-09-27 20:23:36: Client disconnected due to protocol error.
[20:23:37] INFO: Successfully send discovery information to Home Assistant.
[20:23:37] INFO: Successfully send service information to the Supervisor.

[bohdan-s]

Hi.
That’s a bit of a red herring.
The issue is with the model not being detected.
Set the model in config.yaml to a model listed in the registers.yaml file and it will work. Most models overlap 90% of registers so it won’t cause issues.
Next update will have a fall back to a “generic” model if it can’t be detected.