Plugwise core and custom_component

Ok gezien. Zie je dit ook terug in de history graph van de interval sensor?
En hoe zien de history graphs van de andere sensoren eruit?

1 Like

oops ik geloof dat ik ook even andere momenten moet gaan kijken in het dashboard image

image
there are values now. Thx for all the support

Great, I kind of figured that was the problem :slight_smile:

sorry for my fault

I have used this integration (beta version, because the built-in version wouldn’t install it) to setup my Plugwise sensors. Strangly the measured watts of the sensor.sensor_electricity_consumed_interval give me lower readings then when I check the Stretch API?

I created a seperate topic just before I found this topic; Template sensor measuring to low energy

What could be the issue here?

Is there a sensor to report back if the heating is switched on/off? From the graph I can see (yellow) that the integration already knows when the heating is switched on. But I’d like to trigger a task based on this.
Screenshot_20220212_101456

@Ceaus No there is not at the moment, but we are working on adding a binary_sensor.
Will let you know when it’s available.

1 Like

@bouwew Awesome, thanks. I appreciate the hard work and dedication. Hats off!

NEW FEB 2022 [0.21.0]

  • Smile: refactor code following the coming HA Core update
    • Link to plugwise v0.16.6 - https://github.com/plugwise/python-plugwise/releases/tag/v0.16.6
    • Refactor code following the work done on the HA Core plugwise code, a big thank you to @Frenck!!
    • REMOVED: device_state sensor
    • ADDED: binary_sensors showing the heating and cooling (when cooling is present) states
    • Support Stretch with fw 2.7.18
    • Improve test scripting

The update is available via HACS, please test and if you find any problem, create an Issue here: https://github.com/plugwise/plugwise-beta/issues

Any question, let us know in this thread.

@Ceaus please test plugwise-beta v0.21.0.

Works like a charm :slight_smile: I now have the circulation pump activated in sync with Anna being switched on/off. The pump was running 24/7 at 57 Watts. Not anymore!

Do you have a donations option? I’d like to share a bit of my savings with you.

In the meantime, there have been two minor Plugwise-beta updates:

V0.21.1:

  • Fix issue where notifications would cause an error (see issue #238)
  • Restore Homekit-functionality present in v0.20.1 and earlier versions

V0.21.2:

  • Make HomeKit emulation an option (like scan-interval)

Detailed release info:

Also FYI: in HA Core v2022.3.0 the Plugwise Integration will be fully updated.
The code-base of the Core Plugwise Integration and Plugwise-beta is now the same.
Please note: the Core Integration will not have the Options (change scan_interval, enable HomeKit emulation) that are present in Plugwise-beta.

Today we released a minor Plugwise-beta update:

V0.21.5:

  • There are two (minor) changes that may or may not be breaking in your setup, please read the detailed release notes for more information. Your opentherm outdoor_temperature sensor has been renamed and the schedule attributes of your thermostat are named schedules (and not schema’s).
  • Following up on a great suggestion by @sophof there is now a select entity to change your active schedule from within Home Assistant

These should be available for the Core version soon ™

Hi and thanks for developing the plugwise integration!

I have an (ancient) plugwise stick plugged into my Odroid N2+ that runs HA. When I install the integration I select stick and then it’s asking me for the USB Path. How do I figure out what my USB Path is? I’ve tried the default /dev/ttyUSB0 but that doesn’t work.

I’ve also tried ha hardware info in the terminal, but I don’t see USB devices listed there. Do I need to do anything to get it to recognise the USB stick?

I suggest looking at and using the /dev/serial/by-id/... or /dev/serial/by-path... options, these will always stay the same after a reboot.

You need to check these paths from outside HA, in Linux itself.

Thanks, I’ll have a look at that.

hi dev’s,

should the select entity already be available in the dev nightly and core integration? Currently running 2022.4.0.dev20220324

I believe to have seen it being merged, but still I dont get that entity in my integration panels. Or is it still only in the custom component?

Hi Marius,

It should be in dev, the PR has been merged 3 days ago.

Please note, it will only show when you have more than one Schedule defined, if there’s only one, there’s no selection possible.

ofc… that was it, I only had 1 schedule. fixed that:

nice, thanks!
guess Ive got to make a more definitive choice with naming to pick Dutch/Schema or English/Schedule…