Not working properly new firmware #13

Erdk2 · 2018-09-18T11:06:09Z

No description provided.

tavicu · 2018-09-21T09:30:43Z

Hi @Erdk2, The power on works because it's using a standard function.

Your TV probably have a new version of OS for Smart TV with a new API.

Since i don't have a TV like that, i can't help you with the problem.

Unless you want to donate one :P

eduardoboucas · 2018-10-04T00:26:12Z

I'm on the same firmware version and I'm seeing the exact same issue.

I'm pretty familiar with JavaScript, so I'm happy to have a go at this. Any chance you could share any pointers on how to approach this, @tavicu? My main question is where to find information about these APIs – is there any form of documentation anywhere, or is it reverse engineered?

Thanks!

eduardoboucas · 2018-10-04T00:55:18Z

I was able to plant some logs and see what is being returned in a few places of the application when the power off command is executed.

homebridge-samsung-tizen/lib/SamsungRemote.js

Line 291 in b00637c

data = JSON.parse(data);
```
{ event: 'ms.channel.unauthorized' }
```

homebridge-samsung-tizen/lib/SamsungRemote.js

Line 281 in b00637c

this.socket.on('error', (error) => reject(error));

{ RangeError: Invalid WebSocket frame: invalid status code 1005
    at Receiver.controlMessage (/usr/lib/node_modules/homebridge-samsung-tizen/node_modules/ws/lib/receiver.js:441:18)
    at Receiver.getData (/usr/lib/node_modules/homebridge-samsung-tizen/node_modules/ws/lib/receiver.js:329:42)
    at Receiver.startLoop (/usr/lib/node_modules/homebridge-samsung-tizen/node_modules/ws/lib/receiver.js:133:22)
    at Receiver._write (/usr/lib/node_modules/homebridge-samsung-tizen/node_modules/ws/lib/receiver.js:69:10)
    at doWrite (_stream_writable.js:396:12)
    at writeOrBuffer (_stream_writable.js:382:5)
    at Receiver.Writable.write (_stream_writable.js:290:11)
    at Socket.socketOnData (/usr/lib/node_modules/homebridge-samsung-tizen/node_modules/ws/lib/websocket.js:795:35)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7) [Symbol(status-code)]: 1002 }

tavicu · 2018-10-04T04:45:04Z

Hi @eduardoboucas

It looks like you didn’t authorize the api on the first connection.

You can check in Settings - General - External Device Manager - Device List. Maybe you clicked Disallow.

Let me know!

eduardoboucas · 2018-10-04T10:13:15Z

Hi @tavicu, thanks for the quick reply!

I don't have any devices on the Device List window, it just says "No equipment stored". In fact, I've never seen any authorisation prompt, except when I tried pairing with an older plugin.

If this is an authorisation issue, is it normal that the power ON command works fine? And is there any other way I could troubleshoot an authorisation problem?

Also, I'm happy to plant some more logs in other parts of the application if that helps.

Thanks again.

tavicu · 2018-10-04T10:35:38Z

Hi @eduardoboucas
It is normal to work the power ON. I am using Wake on Lan for power on and the tv api for the rest of commands.

Can you try to access this url and see if it works? http://TV_IP:8001/api/v2/

eduardoboucas · 2018-10-04T10:42:11Z

It does work, here's what I see:

{  
   "device":{  
      "FrameTVSupport":"false",
      "GamePadSupport":"true",
      "ImeSyncedSupport":"true",
      "OS":"Tizen",
      "TokenAuthSupport":"true",
      "VoiceSupport":"true",
      "countryCode":"PT",
      "description":"Samsung DTV RCR",
      "developerIP":"0.0.0.0",
      "developerMode":"0",
      "duid":"uuid:<DEVICE_ID>",
      "firmwareVersion":"Unknown",
      "id":"uuid:<DEVICE_ID>",
      "ip":"192.168.1.78",
      "model":"18_KANTME_UHD",
      "modelName":"UE65NU7455",
      "name":"[TV] Samsung 7 Series (65)",
      "networkType":"wired",
      "resolution":"3840x2160",
      "smartHubAgreement":"true",
      "type":"Samsung SmartTV",
      "udn":"uuid:<DEVICE_ID>",
      "wifiMac":"<MAC ADDRESS>"
   },
   "id":"uuid:<DEVICE_ID>",
   "isSupport":"{\"DMP_DRM_PLAYREADY\":\"false\",\"DMP_DRM_WIDEVINE\":\"false\",\"DMP_available\":\"true\",\"EDEN_available\":\"true\",\"FrameTVSupport\":\"false\",\"ImeSyncedSupport\":\"true\",\"TokenAuthSupport\":\"true\",\"remote_available\":\"true\",\"remote_fourDirections\":\"true\",\"remote_touchPad\":\"true\",\"remote_voiceControl\":\"true\"}\n",
   "name":"[TV] Samsung 7 Series (65)",
   "remote":"1.0",
   "type":"Samsung SmartTV",
   "uri":"http://192.168.1.78:8001/api/v2/",
   "version":"2.0.25"
}

tavicu · 2018-10-04T10:56:54Z

I think some of the TV's are using another auth method.

Can you please try the demo from this repo?
https://github.com/tdudek/samsung-remote-models-2014-and-newer

And also if this url return something: http://${this.config.ip}:8001/ms/1.0/

eduardoboucas · 2018-10-04T11:47:43Z

Can you please try the demo from this repo?

I ran demo example, inserted the IP and clicked to connect. I saw an authorisation prompt on my TV asking if I wanted to allow the device to connect. I clicked Allow and then clicked Confirm on the web app, but the web app then asks me for a pairing code that the TV was supposed to show. Trouble is, there was no pairing code. Nothing really happened on the TV after I clicked Allow.

And also if this url return something: http://${this.config.ip}:8001/ms/1.0/

This returns <html><body>404</body></html>

tavicu · 2018-10-04T11:50:40Z

That's cool! It means that your TV supports my plugin.

The problem is why when you try to send a command for the first time (power off) it's not asking for authorisation like it did now ...

eduardoboucas · 2018-10-04T11:58:33Z

Can you point me to any relevant documentation so that I can try to poke around? I've been looking at various pages in the Samsung Developer portal (e.g. https://developer.samsung.com/tv/develop/getting-started/creating-tv-applications), but there's too much content and I can't find the relevant API references for what we're trying to do.

We're not exactly building a TV application, we're trying to interact with it from an external device. Or would that be the same, as far as the APIs are concerned?

tavicu · 2018-10-04T12:02:40Z

Unfortunately there is no documentation for this API.

Let me know what name did you put in config file and i will try to make a command for you to run and see the result :)

eduardoboucas · 2018-10-04T12:08:13Z

I just noticed that when I hit http://192.168.1.78:8001/ms/1.0, I do see an authorisation prompt in the TV. However, nothing happens after I select Allow, and subsequently hitting the same endpoint simply results in the response I shared above.

As for my config, here's what it looks like:

{  
   "bridge":{  
      "name":"Homebridge",
      "username":"CC:22:3D:E3:CE:30",
      "port":51826,
      "pin":"031-45-154"
   },
   "description":"Home",
   "accessories":[  

   ],
   "platforms":[  
      {  
         "platform":"SamsungTizen",
         "devices":[  
            {  
               "name":"Living room TV",
               "ip":"192.168.1.78",
               "mac":"<MAC>"
            }
         ]
      }
   ]
}

Let me know if you need any other info.

Thanks again for your help. Much appreciated!

eduardoboucas · 2018-10-04T13:36:53Z

I have removed the bridge from my HomeKit app and added it back again. Now the error seems to be slightly different. I see this when trying to send the power off command:

Oct 04 14:29:48 raspberrypi homebridge[2476]: [2018-10-4 14:29:48] [Living room TV] Power: Failed to send the command to TV

And this is shown in the console, as a result of the logs I planted:

Oct 04 14:31:48 raspberrypi homebridge[2476]: Error: WebSocket was closed before the connection was established
Oct 04 14:31:48 raspberrypi homebridge[2476]:     at WebSocket.close (/usr/lib/node_modules/homebridge-samsung-tizen/node_modules/ws/lib/websocket.js:198:14)
Oct 04 14:31:48 raspberrypi homebridge[2476]:     at SamsungRemote._closeSocket (/usr/lib/node_modules/homebridge-samsung-tizen/lib/SamsungRemote.js:337:25)
Oct 04 14:31:48 raspberrypi homebridge[2476]:     at Timeout.socket.timeout.setTimeout [as _onTimeout] (/usr/lib/node_modules/homebridge-samsung-tizen/lib/SamsungRemote.js:274:61)
Oct 04 14:31:48 raspberrypi homebridge[2476]:     at ontimeout (timers.js:498:11)
Oct 04 14:31:48 raspberrypi homebridge[2476]:     at tryOnTimeout (timers.js:323:5)
Oct 04 14:31:48 raspberrypi homebridge[2476]:     at Timer.listOnTimeout (timers.js:290:5)
Oct 04 14:31:48 raspberrypi homebridge[2476]: error: Error: WebSocket was closed before the connection was established
Oct 04 14:31:48 raspberrypi homebridge[2476]:     at WebSocket.close (/usr/lib/node_modules/homebridge-samsung-tizen/node_modules/ws/lib/websocket.js:198:14)
Oct 04 14:31:48 raspberrypi homebridge[2476]:     at SamsungRemote._closeSocket (/usr/lib/node_modules/homebridge-samsung-tizen/lib/SamsungRemote.js:337:25)
Oct 04 14:31:48 raspberrypi homebridge[2476]:     at Timeout.socket.timeout.setTimeout [as _onTimeout] (/usr/lib/node_modules/homebridge-samsung-tizen/lib/SamsungRemote.js:274:61)
Oct 04 14:31:48 raspberrypi homebridge[2476]:     at ontimeout (timers.js:498:11)
Oct 04 14:31:48 raspberrypi homebridge[2476]:     at tryOnTimeout (timers.js:323:5)
Oct 04 14:31:48 raspberrypi homebridge[2476]:     at Timer.listOnTimeout (timers.js:290:5)

Also, I can see from the logs that the plugin is trying to access this URL at some point: http://192.168.1.78:8001/api/v2/channels/samsung.remote.control?name=TGl2aW5nIHJvb20gVFY=. When I try to access it directly on a browser, I get the authorisation prompt on the TV, select Allow and then nothing happens. The browser responds with the same response as the other endpoint: <html><body>404</body></html>.

tavicu · 2018-10-04T14:26:51Z

can you try to run from the server this command?

curl -I -L http://192.168.1.78:8001/api/v2/channels/samsung.remote.control?name=TGl2aW5nIHJvb20gVFY=

flobernd · 2018-10-04T20:43:50Z

I tried it on my Q7FN TV and got the following result:

curl -I -L http://192.168.178.129:8001/api/v2/channels/samsung.remote.control?name=U2Ftc3VuZyBRN0ZO
HTTP/1.0 403 Forbidden
content-type: text/html
content-length: 38

The name of my device in the homebridge config is "Samsung Q7FN" aka "U2Ftc3VuZyBRN0ZO" in base64.

The root API URL prints the following information

{
  "device": {
    "FrameTVSupport": "false",
    "GamePadSupport": "true",
    "ImeSyncedSupport": "true",
    "OS": "Tizen",
    "TokenAuthSupport": "true",
    "VoiceSupport": "true",
    "countryCode": "DE",
    "description": "Samsung DTV RCR",
    "developerIP": "0.0.0.0",
    "developerMode": "0",
    "duid": "uuid:7f7a5e4b-1d6b-49e7-9aa5-5a347a3db72f",
    "firmwareVersion": "Unknown",
    "id": "uuid:7f7a5e4b-1d6b-49e7-9aa5-5a347a3db72f",
    "ip": "192.168.178.129",
    "model": "18_KANTM2_QTV",
    "modelName": "QE55Q7FNA",
    "name": "[TV] Samsung Q7 Series (55)",
    "networkType": "wired",
    "resolution": "3840x2160",
    "smartHubAgreement": "true",
    "type": "Samsung SmartTV",
    "udn": "uuid:7f7a5e4b-1d6b-49e7-9aa5-5a347a3db72f",
    "wifiMac": "64:1c:b0:a5:05:7d"
  },
  "id": "uuid:7f7a5e4b-1d6b-49e7-9aa5-5a347a3db72f",
  "isSupport": "{\"DMP_DRM_PLAYREADY\":\"false\",\"DMP_DRM_WIDEVINE\":\"false\",\"DMP_available\":\"true\",\"EDEN_available\":\"true\",\"FrameTVSupport\":\"false\",\"ImeSyncedSupport\":\"true\",\"TokenAuthSupport\":\"true\",\"remote_available\":\"true\",\"remote_fourDirections\":\"true\",\"remote_touchPad\":\"true\",\"remote_voiceControl\":\"true\"}\n",
  "name": "[TV] Samsung Q7 Series (55)",
  "remote": "1.0",
  "type": "Samsung SmartTV",
  "uri": "http://192.168.178.129:8001/api/v2/",
  "version": "2.0.25"
}

aleibz98 · 2018-10-05T14:08:55Z

can you try to run from the server this command?

curl -I -L http://192.168.1.78:8001/api/v2/channels/samsung.remote.control?name=TGl2aW5nIHJvb20gVFY=

And this is what I get when I run the command...
HTTP/1.1 404 Not Found
X-Powered-By: Express
Access-Control-Allow-Origin: *
Access-Control-Allow-Credentials: true
Access-Control-Allow-Methods: GET,PUT,POST,DELETE
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, SilentLaunch
Content-Type: application/json; charset=utf-8
Content-Length: 60
Date: Fri, 05 Oct 2018 14:07:35 GMT
Connection: keep-alive

aleibz98 · 2018-10-05T14:14:33Z

when I run http://192.168.1.54:8001/api/v2/ i get:

{
"id": "uuid:ee0ae248-280e-4e5a-98cc-84deab71a5b5",
"name": "[TV] UE50J6200",
"version": "2.0.25",
"device": {
"type": "Samsung SmartTV",
"duid": "uuid:ee0ae248-280e-4e5a-98cc-84deab71a5b5",
"model": "15_HAWKM_2D",
"modelName": "UE50J6200",
"description": "Samsung DTV RCR",
"networkType": "wired",
"ssid": "",
"ip": "192.168.1.54",
"firmwareVersion": "Unknown",
"name": "[TV] UE50J6200",
"id": "uuid:ee0ae248-280e-4e5a-98cc-84deab71a5b5",
"udn": "uuid:ee0ae248-280e-4e5a-98cc-84deab71a5b5",
"resolution": "1920x1080",
"countryCode": "ES",
"msfVersion": "2.0.25",
"smartHubAgreement": "true",
"wifiMac": "14:bb:6e:49:46:28",
"developerMode": "0",
"developerIP": ""
},
"type": "Samsung SmartTV",
"uri": "http://192.168.1.54:8001/api/v2/"
}

flobernd · 2018-10-05T15:41:27Z

And this is what I get when I run the command...
HTTP/1.1 404 Not Found

You have to change the base64 encoded name part of the URL. It will always return 404, if the name was not found.

For me it returns 403 Forbidden which indicates that I somehow does not have access to the function.

eduardoboucas · 2018-10-05T23:09:44Z

@tavicu I get the same as @flobernd:

HTTP/1.0 403 Forbidden
content-type: text/html
content-length: 38

eduardoboucas · 2018-10-05T23:19:13Z

Btw, this seems to be an issue with all Series 7 models: Ape/samsungctl#89.

flobernd · 2018-10-11T12:57:37Z

A new firmware (1153.3) is available for manual download, but same problem with this one.

cyphers · 2018-10-12T15:30:21Z

2018 models added TokenAuthSupport in August after fooling everyone into thinking normal IP control worked. Samsung designated 6 chosen vendors last November that they have given the information for the protocol. So you would need to reverse engineer one of those 6 to auth for that protocol now. Most likely it's some kind of OAuth and a token parameter now needs to be passed to these APIs.

flobernd · 2018-10-12T16:44:15Z

Which vendors and which apps are on the list?

cyphers · 2018-10-12T17:12:54Z

The Nov 30 2017 announcement identified URC, AMX, Savant, RTI, Crestron, and C4. I don't know if all of those actually completed it, but presumably most did and presumably that's why Samsung felt it was okay to suddenly block the rest of the world last August.

JonoHaysom · 2018-10-15T17:35:40Z

yup. UK firmware TV here and the new firmware killed this except for power on :(

im happy to help troubleshoot too

knudsvik · 2018-10-19T12:34:31Z

Also had issue with power modes. Installed this plugin instead, which works fine: https://www.npmjs.com/package/homebridge-samsung-remote

JonoHaysom · 2018-10-19T13:35:57Z

Also had issue with power modes. Installed this plugin instead, which works fine: https://www.npmjs.com/package/homebridge-samsung-remote

I used to use that one, it didn't work either for the "power off" command.

what firmware and TV model are you using?

tavicu · 2018-10-23T08:55:37Z

Hey! Sorry for not being active. Until December i have a lot of work and i will not be able to help any of you.

logictester · 2018-10-27T16:09:15Z

Anyone knows of any Samsung remote plugin that will work after this TV update? There's no way to revert the TV firmware update

JonoHaysom · 2018-11-14T16:12:28Z

did you add the token to the platforms config now? as "token" : "87915724"

yup, doesn't work, its super weird!

https://github.com/petealves/homebridge-samsung-smart-tv18 <-- works however he has no way to save the token in his implementation so it asks each time on screen if it can control... but the commands are working for WOL and to turn off but I get the authorisation prompt. his web sockets are working and are very fast.

Log for that plugin:
EventedHTTPServer [::ffff:192.168.1.159] HTTP request: /characteristics +7s
HAPServer [CC:22:3D:E3:CB:32] HAP Request: PUT /characteristics +0ms
Accessory [Homebridge] Processing characteristic set: [{"aid":12,"iid":10,"value":true}] +1ms
Accessory [Homebridge] Setting Characteristic "On" to value true +0ms
[14/11/2018, 20:05:46] [TV] Received ON Command: true
[14/11/2018, 20:05:46] [TV] Attempting Wake
[14/11/2018, 20:05:46] [TV] Wake On Lan Successful
EventedHTTPServer [::ffff:192.168.1.128] Sending HTTP event '12.10' with data: {"characteristics":[{"aid":12,"iid":10,"value":true}]} +209ms
EventedHTTPServer [::ffff:192.168.1.159] Muting event '12.10' notification for this connection since it originated here. +1ms
EventedHTTPServer [::ffff:192.168.1.132] Sending HTTP event '12.10' with data: {"characteristics":[{"aid":12,"iid":10,"value":true}]} +0ms
EventedHTTPServer [::ffff:192.168.1.159] HTTP Response is finished +1ms

TV Off:
HAPServer [CC:22:3D:E3:CB:32] HAP Request: PUT /characteristics +0ms
Accessory [Homebridge] Processing characteristic set: [{"aid":12,"iid":10,"value":false}] +1ms
Accessory [Homebridge] Setting Characteristic "On" to value false +0ms
[14/11/2018, 20:06:05] [TV] Received ON Command: false
[14/11/2018, 20:06:08] [TV] WebSocket Connected
[14/11/2018, 20:06:09] [TV] WebSocket Closed

logictester · 2018-11-14T16:22:33Z

i'd suggest uninstalling the plugin and clearing out the config and starting over...

thehauntedmattress · 2018-11-15T01:05:57Z

Thank you so much for this update! I was so worried after seeing earlier comments that all hope was lost. But we all appreciate your development of this! I love controlling my TV using HomeKit, Siri, and Alexa.

logictester · 2018-11-15T17:53:23Z

@tavicu still asks to allow in the morning.... wss://10.0.0.13:8002/api/v2/channels/samsung.remote.control?name=VFY=&token=10985883
[DEBUG] { data:
{ clients: [ [Object] ],
id: 'e0848729-7dd-42a-83ed-aef32ce9a6c' },
event: 'ms.channel.connect' }

TheMisfit68 · 2018-11-15T20:14:10Z

Can't get it to work :-(. Have received the token and, put it in the config and restarted homebridge.
Always see 'Can't reach TV' on each command in the log.

JonoHaysom · 2018-11-16T10:35:08Z

Can't get it to work :-(. Have received the token and, put it in the config and restarted homebridge.
Always see 'Can't reach TV' on each command in the log.

that's the same experience I'm having :(

RST2300 · 2018-11-16T21:21:19Z

I have the same Problem. I have a UE 55 Nu 7179.

JonoHaysom · 2018-11-17T09:52:39Z

QE65Q8 here.. looks like we may need a bit more troubleshooting.

TheMisfit68 · 2018-11-17T10:57:36Z

Mine is a QE49Q7FAM

logictester · 2018-11-19T14:35:23Z

@tavicu the token seems to be changing, my TV keeps asking to allow after a while of working fine, so i've removed the token - and paired again - a new token was presented, set it in the config, but after a few hours was asked to allow again, removed the token again and paired - new token was presented and yet it keeps asking to allow after a few hours again

tavicu · 2018-11-19T14:37:27Z

Hei. I didn't had time in the latest days to look but i will try to make some.

What i can tell is that i use the same version with my tv and never asked me to Allow since the first pair that was 5 days ago. I use my TV and commands every day without a problem!

logictester · 2018-11-19T14:53:02Z

thanks, question - in settings, general, external device manager, device connect manager - do you have access notification set to Always On or something different?

tavicu · 2018-11-19T15:01:57Z

@logictester i will take a look when i get home but i don't think so! It did asked me the first time to Allow. So if it was on Always On, it shouldn't ask. But i will come back with a response :)

logictester · 2018-11-20T13:44:22Z

@tavicu setting the Access Notification to Never seems to do the trick :)!

JonoHaysom · 2018-11-20T13:50:52Z

Nope, that doesn’t work. It won’t show the prompt but it still doesn’t work.

jonasborneland · 2018-11-21T20:39:08Z

@tavicu Thank you so much for the update!! works on my TV after updating your plugin and adding the token to the config. My TV model is: UE40MU6402U 6 Series

TheMisfit68 · 2018-11-21T21:04:34Z

Nope, that doesn’t work. It won’t show the prompt but it still doesn’t work.

same here

JonoHaysom · 2018-11-22T03:56:21Z

looks like its either a Tizen v3 or a series 7-9 issues

KennyVB · 2018-11-26T07:42:57Z

hmm same problem here! UE40KU6075 Samsung
not getting token in debug mode either.. it works tho, can use all the commands i had before i updated to latest. and yes it asked for permission and i press allow. but still fails to pair it says

markgergely · 2018-11-30T05:16:16Z

@tavicu I had the same symptoms as @JonoHaysom with a 65MU8000, the problem is right here: https://github.com/tavicu/homebridge-samsung-tizen/blob/master/lib/SamsungRemote.js#L41
When you are running homebridge on a OSX, -w 1 is an invalid argument for ping:

» ping -t 1 -c 1 -w 1  192.168.7.60                                                                        
ping: illegal option -- w

Thus the ping check fails so it does not even bother sending out the off command.

JonoHaysom · 2018-11-30T07:28:23Z

thanks @markgergely hey @tavicu is it possible to change the code to suit the above for those running home bridge on OS X?

TheMisfit68 · 2018-11-30T17:05:21Z

Just wanna confirm I'm also running Homebridge on OSX

tavicu · 2018-11-30T17:09:16Z

Hei! Sorry for not being active but i had a lot of work at the job. I will push a new update next week at the beginning and try to solve most of the problems, including -w on OS X.

As an update, i still run the same version and the TV never ask me to allow again. Please make sure you update your config file to include the token after pairing.

logictester · 2018-11-30T17:13:32Z

@tavicu ever since i've set the notification in TV settings to first time only - never been asked to allow again :) i run my homebridge as a docker on my LibreELEC Kodi box btw

thehauntedmattress · 2018-11-30T17:31:39Z

I thought my setup was good but the TV did ask me to allow access for Homebridge. I did it again with a new token and I'm fine for now. I just hope that it doesn't ask me again. Any work on fixing that so far?

logictester · 2018-11-30T17:34:10Z

@thehauntedmattress make sure in the TV settings - Remote device management to set the notification setting to first time only

thehauntedmattress · 2018-11-30T17:35:01Z

I had it at first time only and it was still doing it. In fact I turned it off and it still was asking for allow/deny.

tavicu · 2018-12-04T19:12:41Z

I have released a new version.

Fixed OS X bug
Now it will try 3 times to pair before failing
Check if TV is on before trying to pair
Forcing to pair before using accessories
Updated README

Please try to look on the README file at Installation steps!
Especially this one:

On TV go to Settings - General - External Device Manager - Device Connection Manager and set Access Notification to Off

If you still have a problem that is not answered in the Common Issues section please open a new Issue.

tavicu mentioned this issue Nov 30, 2018

Samsung default button #20

Closed

tavicu closed this as completed Dec 4, 2018

Not working properly new firmware #13

Not working properly new firmware #13

Comments

Erdk2 commented Sep 18, 2018 • edited

tavicu commented Sep 21, 2018

eduardoboucas commented Oct 4, 2018

eduardoboucas commented Oct 4, 2018

tavicu commented Oct 4, 2018

eduardoboucas commented Oct 4, 2018

tavicu commented Oct 4, 2018

eduardoboucas commented Oct 4, 2018

tavicu commented Oct 4, 2018 • edited

eduardoboucas commented Oct 4, 2018

tavicu commented Oct 4, 2018

eduardoboucas commented Oct 4, 2018

tavicu commented Oct 4, 2018

eduardoboucas commented Oct 4, 2018

eduardoboucas commented Oct 4, 2018

tavicu commented Oct 4, 2018

flobernd commented Oct 4, 2018 • edited

aleibz98 commented Oct 5, 2018

aleibz98 commented Oct 5, 2018

flobernd commented Oct 5, 2018

eduardoboucas commented Oct 5, 2018

eduardoboucas commented Oct 5, 2018

flobernd commented Oct 11, 2018

cyphers commented Oct 12, 2018

flobernd commented Oct 12, 2018

cyphers commented Oct 12, 2018

JonoHaysom commented Oct 15, 2018

knudsvik commented Oct 19, 2018

JonoHaysom commented Oct 19, 2018

tavicu commented Oct 23, 2018

logictester commented Oct 27, 2018

JonoHaysom commented Nov 14, 2018 • edited

logictester commented Nov 14, 2018

thehauntedmattress commented Nov 15, 2018

logictester commented Nov 15, 2018

TheMisfit68 commented Nov 15, 2018

JonoHaysom commented Nov 16, 2018

RST2300 commented Nov 16, 2018

JonoHaysom commented Nov 17, 2018

TheMisfit68 commented Nov 17, 2018

logictester commented Nov 19, 2018

tavicu commented Nov 19, 2018 • edited

logictester commented Nov 19, 2018

tavicu commented Nov 19, 2018

logictester commented Nov 20, 2018

JonoHaysom commented Nov 20, 2018

jonasborneland commented Nov 21, 2018

TheMisfit68 commented Nov 21, 2018

JonoHaysom commented Nov 22, 2018

KennyVB commented Nov 26, 2018

markgergely commented Nov 30, 2018 • edited

JonoHaysom commented Nov 30, 2018

TheMisfit68 commented Nov 30, 2018

tavicu commented Nov 30, 2018 • edited

logictester commented Nov 30, 2018

thehauntedmattress commented Nov 30, 2018

logictester commented Nov 30, 2018

thehauntedmattress commented Nov 30, 2018

tavicu commented Dec 4, 2018

Erdk2 commented Sep 18, 2018 •

edited

tavicu commented Oct 4, 2018 •

edited

flobernd commented Oct 4, 2018 •

edited

JonoHaysom commented Nov 14, 2018 •

edited

tavicu commented Nov 19, 2018 •

edited

markgergely commented Nov 30, 2018 •

edited

tavicu commented Nov 30, 2018 •

edited