pimatic 0.9.30/0.9.31 crashes on mqttDimmer

---

Hi guys,

I’m fairly new to pimatic, coming from openhab2.

All my devices (MAX!, homematic, Hue, EnOcean and espeasy) are communicating via mqtt. For Max!, homematic and Hue I use homegear with the mqtt function. The espeasy sensors talk mqtt themself and my Eltako FUD61-EnOcean-Dimmer (wzdecke) ist connected via FHEM and their mqttBridge.

The Dimmer has 4 topics in mqtt:
sensor/wzdecke/dim for the dimmer state
sensor/wzdecke/dim/set to set the dimmer
sensor/wzdecke/onoff for the on/off state and
sensor/wzdecke/onoff/set to set on/off

I use the mqtt-plugin which obviously works with my broker (moquitto). I can switch the Dimmer while using the onoff topic and the state gets displayed correctly:

{
  "topic": "sensor/wzdecke/onoff/set",
  "onMessage": "on",
  "offMessage": "off",
  "id": "lampe-decke-onoff",
  "name": "Lampe Decke An/Aus",
  "class": "MqttSwitch",
  "stateTopic": "sensor/wzdecke/onoff"
}

The problem I have is with the dimming function:

{
  "topic": "sensor/wzdecke/dim/set",
  "resolution": 101,
  "id": "lampe-decke",
  "name": "Lampe Decke",
  "class": "MqttDimmer",
  "stateTopic": "sensor/wzdecke/dim"
}

I’ve used the resolution of 101 as stated in the mqtt-plugin readme as the dimmer wants a 0-100 (percent) input. The current state is on the given stateTopic. Sadly pimatic crashed as soon as I set the Dimmer:

21:57:30.988 [pimatic] A uncaught exception occured: AssertionError: level <= 100
21:57:30.988 [pimatic]>    at MqttDimmer.DimmerActuator._setDimlevel (/home/pi/pimatic-app/node_modules/pimatic/lib/devices.coffee:360:7)
21:57:30.988 [pimatic]>    at MqttDimmer._setDimlevel (/home/pi/pimatic-app/node_modules/pimatic/lib/devices.coffee:1:1)
21:57:30.988 [pimatic]>    at MqttClient.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-mqtt/devices/mqtt-dimmer.coffee:27:16)
21:57:30.988 [pimatic]>    at emitThree (events.js:102:20)
21:57:30.988 [pimatic]>    at MqttClient.emit (events.js:175:7)
21:57:30.988 [pimatic]>    at MqttClient._handlePublish (/home/pi/pimatic-app/node_modules/pimatic-mqtt/node_modules/mqtt/lib/client.js:770:12)
21:57:30.988 [pimatic]>    at MqttClient._handlePacket (/home/pi/pimatic-app/node_modules/pimatic-mqtt/node_modules/mqtt/lib/client.js:277:12)
21:57:30.988 [pimatic]>    at process (/home/pi/pimatic-app/node_modules/pimatic-mqtt/node_modules/mqtt/lib/client.js:233:12)
21:57:30.988 [pimatic]>    at Writable.writable._write (/home/pi/pimatic-app/node_modules/pimatic-mqtt/node_modules/mqtt/lib/client.js:243:5)
21:57:30.988 [pimatic]>    at doWrite (/home/pi/pimatic-app/node_modules/pimatic-mqtt/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:237:10)
21:57:30.988 [pimatic]>    at writeOrBuffer (/home/pi/pimatic-app/node_modules/pimatic-mqtt/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:227:5)
21:57:30.988 [pimatic]>    at Writable.write (/home/pi/pimatic-app/node_modules/pimatic-mqtt/node_modules/mqtt/node_modules/readable-stream/lib/_stream_writable.js:194:11)
21:57:30.988 [pimatic]>    at Socket.ondata (_stream_readable.js:542:20)
21:57:30.988 [pimatic]>    at emitOne (events.js:77:13)
21:57:30.988 [pimatic]>    at Socket.emit (events.js:169:7)
21:57:30.988 [pimatic]>    at Socket.emit (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:63:24)
21:57:30.988 [pimatic]>    at readableAddChunk (_stream_readable.js:153:18)
21:57:30.988 [pimatic]>    at Socket.Readable.push (_stream_readable.js:111:10)
21:57:30.988 [pimatic]>    at TCP.onread (net.js:536:20)
21:57:30.988 [pimatic]> This is most probably a bug in pimatic or in a module, please report it!
21:57:31.006 [pimatic] shutting pimatic down...
/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:98
          return framework.destroy().then(function() {
                 ^

ReferenceError: framework is not defined
    at process.uncaughtException (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:85:9)
    at emitOne (events.js:77:13)
    at process.emit (events.js:169:7)
    at process._fatalException (node.js:224:26)

If I don’t use a stateTopic it won’t crash but I can’t see my dimmer state, on/off is displayed correctly. Pimatic is running on a Raspberry Pi 3 with Raspbian Jessie and node version v4.4.7

Maybe someone could point me out what I did wrong.

Thank you,
p

nice to see you here
as said in the chat, i cannot help directly but maybe @wutu or @mwittig have a clue?
i am interested, what are the reasons for you to come over to pimatic?

Hi @leader21,

thanks for the warm welcome.

Mostly because I’m searching for a good alternative to openhab. OH2 is, in my oppinion, far from production ready and OH1 develeopment stands still.
As I see mqtt as the future for IOT communication I’ve tried to connect Pimatic and ended in this thread
I’m trying this at home to learn as much as I can.

Cheers,
p

I’ve tested it again with 0.9.31 and the problem still persists. Just for info

@pmayer I don’t think the error is cause by the recent pimatic updates.

The error message is triggered by an assertion on an invalid dimlevel value. https://github.com/pimatic/pimatic/blob/master/lib/devices.coffee#L360

May be @wutu can help on this. Are you sure resolution has to be set to 101? What is the range supported by the dimmer in question? I guess it is either 100 or 256. As far as I can see the Eltako Dimmer FUD 61 uses a percentage dim value. So, resolution should be 100

Hi @mwittig,

thanks for your answer. I’ve tried with resolution 100 and 99 but got the same error. The 101 comes from the readme:

Resolution of this dimmer. For percent set 101.

The FUD61 want’s a percent Value from 0-100 - you are absolutely right on that.

Cheers,
p

EDIT:
I have debugged this further. Propably it was late yesterday… sorry for that.
The error occurs if I use the “on/off” MqttSwitch, which will put the FUD to 100 percent. This is reflected in the state topic. Also the error will occur when I pull the MqttDimmer to the far right.

In mqtt this is reflected in the state topic:
http://imgur.com/MsvfaWi

I’ve now set dimValueOn to last in the FHEM-EnOcean Config so on switching the FUD on it will be back at the last dimmed value. If this is not 100% the error won’t occur.

May

Hello, sorry for the delayed reactions, I was on vacation.
This bug causes bad rounding. Tonight will be a revised version.

BTW. 101 because:
8bit = 0-255 = 256 steps
12bit = 0-4095 = 4096 steps
% = 0-100 = 101 Steps

I wanted to keep it as open as possible. You can therefore configure any number of step.

@pmayer Hey, fixed in version 0.9.1.

Hey,

thank you - I will try (hopefully) this evening and give you feedback.

Cheers!

Hey @wutu,

I’ve tested it and it worked flawlessly.
Thank you!

so long,
p