theitprofessor Posted May 9, 2023 Posted May 9, 2023 Just to add to the conversation I use Pushover for all notifications, not texts or emails "this is the way" If the device is in your ISY, IoP, or IoX AC you can monitor the state change with a simple program and send a push notification to your phone or table. Very simple to do in a program, might take a slight learning curve to understand the HTTPS POST string, plenty of easy to read short documentation with examples . But once you do one it's mostly reusable, just copy and replace a few words here and there. So if you have a non Insteon device and you use PG3 with a node server like say a Garage Door Opener which puts that Opener in your AC you can simply monitor if something and like the door just opened. Pushover also has about 20 different musical tones you can add in addition to the push notification. So you can make the audio a little more dramatic and get your attention for something like the garage door just opened and it's 2 AM. 1
n4bos Posted May 9, 2023 Author Posted May 9, 2023 I'm looking forward to trying the YoLink device. I have the YoLink freezer monitors in three freezers and they report very reliably even through the metal box of the freezer. MrBill, Can you elaborate a little on how a YoLink device (for example) appears in the eisy? Can you name it like you could with Insteon? I'm not familiar with setting up a node server as I understand is required but I'm sure there is help here if (when) I get lost. Also, I read in one of the eisy documents that the new Insteon devices will not work with eisy. Assuming I didn't misunderstand, that makes it even more compelling to find replacements for my existing Insteon stuff. I use several 2450 I/O Links around here so the gate is kind of a trial case. If I can get that to work, I have no doubt I can get the other things to work.
Geddy Posted May 10, 2023 Posted May 10, 2023 15 hours ago, n4bos said: Can you elaborate a little on how a YoLink device (for example) appears in the eisy? Can you name it like you could with Insteon? I think I recall @MrBill saying elsewhere that he doesn't have any YoLink devices (yet). But you can look through the YoLink area of the forums to learn more or ask specific questions there for help. Also reviewing the YoLink information in the Polyglot store or even the github for the node server might be good sources for self help and answering general questions. 15 hours ago, n4bos said: Also, I read in one of the eisy documents that the new Insteon devices will not work with eisy. Assuming I didn't misunderstand, You did misunderstand that. UDI has confirmed that they are working with Insteon to support the new i3 devices. UDI even posted a block in early March about the efforts to support new devices. https://www.universal-devices.com/i3-support/ As with many things in the IoT/HA field these days nothing should be considered permanent. It's always good to have an idea of what else is out there, but for the foreseeable future I think most of us will be fine with the new iteration of Insteon and the ongoing development that UDI has in place for eisy and Polyglot.
MrBill Posted May 10, 2023 Posted May 10, 2023 16 hours ago, n4bos said: I'm looking forward to trying the YoLink device. I have the YoLink freezer monitors in three freezers and they report very reliably even through the metal box of the freezer. MrBill, Can you elaborate a little on how a YoLink device (for example) appears in the eisy? Can you name it like you could with Insteon? I'm not familiar with setting up a node server as I understand is required but I'm sure there is help here if (when) I get lost. Also, I read in one of the eisy documents that the new Insteon devices will not work with eisy. Assuming I didn't misunderstand, that makes it even more compelling to find replacements for my existing Insteon stuff. I use several 2450 I/O Links around here so the gate is kind of a trial case. If I can get that to work, I have no doubt I can get the other things to work. I don't have any yo-link devices, however in general a device appears as a node in your device tree. You might have an Insteon module named "Blue Lamp", you might have a YoLink node named "Kitchen Refrigerator" or "Gate", the first node would be reporting temps, the second Open/Close etc. Any value on those nodes you should be able to use in an IF statement on a program.... i.e. If gate is open then.... or if insteon-button then {open gate}... etc The only thing I don't like about Yo-link is it requires a cloud server. I always try to find Local only solutions to problems, that don't require the internet or cloud servers. Basically a node server let's you combine sensors, for example if my pool pump starts to draw more current (amps) it probably means the Filter needs to be backwashed but could mean some other trouble... anyway... If pool pump draws greater than 250 then notify bill.... or turn on an Insteon light... or flash a hue bulb blue... you get the idea... --- Also when referencing someone else in the forum you should either quote all or part of their post, and/or type there name preceded by an @ sign. such as: and then select the name when the tag appears. It will then appear in text as @n4bos either of those actions will result in the user being notified that they were quoted or mentioned. As it is I only found your message to me here because @Geddy mentioned me in his reply. (I was in NY last week and have so much unread forum that I wouldn't notice right now just because there are new messages.) 1
n4bos Posted May 10, 2023 Author Posted May 10, 2023 @MrBill said... "Also when referencing someone else in the forum you should either quote all or part of their post, and/or type there name preceded by an @ sign." I wasn't aware of that. Thanks! The YoLink device(s) do require a cloud server to work with THEIR hub (free at this time) but I had assumed (I know, very dangerous) that if the device was being addressed from the eisy, no cloud server would be required, just as if it was an Insteon device, no?
Geddy Posted May 10, 2023 Posted May 10, 2023 1 hour ago, n4bos said: I had assumed (I know, very dangerous) that if the device was being addressed from the eisy, no cloud server would be required, just as if it was an Insteon device, no? No. The node server links to the same cloud system they use. It's as if it's logging in just as you would with their app. It maintains the connection using the ISY Portal (at least that's how I read it as a reply from @Javi in another thread. Also, the YoLink has to handle the information somehow. It has to go from the (local) device to their (local) hub to their cloud then the node server syncs the information to IoX/eisy. It's not making a connection directly from the eisy to the (local) hub. Oh, and your mention you still have to select the name to get the mention to work. Still didn't get the notification to @MrBill, but that should.
n4bos Posted May 10, 2023 Author Posted May 10, 2023 Thanks for the info! BTW, the YoLink sensor arrived and works VERY well at least when hand held AT the gate. Very reliably reports the gate is open or closed. So with that, I will at least now be notified if the gate is opened or closed. Now to get it to control some lights etc. Thanks for the help! 45 minutes ago, Geddy said: Oh, and your mention you still have to select the name to get the mention to work. Did that work??? Steve
Javi Posted May 10, 2023 Posted May 10, 2023 1 hour ago, Geddy said: No. The node server links to the same cloud system they use. It's as if it's logging in just as you would with their app. It maintains the connection using the ISY Portal (at least that's how I read it as a reply from @Javi in another thread. Also, the YoLink has to handle the information somehow. It has to go from the (local) device to their (local) hub to their cloud then the node server syncs the information to IoX/eisy. It's not making a connection directly from the eisy to the (local) hub. I'm not sure how the YoLink Node Server gets data, this would be a question to ask the YoLink Node Server developer. Some devices/services can be connected locally without cloud service (i.e. openSprinkler, iTach), some devices/services require a cloud component (i.e. weather data not obtained from your own weather station). IMHO if you own the device and it is on your local network you should not need a cloud service for local connections. If you own the device, it is on your local network, and you are required to have a cloud service to query/control from the local network, then you have to ask yourself how is the MFG covering server cost. Every connection requires the MFG to foot the bill to maintain the server. We have all seen many companies offer these services for free then later realize they are losing money due to server cost. At that point they shutdown or charge a fee for access to the device that you thought you owned. 1
n4bos Posted May 10, 2023 Author Posted May 10, 2023 48 minutes ago, Javi said: If you own the device, it is on your local network, and you are required to have a cloud service to query/control from the local network, then you have to ask yourself how is the MFG covering server cost. Every connection requires the MFG to foot the bill to maintain the server. We have all seen many companies offer these services for free then later realize they are losing money due to server cost. At that point they shutdown or charge a fee for access to the device that you thought you owned. I agree with your opinion however there are still quite a number of services that aren't charging at least, at this time. The YoLink temperature sensors and the remote open/close sensor work VERY well with their hub and obviously, their server. Honeywell and Nest and of course, Amazon with their Alexia are three more better known ones. Wouldn't surprise me if they started charging after some time but I think that's risky on their part since so many people are using their devices "for free". I was hoping the YoLink integration on the eisy might not require their server but perhaps I was mistaken. I'm planning to bring up my second ISY as a stand alone device to test out the Z-wave link. If that goes well, I'll have more incentive to figure out a more permanent Z-wave implementation .
Recommended Posts