• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 1 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Solved] dimmer protocol kaku_dimmer does not react on dimmervalue
#1
Is there any change in the kaku_dimmer protocol?
I'm using latest nightly v7.0-214-g847bac2
Since update to rewrite backports I can't dim anymore to a specific dimmervalue using protocol kaku_dimmer.
Switching does work.
I'm using Intertechno ITL-250.
Sending ON-Code from state off is turning on the light from brightest value down to last used dimlevel (which is correct behaviour).
If I then send a new dimmervalue the receiver starts looping from bright to dark (which means it received a second ON-Code) instead of going to the dimlevel sent with pilight-send.
The dimlevel seems to be completely ignored by the protocoll code pilight sends (at least the receicer do not recognize it and thinks it's just another ON).
Any idea what could cause this?
 
Reply
#2
Can you try version 80a5ade?
 
Reply
#3
Is this version not installable via apt?
In cause of the segfault problem in 7.0-228-g5a40a80 I followed your recommendation, removed the manual compiled version 7.0-228 and installed 7.0-217 via apt, which solved the segfault error but still has the arctech_dimmer looping issue.

For some reason I couldn't find version 80a5ade via apt.
I used:
Code:
apt list pilight -a
Does this mean I have to purge 7.0-217 again and need to manually download and compile 80a5ade or is there a way via apt?

Do you see a chance for a fix for this issue together with the segfault fix found in 7.0-228-g5a40a80?
If so I would wait for the segfault fix and then testing further about this dimmer issue.
 
Reply
#4
Also what I found (on pilight-daemon version v7.0-217-ged2e1e3) is that when you try to turn on the dimmer via an url without an attached dimmer value the daemon crashes:

With something like this it crashes: http://10.0.0.15/control?device=Dimmer-Lamp&state=on

Using such a command on a non dimmer switch works fine without crashing.

Dimming works when appending a dimmer value, although the value will not be recognized, as described by apartmedia, and will just turn the cycling on:

If the lamp is off and you use something like this http://10.0.0.15/control?device=Dimmer-Lamp&state=on&dimlevel=15, it will turn on to the last dimmed state. Sending it again will start cycling through the various dimmer states. Sending it once more will stop the cycling.

In the log it looks like this: It just tries to reconnect but it won't work until I restart the daemon with service pilight restart:

Code:
[Sep 05 11:52:07:755740] pilight-daemon: DEBUG: broadcasted: {"message":{"id":100,"unit":0,"state":"opened"},"origin":"receiver","protocol":"arctech_contact","uuid":"0000-00-13-ef-f4132f","repeats":2}
[Sep 05 11:52:07:939166] pilight-daemon: DEBUG: possible arctech_dimmer protocol
[Sep 05 11:52:07:939336] pilight-daemon: DEBUG: recevied pulse length of 301
[Sep 05 11:52:07:939395] pilight-daemon: DEBUG: caught minimum # of repeats 3 of arctech_dimmer
[Sep 05 11:52:07:939466] pilight-daemon: DEBUG: called arctech_dimmer parseRaw()
[Sep 05 11:52:07:940655] pilight-daemon: DEBUG: broadcasted: {"message":{"id":100,"unit":0,"dimlevel":0,"state":"on"},"origin":"receiver","protocol":"arctech_dimmer","uuid":"0000-00-13-ef-f4132f","repeats":3}
[Sep 05 11:52:07:941726] pilight-daemon: DEBUG: possible arctech_contact protocol
[Sep 05 11:52:07:942898] pilight-daemon: DEBUG: recevied pulse length of 301
[Sep 05 11:52:07:944013] pilight-daemon: DEBUG: caught minimum # of repeats 3 of arctech_contact
[Sep 05 11:52:07:944211] pilight-daemon: DEBUG: called arctech_contact parseRaw()
[Sep 05 11:52:07:945424] pilight-daemon: DEBUG: broadcasted: {"message":{"id":100,"unit":0,"state":"opened"},"origin":"receiver","protocol":"arctech_contact","uuid":"0000-00-13-ef-f4132f","repeats":3}
[Sep 05 11:52:08:128747] pilight-daemon: DEBUG: possible arctech_dimmer protocol
[Sep 05 11:52:08:128899] pilight-daemon: DEBUG: recevied pulse length of 302
[Sep 05 11:52:08:128982] pilight-daemon: DEBUG: caught minimum # of repeats 4 of arctech_dimmer
[Sep 05 11:52:08:129041] pilight-daemon: DEBUG: called arctech_dimmer parseRaw()
[Sep 05 11:52:08:130239] pilight-daemon: DEBUG: broadcasted: {"message":{"id":100,"unit":0,"dimlevel":0,"state":"on"},"origin":"receiver","protocol":"arctech_dimmer","uuid":"0000-00-13-ef-f4132f","repeats":4}
[Sep 05 11:52:08:131285] pilight-daemon: DEBUG: possible arctech_contact protocol
[Sep 05 11:52:08:132434] pilight-daemon: DEBUG: recevied pulse length of 302
[Sep 05 11:52:08:133562] pilight-daemon: DEBUG: caught minimum # of repeats 4 of arctech_contact
[Sep 05 11:52:08:133763] pilight-daemon: DEBUG: called arctech_contact parseRaw()
[Sep 05 11:52:08:134985] pilight-daemon: DEBUG: broadcasted: {"message":{"id":100,"unit":0,"state":"opened"},"origin":"receiver","protocol":"arctech_contact","uuid":"0000-00-13-ef-f4132f","repeats":4}
[Sep 05 11:52:08:375996] pilight-daemon: DEBUG: ssdp sent search
[Sep 05 11:52:08:476671] pilight-daemon: NOTICE: no pilight ssdp connections found
[Sep 05 11:52:08:476896] pilight-daemon: NOTICE: connection to main pilight daemon lost
[Sep 05 11:52:08:476992] pilight-daemon: NOTICE: trying to reconnect...
[Sep 05 11:52:09:477714] pilight-daemon: DEBUG: ssdp sent search
[Sep 05 11:52:09:586655] pilight-daemon: NOTICE: no pilight ssdp connections found
[Sep 05 11:52:09:586919] pilight-daemon: NOTICE: connection to main pilight daemon lost
[Sep 05 11:52:09:587041] pilight-daemon: NOTICE: trying to reconnect...
[Sep 05 11:52:09:902710] pilight-daemon: DEBUG: cpu: 7.060881%
[Sep 05 11:52:10:587719] pilight-daemon: DEBUG: ssdp sent search
 
Reply
#5
@Lhonco please open separate issues for each one or else i can't follow it anymore.

@apartmedia GUI dimmer issue is not fixed in the 217 version. I'm aware of it.
 
Reply
#6
Do you maybe have a original remote control for these devices? That would help me figure what the original devices actually sent when trying to dim?

I will focus on this issue first.
 
Reply
#7
Hm, the problem with the original normal remote controls is, that they only provide sending ON and OFF codes. If the device receives another ON code while the actual state of the device is ON, it starts cycling through all dim levels until the next ON command is received and then stops at the current value.
So the normal remotes can not send a specific dimmer value with a button as far as I know. The dimmer value can only be reached by stopping an active dimmer loop with another ON command.
The same behavior is now triggered by pilight in the latest versions when trying to send concrete dimmer values via slider. They only send another ON command which trigger the dimming cycle.
So I think, the original remote codes will not be much of a help to sniff out codes for concrete dimmer values...
Or I'm wrong with this?
At least this seems to be the case for Intertechno devices, which I have in use. May be the original KlikAanKlikUit devices and remotes can help here but these are not available to buy at my location.
 
Reply
#8
Just wondering if there a no remote that can do that.
 
Reply
#9
Smile 
I was wondering too the first time, which was one of the reason I fell in love with this pilight feature...
 
Reply
#10
Do you have time to look for such a remote, instead of just wondering and falling in love with pilight.

A bit more on this issue. The latest pilight nightly receives and sends at the same time. So, when a dimmer code is sent, pilight will now also receive a dimmer command at the same time. BUT, the working dimmer command that is sent out, it not something we can parse when receiving. So i tried a different dimmer command that seems more logical but now sending doesn't work anymore.

This is also related to the webgui dimmer issues in another topic. In the old (working) behavior, sending worked, but pilight received the same command differently. So i want to know what the actual remote does.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  [SOLVED] Triggering generic_switch leads to segfault Ulrich.Arnold 19 1,765 10-23-2019, 09:03 AM
Last Post: Ulrich.Arnold
  regex mask for protocol options not working Niek 2 1,788 01-06-2019, 12:20 AM
Last Post: Niek
  Protocol options defined as JSON_ARRAY getting lost Niek 6 2,149 01-01-2019, 11:03 AM
Last Post: curlymo
  ][solved]Segfault when retrieving big chunked http message Niek 21 6,388 11-29-2018, 03:17 PM
Last Post: curlymo
  [Solved] config.json not updated Niek 6 1,666 12-31-2017, 03:19 PM
Last Post: curlymo
  [Solved] callback not executing when dns lookup fails Niek 1 792 10-08-2017, 11:44 AM
Last Post: curlymo
  [Solved] Rules switching state based on another device state not working apartmedia 6 2,625 09-27-2017, 01:41 PM
Last Post: apartmedia
  [Solved] connection to main pilight daemon lost TopdRob 20 4,733 09-17-2017, 04:30 PM
Last Post: curlymo
  [Solved] Webgui not working in IE Ulrich.Arnold 7 1,977 09-12-2017, 05:22 PM
Last Post: Ulrich.Arnold
  [Solved] Sunriseset v7 fails after update and gives negative values PPacman 7 1,822 09-06-2017, 06:25 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)