Is that the 3.0 HNS system @Antiloop? There should be more details in the log but it already identifies as Stretch chances are it stopped at python code line 222 as we’ve restricted the supported devices the module support.
Can you check if it gives XML output on http://{your_ip}/core/domain_objects? If so the full list of endpoints required to support new environments is on this page
We’re willing to have a look and the fact that you see ‘stretch’ and version returned looks promising. We can’t make any full commitments, but if we can get a version number out of it and the XML (we already have some Stretch XML data, but two environments is the least to be able to code properly) we might be able to cook something up.
This might be useful: I discovered that it’s possible to dismiss notifications on the Plugwise Smile Gateway by sending a DELETE request to the /core/notifications endpoint (I didn’t find any way to dismiss them in the web app). At least now I can get my thermostat display to turn blue again
I don’t have any boiler control yet but am looking into getting an Adam so I can use OpenTherm.
I already have a ZigBee network and don’t really want to build another one if I can help it, so I would be connecting TRVs to Home Assistant directly and let it manage the boiler through Adam.
With an Adam, would I be able to set the boiler water temperature, and tell it to turn on? Or would I manage this by overriding the current and set temperature which would otherwise be provided by the thermostat?
Would my actual thermostat (not a Plugwise one - generic OpenTherm) then show up as a separate thermostat?
Is this a good and reasonable approach?
If it’s impractical to use an Adam and let HA manage everything I’d probably go with a full ecosystem solution instead, but I like the idea of having more flexibility through the use of HA to manage everything.
What type is your boiler? Is it a gas-fired water-heater (in Dutch CV-ketel) controllable by OpenTherm? Or is it a water-tank with an electrical heating element?
What type is your boiler? Is it a gas-fired water-heater (in Dutch CV-ketel) controllable by OpenTherm? Or is it a water-tank with an electrical heating element?
I have what’s referred to in the UK as a combi boiler. It’s gas-fired, and heats up water for domestic use and for the radiators. These water temperatures can be controlled separately through OpenTherm or on the boiler itself. It doesn’t have a tank.
It’s an Ideal Vogue C26.
What is a TRV?
Sorry. Thermostatic Radiator Valve. Opens and closes valve to let water into radiator until it’s at the desired temperature.
Regarding your TRV’s, are these zigbee enabled? And do these have open/close-control similar to the Plugwise Tom?
Please note: the functionality of the Plugwise Component is limited. It was made to make information from the Plugwise system available as entities in Home Assistant. So, Home Assistant is not doing any control, this is all done by the Plugwise software present in the Adam.
There is some limited manipulation of control-inputs available via Home Assisistant: you can change the temperature-setpoints of the connected thermostats, you can turn a weekschedule on and off, and you can activate presets.
What you have in mind is at the moment not possible with the Adam and the Plugwise component. From what I know, parts of what you have in mind, should be possible but require software development.
Regarding your TRV’s, are these zigbee enabled? And do these have open/close-control similar to the Plugwise Tom?
They probably would be, but part of the point of doing this with HA would be to increase flexibility so that I can integrate literally anything with the climate control system and not be limited to things the Adam would support directly.
Please note: the functionality of the Plugwise Component is limited. It was made to make information from the Plugwise system available as entities in Home Assistant. So, Home Assistant is not doing any control, this is all done by the Plugwise software present in the Adam.
Ahh, this clarifies things greatly. Fair enough. Thank you very much.
FYI, we have added initial support for the Plugwise Stretch with firmware 3.1 to Plugwise-beta.
If you have such a Stretch and are interested in helping us test, please leave a message in this topic.
I know of two types of Stretch, with firmware 2.3.x and with firmware 3.1.11. Both support the old Circles and Stealths. We are working with the two owners of these to develop the support in Plugwise-beta (and later to be included in HA Core Plugwise).
Not sure about the Scan, the 2.3.x-owner has a Scan but that one does not function in combination with his Stretch.
The Plugs are only compatible with the Adam as far as I know: I have an Adam and 3 Plugs.
We’ve made Plugwise-beta more equal to Core Plugwise, unfortunately this means that you’ll have to remove your plugwise integrations before installing the update. And, after restarting HA Core, re-add them. Sorry about that but unfortunately this is needed as the last step to become fully interchangeable with Core Plugwise.
The P1 was given two devices while there should have been one. This is now fixed. If you follow the above recommendation you should see the single device after the update and restart.
CHANGES:
Support the Plugwise Stretch v2 and v3
Support P1 with firmware 2.1
Support switching-groups, for the Adam with Plugs and the Stretches
Various improvements in the Plugwise_Smile code, among others, less data is being read from the Smiles
Please test this version and let us know if you encounter any bugs. If yes, please create an Issue in the Plugwise github.
@philipk89 FYI, your suggestion will be implemented in Plugwise_Smile v1.5.0 and will be made available as a service in Plugwise-beta v0.9.0, planned to be released after HA Core 0.115.0 has been released.
Progress-update: with all the hard work @bouwew performed over the weeks there has been much improvement! The current aim is to get all of it into HA Core as soon as possible, just go give you a heads-up on that: 0.115 will already include the ability to configure your interval time and will be paving the way with the newer version of our Smile-module towards Core support for Stretch-es as well.
Already accepted for 0.116 is our testing PR (so if you like to submit a patch straight towards HA Core, you can test the waters ) - do note that we’re happy to invite you to our github-team to develop for the Smile-module and beta custom-component! This will ensure having lots of friendly users to test your code first.
Also submitted for 0.116 is the ability (for those of you with creative/remote Smiles) to add a port number when configuring manually. Speaking of configuring manually, when doing so you should no longer see the ‘discovered Smile’ still popping up (or having to ignore it) in 0.116, we patched that and it has been accepted.
Bouwes’ progress on both notifications- and stretch-support are almost ready to go into PRs - as the Core-team has a lot of PRs to review this may take some time. If you have some spare time and want to give back to the community, just leave your comment or review a PR (or two, or three …). It really helps the Core team and ensures newer functionality can be included sooner. Have a look a the second column (dubbed Review) at https://github.com/home-assistant/core/projects/4 pick one and leave your constructive thoughts!
Anyway, kudos to Bouwe for his efforts and many thanks to those testing and providing feedback!
The new release is meant for Core v0.115, for the older versions the sensors don’t work due to an under-the-hood-change in Core.
Also, a service has been added: plugwise.delete_notification, so now the Plugwise Notification(s) can be dismissed from within Core.
And, adding a port-number has been adapted to the Core-standard-way of doing things.
