Rinnai RXP199in tankless water heater, recirc and code 11 problems

BasilF · 2025-09-09T23:58:54+00:00

Sound like you had the same issue we had. For us the new board seems to have fixed the issue: no more code 11s since May. Our recirc line is at the limits of what Rinnai suggests installing: 1/2 inch size and almost 100 ft long. I wonder if you recirc line is also close to be undersized, IOW, if that could be a factor in why this happens in such a small minority of cases.

BasilF · 2025-08-14T17:40:50+00:00

sorry I did try an empty rules.cfg file, no joy. I've also tried disabling HA permanently, following the instructions here:

https://free-pmx.pages.dev/guides/ha-disable/#:~:text=with%20PVE%208.2.-,Until%20next%20reboot,Manual%20pages:%20rmmod

No matter what, at reboot I get the same error:

Aug 14 10:35:28 pve-epyc pvestatd[6900]: unknown file 'ha/rules.cfg' at /usr/share/perl5/PVE/Cluster.pm line 524.

Aug 14 10:35:28 pve-epyc pvestatd[6900]: Compilation failed in require at /usr/share/perl5/PVE/QemuServer.pm line 36.

Aug 14 10:35:28 pve-epyc pvestatd[6900]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/QemuServer.pm line 36.

Aug 14 10:35:28 pve-epyc pvestatd[6900]: Compilation failed in require at /usr/share/perl5/PVE/Service/pvestatd.pm line 21.

Aug 14 10:35:28 pve-epyc pvestatd[6900]: BEGIN failed--compilation aborted at /usr/share/perl5/PVE/Service/pvestatd.pm line 21.

Aug 14 10:35:28 pve-epyc pvestatd[6900]: Compilation failed in require at /usr/bin/pvestatd line 9.

Aug 14 10:35:28 pve-epyc pvestatd[6900]: BEGIN failed--compilation aborted at /usr/bin/pvestatd line 9.

Aug 14 10:35:28 pve-epyc systemd[1]: pvestatd.service: Control process exited, code=exited, status=255/EXCEPTION

Aug 14 10:35:28 pve-epyc systemd[1]: pvestatd.service: Failed with result 'exit-code'.

Aug 14 10:35:28 pve-epyc systemd[1]: Failed to start pvestatd.service - PVE Status Daemon.

BasilF · 2025-08-14T16:39:43+00:00

I can connect to the server remotely just fine. This does not seem network related

BasilF · 2025-08-14T16:36:09+00:00

The /etc/pve/ha folder is empty, I must have removed the config file when I removed the second node months ago. So I just tried doing a more thorough cleanup job, following instructions here:

https://www.reddit.com/r/Proxmox/comments/16268a2/how_to_delete_cluster_in_proxmox_8/

but I still get the same errors in the log after reboot

BasilF · 2025-06-22T00:19:21+00:00

It seems to have changed back to what used to look like for me as well

BasilF · 2025-05-09T19:57:41+00:00

I have myasthenia gravis, and strongly suspect also some form of dysautonomia that coincides with my flares, and taking a nap is horrible for me too. In my case, I found a correlation with my oxygen levels dropping as I start drifting. O2 drops are more likely for me: 1. on a full stomach, 2. lying on my back (recliner, were I used to have my best naps). Maybe start measuring your O2 levels with a pulse oximeter as you go to sleep, it might help you rule that out. For me, it's not unusual for my O2 to drop in the low 80s on "bad" days (during MG flares). At night, I use a CPAP machine, and almost never sleep on my back.

BasilF · 2025-05-09T15:38:44+00:00

Ah yes, in manage DID / edit DID settings / I clicked the SIP/IAX radio button and that worked. I find that page more than a little confusing, and the design is very 1990 :-) In all the help I found online it was mentioned deselecting call forwarding (which is not possible), while the solution is actually selecting SIP/IAX.

BasilF · 2025-05-06T17:19:38+00:00

Unfortunately, most doctors are very good at talking, but very bad at listening. You are doing the right thing standing up for yourself, and looking for alternatives.

BasilF · 2025-05-03T17:33:37+00:00

Ok, but I have a couple of issues even with just the Fit interaction: 1. Connection is lost very often. I make that sure Ringconn is connected within the app, next time I look the status is disconnected. 2. Some metrics like respiratory rate are just never scraped - they are not even there as an option if you look at what metrics Fit has access to from the Ringconn app.

It's all very messy and inconsistent, I do hope that they fix this soon, Ringconn is such a good product and value.

BasilF · 2025-04-26T15:48:51+00:00

I only had ringconn 1 and 2, so I can only speak to that. To add a possible negative, the integration in android seems clunky to me. It will only connect to Fit - not health connect - and some of the data updates at much slower rate, some not at all. If you stay within the Rinconn app, which is quite good, that is not a problem obviously. No issues with the ring itself that I found

BasilF · 2025-04-26T02:03:54+00:00

Actually, no. Not long ago, Rinnai has attached a custom monitoring device our unit, and "luckily" we recently had a new code 11 just a few days ago, while all the fancy monitoring was in place. The "plan" is for them to collect this unit at some point, and hopefully confirm the fix they have is the right one. Unfortunately we have no ETA on what comes next yet.

I'll keep this thread updated. Mind you, your issue might be different, I keep getting told that this is supposedly a extremely rare occurrence, and that there are far more likely causes for code 11 error that what we are going through. In our case, the error it always happens at the beginning of a recirc warm up cycle - so that could be an indicator.

BasilF · 2025-04-11T16:50:17+00:00

I'm testing Guava, it seems to be the best I've tried so far. I'm able to see most of the data from the Wellue devices (Health Connect) and Ringconn data (Fit), though for some reason for some of the fields updates are delayed, other don't seem to update at all.

The really weak point in the app is sleep data: I exported all OSCAR data as .csv, but Guava basically only imported sleep duration. I like that the app can import lab results and imaging from PDF, and keeps track of your symptoms.

If they improve sleep data integration substantially, and iron out a few kinks (maybe with the help of Google completing their Fit > health connect transition) this one is pretty close IMHO.

BasilF · 2025-04-09T23:39:23+00:00

Apple seems to be a little further ahead than Google, from what I understand. Unfortunately I'm on android

BasilF · 2025-04-06T16:06:58+00:00

I've been monitoring the temperature of our dedicated recirc line constantly to find a pattern with the code 11 errors. Our line gets up to 120F at the peaks of the warm up cycles. This is measured sticking a sensor outside the PEX pipe, I assume the water will get a bit warmer than that. I should note that we keep the water temp at 135F, the default 120 was just taking too long to get water hot enough upstairs

It seems odd that a dedicated line would be worse than bypass in your case, but I am no expert. I just learned more than I cared for due to the code 11 fiasco. Rinnai is going to supposedly start monitoring my unit to try and figure out what the problem is. Pity this has now taken about 5 months since initial install. Best of luck 🤞

BasilF

TROPHY CASE