I dont know why, but suddenly stopped work this compute. Probably with some update Pimatic?
https://github.com/wutu/pimatic-mqtt/blob/master/devices/mqtt-dimmer.coffee#L49
Returns NaN result. Does anyone know what is wrong?
Malfunctioning compute
I dont know why, but suddenly stopped work this compute. Probably with some update Pimatic?
https://github.com/wutu/pimatic-mqtt/blob/master/devices/mqtt-dimmer.coffee#L49
Returns NaN result. Does anyone know what is wrong?
Pimatic = Smart Home
@wutu said in Malfunctioning compute:
ddenly stopped work this compute. Probably with some update Pimatic?
Did you check the value of devlevel
and @resolution
before the statement is executed?
Set a breakpoint before the statement and check the the data with debugger.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
@mwittig said in Malfunctioning compute:
Did you check the value of devlevel and @resolution before the statement is executed?
Set a breakpoint before the statement and check the the data with debugger.
Of course I did. Both values come alright.
Pimatic = Smart Home
@wutu said in Malfunctioning compute:
Of course I did. Both values come alright.
Which values do you have devlevel
and @resolution
? I’ll try to reproduce the case
EDIT: Make sure @resolution isn’t null or 0 at some point
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
@mwittig said in Malfunctioning compute:
Which values do you have devlevel and @resolution? I’ll try to reproduce the case
@resolution for example 255
The device then sends back 0-255 on state topic
EDIT: Make sure @resolution isn’t null or 0 at some point
see above
Pimatic = Smart Home