ncat <control r IP> 9798

[hokiebrian]

I am able to connect locally to my Control R Module.

ncat 192.168.x.x 9798

monitor
help for help

Typing "list" gives all the properties that are seen in the cloud. This does not require any auth to access. From what I can gather, it is the same data that is current in the cloud - it isn't actually "real time". Anyone know anything more about this console?

"help" shows all commands, many available.

Also, port 9799 is open. When connecting, get "{"protocol":[1]}" - I have no idea what that might be for.

Anyways - it's local and requires no auth. That was attractive. I can do a custom sensor to pull the data, it's just updated at the maintenance interval though and I'm not sure how to trigger that using the port 9798 console.

[explosivo22]

Amazing find. I will work on investigating on my end to see what all can be done.

[explosivo22]

I did some digging and there is just a few things missing from the local port as far as water heater information.

I currently have what I would call a hybrid solution up and running. I use the cloud to setup the integration and pull the water heater name, serial number, model, and the local IP address. I then set it up to use the local IP and port to make all the calls locally so no cloud calls are involved to change any values.

I thought about going full local and asking just the for host name, but currently that would require the integration to be removed and added back. I was thinking maybe we hold off on that unless we have enough people that want complete local.
We only call the cloud on initial setup to get the missing information and only once on initial startup when your HA instance is restarted to maintain that information.

If you would like to try out an alpha version, I have created a branch dev-local with all these new features that you could download and install on your HA instance to try out. I have been getting a couple errors, but I think I know what that is related to I just need to implement those fixes now.

[talex-05]

I've tried to install from the dev-local branch, but HA does not populate with any devices or entities.
HACS does not give me the option to install from dev-local branch even with allowing betas. If I try adding through custom repository menu HA states that it is available in the store. I installed 1.3.8, overwrote files in custom_components\rinnai with dev-local files, reboot, add integration, config flow succeeds, but only the integration update sensor is created. I am able to ncat to the host on 9798. Apologies as I'm not an HA expert

[explosivo22]

I have actually got an issue in this branch right now that I am working through. The local information does not come in clean at all, so I am sorting through all that.

[talex-05]

I appreciate your time and efforts! Is the install process as I described correct?

[joshmackey]

Started playing with this myself.

The values from list are live except for the ones prefixed with m. Pasting the output of list below for any onlookers.

list
               m01_water_flow_rate_raw:  9 (0x9) {116s}
                m02_outlet_temperature:  133 (0x85) {115s}
              m03_combustion_hours_raw:  0 (0x0) {2h}
                 m04_combustion_cycles:  0 (0x0) {2h}
                     m05_fan_frequency:  175 (0xaf) {110s}
          m06_other_system_controllers:  101 (0x65) {2h}
       m07_water_flow_control_position:  1 (0x1) {2h}
                 m08_inlet_temperature:  42 (0x2a) {106s}
                       m09_fan_current:  38 (0x26) {104s}
            m10_total_bath_fill_volume:  0 (0x0) {2h}
 m11_heat_exchanger_outlet_temperature:  136 (0x88) {101s}
             m12_bypass_servo_position:  11 (0xb) {100s}
                                   m13:  null {-}
              m14_internal_temperature:  null {-}
     m15_indoor_antifreeze_temperature:  61 (0x3d) {98s}
                                   m16:  null {-}
    m17_outdoor_antifreeze_temperature:  null {-}
                                   m18:  null {-}
                        m19_pump_hours:  0 (0x0) {2h}
                       m20_pump_cycles:  0 (0x0) {2h}
               m21_exhaust_temperature:  66 (0x42) {94s}
                ma__total_water_volume:  null {-}
                      maintenance_list:  '1,2,3,4,5,6,7,8,9,10,11,12,15,19,20,21,100,101,102,120,121,122' {2h}
                    mc__total_calories:  null {-}
                            error_code:  '   ' {2h}
                      lime_scale_error:  null {-}
                   domestic_combustion:  false {41s}
                  domestic_temperature:  135 (0x87) {93m}
                 recirculation_capable:  true {2h}
                recirculation_duration:  null {-}
                     temperature_table:  2 (0x2) {2h}
                          module_start:  null {-}
                           device_boot:  null {-}
                           ap_mac_addr:  '-----------' {2h}
                             public_ip:  null {-}
                              local_ip:  'x.x.x.x' {2h}
                wifi_channel_frequency:  '2462' {2h}
                  wifi_signal_strength:  '-80' {215s}
                             wifi_ssid:  '---------' {2h}
             recirculation_temperature:  null {-}
                      zigbee_inventory:  '[]' {2h}
                         zigbee_status:  null {-}
                          warning_code:  '   ' {2h}
              do_maintenance_retrieval:  null {85s}
                          lock_enabled:  false {2h}
          maximum_domestic_temperature:  null {-}
          minimum_domestic_temperature:  null {-}
                     operation_enabled:  true {2h}
                       priority_status:  false {2h}
                 recirculation_enabled:  false {244s}
          recirculation_not_configured:  null {-}
              set_domestic_temperature:+ null {-}
                 set_operation_enabled:  null {-}
                   set_priority_status:  null {-}
             set_recirculation_enabled:  null {9m}
                              schedule:+ null {-}
                      schedule_enabled:+ null {-}
                      schedule_holiday:+ null {-}
                              timezone:+ 'PST8PDT,M3.2.0,M11.1.0' {2h}
                  heater_serial_number:  null {-}
                                 model:  null {-}
               module_firmware_version:  '238' {2h}
                      module_log_level:+ null {-}
                     rinnai_registered:  null {-}
                             do_zigbee:  null {-}
                          baton_shadow:  null {-}
                            baton_info:  null {-}
                             exception:  null {-}
                               ca_info:  null {-}

[joshmackey]

Turning on trace mode makes the system output when a property changes it seems.

[sirmeili]

This looks interesting. Has the local stuff made it into the main release yet?

[explosivo22]

This has not yet. I have worked on it, but keep running into errors parsing all the data over time which seems to cause the local side to stop responding or locking up one of the two. I am still working on it though locally.

[sazwerner]

Hi @explosivo22 , Any details you can share about the parsing errors you're seeing or repro steps? I'd be happy to contribute some time and help out where possible.

[TesLocker]

This Rinnai integration enables our home’s most used and most loved automations. We would love to be able to run with local communcation. Thanks for all the work that has gone into the cloud version, and now the local version!

[explosivo22]

Hi @explosivo22 , Any details you can share about the parsing errors you're seeing or repro steps? I'd be happy to contribute some time and help out where possible.

@sazwerner I have managed to get this branch at least what I would consider stable. I have been running it for a couple months and have only saw a couple errors in the log related to connection issues which I attribute to network or just HA issues. The hardest part is everything from this connection comes back as byte data and parsing the correct location is the hardest part.

This Rinnai integration enables our home’s most used and most loved automations. We would love to be able to run with local communcation. Thanks for all the work that has gone into the cloud version, and now the local version!

@TesLocker Currently I have this as what I would consider hybrid. I use the cloud initially to grab the name and device IP reported. I then make the connection locally and continue doing only local calls after setup. I am still working on the full local solution, but anyone could test this out now if you manually install the dev-local branch files. You will need to remove the integration first due to the differences in the setup process currently. I plan to continue working on this though.