1-Wire Temperature Sensors Not Updating

[Deac99]

Has anyone experienced 1-Wire Temperature Sensors not getting updated in the software?  I had about 10 sensors that have all been working fine, then I added about 10 more sensors but in the mean time upgraded to V9 Software and they don't seem to work anymore.

Specifically what is happening is I will get them working but after a few hours they simply stop updating in the software.

I open Live view and they are all showing but showing old temperatures and they do not update.

I click on "1-Wire Monitor"  and instantly everything is updated and it will work for a few hours, but then it gets hung up again.

Very concerned because before if I disconnected a sensor (to simulate a broken wire or whatever type of fault) it would show as -30 and I could have it send me an alarm, but now if I disconnect a sensor it just continues showing the last value and the heat valves stay in whatever position they were in when it stopped working.

I've sent a ticket to Loxone but I figured I'd reach out to the community as well in case someone else has seen this.

[Clegger]

Hmm. I noticed a few days ago that all the temps in our system were "stuck" at their last values, but haven't had time to look into it. Just looking at the config now, the 1-wire extension seems to have disappeared completely, presumably since the last update. I tried adding it back by searching, but get the message that "The search was stopped because Extension '1-wire extension' is offline!"

I don't have time to go any further until the weekend, but if you learn anything from Loxone, could you please share with the list?

Many thanks

[Deac99]

OK I got it figured out.  I forgot that the extension has a maximum of 20 sensors.  I ended up with 26 sensors on the bus and I have long runs and a somewhat complicated topography.  Lox Support said you can get away with more than 20 if you have short runs and easy topography but in my case - it was a no-go.  To verify if this is happening you can check the miniserver for CRC errors.  An additional thing that really bothered me is that the bus stopped working and I was not notified of an error.  

I figured out how to correct all that and made some notes for myself in case I run into that issue again.  Below are my notes - I ended up making a sensor fault mailer for each sensor because I am not in my house over the winter and I depend on the Loxone to keep the house from freezing.

To see if there are CRC errors:

Click on 1 wire extension in periphery window

Click on device status

Right click on the 1 wire extension in status window

Click on detailed device information Give it a few seconds and a txt file will come up with information.

You should have many packets with 0 or very few CRC errors.  CRC errors are caused by having too many sensors or too long a run or noise in the lines.

 

It should say 0 85 Degree problems or close to zero -  85 Degree problems are caused by not having enough voltage for the sensor.

 

If there are excessive CRC errors the bus will stop running and the values on the Loxone will show the last value which could cause serious failures.

 

To get an alarm upon failure of a sensor:

Click on the sensor

Check “Display Error Output”

Check Use Validation and enter a value for Receive Timeout – This value will depend on how often you poll for temperature, I used 60 seconds

Go to Messages in periphery

[Rahul and Nandita Thakrar]

I just found this as I've been having some issues with my 1-wire sensors. They were all working and suddenly they have just stopped (they can't even be detected). The error I am getting is the 0 85 Degree problem referred to in the previous post.

Here is the output of that text file which based on the previous post indicates not enough voltage for the sensor. Any idea how I can rectify that? Thanks

Name: 1-Wire Extension (Utility)
Type: 1-Wire Extension



** Extension-Info **

Serial: 05D91F92
Firmware Version: 12010322
Hardware Version: 2
LastReceived 233 s ago
Serial: 05d91f92
Firmware Version: 12010322
Hardware Version: 2


1-Wire Serial 28.80.77.55.0E.00.00.65: 0 Packet Requests, 0 CRC Errors, 0 85 Degree Problems;

1-Wire Serial 28.42.DA.9C.0E.00.00.E1: 0 Packet Requests, 0 CRC Errors, 0 85 Degree Problems;

1-Wire Serial 28.A2.87.99.0E.00.00.30: 0 Packet Requests, 0 CRC Errors, 0 85 Degree Problems;

1-Wire Serial 28.2A.C0.99.0E.00.00.C3: 0 Packet Requests, 0 CRC Errors, 0 85 Degree Problems;

1-Wire Serial 28.1A.74.55.0E.00.00.55: 0 Packet Requests, 0 CRC Errors, 0 85 Degree Problems;

1-Wire Serial 28.BE.EC.99.0E.00.00.77: 0 Packet Requests, 0 CRC Errors, 0 85 Degree Problems;

1-Wire Serial 28.E1.C1.97.0E.00.00.7C: 0 Packet Requests, 0 CRC Errors, 0 85 Degree Problems;

1-Wire Serial 28.ED.96.99.0E.00.00.D0: 0 Packet Requests, 0 CRC Errors, 0 85 Degree Problems;

1-Wire Serial 28.8B.77.55.0E.00.00.9D: 0 Packet Requests, 0 CRC Errors, 0 85 Degree Problems;

1-Wire Serial 28.1B.65.99.0E.00.00.F8: 0 Packet Requests, 0 CRC Errors, 0 85 Degree Problems;

1-Wire Serial 28.7F.8E.99.0E.00.00.4D: 0 Packet Requests, 0 CRC Errors, 0 85 Degree Problems;

1-Wire Serial 28.32.E7.99.0E.00.00.90: 0 Packet Requests, 0 CRC Errors, 0 85 Degree Problems; 

[David]

You’re most likely going to need to disconnect sensors and/or wiring methodically until you find it works again. This will be the only way to rule out a faulty sensor or wiring issue.

David

[Rahul and Nandita Thakrar]

Thanks - tried this and worked out which sensor was faulty! Thankfully not the probes which are in the floor!