#Hi everyone I m posting this over from

1 messages · Page 1 of 1 (latest)

rose jackal
#

Can someone please help me to debug this further?

wet walrus
#

His stuff is nuts trying to troubleshoot.

rose jackal
#

But is there something I can reset? I don't get it, why it worked flawlessly before and now only for the the hue dimming switches not.

#

In fact, nothing has changed during the zigbee adapter migration.

wet walrus
#

What's the new stick?

#

/old stick

#

might be a clue there

#

As complicated as that code is, it's hard to blame the code if it has not changed but the stick changed.

rose jackal
#

Old stick was conbee II and the new one is the sonoff usb 3.0 plus

#

I had to re-pair the devices, but the came back with the same friendly name

#

Even if i setup a new automation based on the blueprint, it is not working

#

But a normal automation, without blueprint just works

wet walrus
#

If I remember correctly, the conbee needed some tweak somewhere to get it working right with Z2M. I have only usd the sonoff stick you have.

#

That tweak is not still on is it?

rose jackal
#

No, the tweak is deactivated

#

The network operates without problems

#

I have also set in the Z2M option

device_options:
  transition: 1
  legacy: false
wet walrus
#

Latest firmware on the ztick?

rose jackal
#

yes

wet walrus
#

I don't know if it wil help, but you haven't posted the error code yet.

rose jackal
#

Which error code do you mean?

#

At the beginning of this thread I have appended the automation trace, this is all I have.

wet walrus
#

That trace tells me a lot but so much I don't know that you tried to do and what didn't happen. It tells me everything rendered and ran.

#

What is this dimmer doing, it there an error code somewhere

#

There's 1100 lines in that trace and no way to search, I don't see an error in there

#

You are going to need to find EPMatt on the blueprint exchange post for this or his website or github. Also you need to highlight the actual error in that.

#

He could probably tell you in a minute what is happening.

rose jackal
#

Ok sorry. I have clicked the "on button" on the switch. This should have activated the action from " On button short press" which is activating a scene "Arbeitsplatz Hell"

#

There is no error shown for the dimming switch, just nothing happens

#

The lights stay off

#

But nothing more

#

The problem with EPMatt is, that he seems to be offline since a few months.

#

At the blueprint thread in the HA forum, someone mentioned that he had to change legacy: false (which seems to be true as default), but this option I have set globally as shown above.

wet walrus
#

Legacy on and off is a big deal. It changes the whole backend of how stuff is dealt with in Z2M.

rose jackal
#

Yes, but false is the recommended value from Blueprint docs

#

And this was false all the time

wet walrus
#

Well his code is beyond what I am prepared to deal with, I don't know that I can add any more. Perhaps someone else has an idea.
Is there another blueprint that is being supported that you could use? What is the device model?

rose jackal
#

Philips 324131092621

#

I can use any other Blueprint, or just create my own automation. I wanted to be prepared for the future if i want to use dimming function.

#

Thank you for your help

wet walrus
#

You have the hardwate and those blueprints installed. It you have the time and the chops try to fix it. That's my suggestion.

#

The device doesn't need an ota update, does it? I see it supports that.

rose jackal
#

It has the lates update.

wet walrus
rose jackal
#

that's funny, I'm currently reading this topic

wet walrus
#

That's where I would go

rose jackal
#

but I don't think that I need the second one, because HA legacy off is not the same as the device legacy off

#

I have the sensor.dimmer_action

#

But i will try

wet walrus
#

The main diffeeence from what I can see is the action sensor. You have one or not...

rose jackal
#

Correct, I have the action sensor

#

The action sensor is also needed in the blueprint from EPMatt

wet walrus
#

#2 might work either way, but would have to test it.

rose jackal
#

Ok for this blueprint I have to fill in a action for every button.

wet walrus
#

Nope, those topics are not there if the sensor is there.

#

Yup. this is nice because you can spool up a script to call and do almost anything, or use the gui I guess .

rose jackal
#

But it is not what I want. Because I have to fill in actions for 2x4 Buttons and I don't have that much actions 😄

wet walrus
#

I see, the goof didn't put null defaults in there...

rose jackal
wet walrus
# 
    action_on_hold:
      name: on-hold
      description: select action to run when you hold I
      default: []
      selector:
        action:

like that.

rose jackal
#

I have tried the one from my link above, but with this one the automation isn't even triggered..

wet walrus
#

That trigger looks odd to me

#

Never mind, I guess that's a thing. I've never tried it.

#

The thing is with legacy mode you get a lot of null triggers. It's why they went to the other way. You usually have to screen those out with a template in the trigger statement.

rose jackal
#

Hmm I noticed something which is strange

wet walrus
#

I bet if you push the button a bunch of times it will hit at some point.
For instance, this is a trigger that I use for my cube sensor blueprint...

trigger:
- platform: state
  entity_id: !input 'remote'
condition:
  condition: template
  value_template: '{{ trigger.to_state.attributes.action in (''rotate_right'', ''rotate_left'',
    ''flip90'', ''flip180'', ''slide'', ''tap'', ''shake'', ''fall'') }}'

Adding a condition like this will toss null triggers and five you only valid ones.

rose jackal
#

action: off_press

#

This is in the mqtt topic

wet walrus
#

I noticed those in the device dexcription

rose jackal
#

but it should be off-press?

wet walrus
#

that's just another action, when you release the button

rose jackal
#

It has different names

#

off_press and off-press

wet walrus
#

Saw that somewhere as well, a device firmware / model change did that. You have to have the one that your device is sending

rose jackal
#

off_press is my action

#

with underscore instead of dash

#

I have to check if the action in the awesome HA blueprint is triggered with underscore or dash

# 
zigbee2mqtt:
      button_on_short: [on-press]
#

I think this is it

#

all the blueprints are listening for actions with dashes. And my actions changed from dashes (this is why it was working before) to underscores..

wet walrus
#

there you go!

#

Be sure to share that on the exchange so others will be helped if it's a fix.

rose jackal
#

I can confirm, this was the problem

rose jackal
#

And now i know why I have _ instead of -

#

It is indeed the legacy: false option. I was pretty sure that this was always there, but it seems that this was automatically added yesterday.