Domoticz

leby wrote: ↑Monday 21 January 2019 6:53 In this installation I have a Pi3 with raspbian-stretch-lite that is updated.


It was two different jessie or wheezy to chosse from, I don't know but earlier versions of Pi
installation instructions points to jesse so i choose that one.

cd /etc/apt/sources.list.d/
rm mosquitto-jessie.list
wget http://repo.mosquitto.org/debian/mosquitto-stretch.list
apt-get update
apt-get install libwebsockets-dev mosquitto

besix wrote: ↑Friday 25 January 2019 12:26 The plugin works, and I'm glad I only have a question
Why the plugin adds new 2 device?
The first is a switch and is Ok

leby wrote: ↑Tuesday 29 January 2019 6:43 @Iwolf I seem to have no luck getting the Shelly to report back to Domoticz. No new device is turning up.

Thorgal789 wrote: ↑Sunday 03 February 2019 18:29 Hi, first thx for the plugin, but I have a question, why have you used mqtt ?
It's just http api, you can make the plugin interact directly with the device, why have you added intermediary, there is a reason for that ?

leby wrote: ↑Saturday 02 February 2019 12:37 I did however see when I hade the MQTT.fx tool running that Domoticz published sensor info on the network.
To minimize interference I therefor changed broker publish to "None"
none.JPG

I am very glad, that you can make it work.
But i am a little confused about the second image in your post. ShellyMQTT has nothing to do with "MQTT Client Gateway with LAN interface". And in fact they are using different topic's (shellies/#, domoticz/in, domoticz/out) and it is unlikely to ever interfere with each other's operation. Unless you are using the same IDX that Domoticz assigned to a Shelly device in an other device also, such as a Sonoff-Tasmota through standard MQTT.

lwolf wrote: ↑Monday 04 February 2019 10:34

Thorgal789 wrote: ↑Sunday 03 February 2019 18:29 Hi, first thx for the plugin, but I have a question, why have you used mqtt ?
It's just http api, you can make the plugin interact directly with the device, why have you added intermediary, there is a reason for that ?

Hi,
Not sure what you mean under "intermediary" and "just http api".
Shellies supports HTTP API and MQTT API also.

Shelly devices could be polled one-by-one with HTTP, if you knew they IP addresses but why? Sending commands to a device is only a part of the story, there has to be some status messages... Do you think that polling several IP addresses through HTTP in every second is more efficient than connecting only one address: the MQTT broker, which will let you know almost instantly if there are anything changed? Such as a user pushed a detached Shelly button...
I do not think so.

This plugin grabs incoming MQTT messages from Shellies, and updates or creates the appropriate Domoticz device, and forwards incoming messages from Domoticz to the appropriate MQTT path. There are no HTTP parts in it.

zygios wrote: ↑Monday 04 February 2019 19:01 I tryed to disable my currect MQTT Client Gateway with LAN interface and install Shelly MQTT and it works perfectly with Shelly2 (5 new devices found and I can control it from Domoticz).
How to make connections to same mqtt server?

leby wrote: ↑Monday 04 February 2019 14:22 Probably only me that misunderstood how to set it up in the first place. Do I understand you correctly that I can scrap the "MQTT Client Gateway with LAN interface" and only using the HW "Shelly MQTT"?

leby wrote: ↑Monday 04 February 2019 14:22 btw, have Allterco Robotics supplied you with a 2.5 version so we can expect support for that one also?