Author Topic: Bug: Danfoss LC13  (Read 280 times)

Offline cokeman

  • Full Member
  • ***
  • Posts: 114
  • Karma: +1/-0
Bug: Danfoss LC13
« on: September 11, 2018, 02:48:25 pm »
Hi

The Danfoss LC13 (and perhaps a lot other devices)
When you adjust the temperature and, then the device wakes up, it adjust. just like we want.

But....

You adjust, vera reloads, and then the device wakes up.... well there is no command to change temperature anymore :-(

I adjust 15 LC13 via scripts, and I often see a reload and then need to execute the script 2-3 times to get all adjusted.
Vera 3 in the summerhouse, Vera Plus at home
@Denmark

Offline Maegda

  • Customer Care
  • Global Moderator
  • Jr. Member
  • *****
  • Posts: 92
  • Karma: +2/-1
Re: Bug: Danfoss LC13
« Reply #1 on: September 12, 2018, 04:39:33 am »
Hello cokeman,

Why would Vera reload? Maybe we can find out from the logs, I sent you an email, could you reply so we may work on this?

Enjoy the day,
Vera Control, Ltd.  Smarter Home Control
support@getvera.com  +1 (866) 966-2272

Offline pit

  • Sr. Newbie
  • *
  • Posts: 44
  • Karma: +3/-0
Re: Bug: Danfoss LC13
« Reply #2 on: September 12, 2018, 10:17:20 am »
I use Popp POPE010101 (= Danfoss) and at the beginning I had similar strange problems with this device. Then I turned off polling (which was activated as default) and immediately the problems disappeared.

Offline cokeman

  • Full Member
  • ***
  • Posts: 114
  • Karma: +1/-0
Re: Bug: Danfoss LC13
« Reply #3 on: September 13, 2018, 02:45:08 pm »
Hi

Well, please do this test.

in gui, adjust temperature on 2 devices and then wake one up (Press temp down button on the device), and see that it will adjust.

Then reload the engine (Settings -> Z-wave settings -> advanced -> Reload engine)

wait until reload is complete and then wake up second device. when I do this, there is no command to change temperature.

 
Vera 3 in the summerhouse, Vera Plus at home
@Denmark

Offline pit

  • Sr. Newbie
  • *
  • Posts: 44
  • Karma: +3/-0
Re: Bug: Danfoss LC13
« Reply #4 on: September 14, 2018, 03:54:12 am »
I tried it with no problem.
For me your problem looks similar to my former problems. After some surveillance I noticed, that the real wakeup period of device and the wakeup period of the device noticed in vera were different. If vera and the device did not connect for a certain time, then the device seems to go in a "sleeping" state with a  long wakeup cycle. Then the device was not more reacheable from vera.

First I bypassed the problem with 5 min wakeup time - and so the device and vera met for setpoint sync all 10 min (! not all 5 min ! ). Then I realized, that the problem was caused by polling. After switch off polling (settings > Poll this node at most once every 0 sec) the wakeuptime in the device and in vera matched and all problems disappeared.

By the way: Normally I also use lua to set and watch the devices. I use "SetCurrentSetpoint".