1.3.0 and 400:Bad Request

jkandasa

@skywatch Can you check it on network response in the browser? also, check the MyController.log.
clearing cache resolves the issue some time.

UPDATE: Initially, I understand your query wrongly. I guess the problem with the range. Can you disable the ack for that gateway and check it?

skywatch

Range wasn't the issue as the relays still operated, just kept getting that damn pop-up message!

I have disabled ack in the gateway and node, no more pop-ups. But now I don't know for sure the status of the relays and so back to the old problem of 'is it off or is it on?'

As an aside, I have tracked some issues down to bad dupont cables from china - now soldering wires directly instead on new modules once the node works as intended....

Anything you can suggest to get ack working without errors?

jkandasa

@skywatch It is strange, that without ack it works for you and with ack is not working
can you post your gateway setting edit page? I want to see values for,

Ack enabled
Failed retry count
Ack wait time(Milliseconds)

skywatch

No problem....

Ack enabled - Ticked
Failed retry count - 7
Ack wait time(Milliseconds) - tried 2000 and 3500

Thanks for the help

jkandasa

@skywatch All the values look better. Ack wait time(Milliseconds) value 2000 is big enough.
Till now I didn't get any clue.

Can you enable DEBUG for the followings and send the mycontroller/logs/mycontroller.log log file?

  <logger level="DEBUG" name="org.mycontroller.standalone.provider" />
  <logger level="DEBUG" name="org.mycontroller.standalone.provider.mysensors" />

  <logger level="DEBUG" name="org.mycontroller.standalone.gateway" />
  <logger level="DEBUG" name="org.mycontroller.standalone.gateway.ethernet" />
  <logger level="DEBUG" name="org.mycontroller.standalone.gateway.mqtt" />
  <logger level="DEBUG" name="org.mycontroller.standalone.gateway.serial" />

skywatch

Of course!

Give me a few days as its the World Cup and amazingly England are still hanging in there

jkandasa

@skywatch Sure, enjoy! have a fun time

skywatch

@jkandasa I am sorry I didn't get back to this sooner, but as you know I have other issues taking my time.

So today I still get

I will add the debug and see what happens...But what is the message actually telling me? It seems that the message was sent OK and ack received, no?

jkandasa

@skywatch Message says, received acknowledgment
For this message should not throw 400 I hope we have some issue in the code. For good message, it says as bad.

skywatch

@jkandasa said in 1.3.0 and 400:Bad Request:

I hope we have some issue in the code. For good message, it says as bad.

That's what I thought. I am now using latest 1.4.0 snapshot FYI.

Trouble is that sometimes when this happens it resends the command. My amplifier only has one button that toggles the power on and off, no descrete commands. The result is the amp turns on and off and on and off and on and off (You get the idea and how annoying it is).

jkandasa

@skywatch can you send gateway raw message on this particular period(error occurred)?

skywatch

@jkandasa I will try and replicate this tonight/tomorrow and send you the log.

skywatch

@jkandasa Sorry, I completely forgot about this after the system crashed.

I will look into it again and send you the log......

skywatch

Sorry for the dumb question - but I can't think how to get the raw gateway message you want - Can you please give me a hint?

jkandasa

@skywatch np, this one help you, https://github.com/mycontroller-org/mycontroller/issues/473

1.3.0 and 400:Bad Request

0

587

529

3.4k