Shelly Binding

You need to install coap services

openhab> feature:list | grep -i coap
openhab-core-io-transport-coap                    │ 4.3.2            │          │ Started     │ distro-4.3.2             │
openhab-transport-coap                            │ 4.3.2            │          │ Started     │ distro-4.3.2             │ CoAP Transport
openhab.tp-coap                                   │ 4.3.2            │          │ Started     │ distro-4.3.2             │ Californium CoAP library

Also, I’ve got the add-on store TRÅDFRI Binding installed…

What is the output of

bundle:list | grep Californium

In worst case try installing coap services anyway. Either by console or by removing&reinstalling Tradri binding to make sure, all components are added.

Furthermore check permission rights of the shelly .jar file in the addons folder.

openhab> bundle:list | grep Californium
280 │ Active │  80 │ 2.7.4                 │ Californium (Cf) Core
281 │ Active │  80 │ 2.7.4                 │ Californium (Cf) Element Connector
282 │ Active │  80 │ 2.7.4                 │ Californium (Cf) OSGi
erik@MinipcLG2:/usr/share/openhab/addons$ ls -pal
totaal 768
drwxr-xr-x 2 openhab openhab   4096 jan 29 15:49 ./
drwxr-xr-x 4 openhab openhab   4096 jan 13 06:07 ../
-rw-r--r-- 1 root    root    588349 jan 29 15:49 org.openhab.binding.shelly-4.3.5-SNAPSHOT-zonderoplossingBLU.jar
-rw-r--r-- 1 root    root    182887 jan 25 12:43 org.openhab.binding.unifiprotect-4.0.0-latest.jar
-rw-r--r-- 1 openhab openhab     70 jan 12 22:13 README

Same permissions as always, and the binding does work. It just gave an error at startup…

Hi developers,

Is the Shelly Pro Dual Cover / Shutter PM in any way supported by the recent binding? I don’t seem to be able to find any reference to it in the documentation, so that makes me guessing the device is not supported. Is it gonna be supported in the future, are there any plans for that? Thanx.

Best regards,
Jesse

Hi, no it’s not, but on the list

@markus7017, I’m not mistaken that the ‘wrap-up’ problem is not fixed in the latest jar, right? (To avoid waiting for something that’s there already :))

Ok, thanx Markus!
Looking foreward to that.
If you need any help testing by that time, I’ll gladly participate.

Not yet, I‘m thinking about a proper logic

Problems with Button2

the questions goes to the shelly Button1 or Button2 Users, or to @markus7017

I have two rules created which sends to seven different shellys the command “ON” or “OFF”
When running the rule per “hand” in the rules section with the “play icon” everything is fine. All lights switch ON, or OFF.

This scenario I have now put on a shelly button2.
Like when the status from the channel from the button triggered, with “SHORT_PRESSED” then run the rule “light on”
It works wonderfull.

The same stuff for switch off the lights:
So when the status from the channel from the button triggered, with “DOUBLE_PRESSED” then run the rule “light off”

→ But here only three from the seven lights went off. The others stay on…

Any idea, why this four shellys stay on?

The log file say’s that all seven shelly get the right command to switch off. But they stay on…

Thanks for all the tipps…

I uploaded a special build, which keeps a table for devices, which have been already discovered. If a new (or overlapping) mDNS request comes in the device discovery (incl. API calls) is skipped, instead a message is displayed. The mechanism works in general (I see those messages), but I hadn’t the problem with overlapping mDNS requests.

org.openhab.binding.shelly-4.3.5-discovery-SNAPSHOT.jar
Make sure to remove the old jar before installing the new one.

Please test this build and report the results. Maybe I move from WS to http calls for discovery to reduce network traffic, but that’s an independent step. First I want to get the discovery process in those scenarios stable.

No, this change was requested by the maintainers, but you could check the StatusDetail, which indicates the configpending state

please try this build and check the situation where pid is wrapping from 255 to 0

org.openhab.binding.shelly-4.3.5-SNAPSHOT.jar

1 Like

Ok thx. AFAIK statusdetail isn’t available in rulesdsl.
But it’s OK. Thx for the answer.
Greets

I seem able to switch Shelly’s on and off, but at startup, I got these warn messages:

openhab> log:display | grep -i shelly | grep -i warn
20:27:55.602 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyplus1pm' for thing 'shelly:shellyplus1pm:d4d4da7de204' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.605 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shelly1mini' for thing 'shelly:shelly1mini:6055f998852c' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.607 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyplusplug' for thing 'shelly:shellyplusplug:e465b8b80068' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.609 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyblubutton' for thing 'shelly:shellyblubutton:b0c7debd414c' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.610 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyblumotion' for thing 'shelly:shellyblumotion:b0c7de77152a' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.611 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shelly1mini' for thing 'shelly:shelly1mini:6055f9988f3c' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.612 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellybludw' for thing 'shelly:shellybludw:3c2ef5694b59' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.614 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellybludw' for thing 'shelly:shellybludw:b0c7debe5486' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.615 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyplus2pm-relay' for thing 'shelly:shellyplus2pm-relay:80646fca43dc' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.616 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyblubutton' for thing 'shelly:shellyblubutton:f4b3b18267a9' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.618 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shelly1mini' for thing 'shelly:shelly1mini:6055f99877dc' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.619 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyblumotion' for thing 'shelly:shellyblumotion:b0c7de422d7a' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.620 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyplusplug' for thing 'shelly:shellyplusplug:e465b8b29fec' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.621 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyplusplug' for thing 'shelly:shellyplusplug:fcb467269c34' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.622 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyplus2pm-relay' for thing 'shelly:shellyplus2pm-relay:d4d4da09b2c8' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.624 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyplusplug' for thing 'shelly:shellyplusplug:c82e180a06cc' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.625 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyplus1pm' for thing 'shelly:shellyplus1pm:d4d4da7df89c' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.627 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellybludw' for thing 'shelly:shellybludw:3c2ef572b984' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.628 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellybludw' for thing 'shelly:shellybludw:60efab0dc93e' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.629 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shelly1mini' for thing 'shelly:shelly1mini:6055f998dd18' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.630 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shelly1mini' for thing 'shelly:shelly1mini:6055f9985660' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.631 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyplusplug' for thing 'shelly:shellyplusplug:08f9e0fd6d70' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.633 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyrgbw2-white' for thing 'shelly:shellyrgbw2-white:48e729665a1c' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.634 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shelly1mini' for thing 'shelly:shelly1mini:6055f998d980' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:55.635 [WARN ] [.core.thing.internal.ThingManagerImpl] - A thing handler factory claims to support 'shelly:shellyplus1pm' for thing 'shelly:shellyplus1pm:d4d4da7df8a8' for more than 120s, but the thing type can't be found in the registry. This should be fixed in the binding.
20:27:57.638 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyplus1pm:d4d4da7de204' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.641 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyplus1pm:d4d4da7de204' because the thing type was not found in registry.
20:27:57.669 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shelly1mini:6055f998852c' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.670 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shelly1mini:6055f998852c' because the thing type was not found in registry.
20:27:57.675 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyplusplug:e465b8b80068' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.676 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyplusplug:e465b8b80068' because the thing type was not found in registry.
20:27:57.682 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyblubutton:b0c7debd414c' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.683 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyblubutton:b0c7debd414c' because the thing type was not found in registry.
20:27:57.689 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyblumotion:b0c7de77152a' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.690 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyblumotion:b0c7de77152a' because the thing type was not found in registry.
20:27:57.695 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shelly1mini:6055f9988f3c' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.696 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shelly1mini:6055f9988f3c' because the thing type was not found in registry.
20:27:57.701 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellybludw:3c2ef5694b59' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.702 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellybludw:3c2ef5694b59' because the thing type was not found in registry.
20:27:57.708 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellybludw:b0c7debe5486' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.709 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellybludw:b0c7debe5486' because the thing type was not found in registry.
20:27:57.714 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyplus2pm-relay:80646fca43dc' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.715 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyplus2pm-relay:80646fca43dc' because the thing type was not found in registry.
20:27:57.721 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyblubutton:f4b3b18267a9' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.722 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyblubutton:f4b3b18267a9' because the thing type was not found in registry.
20:27:57.727 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shelly1mini:6055f99877dc' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.728 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shelly1mini:6055f99877dc' because the thing type was not found in registry.
20:27:57.732 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyblumotion:b0c7de422d7a' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.733 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyblumotion:b0c7de422d7a' because the thing type was not found in registry.
20:27:57.738 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyplusplug:e465b8b29fec' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.739 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyplusplug:e465b8b29fec' because the thing type was not found in registry.
20:27:57.744 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyplusplug:fcb467269c34' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.745 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyplusplug:fcb467269c34' because the thing type was not found in registry.
20:27:57.751 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyplus2pm-relay:d4d4da09b2c8' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.752 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyplus2pm-relay:d4d4da09b2c8' because the thing type was not found in registry.
20:27:57.758 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyplusplug:c82e180a06cc' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.759 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyplusplug:c82e180a06cc' because the thing type was not found in registry.
20:27:57.764 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyplus1pm:d4d4da7df89c' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.765 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyplus1pm:d4d4da7df89c' because the thing type was not found in registry.
20:27:57.771 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellybludw:3c2ef572b984' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.772 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellybludw:3c2ef572b984' because the thing type was not found in registry.
20:27:57.779 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellybludw:60efab0dc93e' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.780 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellybludw:60efab0dc93e' because the thing type was not found in registry.
20:27:57.787 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shelly1mini:6055f998dd18' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.787 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shelly1mini:6055f998dd18' because the thing type was not found in registry.
20:27:57.794 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shelly1mini:6055f9985660' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.794 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shelly1mini:6055f9985660' because the thing type was not found in registry.
20:27:57.801 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyplusplug:08f9e0fd6d70' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.802 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyrgbw2-white:48e729665a1c' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.803 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyrgbw2-white:48e729665a1c' because the thing type was not found in registry.
20:27:57.818 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shelly1mini:6055f998d980' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.819 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shelly1mini:6055f998d980' because the thing type was not found in registry.
20:27:57.824 [WARN ] [.core.thing.internal.ThingManagerImpl] - Channel types or config descriptions for thing 'shelly:shellyplus1pm:d4d4da7df8a8' are missing in the respective registry for more than 120s. In case it does not happen immediately after an upgrade, it should be fixed in the binding.
20:27:57.825 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyplus1pm:d4d4da7df8a8' because the thing type was not found in registry.
20:27:59.990 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyrgbw2-white:48e729665a1c' because the thing type was not found in registry.
20:27:59.991 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyrgbw2-white:48e729665a1c' because the thing type was not found in registry.
20:28:00.075 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyrgbw2-white:48e729665a1c' because the thing type was not found in registry.
20:28:00.076 [WARN ] [.core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'shelly:shellyrgbw2-white:48e729665a1c' because the thing type was not found in registry.

(I didn’t delete my things prior to switching the jar files. Maybe that’s the reason?)

(Which logic did you settle for, in the end? :))

strange, never saw that, unless we have an endless loop somewhere
try it

I’m afraid something is off…

First, I couldn’t edit Shelly things anymore; they all looked like this:

So I figured I deleted them all, as prescribed in your documentation. (This meant “forcefully removing” or how is it called one thing which I had disabled, but obviously couldn’t re-enable.)

I then followed all the steps of your above-mentioned documentation, but now the binding doesn’t appear in the UI, and none of the things are discovered:

However, in the CLI:

openhab> bundle:list | grep -i Shelly
336 │ Active │  80 │ 5.0.0.202502041838    │ openHAB Add-ons :: Bundles :: Shelly Binding

There were also the WARN logs I posted earlier…?

So reverted to the earlier jar without the PID fix to re-add my things…

I’m now on the newest version again. The UI view and CLI output is still the same, so not good. Awaiting instructions :wink:

In the meantime, I noticed that my BLU Buttons and BLU Door/Window devices don’t work properly anymore… So I’m reverting back to the jar before the PID fix (so the one of a few weeks ago, where it’s possible an older packet supplants a newer one).

@markus7017, I’ll send you a PM with my logs.

Hi Markus,

I’ve seen no reply to my feedback on this, so I assume there is nothing to re-test yet for Shelly Plus Uni with your very latest Snapshot, is it?
Did my feedback help you or is it lacking anything to get the missing counter channel onboarded in a future build?
Just asking as I might find time this weekend in case you needed more and not to chase you.

Somehting else, but way lower on my personal wish list than the BLU saga…

I installed a Shelly Flood yesterday. It didn’t go smoothly… First I saw it in the inbox immediately, but noticed I had not yet given it a static IP address. But after that, the device was never detected, also not after running discovery 3 times.

I also noticed the device went offline automatically; but that seems to be by design… (I think the Shelly app/GUI could be a bit more clear about that, but okay…)

But I ended up creating the thing manually (which was the first time I had to do that for a Shelly device).

But the items connected to channels don’t get updated (they did pass a value the first time…):


and

versus:
image
and
image

The binding logs show that there was interaction at 10/02 09:57:

2025-02-10 09:57:40.137 [TRACE] [y.internal.handler.ShellyBaseHandler] - shelly1mini-6055f9988f3c: Watchdog restarted (expires in 70 sec)
2025-02-10 09:57:40.137 [TRACE] [.internal.handler.ShellyRelayHandler] - shelly1mini-6055f9988f3c: Updating 1 relay(s)
2025-02-10 09:57:42.850 [TRACE] [discovery.ShellyDiscoveryParticipant] - shellyflood-c8c9a316dfcc: Shelly device discovered with empty IP address (service-name=[ServiceInfoImpl@566224161 name: 'shellyflood-C8C9A316DFCC._http._tcp.local.' address: '(null):0' status: 'DNS: pi-hole.local. [pi.hole/192.168.1.9] state: probing 1 task: null', has NO data
	shellyflood-C8C9A316DFCC._http._tcp.local.: ])
2025-02-10 09:57:42.851 [DEBUG] [discovery.ShellyDiscoveryParticipant] - shellyflood-c8c9a316dfcc: Shelly device discovered: IP-Adress=192.168.1.47, type=shellyflood
2025-02-10 09:57:42.851 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyflood-c8c9a316dfcc: HTTP GET http://192.168.1.47/shelly
Accept-Encoding: gzip
User-Agent: Jetty/9.4.54.v20240208
Content-Type: application/x-www-form-urlencoded



2025-02-10 09:57:43.915 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyflood-c8c9a316dfcc: HTTP Response 200: {"type":"SHWT-1","mac":"C8C9A316DFCC","auth":false,"fw":"20230913-112632/v1.14.0-gcb84623","discoverable":false,"longid":1,"sleep_mode":true}
Server: Mongoose/6.18
Connection: close
Content-Type: application/json
Content-Length: 141


2025-02-10 09:57:43.916 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyflood-c8c9a316dfcc: HTTP GET http://192.168.1.47/shelly
Accept-Encoding: gzip
User-Agent: Jetty/9.4.54.v20240208
Content-Type: application/x-www-form-urlencoded



2025-02-10 09:57:43.931 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyflood-c8c9a316dfcc: HTTP Response 200: {"type":"SHWT-1","mac":"C8C9A316DFCC","auth":false,"fw":"20230913-112632/v1.14.0-gcb84623","discoverable":false,"longid":1,"sleep_mode":true}
Server: Mongoose/6.18
Connection: close
Content-Type: application/json
Content-Length: 141


2025-02-10 09:57:43.931 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyflood-c8c9a316dfcc: HTTP GET http://192.168.1.47/settings
Accept-Encoding: gzip
User-Agent: Jetty/9.4.54.v20240208
Content-Type: application/x-www-form-urlencoded



2025-02-10 09:57:43.964 [TRACE] [shelly.internal.api.ShellyHttpClient] - shellyflood-c8c9a316dfcc: HTTP Response 200: {"device":{"type":"SHWT-1","mac":"C8C9A316DFCC","hostname":"shellyflood-C8C9A316DFCC","sleep_mode":true},"wifi_ap":{"enabled":false,"ssid":"shellyflood-C8C9A316DFCC","key":""},"wifi_sta":{"enabled":true,"ssid":[*redacted before posting*],"ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"wifi_sta1":{"enabled":false,"ssid":null,"ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"mqtt": {"enable":false,"server":"192.168.33.3:1883","user":"","id":"shellyflood-C8C9A316DFCC","reconnect_timeout_max":60.000000,"reconnect_timeout_min":2.000000,"clean_session":true,"keep_alive":60,"max_qos":0,"retain":false,"update_period":30},"coiot": {"enabled":true,"update_period":15,"peer":""},"sntp":{"server":"time.google.com","enabled":true},"login":{"enabled":false,"unprotected":false,"username":"admin"},"pin_code":"","name":null,"fw":"20230913-112632/v1.14.0-gcb84623","pon_wifi_reset":false,"discoverable":false,"build_info":{"build_id":"20230913-112632/v1.14.0-gcb84623","build_timestamp":"2023-09-13T11:26:32Z","build_version":"1.0"},"cloud":{"enabled":true,"connected":true},"timezone":"Europe/Brussels","lat":[*redacted before posting*],"lng":[*redacted before posting*],"tzautodetect":true,"tz_utc_offset":3600,"tz_dst":false,"tz_dst_auto":true,"time":"09:57","unixtime":1739177864,"debug_enable":false,"allow_cross_origin":false,"actions":{"active":false,"names":["report_url","flood_detected_url","flood_gone_url","temp_over_url","temp_under_url"]},"sensors":{"temperature_threshold":1.0,"temperature_unit":"C"},"sleep_mode":{"period":12,"unit":"h"},"rain_sensor":false,"temperature_offset":0.0}
Server: Mongoose/6.18
Connection: close
Content-Type: application/json
Content-Length: 1572

(I redacted some of the data.)

I see "auth":false a few times. But userId and password are not mandatory parameters in the thing configuration, and I didn’t “Restrict login” or something like that…

This is the thing: