• 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
["SOLVED"] Not able to control intertechno ITR-1500
#1
Hello everyone,

I try to control the intertechno IT-1500 with pilight. I already read the remote signal by using pilight-receive and adjusted the config file. Now I try to switch the power sockets with the webgui and with pilight-send but in both cases nothing happens. pilight-receive shows the actions, but just the "origin": "sender"-entry. That's why I tested the functionality with 433Utils. Sender and receiver seem to work correct. I also tried to send raw code. A success was the following command.


Code:
pilight-send -p raw -c "302 906 302 906 302 906 1208 302 302 906 302
906 302 906 1208 302 302 906 302 906 302 906 1208 302 302 906 302 906
302 906 1208 302 302 906 302 906 302 906 906 302 302 906 1208 302 302
906 302 906 302 10268"

By executing this line pilight-receive shows some entries with "origin": "receiver". So the setup kind of works with pilight I guess.

I would be grateful for any kind of help and advice.
 
Reply
#2
Can you post the pilight-receive output you are getting?
 
Reply
#3
When I use the remote control (ITT-1500) for switching it on and off pilight-receive does output

(on)

Code:
{
       "message": {
               "id": 26738834,
               "unit": 0,
               "state": "on"
       },
       "origin": "receiver",
       "protocol": "arctech_switch",
       "uuid": "0000-74-da-38-618eb4",
       "repeats": 1
}
{
       "message": {
               "id": 26738834,
               "unit": 0,
               "state": "up"
       },
       "origin": "receiver",
       "protocol": "arctech_screen",
       "uuid": "0000-74-da-38-618eb4",
       "repeats": 1
}


(off)
Code:
{
       "message": {
               "id": 26738834,
               "unit": 0,
               "state": "off"
       },
       "origin": "receiver",
       "protocol": "arctech_switch",
       "uuid": "0000-74-da-38-618eb4",
       "repeats": 1
}
{
       "message": {
               "id": 26738834,
               "unit": 0,
               "state": "down"
       },
       "origin": "receiver",
       "protocol": "arctech_screen",
       "uuid": "0000-74-da-38-618eb4",
       "repeats": 1
}
{
       "message": {
               "id": 26738834,
               "unit": 0,
               "state": "closed"
       },
       "origin": "receiver",
       "protocol": "arctech_contact",
       "uuid": "0000-74-da-38-618eb4",
       "repeats": 1
}




That is why I changed the config file (I also tried different protocols) to 

Code:
{
       "devices": {
               "Switch1": {
                       "protocol": [ "kaku_switch" ],
                       "id": [{
                               "id": 26738834,
                               "unit": 0
                       }],
                       "state": "off"
               }
       },
       "rules": {},
       "gui": {
               "Switch1": {
                       "name": "Switch Nr 1",
                       "group": [ "MeineSwitches" ],
                       "media": [ "all" ]
               }
       },
       "settings": {
               "log-level": 6,
               "pid-file": "/var/run/pilight.pid",
               "log-file": "/var/log/pilight.log",
               "webserver-enable": 1,
               "webserver-root": "/usr/local/share/pilight/webgui",
               "webserver-http-port": 5001,
               "webserver-https-port": 5002,
               "webserver-cache": 1,
               "gpio-platform": "raspberrypi2"
       },
       "hardware": {
               "433gpio": {
                       "sender": 0,
                       "receiver": 1
               }
       },
       "registry": {
               "webserver": {
                       "ssl": {
                               "certificate": {
                                       "secure": 0,
                                       "location": "/etc/pilight/pilight.pem"
                               }
                       }
               },
               "pilight": {
                       "version": {
                               "current": "8.1.2"
                       }
               }
       }
}


When I now use the pilight webgui for switching pilight-receive does output

Code:
{
       "origin": "sender",
       "protocol": "arctech_switch",
       "message": {
               "id": 26738834,
               "unit": 0,
               "state": "on"
       },
       "repeat": 1,
       "uuid": "0000-74-da-38-618eb4"
}
{
       "origin": "sender",
       "protocol": "arctech_switch",
       "message": {
               "id": 26738834,
               "unit": 0,
               "state": "off"
       },
       "repeat": 1,
       "uuid": "0000-74-da-38-618eb4"
}


With

Code:
pilight-send -p kaku_switch -i 26738834 -u 0 --on
I get

Code:
{
       "origin": "sender",
       "protocol": "arctech_switch",
       "message": {
               "id": 26738834,
               "unit": 0,
               "state": "on"
       },
       "repeat": 1,
       "uuid": "0000-74-da-38-618eb4"
}


And with

Code:
pilight-send -p kaku_switch -i 26738834 -u 0 --off
I get

Code:
{
       "origin": "sender",
       "protocol": "arctech_switch",
       "message": {
               "id": 26738834,
               "unit": 0,
               "state": "off"
       },
       "repeat": 1,
       "uuid": "0000-74-da-38-618eb4"
}


While

Code:
pilight-send -p raw -c "302 906 302 906 302 906 1208 302 302 906 302
906 302 906 1208 302 302 906 302 906 302 906 1208 302 302 906 302 906
302 906 1208 302 302 906 302 906 302 906 906 302 302 906 1208 302 302
906 302 906 302 10268"


does

Code:
{
       "message": {
               "systemcode": 21,
               "unitcode": 10,
               "state": "off"
       },
       "origin": "receiver",
       "protocol": "pollin",
       "uuid": "0000-74-da-38-618eb4",
       "repeats": 1
}
{
       "message": {
               "unitcode": 768955,
               "state": "opened"
       },
       "origin": "receiver",
       "protocol": "ev1527",
       "uuid": "0000-74-da-38-618eb4",
       "repeats": 1
}
{
       "message": {
               "systemcode": 21,
               "unitcode": 10,
               "state": "off"
       },
       "origin": "receiver",
       "protocol": "elro_800_switch",
       "uuid": "0000-74-da-38-618eb4",
       "repeats": 1
}
{
       "message": {
               "systemcode": 21,
               "unitcode": 10,
               "state": "closed"
       },
       "origin": "receiver",
       "protocol": "elro_800_contact",
       "uuid": "0000-74-da-38-618eb4",
       "repeats": 1
}
 
Reply
#4
Can you try letting the device learn the codes sent by pilight?
 
Reply
#5
I tried, but I didn't succeed.
 
Reply
#6
The raw codes you are sending can't belong to the new kaku switches, because those have a pulse stream length of 132, while your raw code is 50 pulses long.

Can you post the output of pilight-debug while pressing any button of the remote?
 
Reply
#7
Sorry, I should have mentioned that the raw code should only show that the setup works in principle. I know that it does not belong to my switches.

pilight-debug does output quite a lot even when i do not press any button. Maybe because of someone else using this frequency or because of measurement noise? When I press the on-button on the remote I get entries like

Code:
--[RESULTS]--

time:           Sun Sep 23 16:19:40 2018
hardware:       433gpio
pulse:          4
rawlen:         131
pulselen:       315

Raw code:
509 2522 237 325 237 1390 257 1361 251 332 272 1359 249 330 242 321 237 1387 249 319 243 1392 240 1372 240 331 240 1396 231 328 240 322 240 1400 243 325 237 1392 247 322 239 1391 242 319 243 1385 249 658 1316 237 325 234 1448 182 326 241 1392 240 322 243 1400 227 324 237 1416 231 327 236 1386 332 246 234 1395 242 1385 240 332 237 330 233 1398 234 391 164 1412 233 1385 239 329 238 325 238 1384 253 320 239 1403 244 1382 270 310 238 320 240 1386 245 326 249 1378 243 1379 248 370 238 290 237 1391 238 327 298 1329 242 329 232 1389 243 330 234 1392 237 10736
--[RESULTS]--

time:           Sun Sep 23 16:19:40 2018
hardware:       433gpio
pulse:          4
rawlen:         132
pulselen:       316

Raw code:
498 2506 242 324 237 1383 248 1375 251 331 239 1402 224 332 237 319 243 1404 228 325 241 1382 248 1375 290 300 230 1381 244 329 241 344 211 1399 247 319 244 1383 252 318 239 1393 243 323 240 1386 246 322 241 1490 141 350 228 1386 290 291 232 1383 245 325 239 1382 251 321 242 1404 240 397 150 1416 239 322 241 1385 247 1378 246 352 221 321 242 1392 243 311 237 1417 231 1375 245 334 236 325 238 1388 248 326 236 1400 286 1342 243 333 240 321 299 1322 240 325 239 1391 243 1410 217 333 231 326 237 1398 236 328 442 1220 216 331 235 1393 239 337 297 1309 244 10746
--[RESULTS]--

time:           Sun Sep 23 16:19:40 2018
hardware:       433gpio
pulse:          4
rawlen:         132
pulselen:       316

Raw code:
567 2511 213 320 238 1395 240 1372 251 344 230 1375 248 328 243 347 217 1380 251 330 236 1383 250 1377 245 328 239 1377 248 354 219 332 236 1410 224 326 235 1386 256 351 200 1384 249 324 239 1388 245 322 239 1383 251 321 308 1333 238 317 242 1383 246 330 236 1385 250 329 235 1394 252 322 236 1437 215 319 241 1392 243 1378 245 334 234 326 239 1388 289 289 230 1383 261 1381 230 332 242 325 239 1393 239 325 237 1415 231 1381 243 340 231 326 234 1449 197 312 241 1388 246 1381 244 331 237 323 238 1392 243 324 240 1394 241 321 238 1443 237 285 231 1388 239 10758
 
Reply
#8
I now tried most sample raw codes for switches in the manual and I noticed 2 things.

#1

All codes with a pulse stream length of 50 (and the single one with 116) work and those with a pulse stream length of 132 do not work.

#2

Many example codes with a pulse stream length should represent
  • Unit: 20
  • ID: 1
  • Fixed: always 0
  • State: Off,
but pilight-receive does output


Code:
{
       "message": {
               "id": 15,
               "unit": 10,
               "state": "on"
       },
       "origin": "receiver",
       "protocol": "arctech_switch_old",
       "uuid": "0000-74-da-38-618eb4",
       "repeats": 1
}
{
       "message": {
               "id": 15,
               "unit": 10,
               "state": "up"
       },
       "origin": "receiver",
       "protocol": "arctech_screen_old",
       "uuid": "0000-74-da-38-618eb4",
       "repeats": 1
}
 
Reply
#9
Please try sending this raw pulse stream:
Code:
pilight-raw -c "567 2511 213 320 238 1395 240 1372 251 344 230 1375 248 328 243 347 217 1380 251 330 236 1383 250 1377 245 328 239 1377 248 354 219 332 236 1410 224 326 235 1386 256 351 200 1384 249 324 239 1388 245 322 239 1383 251 321 308 1333 238 317 242 1383 246 330 236 1385 250 329 235 1394 252 322 236 1437 215 319 241 1392 243 1378 245 334 234 326 239 1388 289 289 230 1383 261 1381 230 332 242 325 239 1393 239 325 237 1415 231 1381 243 340 231 326 234 1449 197 312 241 1388 246 1381 244 331 237 323 238 1392 243 324 240 1394 241 321 238 1443 237 285 231 1388 239 10758"

This should be an on command
 
Reply
#10
When I run

Code:
pilight-raw -c "567 2511 213 320 238 1395 240 1372 251 344 230 1375 248 328 243 347 217 1380 251 330 236 1383 250 1377 245 328 239 1377 248 354 219 332 236 1410 224 326 235 1386 256 351 200 1384 249 324 239 1388 245 322 239 1383 251 321 308 1333 238 317 242 1383 246 330 236 1385 250 329 235 1394 252 322 236 1437 215 319 241 1392 243 1378 245 334 234 326 239 1388 289 289 230 1383 261 1381 230 332 242 325 239 1393 239 325 237 1415 231 1381 243 340 231 326 234 1449 197 312 241 1388 246 1381 244 331 237 323 238 1392 243 324 240 1394 241 321 238 1443 237 285 231 1388 239 10758"


I get


Code:
pilight-raw: ERROR: invalid option -- '-c'




But with

Code:
pilight-send -p raw -c "567 2511 213 320 238 1395 240 1372 251 344 230 1375 248 328 243 347 217 1380 251 330 236 1383 250 1377 245 328 239 1377 248 354 219 332 236 1410 224 326 235 1386 256 351 200 1384 249 324 239 1388 245 322 239 1383 251 321 308 1333 238 317 242 1383 246 330 236 1385 250 329 235 1394 252 322 236 1437 215 319 241 1392 243 1378 245 334 234 326 239 1388 289 289 230 1383 261 1381 230 332 242 325 239 1393 239 325 237 1415 231 1381 243 340 231 326 234 1449 197 312 241 1388 246 1381 244 331 237 323 238 1392 243 324 240 1394 241 321 238 1443 237 285 231 1388 239 10758"


pilight-receive outputs


Code:
{
       "message": {
               "id": 26738834,
               "unit": 0,
               "state": "on"
       },
       "origin": "receiver",
       "protocol": "arctech_switch",
       "uuid": "0000-74-da-38-618eb4",
       "repeats": 1
}
{
       "message": {
               "id": 26738834,
               "unit": 0,
               "state": "up"
       },
       "origin": "receiver",
       "protocol": "arctech_screen",
       "uuid": "0000-74-da-38-618eb4",
       "repeats": 1
}
{
       "message": {
               "id": 26738834,
               "unit": 0,
               "state": "opened"
       },
       "origin": "receiver",
       "protocol": "arctech_contact",
       "uuid": "0000-74-da-38-618eb4",
       "repeats": 1
}


This is definitely a success, but the remote socket is still not switched on. :/
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  Solved - On / Off Command is the same command tigrablue 11 406 07-23-2019, 11:24 AM
Last Post: curlymo
  error pilightsend, recieve and control hansipi 2 428 11-04-2018, 03:46 PM
Last Post: hansipi
  [solved] kwmobile: repeating the remote signal doesn't work dawncrow 9 898 10-25-2018, 03:46 PM
Last Post: dawncrow
  [solved] raw and debug Traeumer 2 486 09-27-2018, 09:43 PM
Last Post: Traeumer
  [SOLVED] Home Assistant switch gpio segalion 5 776 09-10-2018, 12:39 PM
Last Post: segalion
  smtp / solved Traeumer 7 668 08-21-2018, 08:47 PM
Last Post: curlymo
  [SOLVED] pilight wont start since update from 8.0.8 to 8.1.2 pukington 5 1,466 08-08-2018, 05:34 PM
Last Post: curlymo
  [SOLVED] mbedtls_ssl_handshake: SSL - Processing of the ClientHello ha hansrijn2 4 693 08-08-2018, 01:52 PM
Last Post: hansrijn2
Rainbow Trying to control RF Celling FAN bennyboy 0 359 06-23-2018, 05:49 PM
Last Post: bennyboy
  [Solved] reach of pilight hardware PT-Biker 2 880 05-21-2018, 08:28 AM
Last Post: PT-Biker

Forum Jump:


Browsing: 1 Guest(s)