TriLife

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...

Hi @jkosharek, Not sure about the error you're getting from the beta-store install. Are you on an eISY or Polisy? Which PG and IoX versions? I'm traveling at the moment, won't be back at my terminal to help you troubleshoot for a few more days... Cheers.

Greetings, By default, on PG3/x you do not need user/PW for things to run. You do, however need to use port 1884. Hope that helps. Please use @TriLife to ping me. I'm out of town for a few days and not monitoring the forum. Cheers.

Thanks Bob, If VNC is supported, that makes life a lot simpler. No additional wires, eISY stays in the IT cabinet etc. I'll wait for @Michel Kohanim's input on what I need to do to get VNC set up that way. Cheers.

Greetings, A couple of questions on using the eISY as a desktop. 1- the unit has 2 HDMI outputs. But can I use just one of them to drive two monitors via a KVM switch in extended mode? (Trying to decide which KVM to buy) 2- what is the version and resolution of the HDMI outputs? 3- is it possible to use the eISY as a desktop with a remote access program like VNC or remote desktop (set up like a Raspberry Pi)? If so, which application would you recommend? I use VNC for my RPis and Remote Desktop for my Win PCs. Cheers.

Greetings; I'm expanding the MQTT node server that @xKing started a while ago. I added a "dimmer" device based on Tasmota. I can ON/OFF/DIM/BRIGHTEN from the AC and from the Tasmota web UI. When I use Google Voice, "Turn ON/OFF Dimmer" works as well. It doesn't respond to "DIM/BRIGHTEN Dimmer" or similar language like "SET dimmer to 30%". Notably absent from Google Home GUI are dim/bright controls! I did set the device up as a LIGHT in ISY Portal and it has hint = [2,9,0,0]. Any ideas? Thanks

Good Morning @EWhite, your MQTT node server should be asking you to upgrade (from Beta). Again! But this time you should see version 0.0.12 (Thanks @bpwwer) and that will hopefully be the last of it. Until someone asks for an iteration! Sorry for all the iterations.