This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
RamonBaas
About
- Username
- RamonBaas
- Joined
- -
- Visits
- 848
- Last Active
- Roles
- Member
Comments
-
@keverjeroen Added decoding of UPM, but likely the signal reception part won't work correctly (yet). The signal uses differential Manchester, so probably some bits will need to be inverted before it will work. Looking forward to receive some sample …
-
@keverjeroen Thanks, that is good stuff! Should be able to create a signal definition and data decoding based on this (once I get some spare time).
-
@keverjeroen Is there anything of a type nr on the sensor (do you have a picture)? How far is it away from Homey? Otherwise we'd need to look at the values in the arrays of the recording.
-
@Tomvz You might just be in luck. I've just bought a MCT-442 myself as well last week, so who knows .
-
Don't need to. It is treated as a RS232 signal this way, not a TTL signal.
-
@TedTolboom You can use a USR-TCP232-T2 (or USR-TCP232-E2 as on the picture) with a MINI (TTL) RS232.
-
If you use a simple serial to ethernet device, you can use this one as well: https://github.com/nlrb/nl.dsmr.p1
-
@BasVanDenBosch Not each value is a bit. It is a duration in ms how long there is an 'on' signal or not (for ASK encoding). In your case you can see two words: approx. [1380, 610] and [390, 1600] (sum is both 1990). As the intervals have some variat…
-
@maxxie01 Well, there is a clear pattern. 4 groups of 6 (or more like 3) bits (00 = 0, 01 = 1). Group 1: A/B/C (A: 0 1 1, B: 1 0 1, C: 1 1 0) Group 2: Always 1 1 1 Group 3: on or off (on: 1 0 1, off 1 1 1) Group 4: same data as group 3 (check) As …
-
@Robbertos I only have one fireplace at home and it has a different remote . So I don't know what signal your remote sends unfortunately. You'll either need to capture the signal or provide me with the remote and I can capture the signal for you.
-
You can try to capture 868 Mhz signals using the Chrome console with the command api('POST', '/manager/microcontroller/record', { frequency: '868' }, console.log)
-
@pagocs Glad you like it. To be honest, I haven't been able to receive anything useful with Homey on 868 MHz. Where the 433 spectrum configuration is relatively broad, it seems very narrow for 868. From the docs: ... This comes down to a frequency b…
-
@Jeroenvano Zone alarm active should only be triggered when there is an actual alarm. It then lists the zones which have triggered the alarm. I'll need to check why it triggers while there is no alarm. Can you submit an issue on GitHub?
-
@RemcoHannink As far as I can see the connections are still in the same place. Your numbering is just different from mine. If you have a 12-pin header, looks like they omitted pins 13 & 14.
-
Do you have DIP switches in the remote to set the channel?
-
@TedTolboom Recognizing the signal during pairing can indeed be difficult. Luckily this is only needed once. Sometimes you need to hold e.g. the down key pressed for a minute or more. There also appears to be a newer version of the protocol with a d…
-
@RuudvB "And rest assured: we made sure that no matter how you connect Slide, it'll always be hidden behind your curtains!"
-
@TedTolboom For the Mertik 433 control, have a look here: https://github.com/nlrb/com.mertik.maxitrol Be aware that there is still an issue open related to sending 433 signals: https://github.com/athombv/homey/issues/1076 So best to only turn it up…
-
@RemcoHannink The node-crc module you can clone separately. I've committed the fixes on the app for the other issues you saw (had them locally, but forgot to push them).
-
@RemcoHannink Good to hear that is works! With google you can already find the TTL pinout of the PowerMax+ (1 Tx, 3 Rx, 5 Gnd). Is there a Vcc as well that you can use from the alarm?
-
Version 1.0.0 is available on GitHub.
-
dr.jake said: When i manually (force/request) the update to 1.01 I get an error message with an exclamation mark icon : "extractpath_not_writable". I can only click on "ok" . Please help @dr.jake When you get "extractpath_not_writable" t…
-
Still there: https://github.com/nlrb/com.tclcode.otgw
-
@Pils: Limited range is indeed an Athom/Homey thing which they have on their list to solve SOON(TM). This cannot be solved in any app.
-
@RemcoHannink That is good to hear! Since the data contains no device ID (that I know of) it will call it 'TH' (Temperature Humidity) + the unique code. As the W044 is known to be Alectov1, I'm curious which devices @ArenBreur has and what RFlink/D…
-
@ArenBreur Ah, you do have a wind sensor as well! So that may have been the data I've seen. The Alecto v1 protocol does carry battery info. Can you send a log file that I have some data to work with?
-
@hnijveen So obesity went into anorexia with a negative value of 30MB - don't know in which case you'd need to worry more...
-
@Jeroenvano Glad you like it!
-
@ArenBreur Thanks. Is this a temp/hum sensor? If so, we likely have the bits reversed. Also, if you happen to have the actual values at that moment, that would help.
-
@ArenBreur Thanks for the log. One last thing we can try is see if signal recognition gets better without looking for the sync bit. I've updated the code to remove the sof.