Home Assistant Neviweb130 Custom Components

🇫🇷 Version française

💛 Enjoying this integration?
If you'd like to support its ongoing development, you can contribute here:

Custom components to support Neviweb devices in Home Assistant (HA). Neviweb is a platform created by Sinopé Technologies to interact with their smart devices like thermostats, light switches/dimmers , load controllers, plug, valves and water leak detector etc.

Neviweb130 (Sinope Neviweb130 in HACS) will manage the Zigbee devices connected to Neviweb via the GT130 gateway and the new Wi-Fi devices connected directly to Neviweb. It is presently almost up to date with Neviweb but some information are still missing from Sinopé. As new devices are launched by Sinopé, they are added to this custom-component. If you have a device that is not supported yet, please open an issue and I'll add it quickly.

Report a problem or suggest an improvement: Open an issue

Table of contents

• Announcement
• Supported devices
• Prerequisite
• Installation
• Configuration
• Multi_accounts
• Sedna valve
• GT130
• Update system
• Request counter
• Multi instance (obsolete)
• Services / Actions
• Debugging
• Eco-Sinopé
• Energy statistic
• Localisation (language)
• Sedna flow meeter
• Troubleshooting
• Customization
• Device hard reset
• TO DO

Announcement

Big changes for Sedna valve devices

Since version 2.6.2, valves devices are supported as new HA valve entities. They are no longer supported as switch. This will cause all your switch.neviweb130_switch_sedna_valve to be replaced by valve.neviweb130_valve_sedna_valve entities. You will need to revise your automations and cards to retrieve your valve entities.

Supported Devices

Here is a list of currently supported devices. Basically, it's everything that can be added in Neviweb.

• Zigbee thermostats:
  • Sinopé TH1123ZB 3000W Line voltage thermostat
  • Sinopé TH1124ZB 4000W Line voltage thermostat
  • Sinopé TH1123ZB 3000W Thermostat for public areas
  • Sinopé TH1124ZB 4000W Thermostat for public areas
  • Sinopé TH1123ZB-G2 3000W Thermostat second generation
  • Sinopé TH1124ZB-G2 4000W Thermostat second generation
  • Sinopé TH1134ZB-HC for control of heating/cooling interlocking
  • Sinopé TH1300ZB 3600W Floor heating thermostat
  • Sinopé TH1320ZB-04 Floor heating thermostat
  • Sinopé TH1400ZB Low voltage thermostat
  • Sinopé TH1500ZB 3600W double pole thermostat
  • Nordik TH1420ZB-01 Nordik low voltage radiant hydroponic floor thermostat
  • Ouellet OTH3600-GA-ZB Ouellet Floor thermostat
  • Ouellet OTH4000-ZB Ouellet 4000W Line voltage thermostat
• Wi-Fi thermostats (no need for GT130):
  • Sinopé TH1124WF Wi-Fi 4000W Line voltage thermostat
  • Sinopé TH1123WF Wi-Fi 3000W Line voltage thermostat
  • Sinopé TH1133WF Wi-Fi 3000W Line voltage thermostat lite
  • Sinopé TH1133CR Sinopé Evo 3000w Line voltage thermostat lite
  • Sinopé TH1134WF Wi-Fi 4000W Line voltage thermostat lite
  • Sinopé TH1134CR Sinopé Evo 4000w Line voltage thermostat lite
  • Sinopé TH1143WF Wi-Fi 3000W two wires connection, color screen
  • Sinopé TH1144WF WI-Fi 4000W two wires connection, color screen
  • Sinopé TH1145WF Wi-Fi ? two wires connection, color screen
  • Sinopé TH1300WF Wi-Fi 3600W floor thermostat
  • Sinopé TH1310WF Wi-Fi 3600W floor thermostat
  • Sinopé TH1325WF Wi-Fi 3600W floor thermostat
  • Sinopé TH1400WF Wi-Fi low voltage thermostat
  • Sinopé TH1500WF Wi-Fi 3600W double pole thermostat
  • Sinopé TH6500WF Wi-Fi heat/cool
  • Sinopé TH6510WF Wi-Fi heat/cool
  • Sinopé TH6250WF Wi-Fi heat/cool
  • Sinopé TH6250WF_PRO Wi-Fi heat/cool
  • Sinopé THEWF01 Wi-Fi lite thermostat
  • Flextherm concerto connect FLP55 floor thermostat (sku FLP55 do not provide energy stats in Neviweb)
  • Flextherm True Comfort floor thermostat
  • SRM40 floor thermostat
• Heatpump controller:
  • Sinopé HP6000ZB-GE for Ouellet heat pump with Gree connector
  • Sinopé HP6000ZB-MA for Ouellet Convectair heat pump with Midea connector
  • Sinopé PH6000ZB-HS for Hisense, Haxxair and Zephyr heat pump
• Wi-Fi Heatpump controller:
  • Sinopé HP6000WF-MA for Ouellet Convectair heat pump with Midea connector
  • Sinopé HP6000WF-GE for Ouellet heat pump with Gree connector
  • Sinopé HP6000WF-TCL for Runtru/Ameristar heat pump
• Zigbee lighting:
  • Sinopé SW2500ZB Light switch
  • Sinopé SW2500ZB-G2 Light switch
  • Sinopé DM2500ZB Dimmer
  • Sinopé DM2500ZB-G2 Dimmer
  • Sinopé DM2550ZB Dimmer
  • Sinopé DM2550ZB-G2 Dimmer
• Zigbee lighting connected to Sedna valve:
  • Sinopé SW2500ZB-VA Light switch
  • Sinopé DM2500ZB-VA Dimmer
  • Sinopé DM2550ZB-VA Dimmer
• Zigbee specialized control:
  • Sinopé RM3250ZB Load controller 50A
  • Sinopé RM3500ZB Calypso load controller 20,8A for water heater
  • Sinopé SP2610ZB in-wall outlet
  • Sinopé SP2600ZB smart portable plug
  • Sinopé MC3100ZB Sedna valve multi-controller for alarm system
• Zigbee specialized control connected to Sedna valve:
  • Sinopé RM3250ZB-VA Load controller 50A
  • Sinopé SP2610ZB-VA in-wall outlet
  • Sinopé SP2600ZB-VA smart portable plug
  • Sinopé MC3100ZB-VA Sedna valve multi-controller for alarm system
• Wi-Fi specialized control:
  • Sinopé RM3500WF Load controller for water heater
  • Sinopé RM3510WF Load controller for water heater
  • Sinopé RM3250WF load controller 50A, Wi-Fi
• Water leak detector and valves:
  • Sinopé VA4201WZ, VA4221WZ, sedna valve 1 inch
  • Sinopé VA4200WZ, VA4220WZ, sedna valve 3/4 inch Wi-Fi
  • Sinopé VA4200ZB, sedna valve 3/4 inch Zigbee
  • Sinopé VA4220WZ, sedna 2e gen 3/4 inch
  • Sinopé VA4220WF, sedna 2e gen 3/4 inch, Wi-Fi
  • Sinopé VA4220ZB, sedna 2e gen 3/4 inch, Zigbee
  • Sinopé VA4221WZ, sedna 2e gen 1 inch
  • Sinopé VA4221WF, sedna 2e gen 1 inch, Wi-Fi
  • Sinopé VA4221ZB, sedna 2e gen 1 inch, Zigbee
  • Sinopé WL4200, water leak detector
  • Sinopé WL4200S, water leak detector with sensor
  • Sinopé WL4200C, perimeter cable water leak detector
  • Sinopé WL4200ZB, water leak detector
  • Sinopé WL4210, water leak detector
  • Sinopé WL4210S, water leak detector with sensor
  • Sinopé WL4210C, perimeter cable water leak detector
  • Sinopé WL4210ZB, water leak detector
  • Sinopé WL4200ZB, connected to Sedna valve
  • Sinopé ACT4220WF-M, VA4220WF-M, sedna multi-residential master valve 2e gen 3/4 inch, Wi-Fi
  • Sinopé ACT4220ZB-M, VA4220ZB-M, sedna multi-residential slave valve 2e gen 3/4 inch, Zigbee
  • Sinopé ACT4221WF-M, VA4221WF-M, sedna multi-residential master valve 2e gen. 1 inch, Wi-Fi
  • Sinopé ACT4221ZB-M, VA4221ZB-M, sedna multi-residential slave valve 2e gen. 1 inch, Zigbee
• Flow sensor: (supported as attribute for the 2e gen Sedna valves)
  • Sinopé FS4220, 3/4 inch flow sensor
  • Sinopé FS4221, 1 inch flow sensor
• Tank level monitor:
  • Sinopé LM4110-ZB, Propane tank level monitor
  • Sinopé LM4110-LTE, Propane tank level monitor LTE
• Gateway:
  • GT130
  • GT4220WF-M, mesh gateway
• Power supply:
  • Sinopé ACUPS-01, battery backup for Sedna valve, GT130 or GT125

Prerequisite

You need to connect your devices to a GT130 web gateway and add them in your Neviweb portal before being able to interact with them within Home Assistant. Wi-Fi devices must be connected directly to Neviweb. Some Zigbee devices can be connected directly to a Sedna valve which is connected to Neviweb directly. Please refer to the instructions manual of your device or visit Neviweb support

Wi-Fi devices can be connected in the same network (location) then the GT130 Zigbee devices or in a separate network. Neviweb130 support up to three networks in neviweb.

There are four custom components giving you the choice to manage your devices via the neviweb portal or directly via local

• neviweb (HACS: Sinope Neviweb) custom component to manage your devices via Neviweb portal.
• sinope (HACS: Sinope GT125) custom component to manage your devices directly via your GT125 web gateway.
• Zigbee gateway:
  • neviweb130 (HACS: Sinope Neviweb130) this custom component, to manage your devices via neviweb portal.
  • sinope-zha where I put all new Sinopé devices quirks before they are merged into zha-device-handlers. Buy a Zigbee gateway like Dresden ConBee II usb dongle and manage your Zigbee device locally via ZHA component. I'm adding support for Sinopé Zigbee in zha-device-handlers. You can test new Sinopé devices quirks in HA by coping the sinope-zha files directly in your HA setup. ZHA will load them in place of the standard sinopé quirks.

You need to install only one of them but all can be used at the same time on HA. Zigbee devices managed directly via ConBee II must be removed from Neviweb as they cannot be on two Zigbee networks at the same time.

Installation

Neviweb130 custom component to manage your device via Neviweb portal:

There are two methods to install this custom component:

• Via HACS component:
  • This repository is compatible with the Home Assistant Community Store (HACS).
  • After installing HACS, install 'Sinope neviweb-130' (neviweb130) from the store, and use the configuration.yaml example below.
• Manually via direct download:

  • Download the zip file of this repository using the top right, green download button.

  • Extract the zip file on your computer, then copy the entire custom_components folder inside your Home Assistant config directory (where you can find your configuration.yaml file).

  • Your config directory should look like this:

    config/
      configuration.yaml
      custom_components/
        neviweb130/
          translations/
            en.json
            fr.json
          __init__.py
          climate.py
          const.py
          helpers.py
          light.py
          manifest.json
          schema.py
          sensor.py
          services.yaml
          string.json
          switch.py
          update.py
          valve.py
    

Legacy configuration

To enable Neviweb130 management in your installation, add the following to your configuration.yaml file, then restart Home Assistant.

# Example configuration.yaml entry
neviweb130:
  username: '«your Neviweb username»'
  password: '«your Neviweb password»'
  network: '«your gt130 location name in Neviweb»'   # gt130 emplacement dans Neviweb
  network2: '«your second location name in Neviweb»' # 2e emplacement
  network3: '«your third location name in Neviweb»'  # 3e emplacement
  scan_interval: 360
  homekit_mode: False
  ignore_miwi: False
  stat_interval: 1800
  notify: "both"
  safe_mode: "-"

Networks names are the names found on top of first page after logging into Neviweb. If you have more then one network, just click on icon on top to find all networks names. Select the one used for Zigbee GT130 or Wi-Fi devices. Both devices types must be on same network to work in neviweb130. If you have two networks for two GT130 or two Wi-Fi groups then you can add network2 parameter in your configuration.yaml. See below. You can't mix miwi devices and Zigbee/Wi-Fi devices on the same network. For miwi devices install Neviweb custom_component which can run along with this custom_component in HA.

Configuration options:

key	required	default	description
username	yes		Your email address used to log in Neviweb.
password	yes		Your Neviweb password.
network	no	if not specified, 1st location found is used. Write the name of the GT130 location in Neviweb you want to control.	Network name is the location name in Neviweb written on top center of first page, where your Wi-Fi or Zigbee devices are registered.
network2	no	2nd location found	The name of the second location you want to control (Zigbee and/or Wi-Fi only). Don't add it if you have only one network.
network3	no	3rd location found	The name of the third location you want to control (Zigbee and/or Wi-Fi only). Don't add it if you have only one network.
scan_interval	no	540	The number of seconds between each access to Neviweb to update device state. Sinopé asked for a minimum of 5 minutes between polling now so you can reduce scan_interval to 300. Don't go over 600, the session will expire.
homekit_mode	no	False	Add support for Homekit specific values. Not needed if you don't use homekit.
ignore_miwi	no	False	Ignore miwi devices if present in same location then Zigbee and/or Wi-Fi devices. Warm if we set wrong Neviweb location.
stat_interval	no	1800	The number of seconds between each access to Neviweb for energy statistic update. Scan will start after 5 minutes from HA startup and will be updated at every 300 to 1800 seconds.
notify	no	both	The method to send notification in case of device error. value option are nothing, logging, notification, both.
safe_mode	no	-	Safe mode is used to run device update in a way that won't crash in case of bad or missing parameters. If a device receive DVCATTRNSPTD error, safe_mode will fire automatically for that device to detect faulty attribute and allow device update to complete. Default value is "-". If you want to test device attributes put device ID as safe_mode value as "12345".

If you have a GT125 also connected to Neviweb the network parameter is mandatory, or it is possible that during the setup, the GT125 network will be picked up accidentally. If you have only two GT130/Wi-Fi network, you can omit there names as during setup, the first two network found will be picked up automatically. If you prefer to add networks names make sure that they are written «exactly» as in Neviweb. (first letter capitalized or not). Avoid also accented letters as Home Assistant will remove them and location name won't match preventing custom_component loading.

Multi-Account Configuration

(New in v3.1.0)

If you need to control devices from multiple Neviweb accounts (e.g., your home and a neighbor's), you can now use the new multi-account configuration format. This eliminates the need to duplicate the custom component folder.

# Multi-account configuration example
neviweb130:
  accounts:
    # Account with multiple locations (home + chalet)
    - username: 'your_email@example.com'
      password: 'your_password'
      # location was called network in previous versions.
      #
      # Optional: you can target up to 3 locations for this account:
      #   location / location2 / location3 (or network / network2 / network3)
      #
      # If you omit all locations, the integration will automatically use the first 1–3 locations
      # returned by Neviweb for this account.
    
    # Separate account for parents (using 'network' - works the same as 'location')
    - username: 'parents_email@example.com'
      password: 'parents_password'
      location: '5678'           # Optional: location id/name (or use 'network')
      prefix: 'parents'          # Optional: account alias (used in entity naming)
  
  # Global settings (apply to all accounts)
  scan_interval: 360
  homekit_mode: False
  ignore_miwi: False
  stat_interval: 1800
  notify: "both"
  safe_mode: "-"

⚠️ Important: Entity Name Conflicts in Multi-Account Setup

Entity names are built from the integration domain (neviweb130), plus optional prefix and/or location values.

Problem: If you omit both prefix and location for multiple accounts, and both accounts have devices with similar names (e.g., both have a thermostat called "LivingRoom"), Home Assistant may auto-suffix entity_ids:

• climate.neviweb130_livingroom
• climate.neviweb130_livingroom_2 ← Collision handled by HA

Solution: Provide either a unique prefix (account alias), or explicit location names/ids, to keep entity_ids stable and readable:

accounts:
  - username: 'user1@example.com'
    password: 'pass1'
    location: 'Home'
    prefix: 'me'          # ← account alias
  - username: 'user2@example.com'
    password: 'pass2'
    location: 'Chalet'
    prefix: 'parents'     # ← different account alias

Example: climate.neviweb130_parents_chalet_climate_livingroom.

Multi-account configuration options:

key	required	default	description
accounts	yes (for multi-account)		List of accounts to connect to
username	yes		Your email address for this Neviweb account
password	yes		The password for this Neviweb account
location (or network)	no	first location found	Location id/name for this account (network #1).
location2 (or network2)	no	second location found	Location id/name for this account (network #2).
location3 (or network3)	no	third location found	Location id/name for this account (network #3).
prefix	no	(empty)	Optional account alias used in entity naming to distinguish accounts.

Notes:

• prefix is optional. If omitted, it is not included in the entity name (Home Assistant may auto-suffix entity_ids if collisions occur).
• If your location names/ids are already unique across your accounts (e.g., you use an address, site code, or other unique label), you can omit prefix entirely and rely on location to distinguish entities.
• Each account maintains its own independent connection to Neviweb.
• Multiple locations per account:
  • If you omit all locations, the integration will automatically use the first 1–3 locations returned by Neviweb.
  • Or you can explicitly set location2 and location3.
• Both location* and network* are accepted as aliases in the new format for consistency with the legacy format.
• Global settings (scan_interval, homekit_mode, etc.) apply to all accounts.
• The legacy single-account configuration format (shown above) remains fully supported for backward compatibility.

Example entity names:

• Legacy single-account config (backward compatible naming):
  • 1st location → climate.neviweb130_climate_bedroom
  • 2nd location → climate.neviweb130_climate_2_bedroom
  • 3rd location → climate.neviweb130_climate_3_bedroom
• Multi-account config (accounts:):
  • With prefix + location → climate.neviweb130_parents_chalet_climate_living_room
  • With location only (no prefix) → climate.neviweb130_chalet_climate_living_room

Sedna valve

For Sedna valves there are two ways to connect it to Neviweb:

• Via Wi-Fi direct connection. This way leak sensor are connected directly to the Sedna valve which will close if leak is detected.
• via GT130 in Zigbee mode. This way leak sensor are also connected to the GT130 but on leak detection nothing is passed to the valve. You'll need to set some automation rule in Neviweb or HA, to have the Sedna valve close if leak is detected by sensor.

Both ways are supported by this custom component.

Gateway GT130

It is now possible to know if your GT130 is still online of offline with Neviweb via the gateway_status attribute. The GT130 is detected as sensor.neviweb130_sensor_gt130

Updater system

Neviweb130 now include a complete update system that include:

• Automatic update check every 6 hours:

  • New update available.
  • Pre-release available.
  • Breaking changes.
  • Version notes.

• SHA-256 validation:

  • Get official SHA-256 from GitHub.
  • Download update zip file.
  • Validate SHA-256.
  • If mismatch, cancel update and notify.

• Auto Rollback if error detected during update:

  • Restore old version automatically.
  • Notify user of the problem.

• Persistent notifications on:

  • Success: "Update successful".
  • Fail: "Update fail, rollback performed".
  • SHA-256 error: "Update aborted for security".

• Breaking changes detection: The updator scan version notes from GitHub. If breaking changes are detected:

  • Add special icon in updater card.
  • Add (Breaking changes) in updater title.

• Pre-release detection if version contain, b0, -beta or rc1 etc: The updator scan update version from GitHub. If pre-release version is detected:

  • Add special icon in updater card.
  • Add (Pre-release) in updater title.

• Backup option: Add a button to allow for system backup before update. All the config directory and database are backuped.

• Version notes can be viewed via link provided on the update card that point to GitHub releases motes.

• Updater have many attributes to help user:

  • check_interval: 6h, (will become an option in futur version)
  • last_check: date/time of last available version check.
  • next_check: date/time of next available version check.
  • last_update_success: Last date/time an update was done.
  • update_status: list all step performed during update.
  • rollback_status: If an update fail, last active version will be rolled back.
  • update_percentage: Show a slider for update process followup.

You will need to deactivate HACS update card or you will get two updates notifications with two updates cards. This can be done in parameters / devices & services / HACS. Pick 'Sinope Neviweb130' line and deactivate the pre-release button if set. Locate the Sinope Neviweb130 integration and click on the three vertical dots on the right end of the line. There are two options: 2 entities and deactivate the device. Clic on 2 entities. Then select update. Click on the configuration button and deactivate option Visible. It will still be possible to do manual update or redownload neviweb130 via HACS.

You can also wait for a new update and select HACS update card. Then clic on the configuration button and deactivate the Visible option.

Neviweb daily request counter

As Sinopé is becoming more picky about request number per day, limit fixed to 30000. If you reach that limit you will be disconnected until midnight. This is very bad if you have many devices or doing development on neviweb130. I've added a daily Neviweb request counter that is reset to 0 at midnight and suvive HA restart. It create a sensor sensor.neviweb130_daily_requests that increase at each request: update, stats polling, error status, etc. The sensor survive HA restart and is set back to 0 at midnight every days.

This way it is possible to improve your scan_interval to get the higher frequency without busting the limit. When reaching 25000 requests, neviweb130 will send a notification. Eventually this warning limit will be configurable.

Running more than one instance of neviweb130 to manage different Neviweb connections

This section is still working but as Neviweb130 now support multi account directly, it become obsolete.

It is possible to run two instance of neviweb130, but you need to use two different username (email) and password to connect to Neviweb. Steps to achieve this:

• Create another directory in config/custom_components like neviweb131.
• Copy all files from directory neviweb130 to new directory neviweb131.
• In neviweb131, edit file manifest.json to change the line #2, "domain": "neviweb130", and change it to the same name as the directory you just create. "domain": "neviweb131",
• Add a second configuration in configuration.yaml like this:

# Example configuration.yaml entry for a second neviweb130 instance named neviweb131.
neviweb131:
  username: 'your Neviweb username for second connection'
  password: 'your Neviweb password for second connection'
  network: 'your gt130 location name in second Neviweb' (gt130 emplacement dans Neviweb)
  network2: 'your second location name in second Neviweb' (2e emplacement)
  network3: 'your third location name in second Neviweb' (3e emplacement)
  scan_interval: 360
  homekit_mode: False
  ignore_miwi: False
  stat_interval: 1800
  notify: "both"

• Restart Home Assistant

All devices on this second instance will have a name like climate.neviweb131_climate_office_thermostat.

Custom services

Automations require services to be able to send command. Ex. light.turn_on. For the Sinopé devices connected via neviweb130, it is possible to use custom services to send specific information to devices or to change some devices parameters. Those custom services can be accessed via development tool/services or can be used in automation:

• neviweb130.set_second_display, allow to change setting of the thermostats second display from setpoint temperature to outdoor temperature. This needs to be sent only once to each device.
• neviweb130.set_climate_keypad_lock, allow to lock the keypad of the climate device.
• neviweb130.set_light_keypad_lock, allow to lock the keypad of the light device.
• neviweb130.set_switch_keypad_lock, allow to lock the keypad of the switch device.
• neviweb130.set_light_timer, this is used to set a timer in seconds (0 to 10800) to the light devices to turn_off after that delay.
• neviweb130.set_switch_timer, this is used to set a timer in seconds (0 to 10800) to the switch devices and multi controller device to turn_off after that delay.
• neviweb130.set_switch_timer2, this is used to set the timer2 in seconds (0 to 10800) to the switch multi controller device to turn_off after that delay.
• neviweb130.set_led_indicator, this allows to change led indicator color and intensity on light devices for «on» and «off» state. you can send any color in the RGB list via the three color parameters red, green and blue, and you can set intensity of the LED indicator.
• neviweb130.set_time_format, to display time in 12h or 24h on thermostats.
• neviweb130.set_temperature_format, to display temperature in Celsius or Fahrenheit format on thermostats.
• neviweb130.set_backlight, to set backlight intensity in state «on» or «off» for thermostats.
• neviweb130.set_wattage, to set wattageOverload for light devices.
• neviweb130.set_auxiliary_load, to set status and load of the auxiliary heating.
• neviweb130.set_setpoint_min, to set minimum setpoint temperature for thermostats.
• neviweb130.set_setpoint_max, to set maximum setpoint temperature for thermostats.
• neviweb130.set_cool_setpoint_min, to set minimum cooling setpoint for TH1134ZB-HC.
• neviweb130.set_cool_setpoint_max, to set maximum cooling setpoint for TH1134ZB-HC.
• neviweb130.set_floor_limit_low, to set minimum setpoint temperature for floor thermostats. (5 to 34°C), (0 = off)
• neviweb130.set_floor_limit_high, to set maximum setpoint temperature for floor thermostats. (7 to 36°C), (0 = off)
• neviweb130.set_sensor_alert, to set all alert for water leak sensor, temperature, battery, leak, status and set action on valve.
• neviweb130.set_valve_alert, to set low battery alert status.
• neviweb130.set_valve_temp_alert, to set low temperature alert on sedna valve.
• neviweb130.set_early_start, to set early heating on/off for Wi-Fi thermostats.
• neviweb130.set_air_floor_mode, to switch between floor or ambient temperature sensor to control room temperature.
• neviweb130.set_floor_air_limit, to set floor thermostat max air limit temperature.
• neviweb130.set_phase_control, to set phase control mode for DM2550ZB dimmer (reverse or forward).
• neviweb130.set_hvac_dr_options, to set or reset DR period option in Neviweb for thermostats.
• neviweb130.set_hvac_dr_setpoint, to adjust thermostat setpoint reduction during DR period, 100 to -100 (°C*10). 0 will just make the small icon to flash.
• neviweb130.set_load_dr_options, to set or reset DR period options in Neviweb for load controller.
• neviweb130.set_cycle_output, to set main cycle length of low voltage thermostat in minutes.
• neviweb130.set_aux_cycle_output, to set auxiliary cycle length of low voltage thermostats in minutes.
• neviweb130.set_control_onoff, change status of output 1 and 2 on alarm multi-controller for sedna valve.
• neviweb130.set_battery_type, set battery type, alkaline or lithium, for the water leak sensor.
• neviweb130.set_tank_size, to set the water heater tank capacity for Calypso RM3500ZB.
• neviweb130.set_low_temp_protection, to activate or not the water heater protection for water temperature. Below 45°C heating is auto restarted.
• neviweb130.set_controlled_device, to change the name of the device controlled by the RM3250ZB load controller.
• neviweb130.set_flow_meter_model, to change the flow meter model connected to sedna valve 2e gen and start/stop leak protection from flow meter.
• neviweb130.set_flow_meter_delay, to set the leak delay before the valve close if a leak is detected by the flow meter.
• neviweb130.set_flow_meter_options, to set the flow meter action: close the valve (yes/no) and to send alert message (yes/no), or just do nothing.
• neviweb130.set_tank_type, to set tank type for LM4110-ZB, propane or oil.
• neviweb130.set_gauge_type, to set gauge type for LM4110-ZB on propane tank, model 5-95 or 10-80.
• neviweb130.set_low_fuel_alert, to set low fuel level limit for propane tank, 0 (off), 10, 20 or 30%.
• neviweb130.set_tank_height, to set fuel tank height for LM4110-ZB sensor, 0 (off), 23, 24, 35, 38, 47, 48, 50.
• neviweb130.set_fuel_alert, to set fuel alert, on/off for LM4110-ZB.
• neviweb130.set_power_supply, to set power source for Sedna valve between battery, acups-01 or both.
• neviweb130.set_battery_alert, to set battery alert on/off for LM4110-ZB.
• neviweb130.set_input_output_names, to set name for input 1 and 2 and output 1 and 2 of MC3100ZB device.
• neviweb130.set_activation, to activate or block neviweb polling for a device.
• neviweb130.set_sensor_type, to set sensor value 10k or 12k.
• neviweb130.set_remaining_time, to set value for coldLoadPickupRemainingTime attribute.
• neviweb130.set_on_off_input_delay, to set the «on» or «off» delay in seconds for input 1 and 2 of MC3100ZB.
• neviweb130.set_em_heat, to turn on/off aux heat for floor and low voltage thermostats. This is a replacement of turn_aux_heat_on or off that was deprecated by HA. It work differently for the TH6xxxWF devices where it change the preset mode to PRESET.BOOST or back to previous preset mode when turned off.
• neviweb130.set_display_config, to set on/off display on heatpump.
• neviweb130.set_sound_config, to set on/off sound on heatpump.
• neviweb130.set_heat_pump_operation_limit, to set minimum operation temperature for heatpump.
• neviweb130.set_heat_lockout_temperature, to set maximum outside temperature limit to allow heating device operation. Work differently for TH1123ZB-G2, TH1124ZB-G2 and heat/cool devices (TH6xxxWF). Each use different attribute.
• neviweb130.set_cool_lockout_temperature, to set minimum outside temperature limit to allow cooling device operation.
• neviweb130.set_hc_second_display, to set second display of TH1134ZB-HC thermostat.
• neviweb130.set_language, to set display language on TH1134ZB-HC thermostats.
• neviweb130.set_aux_heat_min_time_on, to set auxiliary heating minimum time on.
• neviweb130.set_cool_min_time_on, to set cooling minimum time on.
• neviweb130.set_cool_min_time_off, to set cooling minimum time off.
• neviweb130.set_neviweb_status, to set global Neviweb status, home / away via GT130.
• neviweb130.set_climate_neviweb_status, to set global Neviweb status, home / away via Zigbee or Wi-Fi thermostats.
• neviweb130.set_refuel_alert, to get an alert when the propane tank is refueled,
• neviweb130.set_humidifier_type, to set the type of humidifier device connected to TH6500WF or TH6250WF.
• neviweb130.set_schedule_mode, to set the schedule mode, manual or auto for TH6500WF or TH6250WF.
• neviweb130.set_flow_alarm_disable_timer, to disable abnormal fow alarm for a period from 1 sec. to 24 hrs.
• neviweb130.set_heatcool_setpoint_delta, to set a temperature delta between heating setpoint and cooling setpoint from 1 to 5°C in auto (heat/cool) mode for TH6xxxWF.
• neviweb130.set_fan_filter_reminder, to set the delay between each fan filter cleaning from 1 to 12 month, for TH6xxxWF.
• neviweb130.set_temperature_offset, to adjust temperature sensor from -2 to 2°C with 0.5°C increment, for TH6xxxWF.
• neviweb130.set_aux_heating_source, to select which type of auxiliary heating source is in use for TH6xxxWF.
• neviweb130.set_fan_speed, to set fan speed, on or auto for TH6xxxWF.
• neviweb130.set_switch_temp_alert, to set low temperature alert on / off for MC3100ZB devices.

Logging for debugging

As the file home-assistant.log is no longer available, we have added a new logger that write all logger data about neviweb130 to a file neviweb130_log.txt in your config directory. This file is overwritten each time Ha is restarted. The file is also rotated each time it reach 2 meg in size. Log rotation have a total of 4 files.

To help debugging, add relevant snippet of this file to any issue you may report.

Catch Eco Sinope signal for peak period

If you have at least on thermostat or one load controller registered with Éco-Sinopé program, it is now possible to catch when Neviweb send the signal for pre-heating start period for thermostats or turn_off signal for the load controller. Seven attributes have been added for thermostats and three for load controller to know that peak period is coming and how it is managed:

• For thermostats:

  • eco_status: set to «off» during normal operation, turn «on» during peak period at the beginning of the pre-heating period. this is the attribute to follow to detect a peak start.
  • eco_setpoint: set to «off» during normal operation, turn «on» during peak period if device is managed by Eco-Sinopé.
  • eco_optout: set to «off» during normal operation during peak period, turn «on» if somebody change the setpoint during peak period.
  • eco_power_relative: set to «off» during normal operation, used to set a minimum temperature compared to setpoint where the thermostat will turn on automatically for frost protection.
  • eco_power_absolute: set to «off» during normal operation, used to limit the pi_heating_demand level between 1 to 100% during peak period.
  • eco_setpoint_status: set to «off» during normal operation, turn «on» if device setpoint is changed by Eco-Sinopé.
  • eco_setpoint_delta: set to 0 during normal operation, changed to values between -10 and +10 during peak period. For pre-heating the value is positive and for peak period it is a negative value. This is a delta applied to regular setpoint. -10 = setpoint reduced by 10°C. +2 = setpoint increased by 2°C.

• For load controller:

  • eco_status: set to «off» during normal operation, turn «on» during peak period at the beginning of the pre-heating period. this is the attribute to follow to detect a peak start.
  • eco_onoff: set to «off» during normal operation, turn «on» during peak period if device is managed by Eco-Sinopé. The device is turned off during peak period. Nothing is done during pre-heating period.
  • eco_optout: set to «off» during normal operation during peak period, turn «on» if somebody turn on the device during peak period.

• For Multi-controller MC3100ZB:

  • eco_status: set to «off» during normal operation, turn «on» during peak period at the beginning of the pre-heating period. this is the attribute to follow to detect a peak start.
  • eco_setpoint: set to «off» during normal operation, no change during peak period if device is managed by Eco-Sinopé.
  • eco_optout: set to «off» during normal operation, during peak period, turn «on» if somebody change the onoff value during peak period.
  • eco_power_relative: set to «off» during normal operation, used to set a minimum temperature compared to room temperature value where the MC3100ZB will turn on automatically for frost protection.
  • eco_power_absolute: set to «off» during normal operation, usage unknown.

It is then possible to make an automation to set all HA devices ready for peak period by following the eco_status attribute change from «off» to «on».

Energy statistic

Seven attributes are added to track energy usage for devices:

• total_kwh_count: total count of energy usage to date.
• hourly_kwh_count: total count for hourly usage for current day.
• daily_kwh_count: total count for daily usage for current month.
• monthly_kwh_count: total count for monthly usage for current year.
• hourly_kwh: kwh used for last hour.
• daily_kwh: kwh used for last day.
• monthly_kwh: kwh used for last month.

They are polled from Neviweb every 30 minutes. The first polling start 5 minutes after HA restart. Neviweb have a two hours delay to publish his data. Your data will be delayed by 2 hours.

Track energy consumption in HA Energy dashboard

When energy attributes are available, it is possible to track energy consumption of individual devices in Home Assistant energy dashboard by creating a Template sensor in configuration.yaml:

template:
  - sensor:
      - name: "Basement energy usage"
        unique_id: sensor.basement_energy_usage
        unit_of_measurement: "kWh"
        device_class: energy
        state_class: total_increasing
        state: >-
          {{ state_attr("climate.neviweb130_th1124zb_basement","hourly_kwh_count") }}

or:

template:
  - sensor:
      - name: "Basement energy usage"
        unique_id: sensor.basement_energy_usage
        unit_of_measurement: "kWh"
        device_class: energy
        state_class: total
        state: >-
          {{ state_attr("climate.neviweb130_th1124zb_basement","hourly_kwh") }}

Localisation

Neviweb130 is now translated in French for the errors and notifications messages. The translation is done automatically based on your HA configuration for language. Now French and English are supported. Any language can be added by translating en.json file located in translations directory into other language.

If you modify translations files you will need to not only reload HA but also restart the HA server to force HA to reload translations properly.

Statistic for Sedna flow meeter

Seven attributes are added to track water usage for Sedna valve. They are shown as m³ (cubic meeter) which is what energy module is looking for:

• total_flow_count: total count of water liters usage to date.
• hourly_flow_count: total count of hourly water liters usage for current day.
• daily_flow_count: total count of daily water liters usage for current month.
• monthly_flow_count: total count of monthly water liters usage for current year.
• hourly_flow: water liters used for last hour.
• daily_flow: water liters used for last day.
• monthly_flow: water liters used for last month.

They are polled from Neviweb every 30 minutes. The first polling start 5 minutes after HA restart. Neviweb have a two hours delay to publish his data.

Track water consumption in HA Energy dashboard

When flow attributes are available, it is possible to track water consumption of sedna valve in Home Assistant energy dashboard by creating a Template sensor in configuration.yaml:

template:
  - sensor:
      - name: "Sedna Water Flow"
        unique_id: sensor.sedna_water_flow
        unit_of_measurement: "m³"
        device_class: water
        state_class: total_increasing
        state: >-
          {{ state_attr("valve.neviweb130_valve_water_valve","hourly_flow_count") }}

or:

template:
  - sensor:
      - name: "Sedna Water Flow"
        unique_id: sensor.sedna_water_flow
        unit_of_measurement: "m³"
        device_class: water
        state_class: total
        state: >-
          {{ state_attr("valve.neviweb130_valve_water_valve","hourly_flow") }}

Troubleshooting

if you see your device in the log, but it does not appear in entity list you need to add the device model number in the code. Or you can send the model number to me, so I can add it in the code.

In the log look for lines:

[custom_components.neviweb130] Received gateway data: [{'id': 100225, 'identifier': '500b91400001f750', 'name': 'Chargeur auto', 'family': '2506',...
[custom_components.neviweb130] Received signature data: {'signature': {'model': 2506, 'modelCfg': 0, 'softBuildCfg': 0, 'softVersion': {'minor': 9, 'middle': 2, 'major': 1}, 'hardRev': 2, 'protocol': 'sinopcom'}}

'family': '2506' and 'model': 2506 is what you need to find the model number of your device. It should be added in climate.py, light.py, switch.py, sensor.py or valve.py near line 132 to 136 (climate.py) depending on device type. Then restart HA and your device will be listed in entity list.

If you get a stack trace related to a Neviweb130 component in your home assistant log, you can open an issue

You can also post in one of those threads to get help:

• https://community.home-assistant.io/t/sinope-line-voltage-thermostats
• https://community.home-assistant.io/t/adding-support-for-sinope-light-switch-and-dimmer

Turning on Neviweb130 debug messages in neviweb130_log.txt file

To have a maximum of information to help you, please provide a snippet of your neviweb130_log.txt file. I've added some debug log messages that could help diagnose the problem.

Add those lines to your configuration.yaml file

logger:
  default: warning
  logs:
    custom_components.neviweb130: debug
    homeassistant.service: debug
    homeassistant.config_entries: debug

This will set default log level to warning for all your components, except for Neviweb130 which will display more detailed messages.

Error messages received from Neviweb

In you log you can get those messages from Neviweb:

• ACCDAYREQMAX: Maximum daily request reached ('daily': 30000)... Reduce polling frequency.
• ACCRATELIMIT: Maximum access rate limit reach when login to Neviweb. Too frequent login. Wait few minute before HA restart.
• ACCSESSEXC: To many open session at the same time. This is common if you restart Home Assistant many times and/or you also have an open session on Neviweb.
• DVCACTNSPTD: Device action not supported. Service call is not supported for that specific device.
• DVCATTRNSPTD: Device attribute not supported, The device you have installed have and older firmware and do not support some attributes. Wait for firmware update in Neviweb and the error should disappear or file an issue so we can put an exception in the code.
• DVCBUSY: Neviweb is performing an update and devices are not available. Try later.
• DVCCOMMTO: Device Communication Timeout: device do not respond fast enough, or you are polling that device too frequently.
• DVCNOTSYNC: Device is not in sync with Neviweb. Check your network, router and/or Wi-Fi gateway.
• DVCUNVLB: Device unavailable. Neviweb is unable to connect with specific device, mostly Wi-Fi devices.
• MAINTENANCE: Neviweb access temporary blocked for maintenance... Retry later.
• SVCERR: Service error. Service unavailable. Try later.
• SVCINVREQ: Invalid request sent to Neviweb, service do not exist or malformed request.
• USRBADLOGIN: your login and/or password provided in configuration for Neviweb is no good.
• USRSESSEXP: User session expired. Reduce your scan_interval below 10 minutes or your session will be terminated.
• VALINVLD: Invalid value sent to Neviweb.
• ReadTimeout: Request was sent to the device but no answer came back. Network problem.
• TimeoutError: Timeout error detected... Retry later.

If you find other error code, please forward them to me.

Customization

Custom-ui is almost deprecated and hard to configure. So I've switch to modern lovelace card to ease the process and get better results.

Prerequisites:

• The icons are located in www folder in this repo. Copy them in config/www/neviweb130/. You need to create the neviweb130 under config/www. (called /local in HA)
• Install via HACS the lovelace card: card-mod, mushroom and for stack-in-card.
• Make sure you have at least neviweb130 v4.1.2

Neviweb130 will manage the icon to show depending on heat level for thermostats via the icon_type attribute. For sensors, monitors and valve, battery icon are managed via battery_icon attributes based on battery level. You can retrieve the icon name with template like this example:

Heat level: {{ state_attr('climate.neviweb130_climate_th1124wf', 'icon_type') }}

leak detection: {{ state_attr('sensor.neviweb130_sensor_wl2010', 'icon_type') }}

battery level: {{ state_attr('sensor.neviweb130_sensor_wl2010', 'battery_icon') }}

Those template point directly to /local/neviweb130/(icons)

Old style: (Many examples)

New style based on Mushroom and Tile cards:

(Feel free to improve my icons and let me know.)

Here the code for tile card, mushroom template card and mushroom climate card. Edit your dashboard and add the card. Then edit the code like this:

• tile card:

type: tile
grid_options:
  columns: 12
  rows: 1
entity: climate.neviweb130_climate_th1124wf
name:
  - type: text
    text: Cuisine
  - type: text
    text: Tile card
show_entity_picture: true
vertical: false
features_position: bottom

Mushroom template:

type: custom:mushroom-template-card
entity: climate.neviweb130_climate_th1124wf
features_position: bottom
primary: |
  Cave (
  {{ state_attr(entity, 'temperature') }}
  °C)
  Mushroom template card
secondary: |
  {{ states(entity) }} – ({{ state_attr(entity, 'hvac_action') }})
  Currently: {{ state_attr(entity, 'current_temperature') }} °C
picture: |
  {{ state_attr(entity, 'icon_type') }}
grid_options:
  columns: 12
  rows: 1

• Mushroom Climate:

type: custom:mushroom-climate-card
entity: climate.neviweb130_climate_th1124wf
name: th1124wf Mushroom Climate card
hvac_modes: []
fill_container: true
primary_info: name
secondary_info: state
grid_options:
  columns: 12
  rows: 1
tap_action:
  action: more-info
card_mod:
  style:
    mushroom-shape-icon$: |
      .shape {
        background-color: transparent !important;
        background: url("{{ state_attr('climate.neviweb130_climate_th1124wf', 'icon_type') }}");
        background-size: cover;
        background-position: center;
        border-radius: 50%;
      }
    .: |
      ha-state-icon {
        display: none !important;
      }

You can group the card in a vertical stack card, stack-in-card. Since the entity_picture is defined for all thermostats, valve, sensors you can add the devices directly in a vertical stack card. Icon will be dynamically updated for heat level, battery level etc

type: vertical-stack
cards:
  - type: entities
    entities:
      - entity: climate.neviweb130_climate_th1124wf
      - entity: climate.neviweb130_climate_office
      - entity: climate.neviweb130_climate_kitchen
      .....

Customization for leak sensor

Same as above. For leak detected icon it is the icon_type attribute. For battery level it's the same as above with battery_icon.

Icons are available from www sub-directory. Copy them in config/www/neviweb130 in your HA.

Customization for battery level for monitor and valve:

Same as above with attribute battery_icon, leak_icon and icon_type.

Device hard reset

• Thermostats:

  • Raise the temperature until the display change.
  • Push the two button until CLR appear on the screen.
  • Push once the upper button to get YES on the display.
  • Push both button simultaneously and release immediately. DONE should appear on the screen.
  • The thermostat will restart with factory setup

• thermostats G2:

  • Raise the temperature until the display change.
  • Push and hold the two button until RST appear on the screen.
  • Wait until device restart.

TO DO

• This custom component will be updated to neviweb130-V2 soon. This imply config_flow, coordinator, attributes entities, English/French translation and many more features.
• Improve energy stat polling from Neviweb.