ah right, in the token values they exist. ill investigate more
Additional to this, my P1 dongle went into unavailable state at some point. I could not re-add it in the Homey app.
Turned out this was because it stopped sending it’s mDNS identification (other devices in my network were still discoverable through mDNS).
In order to solve this I restarted the P1 device by unplugging the USB-adapter (mine is powered by USB because of the older type of energy meter). After it reconnected to the WiFi network it could be discovered again.
@Jeroen_Tebbens Hi, many thanks for this wonderful app! It really helps me making my home more automatic and in particular consume my solar energy as it’s generated.
However, since some time I noticed that my P1 dongle is unresponsive. I since removed it from my devices, and re-added it. The strange thing however is that it supplies no information on my gas meter and total energy consumption anymore. I tried removing and re-adding several times, but doesn’t help.
It still registers as normal in the Energy app itself.
My kWh single phase meter on my solar panels works as intended with this same app.
Do you have any idea what causes this effect? And even better, do you have a fix? Thanks!
No clue. Please sent me both a diagnostic report from the HomeWizard app for Homey and your output from your p1
Several bug fixes (P1 numbers and values, SDM230 problem, memory leak) Increase node-fetch module timeout to 20s (to compensate for slow wifi connection issues with Homewizard appliance) Improved solar panel reflection in Energy tab Updated manifest & description to comply with Homey/Athom policy New icons for Heatlink and Energylink (thanks for community sharing)
First of all, great job on this app! Information from de P1 energy device is working very well. One question: is it possible to make a LED ring for the P1 like Plugwise P1 has? Maybe you can ask the developer how he did it? It is a very nice feature where you can see on the LED ring if you’re using power or giving back (with solar panels). Thanks!
Link to plugwise app:
Since about three days we have received the following message in the Homey for our P1 dongle: “Device Unavailable - invalid_capability_id”
We have restarted the HomeWizard app and Promey but to no avail. In the Homewizard app we can simply read the dongle.
Did anything happen to change, an update? I sent a diagnostic report: 640eafb1-dba2-479b-84c6-3d90f6b442d9
Try to pair your dongle again (remove/add). I can’t replicate the issue as I don’t see it with my p1 dongle. I do recall some software issue in Homey firmware that is currently released 7.1.4.
So perhaps try 7.1.4 first and if not, pair the dongle again.
I understand your request. Not sure if I have the time at moment to add that enhancement yet.
I’ll put it to the list.
Refresh time? What is the use case? Currently refresh time is 10 seconds which is fine to be honest. Else it app will eat unnecessary resources and cpu cycles.
Sorry, I replied to the wrong topic I’ll remove it. My request was about the LED ring. Too busy like you
Somehow the dongle works again. Didn’t do anything to make it work again. I checked the Homey app yesterday evening and there it was. Happy me
Perhaps new Homey firmware kicked in? Really clueless on cause. But happy that it resolved for you!
I just bought the P1 dongle. And the dongle and homey are on two separate VLANs. Homey doesn’t seem to be detecting the dongle via this app. All traffic is allowed from homey VLAN to dongle VLAN (but not the other way around). Any ideas why Homey cannot see the dongle?
Yes you need MDNS repeater on your router that connects both VLAN’s.
Pfsense has Avahi, Opnsense calls it mDNS repeater. Not sure what flavor router you have but this is what you need.
Thanks! Appreciate the professional level support
I’ve installed mDNS repeater on my OpnSense installation, and enabled it for both the VLANs, restarted the app on Homey, but still no dice
Dont forget to add rules to allow the http 80/tcp traffic. From one VLAN to another.
So in my case the P1 dongle is in my IoT VLAN and is allowed to talk to my Homey IP.
Is that your homey IP? So that means I need to allow HTTP traffic from my IoT VLAN to Homey IP?
Yes by default (no rules) this is blocked so you need to open it else Homey can’t talk to your Dongle.
Be aware mDNS is only for announcement of the device, you still need to allowed the traffic to flow hence the Homey ->> Dongle p1 80/tcp. Homey is initiator so return traffic is fine.
Okay, I’m a bit confused now. From the screenshot you shared, looks like the dongle is the initiator? Looks like the rule says it allows all traffic from IoT VLAN to Homey?
This sounds strange to me because indeed as you mentioned, I would expect Homey to initiate a connection to the dongle. In my case, all traffic is allowed from the Homey VLAN to the IoT VLAN. The only case this wouldn’t work is if the dongle is trying to talk to homey.
Apologies if this is taking the thread off topic. Happy to move it to DM if you want