@maurizio53 wrote:

Suddenly i get all my google cast devices offline with these errors in my log:

2020-06-12 12:45:08 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/homeassistant/homeassistant/components/cast/discovery.py", line 90, in setup_internal_discovery
    ChromeCastZeroconf.get_zeroconf(),
TypeError: start_discovery() takes from 1 to 2 positional arguments but 3 were given
2020-06-12 12:45:19 ERROR (MainThread) [snitun.client.client_peer] Challenge/Response error with SniTun server
2020-06-12 12:45:25 ERROR (MainThread) [hass_nabucasa.remote] Connection problem to snitun server

What happens? NabuCasa down?

Posts: 1

Participants: 1

Read full topic

@amkochaki wrote:

Hello people

Since I started to access HA through DuckDns I can no longer access the system through mobile app locally only externally. This is very bad because I have several automations that are done according to the status of my cell phone, because now that I can no longer access the HA locally, there is no return due to the mobile app no ​​longer accessing the HA locally. Would anyone have any solution for this?

Posts: 1

Participants: 1

Read full topic

@MontyRisk wrote:

I have 9 hue lights (exterior) which turn on when triggered by a sun elevation.

The automation calls a script which will turn the lights on to a specific brightness and or color. Sometimes a light or two don’t turn on, or if they do the brightness is not what I set in the script.

The Hue Hub (v2) is located near those lights has the latest firmware and it set to ZigBee channel 15.

I noticed the issue last night and checked the HA History, and the light was not listed as unavailable.

While researching this issue a bit more prior to posting this, someone suggested having many lights turning on at the same time might cause the Hue Hub to miss something since the HA commands happen quickly.

One of my thoughts to possibly solve this issue is to call the service again after 2 seconds:

action:
    - service: script.night_lights_on
    - delay: '00:00:02'
    - service: script.night_lights_on

Another idea is changing the Hue ZigBee Channel, but to what? I have 3 2.4ghz WiFi Hotspots utilizing channels 1,6,11.

Do you have any other ideas I could try to solve this issue?

Posts: 1

Participants: 1

Read full topic

@Marcus_Jansson wrote:

Hey,

Having some issues with SMHI integration and Cloud Coverage. Simply I don’t believe it. Currently where I am in Sweden, it’s clear blue sky and has been so since this morning. Though I have a cloud coverage of 50. Right now and has been up to 100 during the morning. I assume that is in percentage, since it goes from 0 to 100. Everything else is fine with SMHI, but I dare not believeingc in the clouds…

Anyone having some experience or information about this?

This is my current cloud coverage:

Skärmavbild 2020-06-12 kl. 14.26.25812×728 29.6 KB

This is my code in configuration.yaml:

sensor:
  - platform: template
    sensors:
      cloud_coverage:
        friendly_name: "Cloud Coverage MJ"
        # I know this is wrong unit of measurement
        unit_of_measurement: 'octas' 
        value_template: "{{ state_attr('weather.smhi_smhi', 'cloudiness') | float }}"

Thanks,
Marcus

Posts: 1

Participants: 1

Read full topic

@CaptainCrunch wrote:

Hi there,

I have sucessfully set up a central HA supervised machine in the basement, being fed by a Raspberry using Zwave2MQTT. I’ve paired a (used) Aeotech Switch 6 with this one and everything is working flawlessly.

The only thing bugging me is the fact that this switches kWh counter is not starting at 0, even after having reset that thing several times. My question therefore is now: how can I reset that meter?
Tried using the trick mentioned at #SOLVED# Switching from HA builtin to Zwave2Mqtt reset accumulated power meter value but it didn’t help either. Regarding the devices config guide (https://aeotec.freshdesk.com/helpdesk/attachments/6102433596), the mentioned topics should be the same for the switch.

Please help!

Posts: 1

Participants: 1

Read full topic

@thoughton wrote:

For a year or so I’ve had these two automations running:

- alias: HomeAssistant startup notification
  trigger:
    platform: homeassistant
    event: start
  action:
    - service: script.house_announce_diningroom
      data_template:
        tts_msg: "Home Assistant, System startup complete"

- alias: HomeAssistant shutdown notification
  trigger:
    platform: homeassistant
    event: shutdown
  action:
    - service: media_player.volume_set
      data:
        entity_id: media_player.dining_room_speaker
        volume_level: 0.4
    - delay: 00:00:01
    - service: script.house_announce_diningroom
      data_template:
        tts_msg: "Home Assistant, System shutdown initiated"

This is documented in the Automation docs here.

These worked fine for months, but at some point a few months back the shutdown one stopped triggering. The startup one continues to work. I’ve been meaning to figure it out for ages but kept procrastinating

It’s not huge deal but it was nice to get an announcement when restart was proceeding normally rather than waiting in suspense keeping an eye out for the dreaded notification badge about a config error. On my RPi3B the shutdown announcement would be maybe 10-20 seconds after I clicked the restart button.

Has anyone got a still-working shutdown automation? Any ideas why mine no longer works?

Posts: 6

Participants: 4

Read full topic

@skozake wrote:

I am beginning to setup a very simple green house that has 3 Sonoff S31 plugs flashed with Tasmota, 2 MiFlora garden pot sensors monitoring ONLY temp, and I have a DHT11 humidity and temp sensor at the top of my canopy. I am searching for input on how I should go about structuring my automations.

The green house needs to have two separate sets of automation, one set for the plants vegetative state, and one set for it’s flowering stage.
In it’s simplest form I only need:

1. Have my light turn on/off on a set schedule, and when my green house is ready to move into flowering have a toggle in HA that allows me to have the lights turn on/off on a new schedule.
2. Two of the Tasmota plugs are labeled dehumidifier and air filter. Based on temp/humidity I will be toggling the plugs on/off. Once again these need to have a “vegetative/flowering” schedule since my desired humidity and temp will change with each plant stage.

As for watering, my system is automatic and does not need to be automated with Home Assistant.

I have all 3 Tasmota plugs connected with MQTT, the 2 MiFlora are over Bluetooth, and the DHT11 is I2C to my RPI. All sensors are working tiptop with HA already.
Also, I am using a RasberryPi 3 B flashed with Home Assistant 0.111.0, running on a SSD.

Any insights would be very helpful.
Okay, woohoo first post!

Posts: 3

Participants: 2

Read full topic

@rherriage wrote:

Hi everyone,

Pardon if this is in the wrong section…

I have a separate linux VM running MQTT broker and Caddy as a reverse proxy for HA (running hassio VM). I’m running into a strange issue the reverse proxy seems to be redirecting to HA. All I get is the top header blue bar and nothing else. I’ve followed the steps in this link Reverse Proxy with Caddy to set up the reverse proxy. Syntax for Caddyfile is a little different as I installed caddy2, but the config per the link is just websocket and transparent mode, which is supposed to be the default for caddy2. I went ahead and added the below config to the Caddyfile to test, but still get this issue.

Here is what I have added to test it, as apparently the transparent keyword adds this to caddy v1, but didn’t work

header_upstream Host {host}
header_upstream X-Real-IP {remote}
header_upstream X-Forwarded-For {remote}
header_upstream X-Forwarded-Port {server_port}
header_upstream X-Forwarded-Proto {scheme}

I’ve tried various things, including removing HTTPS config from the passthrough proxy and HA. Watching the Caddy process (–watch) doesn’t output any errors at all. I’m thinking this may be on some kind of trust issue with HA, but I’ve got the trusted proxy set up, too. At a loss here for a couple of days. HA’s been completely rebooted, proxy has too (for other things)

I’m a network engineer by trade, so tech isn’t foreign, but webservers aren’t exactly my strength

Before I scrap this and move to nginx, has anyone run into this and can provide a little guidance?
Thanks in advance!
Robert

Here is what I get in browser (regular, incognito, etc) no matter what I do (short of removing the reverse proxy config entirely or borking it intentionally)

image1875×617 58.8 KB

Here is my current Caddyfile

domain.com {

root * /usr/share/caddy
file_server
}



domain2.com {

reverse_proxy / {
    to 192.168.5.49:8123
#    transport http {
 #       tls_insecure_skip_verify
  #      tls

   #  }
  }
}

Current http section of config.yaml as you can see, I removed https for testing purposes

http:
  #ssl_certificate: /ssl/fullchain.pem
  #ssl_key: /ssl/privkey.pem
  base_url: http://domain2.com
  use_x_forwarded_for: true
  trusted_proxies: 192.168.5.40

Browsing directly to the IP/port is fine over http (or when enabled, https)

Posts: 1

Participants: 1

Read full topic

@proteusbr wrote:

I have sonoff mini using tasmota 8.3.1 (lite) and SetOption19 1; HA 0.111.1, Hass 227 and Mosquitto Broker 5.1 addon. I have MQTT itegration working with dicovery on. I can send MQTT request to the sonoff and works, But MQTT integrantion can´t find sonoff in auto discovery. I already try SetOption30 on and off. Reboot everything several times. Maybe is a bug, but is my first configuration.

chrome_BT7V5mcdYR1566×1254 136 KB

!

Posts: 3

Participants: 2

Read full topic

@imellor wrote:

I’m using zigbee2mqtt with the Mosquitto broker add-in.
All works well, apart from I have 3 x devices that were previously connected to Smartthings, which I cannot get to join the HA zigbee2mqtt network.

I know my config is OK, because I remove a device from my HA zigbee2mqtt and added it back OK.

lLl three devices I am trying connect are Xiaomi (2 x temp sensors and 1 x movement sensor), I know these devices can be a pain for going to sleep, but I can’t seem to connect these 3 at all?

ANy help or suggestions will be appreciated.

Posts: 1

Participants: 1

Read full topic

@milo wrote:

Hi!
I have a RESTful service that I use that collects information from my car (ignition, speed, location etc).
This is working great and is coded like this if anyone is interested:

  - platform: rest
    name: mf_car
    resource: https://fleetpro.tvg.uk/api/v1/unit/list.json?key=xxxxxx&include=ignition
    headers:
      Content-Type: application/json
      User-Agent: Home Assistant REST sensor
    json_attributes:
      - data
    value_template: 'OK'
  - platform: template
    sensors:
      mf_car_odometer:
        friendly_name: Odometer
        value_template: '{{ states.sensor.mf_car.attributes["data"]["units"][0]["mileage"] | multiply(0.000621371) | round(0)}}'
        #device_class: temperature
        unit_of_measurement: 'mi'
        icon_template: 'mdi:counter'
      mf_car_speed:
        friendly_name: Speed
        value_template: '{{ states.sensor.mf_car.attributes["data"]["units"][0]["speed"] }}'
        #device_class: temperature
        unit_of_measurement: 'kmh'
        icon_template: 'mdi:speedometer'
      mf_car_state:
        friendly_name: "Milo's Car"
        value_template: '{{ states.sensor.mf_car.attributes["data"]["units"][0]["movement_state"]["name"] }}'
        icon_template: 'mdi:state-machine'
      mf_car_state_since:
        friendly_name: State Since
        value_template: '{{ as_timestamp(strptime(states.sensor.mf_car.attributes["data"]["units"][0]["movement_state"]["start"], "%Y-%m-%dT%H:%M:%S")) | timestamp_custom("%d/%m/%y %H:%M") }}'
        icon_template: 'mdi:calendar'
      mf_car_last_update:
        friendly_name: Last Update
        value_template: '{{ as_timestamp(strptime(states.sensor.mf_car.attributes["data"]["units"][0]["last_update"], "%Y-%m-%dT%H:%M:%S")) | timestamp_custom("%d/%m/%y %H:%M") }}'
        icon_template: 'mdi:update'
      mf_car_ignition:
        friendly_name: Ignition
        value_template: '{{ states.sensor.mf_car.attributes["data"]["units"][0]["ignition"]["value"] }}'
        icon_template: 'mdi:car-key'
      mf_car_ignition_since:
        friendly_name: Ignition Since
        value_template: '{{ as_timestamp(strptime(states.sensor.mf_car.attributes["data"]["units"][0]["ignition"]["gmt"], "%Y-%m-%dT%H:%M:%S")) | timestamp_custom("%d/%m/%y %H:%M") }}'
        icon_template: 'mdi:calendar'

The beauty of this is that it does the call itself, gets the data and puts it all into a load of sensors ready to use on lovelace. Great!
But… There is always room for improvement (or I am never happy with what I have).

I can get this data in real time via data forwarding from my cars system… so I’ve got an inbound webhook in automation setup that is receiving and reading data. I just dont know how to pass this data to create some sensors in the action of the automation. Anyone any ideas?

Posts: 1

Participants: 1

Read full topic

@joff wrote:

Hi.
I am getting an error in my log when I have to restart home assistant manually after a crash etc. saying:

Template sensor ‘nodon_smart_plug_weekly_total’ has no entity ids configured to track nor were we able to extract the entities to track from the value template(s). This entity will only be able to be updated manually.

The sensor is used to track weekly power consumption for the zwave smart plug defined as such in my config.:

  # Sensor to read weekly power consumption of smart plug
  - platform: template
    sensors:
      nodon_smart_plug_weekly_total:
        friendly_name: "Nodon Smart Plug Weekly Total"
        unit_of_measurement: kWh
        value_template: "{{ states() | float | round(2) }}"

I have an automation which runs a python script once a week to calculate this total (from the cumulative total which is stored in the smart plug).
When up and running, the setup works fine and the total is updated is each week. It is only upon a system restart it fails.

I am still fairly new to scripting and expect it is something fairly simple, but any help greatly appreciated.

Posts: 2

Participants: 2

Read full topic

@Da9L wrote:

I got myself a ConBee 2 dongle a few months back but I’ve never been able to get it working properly. I’ve narrowed it down to the issue being that even though deconz_events get recognized in HA, where i can see them when listening to them, they don’t always fire the automation I’ve created for them. 4 out of 5 times it works fine, but other times nothing happens. The event is still fired though, bu the automation is not run which toggles the light.

Heres a video showing the problem
https://youtu.be/S1DJe_Nq-js

The particular button you see in the video has the following automation on it

- id: '1591287657276'
  alias: Kontakt - Køkken - Knap 1
  description: ''
  trigger:
  - event_data:
      event: 1002
      id: kokken_kontakt
    event_type: deconz_event
    platform: event
  condition: []
  action:
  - data: {}
    entity_id: light.kokken
    service: light.toggle

At first i thought it could be that my Raspberry Pi 3B+ was simply reaching its limit, as i had some cameras, hue, and other integrations running on it too. But I’ve since moved the installation to my Synology DS918+ and is still acting up just like on the RPi

Furthermore, my Wifi is running on Channel 1, and the ZigBee network for the ConBee is running on Channel 25…

I have also tried to have the ConBee dongle attached without a USB extension cord, 1.5 meter extension cord, and 5 meter extension cord, all to no avail or change in the behavior. This was to be expected though, as the actual button press IS seen in HA if i listen to it, the automation just don’t always fire.

Any suggestion what i can do before i give up on it ?

Posts: 1

Participants: 1

Read full topic

@ChristianG wrote:

Hi everyone,

did anybody manage to integrate the Eltako illuminance sensor into HA? Or is it even possible?

I’m receiving some data, but I dont know how to set it up properly.

2020-06-12 16:16:33 DEBUG (Thread-2) [homeassistant.components.enocean] Received radio packet: 01:97:1C:AF->FF:FF:FF:FF (-92 dBm): 0x01 ['0xa5', '0x84', '0x2', '0x0', '0xf', '0x1', '0x97', '0x1c', '0xaf', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x5c', '0x0'] OrderedDict()
2020-06-12 16:18:13 DEBUG (Thread-2) [homeassistant.components.enocean] Received radio packet: 01:97:1C:AF->FF:FF:FF:FF (-92 dBm): 0x01 ['0xa5', '0x84', '0x2', '0x0', '0xf', '0x1', '0x97', '0x1c', '0xaf', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x5c', '0x0'] OrderedDict()
2020-06-12 16:19:53 DEBUG (Thread-2) [homeassistant.components.enocean] Received radio packet: 01:97:1C:AF->FF:FF:FF:FF (-91 dBm): 0x01 ['0xa5', '0x83', '0x2', '0x0', '0xf', '0x1', '0x97', '0x1c', '0xaf', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x5b', '0x0'] OrderedDict()
2020-06-12 16:21:23 DEBUG (Thread-2) [homeassistant.components.enocean] Received radio packet: 01:97:1C:AF->FF:FF:FF:FF (-92 dBm): 0x01 ['0xa5', '0x84', '0x2', '0x0', '0xf', '0x1', '0x97', '0x1c', '0xaf', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x5c', '0x0'] OrderedDict()
2020-06-12 16:23:04 DEBUG (Thread-2) [homeassistant.components.enocean] Received radio packet: 01:97:1C:AF->FF:FF:FF:FF (-91 dBm): 0x01 ['0xa5', '0x84', '0x2', '0x0', '0xf', '0x1', '0x97', '0x1c', '0xaf', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x5b', '0x0'] OrderedDict()
2020-06-12 16:24:34 DEBUG (Thread-2) [homeassistant.components.enocean] Received radio packet: 01:97:1C:AF->FF:FF:FF:FF (-91 dBm): 0x01 ['0xa5', '0x84', '0x2', '0x0', '0xf', '0x1', '0x97', '0x1c', '0xaf', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x5b', '0x0'] OrderedDict()
2020-06-12 16:26:04 DEBUG (Thread-2) [homeassistant.components.enocean] Received radio packet: 01:97:1C:AF->FF:FF:FF:FF (-91 dBm): 0x01 ['0xa5', '0x84', '0x2', '0x0', '0xf', '0x1', '0x97', '0x1c', '0xaf', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x5b', '0x0'] OrderedDict()
2020-06-12 16:27:44 DEBUG (Thread-2) [homeassistant.components.enocean] Received radio packet: 01:97:1C:AF->FF:FF:FF:FF (-94 dBm): 0x01 ['0xa5', '0x84', '0x2', '0x0', '0xf', '0x1', '0x97', '0x1c', '0xaf', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x5e', '0x0'] OrderedDict()
2020-06-12 16:29:24 DEBUG (Thread-2) [homeassistant.components.enocean] Received radio packet: 01:97:1C:AF->FF:FF:FF:FF (-91 dBm): 0x01 ['0xa5', '0x84', '0x2', '0x0', '0xf', '0x1', '0x97', '0x1c', '0xaf', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x5b', '0x0'] OrderedDict()
2020-06-12 16:30:55 DEBUG (Thread-2) [homeassistant.components.enocean] Received radio packet: 01:97:1C:AF->FF:FF:FF:FF (-91 dBm): 0x01 ['0xa5', '0x84', '0x2', '0x0', '0xf', '0x1', '0x97', '0x1c', '0xaf', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x5b', '0x0'] OrderedDict()

I’ve found some technical instructions about the data, but thats beyond my capabilities.

Apparently they have a lot more devices that someone (me ) might want to use.

Any hints how I could continue?

Thanks,
Christian

Posts: 1

Participants: 1

Read full topic

@mamssw wrote:

Hi everyone! I am new to HA as well as computer programming/coding, so forgive me if my question seems elementary!

I have been working with home automation for the last 15 years (X10 days) and a few years ago I purchased a Smartthings hub. Being dissatisfied with the limited configuration of ST and the fact that it was cloud-based with no backups I looked for alternatives. HA seemed to be a great option for me to manage 120 devices. I initially started with RPi 3, fell in love with it, and soon upgraded it to a NUC.

I loaded the HASS.OS image in the NUC (since I did not need access to a different OS or have to deal with the complexities of docker).

I am showing about 452gb of space left on my SSD hard drive, after loading the disk space integration. My question is can that space be used for something like backing up data, music, photos, etc.

Thanks for any ideas!

Posts: 2

Participants: 2

Read full topic

@jaswalters wrote:

How can I convert my HASSIO instance to not use default_config in the config file?

I tried this on one installation and tanked it. I could no longer access it. Just need some guidance on proper steps as just removing default_config does not seem to be the proper steps.

Posts: 2

Participants: 2

Read full topic

@william57m wrote:

Hi everyone,

I was wondering what would be the best way to implement a dashboard for a wall mounted tablet/screen.

I saw that most of people are using YAML to do that, I already experimented a bit, but I also experimented with custom_panel running a ReactJS application.

As developer I obviously prefer the JS way, but I’d like to have your opinion on that for the capability / performance / maintainability / support over the time.

It seems like everything is doable from the JS, but I’m wondering why most of people are using YAML, I know it is the standard in HA, but it’s not so convenient to implement a dashboard in YAML (or maybe you need to get used to it).

Thanks,
William

Posts: 1

Participants: 1

Read full topic

@Darrel_H wrote:

I’m trying HA (coming from HomeSeer). I’ve got a Linear/Nortek/GoControl z-wave irrigation controller, manual shown here: https://www.homeseer.com/pdfs/Nortek/WI15Z-1-manual.pdf

In HomeSeer it adds easily and has a device with a drop-down to pick options like

• All Valves Off
• Valve 1 on 5 mins
• Valve 1 on 10 mins
• Valve 2 on 5 mins etc.

For status/value pairs, I see

• All Valves Off = 0
• Valve 1 on 5 mins = 1281
• Valve 1 on 10 mins = 2561
• Valve 2 on 5 mins = 1282 etc.

In HA, the node sets up as: Linear (Nortek Security Control LLC) Unknown: type=5749, id=3135
Related entities:

• Linear (Nortek Security Control LLC) Unknown: type=5749, id=3135 SourceNodeId
• Linear (Nortek Security Control LLC) Unknown: type=5749, id=3135 Alarm Level
• Linear (Nortek Security Control LLC) Unknown: type=5749, id=3135 Alarm Type
• Linear (Nortek Security Control LLC) Unknown: type=5749, id=3135 Switch

The Switch entity shows:

• node id 8
• value index 0
• value instance 1
• value id 72057594176946176

If I manually change the state on Switch from On to a value like 1281, nothing.
If I manually change the state on the SourceNodeID entity from 0 to 1281, nothing.

I also noticed when I do Print Node, the log shows it’s querying several classes, but IRRIGATION is not one of them. I’m a bit lost for something that was a one-click-setup in HomeSeer. Hoping for any advice. Thanks!

Posts: 1

Participants: 1

Read full topic

@thoughton wrote:

So I happened to be looking for something else in my log today and noticed this:

## Log Details (WARNING)

Logger: homeassistant.components.hue.light
Source: components/hue/light.py:121
Integration: Philips Hue ([documentation](https://www.home-assistant.io/integrations/hue), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+hue%22))
First occurred: 19:08:49 (1 occurrences)
Last logged: 19:08:49

Please check for software updates of the Dining wall wash bulb in the Philips Hue App.

I had no idea there was an update available or how long it’s been available for. I also didn’t know that HA would be aware of a Hue update and log it. I didn’t get any other notification (e.g. from hue) that an update was available. I haven’t opened the Hue app in months.

Is there a way to watch the log for this message and display it in a lovelace card?

Posts: 1

Participants: 1

Read full topic

@Madivad wrote:

STUPID QUESTION WARNING

I realise that MQTT is a publish/subscribe system and so essentially for any work to be done between devices, the initiating device must publish a message which is received by a broker and sent out to any subscribers.

Subscribers (such as home assistant) can process those messages and publish it’s own message which is then received by those devices subscribed to the returning channel.

My thinking was that a device publishes something, MQTT sends it to HA (because it’s subscribed), HA doesn’t it’s magic and publishes back to the devices own subscribe channel. (basically I just repeated the last paragraph again slightly differently in order to emphasise how I understand it).

But can you orchestrate it such that one device can subscribe to another devices published material?

I’m trying to ratify this in my mind and I’m thinking it just doesn’t work like that, but I can’t satisfy myself either way. I certainly feel like it can’t be done.

P = Publish / S = Subscribe

Device 1 (sw) >> P >>      broker
                           broker  >> S >>  subscriber (HA)
                                          HA does magic
                           broker  << P << subscriber (HA)
Device 2 (light) << S <<   broker

I suppose my question is:

do devices ONLY subscribe and publish to a broker?
or
is it possible for one device to publish to another device that is subscribed to the first device?

ie device two subscribe to device one and device one publish to device two?

I’m not asking if MQTT can do MESH at all, I realise that’s a totaly different concept, I’m more questioning a setup where the broker is optional (in the case of a light switch and relay may be concerned)

LIke I say, I don’t think it’s possible, I’d just like to confirm

---

and pretty much as soon as I drew this, I kind of got the feeling it really is a stupid question, but I suppose this is what I’m asking (which would be akin to throwing your letter out on the street and hoping the receiver picks it up. Well, not really, because device 1 and 2 know each other’s IP address, but what would be the mechanism between the two? Oh, I know… MQTT! LOL

Device 1 (sw) >> P >> 
                       >> S >> Device 2 (light)

I hope I made someone’s day (that there really are stupid people out there… ME!)

Posts: 1

Participants: 1

Read full topic