openHAB 4.2 Milestone discussion

Setup, Configuration and Use News & Important Changes
227

It doesn’t help because it ends up in configuration properties, not the thing properties. Could be that is by design or a bug in core, but not easy to fix for sure.

228

Yes that’s true,I believe you can’t set thing properties like that in thing file, only configuration parameters.

By the way, I believe you found how to fix the issue now.

229

Whatever you fixed here, it works :muscle:
All things are back online.

230

Here is the fix

231

It would be good if someone who uses UI and at least someone who uses gen 2 devices can check if I broke something there.

232

Will check in a couple of minutes….

1 Like
233

Upgraded one of my installations to RC1 and then updated shelly Binding to your patched version.
Not a single shelly device, all Gen2 UI configured is coming online: HANDLER_MISSING_ERROR

234

Can you send the YAML? I‘ll check that

235

Something strange is happening here.
Update of shelly binding resulted in handler missing error and bundle list showed it as a smarthomej binding.
Removed the bundle and installed it again (bundle:install) and now Shellys are back online

UID: shelly:shellyplus1pm:10061cca9514
label: Shelly Plus1PM Bedroom (shellyplus1pm-10061cca9514@192.168.1.59)
thingTypeUID: shelly:shellyplus1pm
configuration:
  enableBluGateway: false
  deviceIp: 192.168.1.59
  updateInterval: 60
  enableRangeExtender: false
236

That‘s really strange. There has never been a smarthome/j Shelly binding. What is returned by list -s | grep shelly now?

237

After a bundle:install from your download link, it is reported correct.
As said, something strange here. Had y couple of unrelated error message…

1 Like
238

I might have mixed up thing. Now it is showing

334 x Active x  80 x 4.2.0.RC1             x org.openhab.binding.shelly
openhab> update org.openhab.binding.shelly http://download.smarthomej.org/org.openhab.binding.shelly-4.2-SNAPSHOT.jar
334 │ Active   │  80 │                       │ mvn:org.openhab.addons.bundles/org.openhab.binding.shelly/4.2.0.RC1
239

Are you using Gen1 or Plus/Pro (Gen 2/3) devices?
Discovered by UI or defined in .things?

240

According to this post, only Gen1 with textual config

241

@hmerk Do you have textual configurations? (.things)

I updated the DEV build with a changed initialization if deviceGeneration property is not set (as usually with .things file definitions). Who can verify
a) That things defined in .things work properly
b) and thiose discovered and added by the UI
c) a complex config with a mix on Gen 1 and Gen 2 - what happens after upgrading the binding

b) is my standard test case and works in my dev and prod setup
c) was done the last days multiple times and works, but based on the DEV build not RC2
For a) I have no setup

242

No, completely UI based….

243

ok, I did a simple test with Shelly 1 and the new version initializes a Shelly 1 defined in .things and multiple Gen2 UI-based, so seems to fix the problem

244

A change, even if possibly not yet perfect, was merged. A new RC2 should be built in the coming hours. So Shelly users, please try 4.2 RC2 when available to confirm that it works well.

1 Like
245

I’ll publish RC2 in the early afternoon - stay tuned!

3 Likes
246

Within my setup (not RC2) I verified a combination of

  • Shelly 1 defined in .things (Gen1)
  • Shelly Plus Plug in .things (Gen2)
  • A Shelly 1 and a 2.5 discovered by UI (Gen 1)
  • A mix of Gen 2 and Gen 3 devices discovered by the UI

so far all looks good with the fix.

1 Like