TriLife

Greetings, If I understand correctly, the ZMatter dongle stores the Z-Wave and Matter configurations locally. Does that mean I could move the dingle to another eISY or even a Home Assistant setup and be up and running? Cheers?

Thanks Paul, I was planning on updating State_Var_Temp every 30mins or so in order to take out small fluctuations. Not too worried about micro-controlling the climate. We drink that wine waaaaay to fast for that And it really has only one command in there which is to turn on the recirc fan, if the outside temp is lower than the cellar temp...

Happy New Year! I want to turn on my wine cellar's air circulation based on the difference in temperature. Outside temp comes from my WestherLink station (Bob's plug-in) and the cellar temp from a Tasmota device If outsideT < cellarT: Turn ON fan... Seemingly simple, I haven't figured out how to do that comparison inside IoX... Any ideas on how to accomplish this? Thanks!

Ok. I'll put it the Production Store as well.

There was a foul-up when merging with a PR. Please install V0.0.34 from the Beta-Store and let me know how this looks. You should have 1 node per analog channel, not 4 like before All others should work as per normal

Ok, let me have a look at this. I'll ping you.

It looks like you still have the old analog node in there.. In PG3X, STOP the plug in, click on NODES and delete n010_chickcoop2 and any other analog nodes you have. Then hit RESTART. Each analog node should only have one analog reading in it. Happy New Year!

I'm wildly guess that you have it on the same device and as a result the key of the analog sensor changed names from Range to Range1 or something... Please send me the output of a 'Status 10' and see if the key of your analog sensor matches the sensor-id of your node configuration... If that's not it, it'll take me until next year to fix it😝 Cheers.

Hi @EWhite, Funny, I was just googling this topic this morning, looking for a mmWave human presence sensor. Thanks for doing the footwork. I can't find the Seed Kit on Amazon yet, only the guts. I'd be glad to work on it, but I need a unit. DM me directly if you would like to pursue that. Cheers

Good morning! So, the MQTT server is now on in the production store, V0.0.33. Thanks for everyone's help and patience!

Thanks @lilyoyo1, I ADDED a new sensor to the end of the list. For my education: When I right-click a Z-Wave sensor: Z-Wave | Synchronize | I get 4 choices, see screenshot What purpose do those 4 commands serve? Cheers.

Merry Christmas to you too!

The original does have BME Support, but not if you have multiple sensors on the same tasmota topic I also haven't tested the original, so if what I sent you doesn't work, we'll have to wait for me to order a BME280. Or you need to configure a Wemos with ONLY a BME280 on it (no other sensors, switches etc)

You asked for it! Please look for V 0.0.33 in the Beta-Store

Hi @EWhite; Merry Christmas! the BME280 not working is not surprising: I have not updated the plugin for the BME280... I would need to order a unit from Amazon for that, in order to troupbleshoot it here. No problem doing that (you can send me some Amazon bucks $15.90), but it would take a couple of weeks to get here... I can try to do it without a test unit as well, and use you as a guinea pig, if you're up to it. Let me know, what you wanto to do. Cheers;

Greetings, I had to remove an AeoTec 6in1 a few weeks ago to fix some water damage in the ceiling. When I plugged it back in it started giving me the rainbow colors, indicating that it has been "dissociated" from the network. In AC, it doesn't respond to Interview etc. Is there a way to add it back into the network into the same ZW013 slot, so I don't have to redo all of my programs? I recall that if I just ADD it goes to tue bottom of the list. Cheers!

Good morning @sjenkins. Thanks for the heads up. I received a message from GitHub, was wondering what that was all about. I took over @xKing's MQTT Plugin after checking with him and UDI. With input from users like @EWhite we've expanded the sensor capabilities of the plug in. That version has been living on in the Beta-store for a while now, while we iron out bugs... I also added a Dimmer. Have a look at it there, please. And then let's figure out the best way to get this out to the production store. Cheers.

Nice life! Happy Holidays

YAY! Apologies to the chickens again! Let me know, if you have any other issues/ideas. Please make sure you mention @TriLife, and keep posting to this thread. Cheers

did you clickREFRESH STORE SORRY, yes, it can take a bit to refresh...

Hi @EWhite, In the meantime, I think I fixed the bug that requires a certain order. I tested it with "switch" front and back. I just pushed the update to the beta store and installed it on my box from there. Still V0.0.31) Can you please confirm?

Hi @EWhite; I have a temporary fix for you in the Beta Store, Version 0.0.31: The trick is that if you have a type "switch" in the same topic as the type "ANALOG", "AM2301" etc, you MUST put the definition of the type "switch" AFTER the analog etc. Like so: devices: - id: "TurbRange" name: "CrkTurbRange" type: "analog" sensor_id: "Range" status_topic: "tele/Creek/SENSOR" cmd_topic: "cmnd/Creek/POWER" - id: "SluiceTH" name: "CrkSluiceTH" type: "TempHumid" sensor_id: "AM2301" status_topic: "tele/Creek/SENSOR" cmd_topic: "cmnd/Creek/power" - id: "Wemos32A1" name: "Wemos 32 A1" type: "analog" sensor_id: "A1" status_topic: "tele/Wemos32/SENSOR" cmd_topic: "cmnd/Wemos32/POWER" - id: "Wemos32A2" name: "Wemos 32 A2" type: "analog" sensor_id: "A2" status_topic: "tele/Wemos32/SENSOR" cmd_topic: "cmnd/Wemos32/POWER" - id: "Wemos32T1" name: "Wemos 32 T1" type: "Temp" sensor_id: "DS18B20-1" status_topic: "tele/Wemos32/SENSOR" cmd_topic: "cmnd/Wemos32/POWER" - id: "Wemos32T2" name: "Wemos 32 T2" type: "Temp" sensor_id: "DS18B20-2" status_topic: "tele/Wemos32/SENSOR" cmd_topic: "cmnd/Wemos32/POWER" - id: "Wemos32TH32" name: "Wemos 32 TH32" type: "TempHumid" sensor_id: "AM2301" status_topic: "tele/Wemos32/SENSOR" cmd_topic: "cmnd/Wemos32/POWER" #SWITCH TYPES AT THE END - id: "Wemos32SW" name: "Wemos 32 SW" type: "switch" # sensor_id: "AM2301" status_topic: "stat/Wemos32/POWER" cmd_topic: "cmnd/Wemos32/power" - id: "Sluice" name: "Creek Sluice" type: "switch" status_topic: "stat/Creek/POWER" cmd_topic: "cmnd/Creek/power" Please download and verify. In the mean-time, I'll try to figure out, why the order matters. Cheers.

@EWhite; Can you please send me your complete devfile.yaml? Thanks

Hi @EWhite, Sorry just saw this. Please apologize to your chickens! Ok, let me have a look at what's going on. Question: which Tasmota device are you using? WeMos D1, if I recall correctly? Only Analog and AM2301 on the device? Exactly what are the symptoms? Also, do you have access to Discord? That might speed up troubleshooting Cheers.

Glad it is fixed. I will be making some changes to the Dimmer node in a few days. Let me know, if this will be an issue...