pimatic-raspbee@0.1.0

---

New Version 0.1.0

Hints:

• During the first start error messages regarding properties may appear.
  Invalid config of device <.....> Property <...> is not a valid property
  These messages must be ignored. At the second restart, these messages no longer exist.
  The plugin performs an automatic transformation of the devices at the first start.

• I highly recommend to discover the sensors again.

more information in the README

CHANGELOG

[0.1.0]

Added

• a new groups device RaspBeeRGBCTGroup with ct and rgb #22
• a new RaspBeeSystem device which represents the deconz api
  • device and sensor discovery over pimatic #25
  • backup deconz api #26
  • send device configuration to deconz
• homekit support for hap plugin dimmer and RGB capabilities #30
• new action provider for dimming / all actions with transition time option
  Example: dim raspbee Light to 75 transition time 2s and set color rgb LightRGB to #FF0000 with transition time 10s
• new predicate provide: recieved from Switch1 event “2001”

Changed

• new RaspBeeMultiSensor device which supports all sensor types
  The new sensor device has been completely refactored and supports all sensor types now #23.
  It also replaces all old sensor devices. However, these are still available for downward compatibility.

Fixed

• #28
• #29

Deprecated

• Following device types are now deprecated but still usable
  • RaspBeeMotionSensor
  • RaspBeeContactSensor
  • RaspBeeLightSensor
  • RaspBeeSwitchSensor
  • RaspBeeWaterSensor
  • RaspBeeDimmerGroup

Security

• Update all package dependencies
  (node 4 support still preserved)

@Kosta,
It looks like a very nice upgrade, thanks.
I updated the plugin and followed your instructions.

Some test results. After a few restarts and devices discovers, i still got the following issues:

1. the following RASPBEE error messages when Pimatic starts
   -ESOCKETTIMEDOUT
   -Connection could not be establised
   -websocket keep alive error, try to reconnect
   In the last version I got only the “websocket keep alive …” error
   But also this time after startup the plugin works!

2. The presence dot stays open, when motion is detected.

got a repeating error

error [pimatic]: An uncaught exception occurred: TypeError: Cannot read property 'message' of undefined
    at WebSocket.<anonymous> (/home/pimatic-app/node_modules/pimatic-raspbee/raspbee-connector.coffee:67:50)
    at WebSocket.emit (events.js:198:13)
    at ClientRequest.req.on (/home/pimatic-app/node_modules/ws/lib/websocket.js:535:10)
    at ClientRequest.emit (events.js:198:13)
    at Socket.socketErrorListener (_http_client.js:392:9)
    at Socket.emit (events.js:198:13)
    at Socket.emit (/home/pimatic-app/node_modules/pimatic/startup.coffee:64:24)
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
 This is most probably a bug in pimatic or in a module, please report it!

fresh setup of pimatic 0.9.50 and your plugin, latest version of deconz docker container. api-key rquest works but this error coours.

edit: every 30 seconds

Also released the according update for pimatic-hap: https://forum.pimatic.org/topic/4683/pimatic-hap-0-12-0

@bertreb

1. the new version has more debug output. now the reason for the connection error is logged.
2. i have the same issue, i will check it.

@quotschmacher
the exception is a bug, i will fix that.
but the exception occurs during error handling when the connection to deconz does not work.
the root cause is a connection problem.

new version:

pimatic-raspbee@0.1.1

Clear BROWSER Cache !

CHANGELOG

[0.1.1]

added

• RuleManager: RGBCT now also color changeable

Fixed

• #31 Motion on GUI not visable
• #32 Contact sensor was the other way round
• RuleManager Error - RaspBeeSystem not a buttondevice
• fix the exception that occurs during error handling when the connection to deconz does not work.

Changed

• Default reset timeout for switch sensors now 1 sec. (100 ms previously)

Thanks for the fast update!
The ‘dot’ is now working.
The 3 raspbee error messages on startup are still there, but after a reconnect retry and few seconds the connection is established.

@kosta said in pimatic-raspbee@0.1.0:

but the exception occurs during error handling when the connection to deconz does not work.
the root cause is a connection problem.

you are right - my fault