Let me see if and when I can reproduce it. Will keep you updated. Fortunately it seems like a minor issue. At least we know when a notification is not disappearing after dismissing it in the notification part a reboot of HA resolves it 
Just FYI, w.r.t. Plugwise Notifications, the Plugwise-beta component can only detect them, it cannot dismiss them: there is not communication back to the Smile. So, the notification has to be dismissed in the Plugwise App.
Or it will disappear automatically, when the error is resolved. This happens in my system when I plug a Plug back into the electricity-socket. I don’t understand why this does not happen in your system, when the connection to the CV-ketel is restored.
Sometimes people assume too much wrt HA Core functionality 
I wasn’t assuming HA is in any way able to dismiss a notification at the Plugwise side. When I noticed the notification in HA I already quickly saw the corresponding notification in Plugwise was (already) gone. Having notifications in HA is causing me stress because I am striving to a faultless system
Sorry, I misread your writing 
I know what you mean, getting Notifications all the time can be annoying.
Please let us know here when you were able to produce the error.
Update 3: v0.5.0 is temporary pulled back, we’ve learned there is a way to implement the changes in a non-BREAKING way.
Update 2: a fix is implemented in Plugwise-beta v0.5.0.
Update: I have it working now. I will let you know when the update fixing this is available (on HACS).
@Atarian I am able to reproduce your issue. I’m trying to solve it, will let you know about a solution once I have it working.
@Atarian, others that are interested: Plugwise-beta v0.5.1 is available for testing.
We have taken extra care so that the implemented changes do not break anything, there should be no risk in updating to this version.
Please test this version (by updating WITHOUT removing the present Plugwise integration(s)) and let us know whether you encounter any problem.
Advice: empty your browsers cache and hard reload, after the update, parts of HA Core are cached in your browser, also parts of Plugwise-beta.
Update to v0.5.1 went seamlessly. Running Home Assistant 0.113.3 and latest HACS (1.3.0b1). Haven’t tried triggering a notification myself.
Great, thanks for letting us know!
I have triggered an error by disconnecting one of the wires that run from the Smile to the CV-ketel.
A question: is there anyone that has a legacy Anna that is still on firmware 1.8?
Does zeroconf-discovery work with the HA Core Plugwise component, in Core v0.113?
any chance for support for Plugwise Stretch ?
it is recognized (by the non beta integration) as ‘stretch v2.3.12’
I’ve already tried to change the username in the plugwise-smile code to ‘stretch’ as that is mandatory
after that the integration gives ‘Unexpected error’ when entering the 8 characters ID from the plugwise stretch
my python is really bad, so I can’t solve it myself, I could extract the /core/ pages or others if that could give a jumpstart
The stretch is not a stick but network enabled, I Will first try to locate my old smile p1 to start with it
The Stick is inside the Stretch, just open it, it’s there, behind a cover.
Plug it in your HA Core Server, install the Plugwise Stick custom_component (e.g. via HACS), restart HA Core and add the Plugwise Stick under Integrations: press the + button --> type “plugwise” --> select Plugwise Stick and so on.
There is still a stick inside the Adam
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
Is this related to https://github.com/plugwise/Plugwise-Smile/issues/81 by any chance?
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.
@Antiloop, please also check for xml-data here: http://{your_ip}/system_status, if present, sent this information as well.
yes the issue is related to issue 81, I think we better continue it here
i’ve extracted this from my system, and yes I think it’s 3.0 HNS although the links are dead at plugwise:
system_status: https://pastebin.com/h2P9eUJ6
core/domain_objects: https://pastebin.com/7YM3H2N5
core/appliances: https://pastebin.com/CQDgLnSy
core/direct_objects: https://pastebin.com/mj6vQC8X
core/locations: https://pastebin.com/cuFwEp4r
core/modules: https://pastebin.com/AxQk74zU
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
Nice find, very useful indeed
FYI Plugwise beta v0.6.0 has been released: https://github.com/plugwise/plugwise-beta/releases/tag/0.6.0
Be sure to read the BREAKING-notes!
Any questions, let us know here
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.
Thanks!