Temperature

[MrBill]

Not sure if this should be one thread or two.  It's really probably really two different topics but since to me it's all one topic I'm just going to do it here as one thread.

 

The problem that I'm trying to solve is obtaining the temperature of two rooms for the purpose of fireplace control.  (The gas fireplaces in each room are already controlled by ISY (but without temperature control), and I already have a nifty nag program to alert me repeatedly if they are running while my away mode is activated, and additionally they are on the checklist for manual off setting if we leave town.) 

 

While researching what product to order, I realized a few things.  1) I don't need a manual temperature control like a thermostat would have.  2) Nor do I want any type of digital display.  3) Nor do I want something large and bulky on the wall (like a thermostat).  Instead I just need the ISY to know the temperature of the room.  So I need a temperature sensor and not a thermostat. 

 

After reading alot of long threads here and doing various searches here and via google, I decided to order two Aeotec Multisensor 6's.  I really have no current use for any of the other values it provides, but thought that I might play with the motion sensor portion as well at some point, primarily tho I just wanted temperature readings.

 

Out-of-the-box these sensors work quite a bit differently than I was expecting.  I remembered something in another thread tho, and went looking for that, after studying it I realized that I should be able to reconfigure the device to make it work using data from this document.  Specifically memory address 40 and 41 needed change.  40 changed to 1, and 41 changed to 10.  (I also planned to disable or raise thresholds of other sensors at some point to save battery, but primarily at this point I was just trying to get temp readings to report anytime the temp changed by 1 degree).

 

I was very confused trying to use the tool in the admin console and watching the Event Viewer for success or failure.  I really didn't know how to interpret much of the Z-wave stuff in the event viewer.   Then I found this thread and decided to try the browser method to set the Z-wave parameters. 

 

That worked much better:  I crafted the REST URLs https://192.168.1.99/rest/zwave/node/ZW003_1/config/query/40

and

https://192.168.1.99/rest/zwave/node/ZW003_1/config/set/40/1/1 (or 0 for the value in the next to last parameter).

 

That worked out much better for me, I could understand the result and see that I can change the value in the device back and forth between 1 and 0, and understand that it was actually changing.  Momentary Success!

 

Then I moved on to location 41, not so much luck.  I can't even get query to work:

 

attempting to set the value with: https://192.168.1.99/rest/zwave/node/ZW003_1/config/set/41/10/2 returns a similar result.

 

I realized the documentation was likely out of date and went searching for a more recent version and found this: https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/6052990305/original/ES%20-%20MultiSensor%206%20V1.08.pdf?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ2JSYZ7O3I4JO6DA%2F20171007%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20171007T173902Z&X-Amz-Expires=300&X-Amz-Signature=d1e7f13779b069c9c7babbf564384ae7b8d7be80d73790b4b828e85cc11966c2&X-Amz-SignedHeaders=Host&response-content-type=application%2Fpdf

 

(hopefully that long retarded looking url won't break for other people, but it's linked from here: https://aeotec.freshdesk.com/support/solutions/articles/6000036562-multisensor-6-firmware-update-6-17-2016-new-information-v1-08-11-02-2016- )

 

The only material change is that address 41 appears in the newer doc revision with a "size" of 3 instead of 2.  However, for the REST query "SIZE" isn't specified.  Thinking about it tho, I went back to the admin console z-wave parameter config tool and looked again at the "size" drop-down and noted that the only possibilities there are the (binary friendly) values of 1, 2, 4 -- No 3!  what the hell?

 

So the questions are:

 

1) is this the best sensor for me to be using for temperature, and if not what is your suggestion?

 

2) if this is the best sensor, can anyone help me figure out why I can't even "query" (let alone "set") location 41.

 

 

 

 

 

[GlowingHair]

I think you made a wise a wise choice with the multisensors, since you plan on using the motion capability in the future. I have two I use in bathrooms for humidity monitoring, and to control lighting during based on motion and ambient light level. With no need for motion, I would have chosen CAO Gadget tags, since they have temperature monitoring (along with other features) but cost about 1/2-2/3 what the Aeotech sensors cost and have worked out very well for my use cases.

[Teken]

Not sure if this should be one thread or two.  It's really probably really two different topics but since to me it's all one topic I'm just going to do it here as one thread.

 

The problem that I'm trying to solve is obtaining the temperature of two rooms for the purpose of fireplace control.  (The gas fireplaces in each room are already controlled by ISY (but without temperature control), and I already have a nifty nag program to alert me repeatedly if they are running while my away mode is activated, and additionally they are on the checklist for manual off setting if we leave town.) 

 

While researching what product to order, I realized a few things.  1) I don't need a manual temperature control like a thermostat would have.  2) Nor do I want any type of digital display.  3) Nor do I want something large and bulky on the wall (like a thermostat).  Instead I just need the ISY to know the temperature of the room.  So I need a temperature sensor and not a thermostat. 

 

After reading alot of long threads here and doing various searches here and via google, I decided to order two Aeotec Multisensor 6's.  I really have no current use for any of the other values it provides, but thought that I might play with the motion sensor portion as well at some point, primarily tho I just wanted temperature readings.

 

Out-of-the-box these sensors work quite a bit differently than I was expecting.  I remembered something in another thread tho, and went looking for that, after studying it I realized that I should be able to reconfigure the device to make it work using data from this document.  Specifically memory address 40 and 41 needed change.  40 changed to 1, and 41 changed to 10.  (I also planned to disable or raise thresholds of other sensors at some point to save battery, but primarily at this point I was just trying to get temp readings to report anytime the temp changed by 1 degree).

 

I was very confused trying to use the tool in the admin console and watching the Event Viewer for success or failure.  I really didn't know how to interpret much of the Z-wave stuff in the event viewer.   Then I found this thread and decided to try the browser method to set the Z-wave parameters. 

 

That worked much better:  I crafted the REST URLs https://192.168.1.99/rest/zwave/node/ZW003_1/config/query/40

and

https://192.168.1.99/rest/zwave/node/ZW003_1/config/set/40/1/1 (or 0 for the value in the next to last parameter).

 

That worked out much better for me, I could understand the result and see that I can change the value in the device back and forth between 1 and 0, and understand that it was actually changing.  Momentary Success!

 

Then I moved on to location 41, not so much luck.  I can't even get query to work:

 

attempting to set the value with: https://192.168.1.99/rest/zwave/node/ZW003_1/config/set/41/10/2 returns a similar result.

 

I realized the documentation was likely out of date and went searching for a more recent version and found this: https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/6052990305/original/ES%20-%20MultiSensor%206%20V1.08.pdf?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJ2JSYZ7O3I4JO6DA%2F20171007%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20171007T173902Z&X-Amz-Expires=300&X-Amz-Signature=d1e7f13779b069c9c7babbf564384ae7b8d7be80d73790b4b828e85cc11966c2&X-Amz-SignedHeaders=Host&response-content-type=application%2Fpdf

 

(hopefully that long retarded looking url won't break for other people, but it's linked from here: https://aeotec.freshdesk.com/support/solutions/articles/6000036562-multisensor-6-firmware-update-6-17-2016-new-information-v1-08-11-02-2016- )

 

The only material change is that address 41 appears in the newer doc revision with a "size" of 3 instead of 2.  However, for the REST query "SIZE" isn't specified.  Thinking about it tho, I went back to the admin console z-wave parameter config tool and looked again at the "size" drop-down and noted that the only possibilities there are the (binary friendly) values of 1, 2, 4 -- No 3!  what the hell?

 

So the questions are:

 

1) is this the best sensor for me to be using for temperature, and if not what is your suggestion?

 

2) if this is the best sensor, can anyone help me figure out why I can't even "query" (let alone "set") location 41.

 

This is a very expansive route to take for little accuracy and long term costs. If running wire isn't practical than the CAO tags which a lot of folks seem to like would be a better fit and value. For me since this is for the long term I went with a hardwired solution using 1-Wire probes. Going this route ensures 100% reliability, consistency, no future out of pocket costs, and offers extreme temperature monitoring in any environment.  

 

I went with the Autelis ISY Bridge to easily integrate with the ISY Series Controller.

 

This is a *local first vs a cloud first* solution and doesn't require a constant cloud connection to operate. So you're not held hostage (IF) & (WHEN) other cloud dependent hardware ever go under or decided to charge you for data and access. 

 

Unfortunately, the vendor has most recently declared this product as not in production due to a lack of sales and hardware no longer being made available.

[MrBill]

I think you made a wise a wise choice with the multisensors, since you plan on using the motion capability in the future. I have two I use in bathrooms for humidity monitoring, and to control lighting during based on motion and ambient light level. With no need for motion, I would have chosen CAO Gadget tags, since they have temperature monitoring (along with other features) but cost about 1/2-2/3 what the Aeotech sensors cost and have worked out very well for my use cases.

 

I did look at CAO gadget tags at one point, my conclusion however was that they required a rasp-pi, is that true or false?  I could have easily overlooked something, as I only spent probably an hour reading on that product.

 

As far as motion, I doubt I'll really have practical use for it, we have two large dogs that have the run of the house.  I'll just add motion into my vacation mode notifications and that will likely be all that's practical.

 

 

This is a very expansive route to take for little accuracy and long term costs. If running wire isn't practical than the CAO tags which a lot of folks seem to like would be a better fit and value. For me since this is for the long term I went with a hardwired solution using 1-Wire probes. Going this route ensures 100% reliability, consistency, no future out of pocket costs, and offers extreme temperature monitoring in any environment.  

 

I went with the Autelis ISY Bridge to easily integrate with the ISY Series Controller.

 

This is a *local first vs a cloud first* solution and doesn't require a constant cloud connection to operate. So you're not held hostage (IF) & (WHEN) other cloud dependent hardware ever go under or decided to charge you for data and access. 

 

Unfortunately, the vendor has most recently declared this product as not in production due to a lack of sales and hardware no longer being made available.

 

I don't want cloud dependencies either, like you I wish that fad would go away , although I do wish I had a better and more reliable way to send notifications to myself (I currently send each twice to myself once as email to sms and the other email to email.  (but now I'm changing the subject.... in any case I've noticed you and I do seem to agree on many topics and methods)

 

As far as expense goes, it's really not a very big one-time expense, for all the arguments that YOU made, IF it solved the objective.  In this case I care not about monitoring energy usage, I simply want comfort level control.   Fishing wires is very possible, I'm crafty like that. (Someday I should make my EZIO2x4 installation look a bit cleaner and publish the pic I promised in another thread)

 

It's too bad the Autelis product is permanently out-of-stock.  I already have Autelis/Pentair Intellitouch Interface and love the way it updates ISY state variables.  I can only imagine his 1-wire firmware worked much the same.

 

As far a the CAO gadget tags go, they seem pi dependent, and at this point I haven't completely decided I want a pi dependncy, but if I choose to move ahead with adding a pi, I do have another use also once I figure out how error trapping works in python, I know what the problem is I just haven't figured out the fix yet, somewhat because of my methods and somewhat because I read very slow when comprehending.

 

At this point the MultiSensors will be going back tho, unless how I can figure out how to get the parameters set so that It reports one degree temp changes with a 1 degree threshold as they happen. 

 

If I ever had many other uses for z-wave traffic this solution may not be good either.  Since this is going to be sending temp changes at one degree intervals 24/7/365, when its really only needed 6 hours a day, 7 days a week for probably 8-12 weeks per year (fireplace season).

[GlowingHair]

The CAO tags are NOT pi dependent, but you do need a smartphone or computer to configure; being into home automation, I assume you have one or the other. They have "Kumo Apps" that can interface with the ISY; there are examples on this site which I have used successfully. They can be configured in one minute increments for reporting, and 1 degree increments for temperature change, so that might help you. The ARE cloud-dependent, so that is an issue for some. I just don't use them for anything safety-critical, but just to add information about the running of the household. I do use a couple of the tags to control ceiling fans (and one of those to control the electric fireplace), which is for comfort, not safety. I also use them so I know when my trash or recyclables have been picked up by city services. I also keep one in my purse to determine if I am home or away. I find them to be cost effective for my use cases,

[Jimbo.Automates]

2) if this is the best sensor, can anyone help me figure out why I can't even "query" (let alone "set") location 41.

 

The param 41 is messed up in all recent versions of the firmware.  A 3 byte value is not legal, and they do not know when or if it will be fixed, Chris has indicated they will make the ISY deal with this in the future.

 

I'm running firmware 1.09 on mine, and I am still not happy with the params that Aeotec has recommended which should provide proper threshold based updates when on battery.  Their support has been really good, but I am currently waiting for a response.

 

My Settings are here, with notes about what support has suggested and my notes

https://docs.google.com/document/d/108vJYiB7BZdLT5d8w8UAHrT18S_QfGMk1NWngz7U1_I/edit?usp=sharing

[MrBill]

The CAO tags are NOT pi dependent, but you do need a smartphone or computer to configure; being into home automation, I assume you have one or the other. They have "Kumo Apps" that can interface with the ISY; there are examples on this site which I have used successfully. They can be configured in one minute increments for reporting, and 1 degree increments for temperature change, so that might help you. The ARE cloud-dependent, so that is an issue for some. I just don't use them for anything safety-critical, but just to add information about the running of the household. I do use a couple of the tags to control ceiling fans (and one of those to control the electric fireplace), which is for comfort, not safety. I also use them so I know when my trash or recyclables have been picked up by city services. I also keep one in my purse to determine if I am home or away. I find them to be cost effective for my use cases,

 

Hmmm, That X's that item off the list.  Frankly I'd rather have a pi dependency than a cloud dependency.  (perhaps my memory is failing and this item got eliminated not for pi but cloud dependency.... frankly I'd rather a pi dependency than cloud.  With a pi I can have a second one ready to be plugged in at a moments notice.  Who knows if any cloud provider will still be in business in 6 months or 2 years, sure a lot use amazon aws under the hood, but when they quit paying the bill the service poofs....

 

Thanks for the info!

 

 

The param 41 is messed up in all recent versions of the firmware.  A 3 byte value is not legal, and they do not know when or if it will be fixed, Chris has indicated they will make the ISY deal with this in the future.

 

I'm running firmware 1.09 on mine, and I am still not happy with the params that Aeotec has recommended which should provide proper threshold based updates when on battery.  Their support has been really good, but I am currently waiting for a response.

 

My Settings are here, with notes about what support has suggested and my notes

https://docs.google.com/document/d/108vJYiB7BZdLT5d8w8UAHrT18S_QfGMk1NWngz7U1_I/edit?usp=sharing

 

I'm sorry, I don't know who Chris is?  Aeotec? UDI? 

 

If this is the case, it sounds like I need to send this device back.  Unless I'm wrong parameter 41 is key to me getting this portion of the detector working in the manner I need it to.  

 

Thanks for the info!

[Jimbo.Automates]

Yes, the Chris in that comment is from UDI who is the main developer. Not sure the timeline when this can be resolved.

 

Also, the Aeotec support is named Chris, I will ping him and see what he has found.

 

I have been using a CT100 that I got cheap as an outside thermometer because I wanted a display as well and it performs very well.

 

 

Sent from my Pixel XL using Tapatalk

[Teken]

I did look at CAO gadget tags at one point, my conclusion however was that they required a rasp-pi, is that true or false?  I could have easily overlooked something, as I only spent probably an hour reading on that product.

 

As far as motion, I doubt I'll really have practical use for it, we have two large dogs that have the run of the house.  I'll just add motion into my vacation mode notifications and that will likely be all that's practical.

 

 

 

I don't want cloud dependencies either, like you I wish that fad would go away , although I do wish I had a better and more reliable way to send notifications to myself (I currently send each twice to myself once as email to sms and the other email to email.  (but now I'm changing the subject.... in any case I've noticed you and I do seem to agree on many topics and methods)

 

As far as expense goes, it's really not a very big one-time expense, for all the arguments that YOU made, IF it solved the objective.  In this case I care not about monitoring energy usage, I simply want comfort level control.   Fishing wires is very possible, I'm crafty like that. (Someday I should make my EZIO2x4 installation look a bit cleaner and publish the pic I promised in another thread)

 

It's too bad the Autelis product is permanently out-of-stock.  I already have Autelis/Pentair Intellitouch Interface and love the way it updates ISY state variables.  I can only imagine his 1-wire firmware worked much the same.

 

As far a the CAO gadget tags go, they seem pi dependent, and at this point I haven't completely decided I want a pi dependncy, but if I choose to move ahead with adding a pi, I do have another use also once I figure out how error trapping works in python, I know what the problem is I just haven't figured out the fix yet, somewhat because of my methods and somewhat because I read very slow when comprehending.

 

At this point the MultiSensors will be going back tho, unless how I can figure out how to get the parameters set so that It reports one degree temp changes with a 1 degree threshold as they happen. 

 

If I ever had many other uses for z-wave traffic this solution may not be good either.  Since this is going to be sending temp changes at one degree intervals 24/7/365, when its really only needed 6 hours a day, 7 days a week for probably 8-12 weeks per year (fireplace season).

 

It really comes down to use case, preference, and long term expectations. 

 

I've been using countless battery operated devices my entire life. At this point I'm trying very hard to reduce them in my home if and when I can. It's quite amazing to see two large bins filled with spare batteries from various little coin cells, AAA, AA, C, D, 9 Volt, CR123, Specialty ~ to ~ massive LiPoe's. Just tired of the expanse, storage, and endless servicing that comes with having battery operated devices.

 

Anytime I can implement a hardwired solution that can be powered via POE, Solar, 120 / 240 VAC.

 

I will . . .

 

It never ceases to amaze me after all of these years there's always that one item that stops working right when you needed it!! In 2017 one would have thought someone could produce an accurate, high quality, long lasting, environmental sensor. Sadly, the only recourse is to use tried and true *Old School* technology like Dallas 1-Wire.

[Jimbo.Automates]

This isn't good news. Here's what Aeotec support says. So basically sending updates based on threshold changes doesn't work after 1.06 firmware. And earlier versions had other issues...

 

I've recently found out there may be issues with Parameter 41 in this firmware version, the only version where it works properly is V1.06 based on some of the tests I've found where Wakeup Report is actually in charge of when thresholds are checked which is something you can consider changing to speed up the checks (wakeup interval report).

 

 

Some possibility is to have Multisensor 6 report temperature at an interval instead of thresholds as a possibility.

 

 

 

Sent from my Pixel XL using Tapatalk

[MrBill]

This isn't good news. Here's what Aeotec support says. So basically sending updates based on threshold changes doesn't work after 1.06 firmware. And earlier versions had other issues...

 

I've recently found out there may be issues with Parameter 41 in this firmware version, the only version where it works properly is V1.06 based on some of the tests I've found where Wakeup Report is actually in charge of when thresholds are checked which is something you can consider changing to speed up the checks (wakeup interval report).

 

 

Some possibility is to have Multisensor 6 report temperature at an interval instead of thresholds as a possibility.

 

 

 

Sent from my Pixel XL using Tapatalk

 

 

Thanks for that. 

 

I'm shocked actually that there are not better options for collecting temperatures into an ISY, z-wave or otherwise.  There are many things that could (should) be temp controlled as well as alarmed (freezer temp).

[larryllix]

Thanks for that. 

 

I'm shocked actually that there are not better options for collecting temperatures into an ISY, z-wave or otherwise.  There are many things that could (should) be temp controlled as well as alarmed (freezer temp).

CAO wireless Tags are very impressive with temperature, humidity, motion, light level, XYZ axis position. Look for several threads here about these units.

 

EDIT:Looking back in the thread I see this has been raised before. They are not 3rd party CPU dependent so no RPi is needed. They do require their own proprietary Tag Manager though, as well as a cloud connection, even though many features are direct on your LAN only. (permissive thing?)...and they do take batteries about once per year CR2032 cheapies.

 

They do not detect motion via iR scanning. They detect motion by changing their physical position.

[Teken]

Thanks for that.

 

I'm shocked actually that there are not better options for collecting temperatures into an ISY, z-wave or otherwise. There are many things that could (should) be temp controlled as well as alarmed (freezer temp).

The closet thing I've found is the (SP) Z-Wave Fibero 1 Wire sensor. I don't recall the model off the top of my head but the one I was really interested supported 1~4 sensors?!?

 

There's a long thread about it here so search for it.

 

The fact it's reliable & accurate 1-Wire, Wireless, and Z-Wave met all of the important criteria I stated up top before.

 

Sadly, I've haven't found a vendor who sells it here at a reasonable price in a North American frequency.

 

Let me know if you do because I would be very interested in a group buy!!!

 

 

 

 

Sent from my iPhone using Tapatalk

[MrBill]

CAO wireless Tags are very impressive with temperature, humidity, motion, light level, XYZ axis position. Look for several threads here about these units.

 

EDIT:Looking back in the thread I see this has been raised before. They are not 3rd party CPU dependent so no RPi is needed. They do require their own proprietary Tag Manager though, as well as a cloud connection, even though many features are direct on your LAN only. (permissive thing?)...and they do take batteries about once per year CR2032 cheapies.

 

They do not detect motion via iR scanning. They detect motion by changing their physical position.

 

I reviewed CAO wireless tags again, after they were raised above. In my mind, I had indeed confused this product with something else, which blurred things for me. This in fact may be the best option.  There is a cloud dependency which I continue to not prefer.  It's a plus to me that additional tags can be used as a simple home/away sensor.  Question, Do I need ISY portal to use these, or does networking module alone allow interface?  (I resist recurring subscriptions, and already own networking module.)

 

 

The closet thing I've found is the (SP) Z-Wave Fibero 1 Wire sensor. I don't recall the model off the top of my head but the one I was really interested supported 1~4 sensors?!?

 

There's a long thread about it here so search for it.

 

The fact it's reliable & accurate 1-Wire, Wireless, and Z-Wave met all of the important criteria I stated up top before.

 

Sadly, I've haven't found a vendor who sells it here at a reasonable price in a North American frequency.

 

Let me know if you do because I would be very interested in a group buy!!!

 

 

 

 

Sent from my iPhone using Tapatalk

 

I'll check into it, I have limited available time for a bit but I'll open a bunch of tabs on the subject on my iPad as I have nearly 4 hours of airplane time coming soon.

 

I haven't done any research yet on this, but another concept that's been floating in my head, is to outfit an Arduino with 1-wire interface and WIFI to update ISY via REST.  Arduino's seem pretty resilient, I built one of these a few years ago and have never had to reload the software or had the memory get scrambled randomly.   I haven't yet done Arduino and Ethernet however, but it shouldn't be a problem.  If that works out, I may build several for different areas and for readily available spares.

[larryllix]

I reviewed CAO wireless tags again, after they were raised above. In my mind, I had indeed confused this product with something else, which blurred things for me. This in fact may be the best option.  There is a cloud dependency which I continue to not prefer.  It's a plus to me that additional tags can be used as a simple home/away sensor.  Question, Do I need ISY portal to use these, or does networking module alone allow interface?  (I resist recurring subscriptions, and already own networking module.)

<snipped>

No. The most difficult part is installing the kumoapp code into kumoapp webpages.

 

I have four. One that tells the temperature of my vehicle glovebox. It was an away/home sensor experiement tht never went away.

One that has been used to calibrate and confirm temperatures and cycles in the run of thermostats I have spent megabucks on.

One outside that is used for wetaher  station things.

One in my cold cellar that backs up an Insteon stat for humidity control.

 

With the supreme temperature accuracy and 0.001C resolution they are handy for checking and calibrating other things.

Fo home/away a little slow detecting away but has detected our vehicle almost 2 km away coming home. (think open garage door vs car home detection logic)

[MrBill]

I just spent more time than I should have reading on CAO wireless tags.  For the one time price with no subscription fees, and because ISY portal is not needed, I will try these out toward the end of this month. (I won't have time to set it up until a non-related revenue producing project wraps up in about 2 weeks.)

 

The multisensor 6's are on the way back to Amazon.  The parameter 41 bug still seems to effect even after changing wakeup interval, it still by default waits for the 2 degree threshold before reporting temp change... meaning if the detector wakes up it doesn't report temp until it has changed by 2 degrees, the default value of missing parameter 41.  

[Teken]

Keep in mind if you're not adverse to running wire to the end points there are quite a few 1-Wire systems in the market. If you do a search in this UDI forum for 1-Wire you will learn there are nice options similar to the Autelis Bridge.

 

But offer vastly more features, options, and won't go poof because of a lack of marketing!

[MrBill]

Keep in mind if you're not adverse to running wire to the end points there are quite a few 1-Wire systems in the market. If you do a search in this UDI forum for 1-Wire you will learn there are nice options similar to the Autelis Bridge.

 

But offer vastly more features, options, and won't go poof because of a lack of marketing!

 

I didn't' realize there were others similar to autellis I'll do as you suggest before proceeding with an order.

 

I agree.  If my kids inherited the house (in the future), and a cloud dependency failed they would probably have no clue what to do.  With a local option, there will always be spare parts on hand with detailed help pages.

[Teken]

I didn't' realize there were others similar to autellis I'll do as you suggest before proceeding with an order.

 

I agree.  If my kids inherited the house (in the future), and a cloud dependency failed they would probably have no clue what to do.  With a local option, there will always be spare parts on hand with detailed help pages.

 

MrBill,

 

To save time here is the related thread I was speaking of. In post 11 you will see the product which supports 4 1-Wire sensors via Z-Wave protocol: https://forum.universal-devices.com/topic/17513-fibaro-fgk-101-doorwindow-sensor-plus-temp/?hl=%2Bfibaro+%2Bfgk+%2B101

 

I still haven't found a vendor who sells this in the USA / Canada Z-Wave frequency so if you do let me know. As I would be really interested in a group buy on this fantastic piece of hardware.