Rika FireNet support

Mystere · December 3, 2020, 8:43pm

Thank you for your share !

Every thinks is good.

ygeffens · December 8, 2020, 1:16pm

I have a Rika pelletstove myself, but I don’t have the firenet usb stick (yet).

Can anyone confirm that

heating power is visible like in this post (Rika FireNet support)
that you can not only read the sensors but also change the heating power from this component

To all contributors nice job !

Mystere · December 8, 2020, 6:56pm

Yes, you can pilot (start and stop) and change temperature with this plugin.

I search to have 22 °C and my temperature is 21°C. I stop the pelletsove
On parameter view. You can up and down temperature.

poele1

ygeffens · December 15, 2020, 1:49pm

@Fockaert
Hi Jan,

I couldn’t wait so I ordered the stick anyway

Added through HACS, worked after clearing browser cache (before I was not able to see the component -has nothing to do with the component, I know).

Thanks Jan for this component.

Can I make a feature request?
On the rika-firenet website I’m able to switch on/off the stove and also change the power (between 30% and 100%)

This would be greatly appreciated when it can be added in a future release.

Fockaert · December 22, 2020, 2:58pm

Hi @ygeffens,

We could add an additional slider for this, assuming the climate component is only for temperature. Could you create new ticket/issue on https://github.com/Fockaert/rika-firenet-custom-component/issues please.

Thanks,
Jan

Fockaert · January 23, 2021, 1:15pm

Hi everyone,

With https://github.com/Fockaert/rika-firenet-custom-component/issues/7 I’ve added support for switch and number entities. But the number entity (https://developers.home-assistant.io/docs/core/entity/number) I’ve issues testing this. I need to find a way for adding a slider on dashboard for updating the value, who can help me with this? If needed I can merge this branch to master if it’s easier testing.

Thanks,
Jan

Fockaert · February 6, 2021, 6:53pm

Hi @ygeffens, with latest home assistant release, a text box is shown with ± buttons to modify the new number entities room power request and room heating power. Merged branch to master, so please try it out

Thanks,
Jan

ygeffens · February 6, 2021, 11:10pm

Thanks Jan

Since I’m using HACS (and installed this component with Hacs) i would expect to se an update notice in HACS, but this is not showing up. Do I have to do something manually to trigger this update ?

Update:
I updated the component manually.

I see these entities:

      - number.woonkamer_heating_power
      - sensor.woonkamer_heating_power
      - number.woonkamer_room_power_request
      - sensor.woonkamer_room_power_request
      - switch.woonkamer

Does the domain ‘number’ exist? I thought it was ‘input_number.xxx’ ?

Fockaert · February 7, 2021, 6:34pm

I got the new version already on HACS, you could try the “update information” option on the options menu. The number entity is a variant like the input_number, but this number entity (https://developers.home-assistant.io/docs/core/entity/number/) will save the value directly on the integration when modified.

ygeffens · February 7, 2021, 8:08pm

What is the difference between _heating_power and _room_power_request?

I can set the heating power between 30% and 100%, like I can do that on the stove. But what is this _room_power_request? Mine is set to 3, but I have no idea what it does…
Maybe it’s not relevant for a pellet stove (?).

About HACS, the component is simply not in the list of installed integrations. Very strange. Not a big problem, it’s working.

Remi_Kiragossian · February 10, 2021, 6:26pm

Very nice job !
But… I can’t connect…

Username/Password is wrong.

Of course, the mail and password are valid.

This integration can manage Multiair? with an external temperature sensor, it will be perfect !

Thanks

Fockaert · February 10, 2021, 7:41pm

room_power_request is used in combination with room thermostat (also for pellet stoves) with number between 1…4. This can be set in the room thermostat settings menu. Probably 3 is the default value.

Thanks,
Jan

Fockaert · February 10, 2021, 7:49pm

Hi @Remi_Kiragossian,

Thanks! Could you reinstall and try again? If still not working, could you share the logs please (only from rika_firenet is sufficient).

On my stove I don’t have multiair, so it’s more difficult to implement. Which options are possible on the Rike Firenet website? Maybe share a few screenshots.

Thanks,
Jan

Remi_Kiragossian · February 10, 2021, 8:03pm

Hi
I don’t see anything about Rika firenet in the logs, but maybe I’m not at the good place ?
I add :

logger:
  default: info
  logs:
    custom_components.rika_firenet: debug
    custom_components.rika-firenet: debug
    custom_components.rika-firenet-custom-component: debug
    custom_components.hacs: debug
    hacs: debug
    queueman: debug
    AIOGitHubAPI: debug

Reinstall do nothing. I also tried on another instance of hassio, without succes.

For multiair :

convectionFan1Active : false / true
convectionFan1Level : 0(auto) / 1 / 2 / 3 / 4 / 5
convectionFan1Area : from '-30' to '+30' (%)
convectionFan2Active : false / true
convectionFan2Level : 0(auto) / 1 / 2 / 3 / 4 / 5
convectionFan2Area : from '-30' to '+30' (%)

I want to make a thermostat with an external sensor for each multi air zone, adjusting convectionFanXActive and convectionFanXLevel compared to difference between target temperature and sensor, and maybe ( also for the main thermostat, a variable adjusted by external temp, or PID)

Thanks

Fockaert · February 11, 2021, 9:25am

For logs I’ve locally:

logger:
logs:
custom_components.rika_firenet: debug

These logs should popup like:

2021-02-11 08:53:07 INFO (SyncWorker_1) [custom_components.rika_firenet.core] setup()

For the multiair, I can easilly add support for those properties you’ve shared, the testing would be on your plate could you create a ticket/issue on github location with these details please.

Thanks,
Jan

Remi_Kiragossian · February 11, 2021, 11:13am

Log said :

2021-02-11 12:04:43 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection] [281473652198368] Sending {'id': 67, 'type': 'result', 'success': True, 'result': {'resources': {'component.rika_firenet.config.title': 'Rika Firenet', 'component.rika_firenet.config.step.user.title': 'Rika Firenet', 'component.rika_firenet.config.step.user.description': 'Setup integration with Rika Firenet', 'component.rika_firenet.config.step.user.data.username': 'Username', 'component.rika_firenet.config.step.user.data.password': 'Password', 'component.rika_firenet.config.error.auth': 'Username/Password is wrong.', 'component.rika_firenet.config.abort.single_instance_allowed': 'Only a single configuration of Rika Firenet is allowed.'}}}

2021-02-11 11:07:39 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for rika_firenet which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.

but it’s difficult to reproduce this error, sometimes nothing added in log, as with wrong login/pass
For the Multiair, it’s done : https://github.com/Fockaert/rika-firenet-custom-component/issues/9

Thanks

Remi_Kiragossian · February 12, 2021, 8:48pm

@Fockaert

i try again but without succes

Fockaert · February 13, 2021, 6:38pm

@Remi_Kiragossian I’ve added more detailed logging on this configuration step, to find the root cause. Could you try again with the latest version please.

Issue created: https://github.com/Fockaert/rika-firenet-custom-component/issues/10

Thanks,
Jan

Remi_Kiragossian · February 13, 2021, 7:30pm

Log said now :

2021-02-13 20:22:09 ERROR (MainThread) [custom_components.rika_firenet.config_flow] test_credentials_exception

Traceback (most recent call last):

File "/config/custom_components/rika_firenet/config_flow.py", line 67, in _test_credentials

coordinator = RikaFirenetCoordinator(

File "/config/custom_components/rika_firenet/core.py", line 29, in __init__

super().__init__(

File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 70, in __init__

self.hass.bus.async_listen_once(

AttributeError: 'NoneType' object has no attribute 'bus'

Thanks for your help.

Fockaert · February 14, 2021, 9:36am

@Remi_Kiragossian The issue should be fixed with latest commit on Master. Some regression was introduced on the config flow when using DataUpdateCoordinator functionality.

For others: With latest changes for supporting MultiAir, multiple switch entities got introduced, the basic on-off switch got renamed with postfix “on off”

Have fun!