• 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:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
pilight-receive with intertechno ITZ-500 remote control
#1
Hi everybody!

I just bought the remote control ITZ-500 from intertechno for my intertechno cmr-500 switches.
To my big surprise I didn't see any telegram of this remote control with pilight-receive, when I tried to find out the protocol. Although I see some telegrams of other devices.
But I can switch the emr-500 switches with pilight, because I tried it out with pilight-send (intertechno_old protocol). 
Can someone please tell me if I am doing something wrong?

The emr-500 switches are used for my roller shutters. Unfortunately I can't stop them in the web-gui, because they are shown as normal switches there. Is there a way to stop them by sending the same command twice with the gui? At the moment I just can open or close them until they reach the end-points.

Best regards,
Pik
 
Reply
#2
Hi,
the ITZ 500 Remote has an encoder wheel, right?
I have one CMR 500. I think the CMR 500 is not fully supported by pilight!
If you want to have this +/- toggles in the WebGui you have to take the Kaku_screen_old protokoll (same as intertechno_screen_old ??)
The problem is, for any reason kaku_screen_old does not work with CMR 500Confused
(There already is a Thread in this forum.)

So you have to take kaku_switch_old. And there are no single buttons in the WebGui Angry

Workarounds:

1. Use the iPhone app (or android, but I dont know the name) "piLightControll". There you can start and stop your shutters without problems.

2. iPhone only: Use Homebridge for the Raspberry and create a pilight as a homekit device. And than a custom scene.

3. replace all CMR 500 with ITL-500. The funktion is the same, but this are newer switches. They are teachable and worked very nice with kaku_screen and kaku_switch. (but xxx_screen protokolls are not compatible with homebridge Unsure )

 
Reply
#3
The issue is caused by the fact that as a standard:
- the GUI interface is currently not yet supporting a third STOP button,
and
- the required JSON object is not implemented in the corresponding screen protocol driver.
 
Reply
#4
Thank you for your answers.

I will try the suggested workarounds.

@wo_rasp:
I don't need a stop button in the web-gui. It would be enough to send the previously send command again. At the moment I can just toggle between on and off.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight-control TML 13 272 Yesterday, 07:51 AM
Last Post: curlymo
  Control Rules by Web GUI scootermacro 1 89 05-10-2020, 09:30 AM
Last Post: curlymo
  API Requests by HTTP from other devices fore use in pilight scootermacro 2 136 05-10-2020, 08:19 AM
Last Post: scootermacro
  Can't send or receive on Raspberry Pi Zero W ChristophH 12 442 04-09-2020, 06:34 PM
Last Post: curlymo
  pilight-send seems successful but doesn't actually send RF signal ayeyebrazov 37 1,967 03-31-2020, 01:02 PM
Last Post: curlymo
  pilight 8.1.5 not working on Raspberry pi after reboot beejayf 4 481 03-08-2020, 12:14 AM
Last Post: beejayf
  pilight cpu usage possibly associated with noticeable sluggishness? hepcat72 4 509 01-28-2020, 08:02 PM
Last Post: hepcat72
  apt.pilight.org stable Release' is not signed. thomasol 2 630 01-23-2020, 11:34 PM
Last Post: thomasol
  pilight and SIGNALduino cc1101 Caleus 0 424 01-19-2020, 09:13 AM
Last Post: Caleus
  filter stopped working after update to pilight 8.1.5 zlin50 19 1,299 01-03-2020, 02:15 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)