@Daniel-Böber did you clear the cache?
-
New pimatic tradfri plugin / IKEA Smart Lights
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@leader21 that fixed it. I did a new tab in inkonito mode an it works. Will go on with testing, thanks!
-
nice to hear! sometimes it can be that easy
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
Compared to the “old” interface in my dashboard the new one looks much smarter, thanks
-
Perfect … the error with the ramup could be ignored… and I’m still working on improvements. Unfortunately my tests to integrate the remote control or the dimmer independent in to pimatic are so far not successful. The gateway sends no status messages from such devices over an observation channel. Currently I’m implementing a status display over bulb connections, some action provider for the color bulbs and a smooth change of brightness and color.
-
BTW it is possible to control the color temperature stepless like the brightness with “homee” smart home system over zigbee. But I have seen no way to do this with the original ikea gateway. litte bit funny
-
Yes I know. Over the gateway it’s also possible to change the color stepless. I’m working on a algorithm from a slider value to x,y color values. The gateway accepts only the 3 fix RGB values, but all x,y values for temperature.
-
would be great if group mood would work. Have 9 Lamps in one room, better to create scenes with the tradfri app
is group mood on your list?
-
Yes. For the sake of completeness I will implement also group moods/scenes. but I prefer one configuration interface -> pimatic
-
@kosta said in New pimatic tradfri plugin / IKEA Smart Lights:
Please be patient, the new release in some days will have a connection test and more debug output.
Hello
I do not know what to do anymore. I still can not control the tradfri gateway (LED bulb E26 1000 lumen).
We reinstalled the pimatic (clean installation) and added only the tradfri plugin and ping plugin.Data from the phone application
Gateway version: 1.1.0015
Remote control version: 1.1.1.1-5.7.2.0info [pimatic]: Device discovered: pimatic-ping: Presence of GW-B072...... info [pimatic]: Device discovered: pimatic-ping: Presence of pi info [pimatic]: Device discovered: pimatic-ping: Presence of router.asus.com info [pimatic]: pimatic-tradfri: scanning for tradfri devices finished info [pimatic]: pimatic-tradfri: gateway not reachable info [pimatic]: pimatic-tradfri: scanning for tradfri devices info [pimatic]: Starting device discovery for 20000ms. debug [pimatic-tradfri]: Try to connect to Tradfri debug [pimatic-tradfri]: ...connection error! info [pimatic]: Listening for HTTP-request on port 80... info [pimatic-mobile-frontend]: rendering html finished info [pimatic-mobile-frontend]: rendering html info [pimatic-mobile-frontend]: packing static assets finished info [pimatic-mobile-frontend]: packing static assets info [pimatic]: New device "Tradfri Dimmer"... info [pimatic]: New device "Tradfri Hub"... info [pimatic-tradfri]: Plugin initialization... info [pimatic-cron]: the time is: Sun Jun 18 2017 17:31:31 GMT+0300 (EEST) info [pimatic]: Loading plugin: "pimatic-ping" (0.9.5) error [pimatic]: Invalid config of pimatic-tradfri: Missing property "rampup" info [pimatic]: Loading plugin: "pimatic-tradfri" (0.1.8) info [pimatic]: Loading plugin: "pimatic-mobile-frontend" (0.9.11) info [pimatic]: Loading plugin: "pimatic-cron" (0.8.8) info [pimatic,ppm]: 2.15.12 { "plugin": "tradfri", "secID": "hwaqPexxxxxxxxx", "hubIP": "192.168.1.208", "debug": true }, { "debug": true, "plugin": "ping", "active": true } { "ntpserver": "192.168.1.208", "id": "tradfri-hub", "name": "Tradfri Hub", "class": "TradfriHub" }, { "address": 65537, "id": "tradfri-dimmer", "name": "Tradfri Dimmer", "class": "TradfriDimmer" }
Thanks in advance for the advice.
-
@Andi-Tudor
hey Andi,please run pimatic in console mode:
cd /path-to-pimatic/ sudo node_modules/pimatic/pimatic.js
then you should get this
17:13:10.043 2017-06-18 Sunday 17:13:10.713 [pimatic] Starting pimatic version 0.9.39 17:13:10.743 [pimatic] settings.debug is true, showing debug output for pimatic core. 17:13:10.992 [pimatic, ppm] 2.15.12 17:13:10.999 [pimatic] Loading plugin: "pimatic-cron" (0.8.8) 17:13:11.062 [pimatic] Loading plugin: "pimatic-mobile-frontend" (0.9.11) 17:13:11.146 [pimatic] Loading plugin: "pimatic-tradfri" (0.1.8) 17:13:11.147 [pimatic] debug is true in plugin config, showing debug output for pimatic-tradfri. 17:13:11.168 [pimatic] Invalid config of pimatic-tradfri: Missing property "rampup" 17:13:11.169 [pimatic-cron] the time is: Sun Jun 18 2017 17:13:11 GMT+0200 (CEST) 17:13:11.171 [pimatic-tradfri] Plugin initialization... 17:13:11.171 [pimatic-tradfri] tradfri cfg: Gateway IP: 10.0.10.107 KEY: SECRETKEY 17:13:11.275 [pimatic-mobile-frontend] packing static assets 17:13:11.420 [pimatic-mobile-frontend] packing static assets finished 17:13:11.421 [pimatic-mobile-frontend] rendering html 17:13:12.294 [pimatic-mobile-frontend] rendering html finished 17:13:12.300 [pimatic] Listening for HTTP-request on port 333... 17:13:21.199 [pimatic-tradfri] Try to connect to Tradfri step() beginning step() beginning step() beginning step() beginning step() beginning step() beginning step() state SERVER_FINISHED --> HANDSHAKE_OVER. 17:13:23.486 [pimatic-tradfri] Gateway online - Firmware: 1.1.0015 17:13:23.487 [pimatic-tradfri] Tradfri plugin ready
If you get only one “step() beginning” message there is a network conection problem.
If you get more but the “HANDSHAKE_OVER” message is missing. Please check the PreSharedKey. -
pi@pi ~/pimatic-app $ sudo node_modules/pimatic/pimatic.js 18:47:35.115 2017-06-18 Sunday 18:47:44.395 [pimatic] Starting pimatic version 0.9.39 18:47:44.812 [pimatic] settings.debug is true, showing debug output for pimatic core. 18:47:48.106 [pimatic, ppm] 2.15.12 18:47:48.187 [pimatic] Loading plugin: "pimatic-cron" (0.8.8) 18:47:48.967 [pimatic] Loading plugin: "pimatic-mobile-frontend" (0.9.11) 18:47:50.114 [pimatic] Loading plugin: "pimatic-tradfri" (0.1.8) 18:47:50.118 [pimatic] debug is true in plugin config, showing debug output for pimatic-tradfri. 18:47:50.479 [pimatic] Invalid config of pimatic-tradfri: Missing property "rampup" 18:47:50.494 [pimatic] Loading plugin: "pimatic-ping" (0.9.5) 18:47:50.498 [pimatic] debug is true in plugin config, showing debug output for pimatic-ping. 18:47:50.581 [pimatic-cron] the time is: Sun Jun 18 2017 18:47:50 GMT+0300 (EEST) 18:47:50.597 [pimatic-tradfri] Plugin initialization... 18:47:50.602 [pimatic-tradfri] tradfri cfg: Gateway IP: 192.168.1.208 KEY: hwaqPec........ 18:47:51.229 [pimatic] New device "Tradfri Hub"... 18:47:51.288 [pimatic] New device "Tradfri Dimmer"... 18:47:51.759 [pimatic-mobile-frontend] packing static assets 18:47:53.943 [pimatic-mobile-frontend] packing static assets finished 18:47:53.958 [pimatic-mobile-frontend] rendering html 18:48:08.115 [pimatic-mobile-frontend] rendering html finished 18:48:08.190 [pimatic] Listening for HTTP-request on port 80... 18:48:08.197 [pimatic-tradfri] Try to connect to Tradfri step() beginning step() beginning step() beginning step() beginning step() beginning 18:48:18.260 [pimatic-tradfri] ...connection error! 18:48:18.268 [pimatic-tradfri] Try to connect to Tradfri step() beginning step() beginning step() beginning
-
This looks like an SSL error. The key is really ok?
I get exactly the same error, if the psk is different.
Maybe a typo with O / 0 or 1 / l -
I am ashamed. It’s my shame. I confused “I” with “1”.
I apologize for your lost time. I’m very very sorry.
Plugin works very well.
Once again I thank you for your work. -
@Andi-Tudor You are welcome!
And some new features will come soon…
-
I have release a new version. 0.1.9
Features
- Scenes/Moods
- Stepless light temperature change with new slider device
- New device option: transition time for smooth changes
- Action provider for all features (set color…)
- Presence of lights
- GUI optimization
The old buttons device is already available but
you should rescan the devices and change it with the new slider device.You should also clean the browser cache after update.
Hint: If you have two pimatic devices for the same bulb, only one of them is observing external changes.
@Felix-Haverkamp : moods are now available
-
@kosta Thank you for updating. For me everything works well.
-
@kosta , Very nice!
I updated the plugin and did get an error;19:43:38.810 [pimatic] error: A uncaught exception occurred: TypeError: Cannot read property 'send' of null 19:43:38.810 [pimatic] error:> at DtlsClientSocket.dgramSocket.once.send (/home/pi/pimatic-app/node_modules/pimatic-tradfri/node_modules/tradfri-coapdtls/node_modules/node-mbed-dtls/client_socket.js:63:22) 19:43:38.810 [pimatic] error:> at RetrySend._send (/home/pi/pimatic-app/node_modules/pimatic-tradfri/node_modules/tradfri-coapdtls/lib/retry_send.js:37:14) 19:43:38.810 [pimatic] error:> at null.RetrySend._bOff [as _onTimeout] (/home/pi/pimatic-app/node_modules/pimatic-tradfri/node_modules/tradfri-coapdtls/lib/retry_send.js:29:10) 19:43:38.810 [pimatic] error:> at Timer.listOnTimeout (timers.js:92:15) 19:43:38.810 [pimatic] error:> This is most probably a bug in pimatic or in a module, please report it! 19:43:38.813 [pimatic] warn: Keeping pimatic alive, but could be in an undefined state, please restart pimatic as soon as possible!
Did another restart of pimatic and it started up without any errors.
Time to get more Tradfri bulbs
Question;
Does the Tradfri hub do a re-transmit if it doesn’t get an “ACK” from the bulb ? Or is that something the tradfri plugin can do? -
I had the same error one time in my production system. The ssl library which i use is timing sensitiv.
I’m working on a resolution of this problem.The Plugin sends a change request 3 times. If it isn’t successfull, the gateway is marked as down. After that, the
plugin makes a cleanup of the ssl-connection to the hub and trys each 10 secounds a full re-establish of the connection.The Hub always reponse with an ACK if the request ist accepted,
and try to send the change to the bulb. I’m not shure how often. But if the bulb is not reachable, the hub send some time later an observing message which marks the bulb down. And the plugin shows the bulb as offline.
If the Bulb is reachable the hub send the new status over the observing channel to the plugin and the status is refreshed. -
Check, thanks!