MQTT Broker implementation

[petrho 5]

2 minutes ago, 10der said:

no. now all coming from dev node.

5 min 

I should garb coffee and can draw flow for you

Now I remembered. Just use the server node and filter it with the device node

Edited November 24, 2018 by petrho

[10der 831]

yep, Sir!

[petrho 5]

Sorry for spamming you. Do you have support for the RGBW device? How can I for example send setW=128?

[10der 831]

 

Please login or register to see this code.

 

32 minutes ago, petrho said:

Sorry for spamming you. Do you have support for the RGBW device? How can I for example send setW=128?

 

look on flow RGBW label

 

Please login or register to see this code.

 

Edited November 24, 2018 by 10der

[petrho 5]

20 hours ago, 10der said:

 

Please login or register to see this code.

  

 

look on flow RGBW label

 

Please login or register to see this code.

  

Thanks for the example. If I just want to send in a value to set the White channel to 128 - how can I do that simple?

[10der 831]

3 hours ago, petrho said:

Thanks for the example. If I just want to send in a value to set the White channel to 128 - how can I do that simple?

Please login or register to see this code.

 

PS: look like a bug.  was designed for color # for white $ but I forget to add setColor command. Ok. will be fixed in the next version. now you may add "name" manually (attached)

[petrho 5]

Sometimes I got following message...

Please login or register to see this attachment.

[10der 831]

can you remove periodic resetting via "inject node" and check it again?

 

ha! stop

[petrho 5]

2 minutes ago, 10der said:

can you remove periodic resetting via "inject node" and check it again?

 

Did you mean the 60 min reset? If yes - there is no difference

[10der 831]

stop. I have checked. 

it fails new code with events triggering.

on it!

[petrho 5]

Just now, 10der said:

stop. I have checked. 

it fails new code with events triggering.

on it!

Yes - it’s related to events

[petrho 5]

Last days (last version?) I sometimes get ”Suspicious Login Attempts Prevented” without any known reason...

[10der 831]

@petrho not sure what red-node is the root issue here

Please login or register to see this image.

 

5 days uptime

[petrho 5]

I get the problem exact same time every night. 00.01

 

only thing I can suspect is that I am switch off a number of devices at same time. Can HC2 and the plugin handle that?

Edited November 30, 2018 by petrho

[10der 831]

3 hours ago, petrho said:

I get the problem exact same time every night. 00.01

so, if you sure what re-set - getting new devices is root issue here, you can simply confirm reproducing just now - just click inject right now and you should be locked by HC2. isn't it?

[petrho 5]

Tested to run everything manually (the reset runt also every 60 minutes) with no problem. Lets see what happened 00:01 tonight

 

Sorry - I got the problem when I runt the reset manually.

[petrho 5]

It’s now possible to reproduce it. It seems happen when I do many requests at same time. Like that turn off a couple of lights exatly same time and/or if a reset maybe is running in parallel.

Please login or register to see this attachment.

[petrho 5]

When modify like this it seems to be more stable (but not so practical)

Please login or register to see this attachment.

[petrho 5]

Hmm still same problems. I don’t know why...  

[10der 831]

@petrho can you stop flow. and look is the issue still here =)