You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The component is not using MQTT. Troy’s component does, but I believe it doesn’t support channels. What would you need MQTT for?
From: Saša Uzelac <notifications@github.com>
Sent: Thursday, January 9, 2020 11:56 PM
To: ziv1234/hass_dynalite_component <hass_dynalite_component@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [ziv1234/hass_dynalite_component] Still using MQTT ? Topic ? (#6)
Is component still using MQTT ?
If so, which topic ?
I tried with parameters "discovery_topic:" and "device_topic:" but it shows error, like invalid parameters.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#6?email_source=notifications&email_token=AD5UNS2N3NWALHX5KYSYRNDQ46MOBA5CNFSM4KE7BM52YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IFF562A>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AD5UNS4NSISWGBK4WDCOUPTQ46MOBANCNFSM4KE7BM5Q>.
I find it easier to debug and follow via MQTT, turn on client on other device and see things as they happen.
No real need, just wondered. Should be no issue this way without MQTT.
Is component still using MQTT ?
If so, which topic ?
I tried with parameters "discovery_topic:" and "device_topic:" but it shows error, like invalid parameters.
The text was updated successfully, but these errors were encountered: