smokegrub

Thanks for the feedback. I don't know how a newly linked device found its way into the hidden devices on MobiLinc but it did. Problem solved.

An Insteon ApplicanceLinc is blue in the device tree of my ISY99i IR Pro. It is used in a program nested in a folder and turns a light on and off at specified times. It performs the task as programmed and it may be turned on and off at the device tree level in the admin control panel. However, it does not appear in the list of devices in MobiLinc. It only appears there as part of the nested program. Does anyone know here know why or should I address my question to MobiLinc?

Glad you found the solution.

Having had a problem similar to this some time ago, try backing up to your desktop then moving the file to where you wish. I use a Mac as well.

Problem solved. You put me on the right track. The problem was that I needed to group them. They now display in the same manner as the other sensors. Thanks.

If I did accidentally, how do I ungroup them? Should I remove them from the folder they have been placed in and then add them back to the folder one at a time?

I have completed installation of a third hidden door sensor. When the first two were completed they were displayed in a hierarchical manner in the device tree: Primary Node Low Battery Heartbeat The one I just finished appears with all 3 nodes at the same level: Primary Node Low Battery Heartbeat The device properly displays its status and, using a program, it sends a notification when opened. Are any of you familiar with what might cause this unusual display in the device tree?

I tested the setup again this morning and the [20] was an artifact caused by incorrectly entering my TSTAT device number with the decimal points. When I changed the format to xx xx xx (with spaces) rather than xx.xx.xx the correct temperature was emailed, 68.5 degees F. My thanks to all of you for the help. Now, I must begin my education using variables since this showed me they are essential for some tasks.

Thanks, Stu. Looks like I am getting a reading of [20]. Which, if it is correct, is in degrees centigrade. Do you know how to have the report in degrees fahrenheit?

I set it up with this in the body of the message: Indoor Temps $(sys.node.20 49 6D 1.ST) and that is what I got when I received an alert--no temperature.

Xathros: The device number for my thermostat is 20.29.6D

I read what I could find on variables and it was sketchy at best. I could find no detailed information on how/where to create the variable. Of course, I saw the Variables tab and opened it but I can find nothing that tells me what to put in each of the fields and definitely nothing about where/how I would create the variable ${sys.node.zw011_1.52}. By the way, what is the expression zw011_1.52? Is it supposed to be the device ID? Sorry for the bother but I am in over my head here.

Thanks, Paul. Will read.

That programming is totally foreign to me and I have not yet used variables. Where can I turn to get guidance on how to attempt this?

I have searched and I can find nothing but I thought I would check with the pros before I abandoned the idea. Thanks.

Thanks, I can do that. What I want to know is can its current temperature (whatever that may be) at a given time be sent. In other words, if I want to know what the temperature is at 7:00 am every morning can I get a notification with the actual temperature at that time.

Is it possible to have a 2441ZTH thermostat (powered) notify me daily at 7:00 am of its current temperature and humidity?

I have had similar experiences.

Thanks for the feedback.

I have not yet used Z-Wave and I need some door sensors where the Insteon Hidden Door Sensor is not compatible. Are you using the Z-Wave product? Plusses? Minuses?

My experience with notifications routed by one ISP (Suddenlink ) to another ISP (Cox) are invariably slow, ranging from 5-30 minutes! Notifications originating within Cox and delivered to my Cox account range from seconds to a few minutes. Motion activated photos always take several minutes.

: ) Actually, when something fails to do what it was supposed to do I stumble around a lot trying to figure out which program/scene/device is the culprit. Given that I am 70 years old I have an excuse!

That is pretty much what I do.

19 programs and that seems a lot to me. How do you guys keep up with all those programs?

My thanks, again, to you guys. It sounds like an Elk 9200 and an Insteon 2635-222 are in my future. The solution is expensive, but it sounds perfect for my application. It seems evident that if the Elk fails, it fails open. That could leave us without hot water but feedback and the simplicity of the design seem to indicate such a failure has a low probabilty. If the Insteon device fails, I have a couple of backups on hand.