TriLife

Hello @heardc, Thanks for reaching out. The MQTT plug-in was originally designed to control Tasmota-flashed devices like SonOff. Some creative users have figured out that it can also work with ESPHome. You are the first to try it with Frigate! A few pointers to try and get it to work: If you have the device type configured as "switch", sensor_id will be ignored. sensor_id is for "analog" types only (see bottom of Configuration notes) Not familiar with Frigate's naming conventions. In Tasmota the ID is used in the message, not the NAME. I'd try something like this: - id: "drivedet" name: "driveway detect" type: "switch" status_topic: "frigate/drivedet/detect/state" cmd_topic: "frigate/drivedet/detect/set" The MQTT plug-in will be listening to its messages and look for a topic "frigate/drivedet/detect/state" being sent by frigate (or your camera). If it matches that topic EXACTLY, it'll look at the value of ON/OFF. Likewise, if you click to SET, it will SEND a message with the topic cmd_topic: "frigate/drivedet/detect/set"... QUERY really wouldn't work here, because it is customized for TASMOTA. It sends a topic requesting information, which is completely different from status_topic or cmd_topic. It seems rather unusual that an MQTT plug-in generated message would delete anything, especially that the topic sent by the plug-in is highly unlikely to match a topic monitored by Frigate. Is there a way for you to monitor the MQTT messages being picked up by the Frigate? Cheers.

Hi @polo2883, can you enlighten us on what the issue was? Trying to fix the same issue here. Thanks

Same issue here. upon upgrade the router didn't recognize the eISY and assigned it a new IP. But even after reassigning it to the original slot, IoX refuses to connect, even with entering the IP address. SSH connects (no change in password) and shows that OS was upgraded to 14.1-p6. The odd thing is that I did the same upgrade on my development eISY a couple of weeks ago and it happened without a problem. Came right back up. Filed a ticket #26607 Cheers.

Hi Flex, I'm not familiar with the Control by Web x410. Your Polisy will be the broker. You will not need a cloud broker. Older versions required you to start a separate broker (Polisy and IoX also use it). I'm not sure if the newer versions did away with this. Just make sure you use 1884 (most default to 1883, which is in use.) It should not require a userid/password by default. But you might use your Polisy credentials, just in case. Also, as a heads-up: the MQTT plug-in is meant mostly for Tasmota-flashed esp devices. It somewhat works for ESPHome-flashed devices as well, and a series of custom developed devices. So, if you have a means of configuring your Control by Web to emulate a Tasmota device, or if you know what the typical publication of CbW is, you can give it a shot... As far as "how does MQTT work" is concerned, go to tasmota.github.io. They do a pretty good job explaining MQTT as it pertains to home automation... And since the plug-in is optimized for Tasmota... Finally, think about upgrading from Polisy to the eISY... If you use it, the MQTT broker runs by default. Very easy to set up. I think @Michel Kohanim has some specials running to make it less onerous on the wallet. I made the jump a while ago and couldn't be happier. Any questions, I'll gladly try to help! Cheers

I'll make sure to add this to the instructions on the next iteration.

Hi, you're close! Replace "POWER" with "POWER1", ..2 ..3 .. 4. For each switch you're trying to control... In case you need to controll ALL on/off, create a 5th device and use "POWER0". I'm away from my computer right now. You might want to follow the instructions on lower/upper case for POWER... Tasmota doesn't care, but the MQTT plug-in might.

Greetings from the other side of the world. @sjenkins, I'm wondering, if this can be solved by changing the name of the plug-in from mqtt-poly to MQTT... This would require me to remove the current MQTT from the Beta Store though, or point the MQTT plugin to load from your repository. I could do so early next week, when I'm back from my trip

I only access MQSwitch and MQDimmer with Google Assistant (Voice): when initially called on a hub or hub max, the screen shows the status as ON (and % for dimmer). And after a couple of seconds it reverts to OFF and 0%. When using the Google Home app, you can click a device to turn it on and the GUI shows ON and stays on. But if I independently turn the light off locally, the GUI remains ON, meaning that it doesn't get feedback from the plug-in, or doesn't process it properly. AC does report when a light gets turned off locally. Strong work on powering through all those items @sjenkins! Thanks so much

Glad that worked for you! If you have further ideas on how we can enhance the MQTT plug-in, please contribute on: We started on a list for you, in case you're shy😜 Cheers JR

Good morning @TJF1960, Couldn't keep @sjenkins away from his keyboard! THANKS! There is a for STATUS on the Beta Store MQTT plug-in. Now V39. your PG3 should notify you. just update... It also is on the Production Store, but since we didn't bump the rev, you might not get an update notice. Please let us know how it goes.

Good morning @TJF1960; Ok, 'MQTT' in the Beta Store is now the true blue V 0.0.35. I cloned the repository from GitHub, reverted to V35 and put it in its own branch. (I was reluctant to do this initially, because I am git-phobic 😜. Turns out using Github Desktop it was a breeze!) I also tested it. It reports status back to the AC. Let me know if this works for you. Cheers

Hmmm. I'll have a look at it tomorrow. In the meantime, @sjenkins may have a true-blue V35 in his back pocket, which he cloned to develop V39...

Hi @TJF1960. Yes, MQTT is V35 (although it may say V40 somewhere)

You're absolutely correct @maxnorth. I put those defaults in when I was expanding the plugin a couple of years ago. Some of those fields are necessary on legacy setups (isy994, polisy, PG2, etc). With eISY and PG3x, they have become defaults. I will ask UDI, how many users still are on legacy setups and we'll make adjustments as necessary. Thanks for the feedback!

10- simplify devlist/devfile by using 'defaults' for status_topic and cmd_topic. (They are mostly a combination of 'id' and a set of repetitive strings). This could reduce configuration pain by 80% and typos by 90%. Minimum need: 'id:' and 'type:' optional 'name:' 11- Google Assistant is not reporting device status consistently: it shows correctly for a few seconds and then goes to 'OFF'