Plugwise Smile custom_component (BETA)

If you allow me to add to the discussion:

Appreciate the take on not being able to act, I do think it is a primary value, since the thermostat decides to heat or not, based on this value too.
Outside temp is one of the available sensors in Anna logic and is in the Plugwise interface on purpose…

Added to that, in the app this sensor is well hidden… so having it in the Ha interface is a major plus compared to the App

I could understand it would be an extra effort to include it, but taking it out simply because Ha doesn’t act on it is a real let down. There are many sensors in Ha which aren’t manipulated . As a matter of fact, that’s what a sensor is for: representing a current value, and no more.

What temperature better to have in one’s HA system then the value the climate system uses for heating the Home.

It could very well be the most important one, compared to the many weather integrations that all show different values.

Having the Plugwise temp sensor available is of primary importance …

Please don’t take it out!

Thanks

@Mariusthvdb please don’t mix up things or state things that (imho) don’t go together

Please (also, or at least functional over there) please comment on #63 in github, it will leverage (eventually). Wrt taking things out, selected_schedule isn’t going anywhere - that’s the one pointing out which active (or not) schedule you are (or last were) on.

Taking your posts one by one, abite being a bit blunt about it:

  1. What happened to available_schedules => see #61/#63
  2. outside_temperature had to move, so it moved to a separate sensor, not begin one of the climate.anna attribues (I was merely providing feedback towards your attribute-attempt)
  3. What HA isn’t acting on/providing services for is switching your schedule/schema/whatever you want anything but a couple of presets called => please reply to #63 if anyone finds out that this actually is possible (with abusement as included in that issue)
  4. Scheduled_temperature and temperature of the individual thermostats is shown inside (in your case) climate.anna other sensoric values, not directly affected by a thermostat (or a switch), are stowed under a central device (as indicated before)

And a small sidenote as well, if you auxiliairy_device (whichever that is) actually (physically!) has an outdoor_temperature sensor, the value is just ‘taken from the internet’ just like all them other apps.

1 Like

HiTom,

I do think I mixed up some things, sorry for that…

If necessary Ill add to #63 there, for this thread, only thing left then is the outdoor temp.

Maybe I even misread that… I understand you take it out as an attribute, which would be fine. As long as the separate sensor still is created? Because:

That might be correct, but this is the only one, the Plugwise thermostat uses, and not any of the other weather integration temperature sensors. So it is of primary value for the HA instance.

Thanks for your extensive reply!

cheers, and keep on improving the Plugwise integration, truly appreciated!

@Mariusthvdb
Please test version v0.2.12rc1, the available_schemas issue was much easier to solve than we were expecting.

All there!

Legacy Anna (firmware 1.8) users, please see this:

1 Like

FYI version 0.2.13 is available on the github.
This version is very close to what will be available in HA Core once all PR’s have been merged.

Guys I can confirm the updates. The last couple of days I went from 1.8.0 -> 3.1.11 -> 4.0.19

1 Like

FYI v0.2.15 v0.2.14 is available:

  • more bugfixes and changes under the hood
  • fixes for bugs that have appeared recently,
  • changes under the hood, related to the process of getting the code into HA Core.

FYI, due to especially @CoMPaTech’s efforts, all our Plugwise-PR’s have been accepted and merged into the HA Core dev-branch.
This means that what you know as Plugwise-beta v0.2.15 will become available als Plugwise official in the next HA Core release: 0.111, replacing the present Plugwise official component.

The updated documentation is available here, for now: https://next.home-assistant.io/integrations/plugwise/

2 Likes

The updated Plugwise component is live in HA Core 0.111.0b0!!

2 Likes

And for those of you waiting for it … 0.111 is out and Plugwise Adam/Anna/P1 are (should?) be happily working for all of you. Feel free to stay on plugwise-beta, remove your integrations and re-add them using Plugwise in core itself or double-up. Enjoy it!

Do read the breaking section (as you should always do) before upgrading. Especially since you need the UI to add the component - other than that naming of the entities (which users probably would call sensors or devices) has changed.

1 Like

and are again gone in the core integration on 0.111? Forgive me for getting back to this, it just seems so odd…

and an icon issue:


where before this was showing a percentage icon? maybe a bug, or oversight?

Not sure what causes the first issue, I do see the available schematics in my system. I hope you do not run two Plugwise integrations in parallel? Is there anything shown in the HA Log?

On the icon-issue, looks like the code taking care of this is not in HA Core (yet).

Please create 2 separate Issues for these 2 bugs in the HA Core github, this will help getting the fixes in easier/faster.

Thanks! Nice work!

On the first issue, I just noticed we still need to remove one line of code.
If you create a 2nd schedule, the available ones will be there, sorry :slight_smile:

ok, thanks, you’ll fix it :wink:
so no need for an issue in the repo?

but it was there wasn’t it? Ive always seen the percentage icon on that ever since you added modulation.

The percentage-icon was in plugwise-beta, correct.
And it will return in HA Core.
But, you creating one issue for the missing icon will surely help getting the fix for this accepted.

consider it done: Plugwise: no icon for percentage modulation · Issue #36669 · home-assistant/core · GitHub

1 Like

The integration is not installing on my system.
After the installing window it pops back to the integration list. Rebooted everything, same result.

In what git should I report this, HA core or your Plugwise Smile?

I am currently running on 111.1

||amd64|

| --- | --- |
|dev|false|
|docker|false|
|hassio|false|
|installation_type|Home Assistant Core|
|os_name|FreeBSD|
|os_version|11.3-RELEASE-p9|
|python_version|3.7.6|
|timezone|Europe/Amsterdam|
|version|0.111.1|
|virtualenv|true|

Still dumping all info here.

2020-06-12 13:20:43 ERROR (SyncWorker_25) [homeassistant.util.package] Unable to install package Plugwise_Smile==0.2.13: ERROR: Command errored out with exit status 1:
     command: /srv/homeassistant/bin/python3.7 -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-ytzy5xzz/lxml/setup.py'"'"'; __file__='"'"'/tmp/pip-install-ytzy5xzz/lxml/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-install-ytzy5xzz/lxml/pip-egg-info
         cwd: /tmp/pip-install-ytzy5xzz/lxml/
    Complete output (3 lines):
    Building lxml version 4.5.1.
    Building without Cython.
    Error: Please make sure the libxml2 and libxslt development packages are installed.
    ----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
WARNING: You are using pip version 20.0.2; however, version 20.1.1 is available.
You should consider upgrading via the '/srv/homeassistant/bin/python3.7 -m pip install --upgrade pip' command.
2020-06-12 13:20:43 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 418, in start
    resp = await task
  File "/srv/homeassistant/lib/python3.7/site-packages/aiohttp/web_app.py", line 458, in _handle
    resp = await handler(request)
  File "/srv/homeassistant/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 119, in impl
    return await handler(request)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/http/real_ip.py", line 39, in real_ip_middleware
    return await handler(request)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/http/auth.py", line 127, in auth_middleware
    return await handler(request)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/http/view.py", line 129, in handle
    result = await result
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/config/config_entries.py", line 112, in post
    return await super().post(request)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/http/data_validator.py", line 60, in wrapper
    result = await method(view, request, *args, **kwargs)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/data_entry_flow.py", line 73, in post
    "show_advanced_options": data["show_advanced_options"],
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/data_entry_flow.py", line 117, in async_init
    flow = await self.async_create_flow(handler, context=context, data=data)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/config_entries.py", line 518, in async_create_flow
    await async_process_deps_reqs(self.hass, self._hass_config, integration)
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/setup.py", line 322, in async_process_deps_reqs
    hass, integration.domain
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/requirements.py", line 78, in async_get_integration_with_requirements
    hass, integration.domain, integration.requirements
  File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/requirements.py", line 130, in async_process_requirements
    raise RequirementsNotFound(name, [req])
homeassistant.requirements.RequirementsNotFound: Requirements for plugwise not found: ['Plugwise_Smile==0.2.13'].