Skip to content

Troubleshooting Guide

Solutions to common issues with the Hitachi CSNet Home integration.

Quick Diagnosis

Start here to identify your issue:

Symptom Likely Category Jump To
Can't find integration when adding Installation Issues
Authentication fails Configuration Issues
No entities created Configuration Issues
Entities show "Unavailable" Connection Issues
Controls don't respond Control Issues
Wrong temperature readings Sensor Issues
Alarms appearing Alarm Issues

Installation Issues

Symptoms: Can't find "Hitachi CSNet Home" when adding integration

Causes: - Integration not properly installed - Home Assistant not restarted after installation - Browser cache showing old data - File permissions incorrect

Solutions:

  1. Verify Installation: 

    ls -la custom_components/csnet_home/
    Should show: __init__.py, manifest.json, and other files

  2. Check manifest.json: 

    cat custom_components/csnet_home/manifest.json
    Should contain valid JSON with "domain": "csnet_home"

  3. Fix Permissions (if needed): 

    chmod -R 755 custom_components/csnet_home/
chown -R homeassistant:homeassistant custom_components/csnet_home/

  4. Clear Browser Cache:

  5. Press Ctrl+Shift+R (or Cmd+Shift+R on Mac)

  6. Or clear browser cache completely

  7. Restart Home Assistant:

  8. Settings → System → Restart

  9. Wait 2-3 minutes for full restart

  10. Check Logs:

  11. Settings → System → Logs
  12. Filter for csnet_home
  13. Look for loading errors

Integration Loads But Shows Errors

Symptoms: Errors in logs about missing dependencies or import failures

Causes: - Missing Python dependencies - Incompatible Home Assistant version - Corrupted files

Solutions:

  1. Check Home Assistant Version:
  2. Requires HA 2023.1.0 or newer

  3. Update if needed

  4. Reinstall Dependencies: 

    pip install -r custom_components/csnet_home/requirements.txt

  5. Reinstall Integration:

  6. Delete custom_components/csnet_home/
  7. Reinstall fresh copy
  8. Restart Home Assistant

Configuration Issues

Authentication Failed

Symptoms: "Invalid credentials" or "Authentication failed" error

Causes: - Incorrect username or password - Typo in credentials - Account locked or inactive - CSNet Manager service down

Solutions:

  1. Test Credentials:
  2. Open https://www.csnetmanager.com
  3. Try logging in with same credentials

  4. If login fails, reset password there

  5. Check for Typos:

  6. Re-enter credentials carefully
  7. Check for extra spaces

  8. Verify caps lock is off

  9. Try Password Reset:

  10. Go to CSNet Manager website
  11. Use "Forgot Password" feature
  12. Set new password

  13. Try again with new password

  14. Check Account Status:

  15. Ensure account is active
  16. Verify email is confirmed

  17. Check for any account restrictions

  18. Test API Availability: 

    curl -I https://www.csnetmanager.com
    Should return HTTP 200

No Entities Created

Symptoms: Configuration succeeds but no climate or sensor entities appear

Causes: - No devices in CSNet Manager account - Devices not properly configured in CSNet Manager - Initial sync not complete - Integration crashed during setup

Solutions:

  1. Verify Devices in CSNet Manager:
  2. Open CSNet Manager app/website
  3. Check that devices appear
  4. Verify zones are configured

  5. Ensure system is online

  6. Wait for Initial Sync:

  7. Can take 1-2 minutes after configuration
  8. Wait for scan_interval (default 60 seconds)

  9. Refresh Home Assistant browser

  10. Check Logs for Errors:

  11. Settings → System → Logs
  12. Look for csnet_home errors

  13. Note any exceptions or failed API calls

  14. Enable Debug Logging: 

    # configuration.yaml
logger:
  logs:
    custom_components.csnet_home: debug

  15. Restart Home Assistant
  16. Try configuration again

  17. Check logs for detailed errors

  18. Remove and Re-add:

  19. Delete the integration
  20. Restart Home Assistant
  21. Add integration again
  22. Wait 2-3 minutes

Wrong Number of Entities

Symptoms: Expected more/fewer zones or sensors

Causes: - System configuration differs from expectations - Some zones disabled in CSNet Manager - DHW not configured - Sensors only appear for certain configurations

Solutions:

  1. Count Zones in CSNet Manager:
  2. Open CSNet Manager app
  3. Count how many thermostats/zones shown

  4. Compare with Home Assistant

  5. Check DHW Configuration:

  6. Water heater entity only appears if DHW configured

  7. Verify in CSNet Manager settings

  8. Review System Type:

  9. Some sensors only for specific configurations
  10. Check sensor.system_controller_unit_model

  11. Fan coil sensors only on compatible systems

  12. Check Entity Registry:

  13. Settings → Devices & Services → Entities
  14. Filter by csnet
  15. Look for disabled entities

Connection Issues

Entities Show "Unavailable"

Symptoms: All or some entities show as "Unavailable"

Causes: - Internet connection lost - CSNet Manager service down - Integration crashed - Authentication expired

Solutions:

  1. Check Internet Connection: 

    ping 8.8.8.8
ping www.csnetmanager.com

  2. Check Connectivity Sensor:

  3. Look at sensor.{device}_connectivity

  4. If "off", device can't reach cloud

  5. Check Last Communication:

  6. Look at sensor.{device}_last_communication

  7. If timestamp is old, connection lost

  8. Restart Integration:

  9. Settings → Devices & Services
  10. Find CSNet Home

  11. Click ⋮ → Reload

  12. Check CSNet Manager Status:

  13. Try accessing www.csnetmanager.com

  14. If site is down, wait for service restoration

  15. Re-authenticate:

  16. Delete integration
  17. Re-add with credentials
  18. May need to refresh authentication

Intermittent Unavailability

Symptoms: Entities become unavailable then recover

Causes: - Unstable internet connection - WiFi signal issues - CSNet Manager service intermittent - Scan interval too aggressive

Solutions:

  1. Check WiFi Signal:
  2. Monitor sensor.{device}_wifi_signal
  3. Should be better than -70 dBm

  4. Move device or improve WiFi if weak

  5. Increase Scan Interval:

  6. Current default: 60 seconds
  7. Try increasing to 120 or 180 seconds

  8. Reduces API call frequency

  9. Monitor Connection: 

    automation:
  - alias: "Log Connection Issues"
    trigger:
      - platform: state
        entity_id: sensor.remote_living_room_connectivity
        to: "off"
    action:
      - service: logbook.log
        data:
          name: "CSNet Connection"
          message: "Device went offline at {{ now() }}"

  10. Check Network Quality:

  11. Run continuous ping test
  12. Check for packet loss
  13. Verify DNS resolution

Control Issues

Temperature Changes Don't Work

Symptoms: Set temperature but system doesn't respond

Causes: - System is off - Temperature already at target - Eco mode using different setpoint - Manual override at physical thermostat - Control sync delay

Solutions:

  1. Check HVAC Mode:
  2. Ensure mode is Heat or Cool (not Off)

  3. Check climate entity state

  4. Check Current vs Target:

  5. Compare current_temperature with temperature

  6. System won't heat if current > target

  7. Check Operation Status:

  8. Look at operation_status_text attribute

  9. Verify system is actually running

  10. Wait for Sync:

  11. Changes can take 1-2 minutes to sync

  12. Wait for next scan_interval update

  13. Verify in CSNet Manager:

  14. Check if change appears in CSNet app

  15. If not, may be API issue

  16. Check for Alarms:

  17. Look at alarm_code attribute
  18. Alarms may prevent operation

Mode Changes Don't Work

Symptoms: Try to change HVAC mode but it doesn't change

Causes: - Unsupported mode for configuration - System protection active - Physical lock-out enabled - API command failed

Solutions:

  1. Check Available Modes:
  2. Look at climate entity attributes

  3. hvac_modes: shows supported modes

  4. Try via CSNet Manager:

  5. Test if mode change works there

  6. If not, physical/system restriction

  7. Check for Errors:

  8. Enable debug logging

  9. Look for API response errors

  10. Restart Integration:

  11. Reload CSNet Home integration
  12. Try mode change again

Preset Mode Doesn't Change

Symptoms: Eco/Comfort mode doesn't switch

Causes: - Feature not supported on zone - Temperature limits prevent change - API command malformed

Solutions:

  1. Check Preset Modes Available:
  2. Look at preset_modes: attribute

  3. Should show [comfort, eco]

  4. Verify ecocomfort Value:

  5. Check integration logs for ecocomfort field

  6. Should be 0 (eco) or 1 (comfort), not -1

  7. Try Temperature Change Instead:

  8. Manually adjust temperature
  9. May be more reliable

Sensor Issues

Sensor Shows "Unknown"

Symptoms: Sensor state is "Unknown" or blank

Causes: - Value not provided by your system - Feature not supported on your model - Initial data sync incomplete - Sensor doesn't apply to configuration

Solutions:

  1. Wait for Full Sync:
  2. First sync can take 1-2 scan intervals

  3. Wait 2-3 minutes after configuration

  4. Check System Type:

  5. Some sensors only on specific models
  6. Water sensors require hydraulic system

  7. Fan sensors require fan coil configuration

  8. Verify Data in API:

  9. Enable debug logging

  10. Check if value exists in /data/elements response

  11. Accept as Expected:

  12. Some sensors genuinely not applicable
  13. Hide/disable unused sensors

Temperature Reading Seems Wrong

Symptoms: Temperature value doesn't match reality

Causes: - Thermostat location not ideal - Sync delay (not real-time) - Unit conversion issue - Sensor calibration needed

Solutions:

  1. Wait for Update:
  2. Sensors update every scan_interval (60s default)

  3. Not real-time, small delays normal

  4. Compare with CSNet Manager:

  5. Check temperature in CSNet app

  6. Should match (if not, report as bug)

  7. Check Thermostat Location:

  8. Ensure thermostat properly located

  9. Not in direct sunlight, draft, or near heat source

  10. Calibrate in CSNet Manager:

  11. Some thermostats can be calibrated
  12. Check CSNet Manager settings

WiFi Signal Showing Weak

Symptoms: sensor.{device}_wifi_signal shows poor value (< -70 dBm)

Causes: - Device far from WiFi router - Interference - WiFi network issues

Solutions:

  1. Improve WiFi Coverage:
  2. Move router closer
  3. Add WiFi extender/mesh node

  4. Use 2.4GHz band (better range)

  5. Reduce Interference:

  6. Change WiFi channel

  7. Move away from interfering devices

  8. Check Device Connectivity:

  9. Monitor sensor.{device}_connectivity
  10. If stable despite weak signal, may be acceptable

Alarm Issues

Alarm Code Appearing

Symptoms: alarm_code sensor shows non-zero value

Causes: - Actual system fault - Temporary condition - Maintenance required - System protection activated

Solutions:

  1. Check Alarm Message:
  2. Look at alarm_message sensor

  3. Read alarm_origin for location

  4. Check CSNet Manager:

  5. Open CSNet Manager app
  6. Look for alarm details there

  7. May have more information

  8. Consult Manual:

  9. Look up alarm code in system manual

  10. Check [Alarm Code Reference]

  11. Basic Checks:

  12. Is system powered on?
  13. Is water pressure adequate (1-2.5 bar)?
  14. Is outdoor unit clear of obstructions?

  15. Are all valves open?

  16. Reset if Temporary:

  17. Some alarms auto-clear
  18. Try turning system off then on

  19. Check if alarm clears

  20. Call for Service:

  21. Persistent alarms need professional service
  22. Contact Hitachi technician
  23. Provide alarm code and description

False Alarm Notifications

Symptoms: Getting alarm notifications but no real issue

Causes: - Transient conditions trigger alarms - Notification automation too sensitive - Alarm history sensor updates

Solutions:

  1. Add Delay to Automation: 

    trigger:
  - platform: state
    entity_id: sensor.remote_living_room_alarm_active
    to: "on"
    for: "00:05:00"  # Wait 5 minutes

  2. Filter by Alarm Code: 

    condition:
  - condition: template
    value_template: "{{ states('sensor.remote_living_room_alarm_code') | int > 10 }}"

  3. Check Alarm History:

  4. Review sensor.alarm_history attributes
  5. See if alarms are clearing quickly

Performance Issues

High CPU Usage

Symptoms: Home Assistant CPU usage high, integration blamed

Causes: - Scan interval too low - Too many concurrent API calls - Logging too verbose

Solutions:

  1. Increase Scan Interval:
  2. Default 60s is good for most

  3. Increase to 120-180s if needed

  4. Disable Debug Logging:

  5. Remove debug logging if enabled

  6. Only enable when actively troubleshooting

  7. Check for Loops:

  8. Review automations using CSNet entities
  9. Ensure no infinite loops

Slow Response

Symptoms: Commands take long time to execute

Causes: - CSNet Manager API is slow - Internet connection latency - Cloud service load

Solutions:

  1. This is Normal:
  2. Cloud-based control has inherent latency
  3. 5-10 second delays are expected

  4. Not same as local control

  5. Check Internet Speed:

  6. Run speed test

  7. Ensure adequate bandwidth

  8. Monitor API Response Times:

  9. Enable debug logging temporarily
  10. Check how long API calls take

Advanced Troubleshooting

Enable Debug Logging

Add to configuration.yaml:

logger:
  default: warning
  logs:
    custom_components.csnet_home: debug

Restart Home Assistant, then: 1. Go to Settings → System → Logs 2. Filter for csnet_home 3. Reproduce issue 4. Capture logs

Capture API Response

  1. Open browser Developer Tools (F12)
  2. Go to www.csnetmanager.com
  3. Navigate to Network tab
  4. Log in
  5. Find /data/elements request
  6. Copy response JSON

This shows what data your system provides.

Check Integration State

# In Developer Tools → Template
{{ states.climate | selectattr('entity_id', 'search', 'remote') | list }}
{{ state_attr('climate.remote_living_room', 'operation_status') }}
{{ states.sensor | selectattr('entity_id', 'search', 'system_controller') | list }}

Restart Integration

Without removing configuration: 1. Go to Settings → Devices & Services 2. Find Hitachi CSNet Home 3. Click ⋮ (three dots) 4. Click Reload

Reinstall Clean

Complete reinstall: 1. Settings → Devices & Services 2. Delete CSNet Home integration 3. Restart Home Assistant 4. Delete custom_components/csnet_home/ folder 5. Reinstall integration files 6. Restart Home Assistant 7. Add integration again

Getting Help

Before Asking for Help

Gather this information:

  1. Home Assistant version: Settings → About
  2. Integration version: Check manifest.json
  3. System type: Yutaki model, zone configuration
  4. Error messages: From logs
  5. Steps to reproduce: What you did before issue

Where to Get Help

GitHub Discussions (Questions): 👉 https://github.com/mmornati/home-assistant-csnet-home/discussions

GitHub Issues (Bugs): 👉 https://github.com/mmornati/home-assistant-csnet-home/issues

When Reporting: - Include all information above - Attach debug logs - Share elements API response (redact personal info) - Describe expected vs actual behavior

Contributing Fixes

Found a bug? Know how to fix it? 1. Fork the repository 2. Create a fix 3. Submit a Pull Request 4. Help others with the same issue!

Common Error Messages

"Config flow could not be loaded"

Meaning: Integration failed to initialize config flow

Fix: - Check installation - Verify all files present - Restart Home Assistant

"Platform error: csnet_home"

Meaning: Error loading climate/sensor platform

Fix: - Check logs for specific error - Verify configuration - May need reinstall

"Update failed"

Meaning: Coordinator couldn't update data

Fix: - Check internet connection - Verify authentication - Check CSNet Manager availability

"Unknown error occurred"

Meaning: Unexpected error in integration

Fix: - Enable debug logging - Check full error in logs - Report as bug if persistent

Prevention Tips

✅ DO

  • Keep Home Assistant updated
  • Keep integration updated
  • Monitor connectivity sensors
  • Have stable internet connection
  • Use recommended scan_interval (60s)
  • Enable logging when troubleshooting
  • Report bugs to help community

❌ DON'T

  • Set scan_interval < 30 seconds
  • Make rapid repeated changes
  • Ignore alarm notifications
  • Disable without investigating
  • Mix multiple integration versions
  • Forget to restart after changes

Next Steps

← Back to Home | Next: FAQ →