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
-
@goldstike: The sensor ID for the thgn132n should be 1a2d with the v2 protocol. Strange to not see this back. Just noticed that I still need to add the data layout for this sensor type.
-
@keverjeroen No clue, but you can always try for just €10 @goldstrike Those should work with Oregon v2 support on. Any clue in the statistics json or debug logging?
-
The TFA-320 looks to be a different protocol, don't know if that one is supported yet. I was referring to this one: https://www.weerstationkopen.nl/accessoires-weerstations/tfa/303150-5-kan-sensor
-
@goldstrike In general Orgeon Scientific sensors are good, but I also use TFA ones (e.g. 30.3150, Cresta protocol).
-
@goldstrike I haven't been able to receive any sensible signal on 868 MHz from a weather sensor. Next to that the Smartwares protocol is proprietary and not documented anywhere.
-
@Homey_Lampje There should also not be a null character according to the spec. It should end with ! CR LF. However, since there is no CRC for v3 the extra character doesn't hurt a lot. The current code should work with or without and extra character…
-
@Homey_Lampje Ok. For now I've updated the v3 regular expression that it will ignore the colon.
-
Well, the telegram parses perfectly as long as there is no colon (':') in the end. My code does not insert this (or let me know where that would happen), so you'll have to figure out where it comes from. How do you convert the serial data to Etherne…
-
Text please...
-
Otherwise PM me a valid v3 telegram, then I can see where the error is.
-
@Homey_Lampje Try the latest update. I've relaxed the end-of-message check.
-
Do you really get '!:' as end of message? Is that according to the spec (the added ':')? If so change || this.incomingTelegram.slice(-3) === '!\r\n')) // v3 to || this.incomingTelegram.slice(-4) === '!:\r\n')) // v3
-
@Homey_Lampje Unfortunately your code broke the v4 (gas) decoding. Based on your inputs I've made a new version that should support v3 & v4. It should automatically detect the version. Can you give it a try?
-
@Homey_Lampje You can always make a PR (Pull Request). Can't break anything. I can always reject it if needed.
-
@Homey_Lampje Have a look here: https://help.github.com/articles/creating-a-pull-request/
-
The updated version is on GitHub.
-
@Homey_Lampje You're close, but the bug is different . The behavior you see occurs because the events are not registered after adding the device. The 'completed' event was never emitted after pairing. Will submit the fix + some additions soon.
-
@ErwinVrieze, @Homey_Lampje The labels are the default Homey labels of the standard capabilities - not something I can control. @Homey_Lampje Good that it is working! Can I merge the code? I'd still like to see whether we can determine from the dat…
-
Clear, so the crc is new in v4. If you have a fix that works for both versions, can you submit a PR?
-
Just noticed the comment in the README of the parser: Will only parse DSMRv4 telegrams (not DSMRv3 or older). Looking at the DSMR spec, the CRC is not optional - it should be there... I can't see what version of the meter you have (1-3:0.2.8), bu…
-
@keverjeroen I guess the effort to decode differential Manchester like this did not pay off :-(. Only very limited messages are received and they are not received correctly. I'm afraid I'm stuck. You could ask Athom to add support for differential M…
-
That should have been enough. I guess it is just a different protocol.
-
How long did it run before making the dump? This doesn't show anything. So I'll either need multiple captures of the signal or a link to a definition of the protocol.
-
@Homey_Lampje I am using the parser of Robert Klep (https://github.com/robertklep/node-dsmr-parser). You could report it there or I can try another parser (e.g. https://github.com/ruudverheijden/node-p1-reader).
-
@jklflipper Your protocol looks different from the one described here (which is implemented): http://members.upc.nl/m.beukelaar/Crestaprotocol.pdf I've updated the code to capture more debug logging. Could you update the code, let is run some time …
-
@jklflipper Can you make sure Cresta/TFA is on, let it run for 30 min and then press 'Download statistics'. That should produce a json file. Can you send me that?
-
@jklflipper What is the actual type on the sensor? The Cresta/TFA sensors are supported. I have two TFA 30.315 that work just fine.
-
@keverjeroen The good news is that there is a pattern in the bit stream. The bad news is that decoding capabilities of Homey are limited and it doesn't decode differential Manchester. I've updated to code to try another decoding approach. Can you gi…
-
Just started playing with my Echo Dot last weekend and indeed it works great. It connects via BT to my Heos. There is even an integration with Vera . Was thinking of creating a skill for Homey, but if Athom makes an integration I'll wait for that (…
-
@keverjeroen As said, it is not expected to fully work yet. So I'd be surprised if the sensor showed up. Can you let it run for 30 mins and then download statistics and send me the json output?