MQTT problem devices not shown

Configuration
1

Not sure if this is a HA problem or not. but giving me major problems
Just purchased a Odroid N2+ to replace the Odroid XU4
in Configuration.yaml:-

mqtt:
  broker: 192.168.1.154
  port: 1883
  client_id: home-assistant
  username: None
  password: None


sensor:
  - platform: time_date
    display_options:
      - 'time'
      - 'date'
      - 'date_time'
#      - 'date_time_iso'
#      - 'time_date'
#      - 'time_utc'
      - 'beat'
#  - platform: state
#    entity_id: sensor.time
  - platform: moon
  
  - platform: mqtt
    name: "Hot Water Temp"
    state_topic: "/iot4/IOT4SH01DS_A03625/temperature"
    unit_of_measurement: "C"

  - platform: mqtt
    name: "Solar Energy"
    state_topic: "shellies/shellyem-109664/emeter/0/energy"
    value_template: "{{ value|float / 60000 }}" # Fix for Watt-minutes
    qos: 1
    unit_of_measurement: "kWh"
#  icon: mdi:chart-bar
  
  - platform: mqtt
    name: "Solar Power"
    state_topic: "shellies/shellyem-109664/emeter/0/power"
#    value_template: "{{ value|float / 1000 }}" # Fix for inverter/em sensor
    qos: 1
    unit_of_measurement: "W"

switch:
    name: Hot Water Boiler
    state_topic: "/iot4/IOT4SH01RELAY_D341DE/relay/0"
    command_topic: "/iot4/IOT4SH01RELAY_D341DE/relay/0/set"
    payload_on: "1"
    payload_off: "0"

  - platform: mqtt
    name: Solar Hot Water
    state_topic: "stat/evilbox1/POWER"
    command_topic: "cmnd/evilbox1/POWER"
    payload_on: "ON"
    payload_off: "OFF"

  - platform: mqtt
    name: Landing Light
    state_topic: "stat/evilbox2/POWER"
    command_topic: "cmnd/evilbox2/POWER"
    payload_on: "ON"
    payload_off: "OFF"

  - platform: mqtt
    name: Immersion load
    state_topic: "shellies/shellyem-109664/relay/0" 
    command_topic: "shellies/shellyem-109664/relay/0/command"
    payload_on: "on"
    payload_off: "off"

  - platform: mqtt
    name: sh-24d7a3
    state_topic: "shellies/shelly1-24D7A3/relay/0" 
    command_topic: "shellies/shelly1-24D7A3/relay/0/command"
    payload_on: "on"
    payload_off: "off"

  - platform: mqtt
    name: sh-24d64e
    state_topic: "shellies/shelly1-24D64E/relay/0" 
    command_topic: "shellies/shelly1-24D64E/relay/0/command"
    payload_on: "on"

```, mosquitto and mosquitto-clients are loaded and running
OS is Ubuntu 20.04LTS
here is the strange bit
If I point from the MQTT integration at the old XU4 on 192.168.1.82:1883, the devices show in lovelace, but water temp is flashing between unavailable and a reading.
Using MQTT Explorer on the old XU4 at xx.xx.xx.82:1883 devices are shown.
BUT
on the N2+ on xx.xx.xx.154:1883 no devices are shown, the mosquitto directory has been copied from one machine to the other so the config file is the same as before.
From MQTT Explorer test.mosquitto.org is functional.
HA companion on my mobile phone is showing the same as lovelace, so the networking through the router looks OK.
any ideas why the devices that talk to the broker on the XU4 wont talk to the broker on the N2. 
As most are wired directly to the mains , I'll try powering the whole house down , in case they are still trying to look for xx.xx.xx.82 , the old XU4..

suggestions appreciated, thanks
2

You did change the mqtt configuration on your devices ?

3

Thanks for the reply
The IOT4 devices I’ve forgotten the password, but one has appeared on MQTT explorer, after powering down the whole house, the temp sensor has not even reappeared on the network yet :(, so far the devices evilbox1 & 2 are showing , and
iot4/IOT4SH01RELAY_D341DE/relay
The shelly devices, I’ll see if I can get in to them, on the hot water boiler switch , which is the most important, now its appeared , do I just past the command_topic into the publish packet in the MQTT intergration in lovelace, or should it discover from mosquitto, its not very clear ???/

4

OK I now have idiot of the year award, I’d forgotten the devices had to be configured, all now up except one which is not finding the network . Thanks for the help

1 Like
5

The one that wouldn’t find the network, had decided to change its default ip address, now fixed