ok all in need of some direction. I am currently running the larizzo docker on an Unraid box with plenty of power and memory talking to a HASSio install on a Ubuntu server VM. The MQTT broker is on another docker and is working fine with other tasmota devices connected to HA. I did a dum dum and upgraded the docker and everything went south. I tried to figure it out with no success, so I tried starting all over and that didn’t work either. I am sure that it is something that I am missing so here is the first part of the new insteon-mqtt.yaml file (only started with two devices and the modem)
type or paste code here#==========================================================================
#
# Insteon <-> MQTT bridge configuration file.
#
# NOTE: the loader supports using a !include tag to load other as a
# item entry so you can do things like this:
#
# insteon:
# devices: !include devices.yaml
#
#==========================================================================
#==========================================================================
#
# Optional logging configuration (can also be set via the command line)
#
#==========================================================================
logging:
# 10=DEBUG, 20=INFO, 30=WARNING, 40=ERROR
level: 10
# Print messages to the screen.
#screen: False
# Print messages to a file.
#file: /var/log/insteon_mqtt.log
#==========================================================================
#
# Insteon configuration
#
#==========================================================================
insteon:
# Serial device:
# USB PLM modem
port: '/dev/ttyUSB0'
#baudrate: 19200
# Network socket:
# Insteon HUB PLM network
#port: 'socket://192.168.1.5:9761'
# PLM modem Insteon hex address
address: 4c.16.49
# Device database file storage location.
#storage: '/var/lib/insteon-mqtt'
storage: 'data'
# Automatically refresh device states and databases (if needed) at
# startup. This may be slow depending on the number of devices.
startup_refresh: False
#------------------------------------------------------------------------
# Devices require the Insteon hex address and an optional name. Note
# that MQTT address topics are always the lower case hex address or
# the input name depending on how they are configured below.
devices:
# On/off switch devices (outlets, wall switches, appliance modules, etc).
switch:
# - 3a.29.84: 'xmas tree'
# - 26.48.ff: 'xmas stairs'
# - 37.2d.20: 'xmas deck'
# Dimming devices (outlets, wall switches, lamp modules, etc).
dimmer:
- 0d.77.2c: 'landing'
- 14.37.2b: 'table_lamp'
# - 3a.29.84: 'lamp2'
# - 48.3d.46
# - 48.b0.ad: 'dim1'
# Battery powered sensors (door, hidden door, window).
battery_sensor:
# - 94.a9.12
# Battery powered motion sensors.
motion:
# - 21.d6.d9: 'door'
# Battery powered mini remotes.
mini_remote4:
mini_remote8:
# - 3f.07.d4: 'remote1'
# Smoke bridge module.
smoke_bridge:
# - 44.a3.79: 'smoke alarm'
# FanLinc fan controller (dimmer+fan).
#fan_linc:
# - 9a.a1.b3
# KeypadLinc dimmers (dimmer+scene controller).
keypad_linc:
# - 46.7b.bc: 'porch'
# KeypadLinc switches (on/off+scene controller).
keypad_linc_sw:
# - 3c.42.9b: 'kp2'
# Leak sensors.
#leak:
# - 21.d6.d9: 'bathroom'
# IOLinc relay controllers
io_linc:
# - 45.33.d4: 'garage'
# On/off ouetlets
#outlet:
# - aa.bb.cc: 'outlet'
# Thermostatus
thermostat:
# - aa.bb.cc: 'downstairs'
#------------------------------------------------------------------------
# FUTURE: Insteon scene definitions.
#scenes:
# - scene_01:
#==========================================================================
#
# MQTT configuration
#
#==========================================================================
mqtt:
broker: 192.168.0.247
port: 1883
# Optional broker login data.
#username:
#password:
# Keep alive time in seconds. This should be smaller than the
# server setting (which is usually ~60 seconds) to insure that
# connections aren't dropped.
keep_alive: 30
# Outbound messages configuration. Retain should generally be 1
# so that the current state is available when someone subscribes.
qos: 1
retain: 1
and each time I issue a command the handler retries three times and fails. I am sure its something I am missing. Its been working fine since the early versions. Here is a brief section of the log
type or paste code here
2019-07-04 22:24:22 INFO Mqtt: MQTT message insteon/command/0d.77.2c b'{ "cmd" : "off" }'
2019-07-04 22:24:22 UI Mqtt: Commanding dimmer device 0d.77.2c (landing) cmd=off
2019-07-04 22:24:22 INFO Dimmer: Dimmer 0d.77.2c cmd: off
2019-07-04 22:24:22 INFO Protocol: Write message to modem: Std: 0d.77.2c, Type.DIRECT, 13 00
2019-07-04 22:24:22 DEBUG Protocol: Write bytes to modem: b'\x02b\rw,\x0f\x13\x00'
2019-07-04 22:24:22 DEBUG Serial: Wrote 8 bytes to serial /dev/ttyUSB0
2019-07-04 22:24:28 WARNING Base: Handler timed out 1 of 3 sent: Std: 0d.77.2c, Type.DIRECT, 13 00
2019-07-04 22:24:28 DEBUG Base: Increasing max_hops to 3
2019-07-04 22:24:28 INFO Protocol: Write message to modem: Std: 0d.77.2c, Type.DIRECT, 13 00
2019-07-04 22:24:28 DEBUG Protocol: Write bytes to modem: b'\x02b\rw,\x0f\x13\x00'
2019-07-04 22:24:28 DEBUG Serial: Wrote 8 bytes to serial /dev/ttyUSB0
2019-07-04 22:24:34 WARNING Base: Handler timed out 2 of 3 sent: Std: 0d.77.2c, Type.DIRECT, 13 00
2019-07-04 22:24:34 DEBUG Base: Increasing max_hops to 3
2019-07-04 22:24:34 INFO Protocol: Write message to modem: Std: 0d.77.2c, Type.DIRECT, 13 00
2019-07-04 22:24:34 DEBUG Protocol: Write bytes to modem: b'\x02b\rw,\x0f\x13\x00'
2019-07-04 22:24:34 DEBUG Serial: Wrote 8 bytes to serial /dev/ttyUSB0
2019-07-04 22:24:40 WARNING Base: Handler timed out 3 of 3 sent: Std: 0d.77.2c, Type.DIRECT, 13 00
2019-07-04 22:24:40 DEBUG Base: Increasing max_hops to 3
2019-07-04 22:24:40 INFO Protocol: Write message to modem: Std: 0d.77.2c, Type.DIRECT, 13 00
2019-07-04 22:24:40 DEBUG Protocol: Write bytes to modem: b'\x02b\rw,\x0f\x13\x00'
2019-07-04 22:24:40 DEBUG Serial: Wrote 8 bytes to serial /dev/ttyUSB0
2019-07-04 22:24:46 WARNING Base: Handler timed out - no more retries (3 sent)
2019-07-04 22:24:46 ERROR Mqtt: Command timed out'
and a few mins later tried this:
2019-07-04 22:26:05 INFO Mqtt: MQTT message insteon/command/0f.e0.a5 b'{ "cmd" : "linking" }'
2019-07-04 22:26:05 UI Mqtt: Commanding Modem device 0f.e0.a5 (modem) cmd=linking
2019-07-04 22:26:05 INFO Protocol: Write message to modem: Modem linking: grp: 1 Cmd.EITHER
2019-07-04 22:26:05 DEBUG Protocol: Write bytes to modem: b'\x02d\x03\x01'
2019-07-04 22:26:05 DEBUG Serial: Wrote 4 bytes to serial /dev/ttyUSB0
2019-07-04 22:26:11 WARNING Base: Handler timed out - no more retries (0 sent)
2019-07-04 22:26:11 ERROR Mqtt: Command timed out
If there is something that I didn’t post and might be needed just let me know.
ThanX
Michael