TriLife

Thanks @Geddy. I'll give @xKing a few days to get back to me and then head to git. Wasn't aware of this option. I have tried the Tasmota User group, but they couldn't help here. Cheers.

Good morning! It has been 4 days since I posted the above question. No answers. Is it the topic, or did I do something to offend the community? Cheers

This worked, kind of. First, the ADC on the Sonoff (3 different units) was given erratic readings. So I ended up ordering a WeMo Mini D1. That worked well. And with the Yaml as shown, I can get readings of ADC and tue relay in the IoX. I cannot, however seem to access the ADC to write a program in IoX. Started a separate thread on this. So far no news on how to fix it. Cheers.

Greetings; I am monitoring the turbidity of my creek and based on water quality want to activate a Sluice gate to divert water to my lagoon. (we get heavy rains here in the mountains of Colombia and water quickly turns to milk-coffee). Using @xKing's MQTT note server, I have the following YAML entries for the tasmotized Wemo Mini D1, which senses trubidity on A0 (GPIO17) and uses D1 (GPIO5) to control the Relay: # Creekside WeMo Mini D1 with ADC. TOPIC in WeMo Mini D1 MQTT CONFIG "Creek"! - id: "Turbidity" name: "Creek Turbidity" type: "analog" status_topic: "tele/Creek/SENSOR" cmd_topic: "cmnd/Creek/power" - id: "Sluice" name: "Creek Sluice" type: "switch" status_topic: "stat/Creek/POWER" cmd_topic: "cmnd/Creek/power" (This is an adaptation of the yaml entries used for a Sonoff 4CH or Dual. Same TOPIC "Creek"), but different id/name. This works) And I do get a reading in the MAIN Panel for CREEK TURBIDITY: And I can control CREEK SLUICE as well However, when I try to create a program to activate CREEK SLUICE according to the reading of CREEK TURBIDITY, the CREEK TURBIDITY sensor is not showing up in the drop down menu. Only the CREEK SLUICE relay status shows. I did scroll all the way to the bottom, just in case 🙂 : Any idea, why this might be the case? Thanks in advance. Cheers.

Follow-up on this: The same .YAML file has another couple of items in it: - id: "ClrTemp" name: "Cellar Temp" type: "TempHumid" status_topic: "tele/ClrTemp/SENSOR" cmd_topic: "cmnd/ClrTemp/POWER" This answers the first question about the syntax for tele/Creek/SENSOR the other entry is for a Sonoff 4CH unit: # QUAD Wine Cellar (TOPIC in Sonoff MQTT CONFIG is "CLR4CH") IP x.120 - id: "ClrCinta" #{1:"Orientes", 2:"Cellar", 3:"Cinta", 4:"Floor"} name: "Cellar Light" type: "switch" status_topic: "stat/CLR4CH/POWER1" cmd_topic: "cmnd/CLR4CH/power1" - id: "ClrFan" name: "Cellar Fan" type: "switch" status_topic: "stat/CLR4CH/POWER2" cmd_topic: "cmnd/CLR4CH/power2" - id: "ClrOpen" name: "Open Cellar" type: "switch" status_topic: "stat/CLR4CH/POWER3" cmd_topic: "cmnd/CLR4CH/power3" - id: "ClrClose" name: "Close Cellar" type: "switch" status_topic: "stat/CLR4CH/POWER4" cmd_topic: "cmnd/CLR4CH/power4" So, based on this, I think I'll have to create 2 ids, one for the analog sensor, the other for the relay. Something like this: # TOPIC in modified Sonoff SV MQTT CONFIG "Creek"! - id: "Turbidity" name: "Creek Turbidity" type: "analog" status_topic: "tele/Creek/SENSOR" - id: "Sluice" name: "Creek Sluice" type: "switch" status_topic: "stat/Creek/POWER" cmd_topic: "cmnd/Creek/power" BTW, the ADC input takes inputs up to 1V only, so a Voltage divider is in order. I'll update after trials.

Greetings; Long time no post! I have a little project, which requires me to read water turbidity and accordingly open/close a sluice. Therea are several approaches to this, but at first glance, the easiest is to use an existing Sonoff Basic (or SV) and have the ADC port read the value of the turbidity sensor (https://tasmota.github.io/docs/ADC/). The Tasmota MQTT would then publish the analog reading to tele/Creek/SENSOR . So far so good. The MQTT node server by @xKing lets me upload a .YAML file, in which I specify all the Sonoff switches I have. An individual entry looks like this: - id: "Creek" name: "Creek Control" type: "switch" status_topic: "stat/Creek/POWER" cmd_topic: "cmnd/Creek/power" The above looks just at the status of the Relay and lets me control it. How do I add the tele/Creek/SENSOR to this, so in IoP, I can read the tele/Creek/SENSOR and turn the cmnd/Creek/power ON? I could write a rule in Tasmota for such a simple task, but eventually I need to integrate data from my Davis WeatherStation into the decision process, so I'd rather get things set up right in the first place. Cheers!

I first bought the ELUTENG unit (which looks identical to the one you suggest on the Canadian site). While it did seem to successfully complete the flash, the Polisy never booted with it. I then reflashed it with the second unit and that worked just fine. It may have been a fluke defective unit, because @CPrince had no issues with it...

Good morning; My eISY is on its way to me, should be around Panama right now! I currently have ISY994 (5.3.0) with the Zwave 500 dongle, hooked up to PG2 on a Polisy (13.1). 100+ sonoff/Tasmotas (MQTT) and a slew of 5V Wired Z-Wave Aeotec Multi-sensor 6s. No PLM, no Insteon. Over the last few days lots of information on this and the 5.5.0. threads. Thanks for all the input! Question: Does Z-Wave migration from ISY/Zwave500 to eISY/Zmatter (for powered Z-Wave devices) work now? Cheers;

Thanks Bob; I have my 100+ Sonoff/Tasmotas running on PG2 and had them running on PG3 as well. (They are on PG2 again, until the migration path of all of my Zwave sensors is clear). On Polisy. That was accomplished by starting Mosquitto on port 1884 and enabling run at boot time. It is very stable, has been for a couple of years. MQTT EXPLORER shows all of my Sonoff/Tasmotas, but doesn't show the Solark15k... Is there a way (maybe via SSH) to see, what the messages/topics the mosquitto broker has coming in on port 1884? when you initially start the broker it does show a stream, but stop and restart seems to blow the whole thing up...

Greetings; I just got this RPi based software by solar-assistant.io, which allows me to get a real -time reading of my Sol-Ark 15k inverter. It connects to the RS485 port and spews out continuous messages via MQTT. It was set on port 1883, but we need to operate on 1884, so they told me how to modify mosquitto.conf to redirect this flow to 1884. So far so good. Except I seen NOTHING showing up anywhere. Neither on MQTT EXPLORER nor on tdmgr_0.2.11, nor any activity inside the PG3 logs... https://solar-assistant.io/help/integration/mqtt This website says that it is "good practice" to run an MQTT Bridge to communicate with the broker... Do we have something like that on Polisy or eISY? If so, how do I access it? " Universal Devices MQTT Bridge" doesn't return anything relevant. Cheers

Thanks for the clarification @lilyoyo1. I don't know about you guys, but for me it's time for a new year's libation. With all the fireworks in this country, we're staying home to comfort our dogs. happy New Year 🎉

That's what I figured, just wanting to make sure. But, if you migrate to ZMatter, is that a one-way street? That means, after migration ( successful or not) if i turn off eISY/ZMatter and turn on Polisy/zwave500 again, will the devices connect to the Polisy again? Or do the individual sensors get uniquely paired with eISY/ZMatter during migration? You understand my concern: migration is sketchy at this point, and I'm wondering if there is a working configuration to fall back on... Cheers and happy new year

If the migration tool isn't ready, would it not be possible to grey out the button until it works, @Michel Kohanim? It seems like there are a lot of people chomping at the bit to migrate and are just creating extra work for themselves and you in the process... Just a thought. Happy New year in any case!

How about we all give the UDI team a break over New Years and postpone any migration to 2023? They've been working very hard (and we've been sharing a ton of useful info for the team), to help us upgrade... Have a very happy New Year! Let's pick up this battle on 2 Jan.

Thanks Steve. Yes, i have all my multisensors configured that way. It's in their full manual. My comment was more directed at some of other weather devices like Davis Instruments. Temperature is their business. You'd think they would have it figured out.

Hi @asbril, Pardon the basic question here: when you say you upgraded both Polisy and eISY, does that mean your Z-Wave devices communicate with both at the same time? Or did you migrate from Polisy to eISY? When you migrate from Polisy/ISY/Z-Wave 500 to eISY/Zmatter do any changes happen to the Z-Wave devices? i.e. if for some reason the migration isn't successful, can i revert to Polisy combo as a fully functional system? Or is that a one-way ticket? cheers.

My eISY is in Auburn, CA, my ZMatter housing in transit to there, and my Polisy with ISY on PG2 (and I) are in Medellín... It'll be the second week of January before eISY shows up here... "Forced patience"... And an opportunity for the major bugs to be worked out. Not touching anything until then! Fortunately my wine cellar still opens with Google Assistant! Y'all have a great holiday season and a próspero año nuevo!

I wish all sensors defaulted to °C! 🤪

Good morning! Any news about the ability to migrate Z-Wave from the ISY dongle to IoP? The last announcement/banner on the website said 13. December or something like that. Shortly after that 5.5.0 was released, but I understood that it didn't include Z-Wave migration... And as a follow-up: if a migration path is not forthcoming l, is the ZMatter dongle functional to connect to Z-Wave sensors? Would that mean removing my two dozen sensors from their 15ft ceilings to re-pair them with the new dongle, or is there an easier way? Thanks.

Understood. No hurry here. You are absolutely right, there shouldn't be a case where this is necessary. But Davis Instruments is really weird and I haven't been able to transfer my date from one sytem to the other. So I am running both for now (priorities). And unless WeatherLink NS is able to handle the rest of the data, I may stay this way... BTW, the way you have it set up right now, DavisWeather uses an API and gets information from the Davis server and WeatherLink gets the information from the WeatherLink LIVE base. Both of these get their data from the weather sensors on my roof. In-house and on my WeatherLink app all data is in METRIC (per my choice). Not sure where the conversion occurs. OK. I'll ask OpenWeather to delete my account. Thanks @bpwwer for the clarification. (this is supposed to go on the very top 🤩) Cheers.

NO DICE. The bottom line seems to be that MQTT doesn't like operating on PG3 running ISY and IoP at the same time. It crashed. So, I'm back to PG2, since as of now there is no migration path for Z-Wave on Zmatter/PG3. Once that is available and I have my eisy here, I'll have an operating ISY/Polisy system and can try to migrate the whole shebang to IoP/eisy. Until then, I'm done with screwing around. Not worth my while. I'll still do the migration guide, once we have a Zwave migration for PG3 on Zmatter. Once again thank you @bpwwer and @Michel Kohanim for trying to help out. Sorry I wasted all of your time trying to find an interim solution. Lesson learned.

Hello there; Migrating from ISY on PG2 to IoP to PG3... bought the ELK NS, but am having a hard time making sense on accessing the keypads. Is there a manual somewhere? Or, at a minimum, can someone tell me how to find the Funcion keys? Cheers

The fix to this was restoring PG2 into PG3... I'm up and running now on PG3 only with IoP and ISY, with the minor detail of: No big deal, but then again, I'm anal! As I mentioned earlier, I ordered a brand new 32GB SSD. Should get it next week. Once I have it, I'll try to document the following to help get users with an old OS and MQTT devices to migrate to PG3: Pre-1: back up everything! 1- Flash OS13.1 2- Edit and save mosquitto.conf 3- Edit rc so mosquitto starts on reboot 4- start mosquitto 5- restore ISY into IoP 6- restore PG3 7- make sure all is running 8- do a Upgrade Packages from IoP... (I left this to last, since I do not yet dare upgrade to 3.1.16 and 5.5.0) (feel free to comment on the above!) Thanks again for all the input @bpwwer and @Michel Kohanim. You guys are awesome! Cheers

Hello Bob; As you said, in PG3 the two node servers on ISY were showing as " unmanaged" . So, I recorded the details and deleted first the DavisWeather node from PG2, leaving MQTT in place. after about half an hour, it still showed unmanaged. So I went ahead and deleted MQTT from PG2 as well. When I say "delete", I mean deleted from PG2, not from within ISY! It's been more than an hour now. they both still show as "unmanaged" on PG3... I rebooted Polisy and ISY. No change. I also changed the credentials for ISY inside PG2 just now, just to make sure it is no longer connected to ISY. No dice. Cheers.

Greetings; Since I had a rather painful migration, I experienced this several times. After installing MQTT node server, when you start configuring it, all fields are blank and no CONFIGURATION HELP is given. fortunately I had screenshots from PG2, so I just added the fields as necessary. Once set up and SAVED, the HELP pops up. On one of the last re-installs (I had too many to count), I tried entering and saving one field at a time. No dice. It wanted all of the fields necessary to connect. Then it splashed the HELP. It all works splendidly. Thanks @xKing. Screenshot when you first enter configuration. and only once it connects with all the necessary info, the config help shows up. Cheers