mancioshell / risco-mqtt-home-assistant

Node Risco Mqtt client for Home Assistant
MIT License
7 stars 7 forks source link

With several partitions the changes were not detected. #3

Open d4icon opened 4 years ago

d4icon commented 4 years ago

Hi, Congratulations on the plugin.

I have a problem, and I think it's a code issue, but see if you can help me.

I am doing several tests and I have realized that with several partitions, it doesn't matter what changes, that partition 0 is always changed.

Could you help me?

thanks

mancioshell commented 4 years ago

Could you explain to me, more in detail the issue? It could be a potential issue because unfortunately i can't test multipartitons in my home environment.

d4icon commented 4 years ago

Yes, of course, I give you more details.

For example, when I launch an armed for partition 1 or 2:

In console: received change state command ARM_AWAY on topic riscopanel / alarm / 2 / set in partition 2

changed state to armed_home on partiton 2 published alarm status armed_away on partition 0 published alarm status disarmed on partition 1 published alarm status disarmed on partition 2

Same for partition 1

The state does maintain it directly, but nothing more. It doesn't matter which partition you choose to always change the 0.

Tell me what information would be most helpful.

I would like to try to visualize the API call from the browser console or similar, but nothing appears, and I don't know how I could do it. (to confirm 100% that it is always sent on 0 ... or not)

thanks

d4icon commented 4 years ago

First of all, I do not know nodeJS, but is it possible that the PartitionId is missing here ???? Anotación 2020-03-01 001257