No issues so far after running 5.2.0.202605030737 about more than 24h.
Everything looks and feels stable!
No issues so far after running 5.2.0.202605030737 about more than 24h.
Everything looks and feels stable!
Update now not only DEV system, also the two other once.
No issue seen with 5.2.0.202605030737
as I said: Don’t expect functional fixes, it’s just refactoring and I need to verify that there are no side effects
everything seems to be running fine so far with the new build and some
Shelly Plus1, 1PM, 2PM, PlugS, TRV
Thank you so much for all your effort.
@Larsen do you even have the energy channels and voltage channels available on the Shelly 1 plus pm?
I’m on openhab 5.1.4 with dev 5.2.0.202605011258
No errors so far.
Greets
Hello. I can confirm, that I have had and still have on all my plus 1PM the energy / power as well as the voltage channel active and running.
All fine so far…
All Things, items were created with 4.x a long time ago…
My PI5 runs with latest OpenHabian 5.1.4, and latest noOpenHAB patches
BTW: Thanks for the tipp with DO NOT UPDATE the shellys to 2.0.0 Beta-1 ![]()
so here its is
* SNSW-001P16EU
if you delet it and add them sometime the voltage channels and enery channels appears sometime not
Have you tried,
And started ZRAM
And started OH
Deleted the cache stopped everything deleted the cache reloaded and rebooted same behavior
I’d really wish that clearing the cache wasn’t one of those “when everything else fails” gotos… it’s very rarely useful. It’s not the data that are cached, it’s the bundles (parts of OH itself). Clearing it only helps if there’s anything wrong with your bundles/installed components, your data are unaffected by a cache clearing.
I"m puzzled now, and have no other idea anymore.
What would be, if you install a new fresh OH with the DEV binding and install the Shelly 1 PM plus?
Same behaviour…I don’t know does it help to get some logs?
I updated the DEV build, could you please verify. Config handling for device address (IP/FQDN/BD) has been changed. That should be the final check before merging.
I’ll the move to the meter issues, saw already 2 bugs
up and running.
what do you exactly mean with:
Config handling for device address (IP/FQDN/BD) has been changed
Where do we have to check if this is working?
If the devices are online, it’s “working”. But, the change only matters if you use names, not IP addresses when you configure the devices. To use names, you must have some kind of name resolution system set up on your local network, so it won’t be viable for many users to test this.
All fine. No issuses seen so far with 5.2.0.202605080611
same here after more than 24h! It is nice to see the binding so stable ![]()