John

similar for client.get(url, localFile, callback): it never retrieves any byte and at some point fails with timeout. all fine on node 9, broken on node 10.5 when using the client.get(url,...

problem with client.get verified to exist on node versions 10.1.0, 10.3.0, 10.4.0 verified to be working fine on node versions 9.4.0 and 9.11.2

a rather simple way of allowing use of generics is to patch the regex in [toSafeString() in src/utils.ts](https://github.com/bcherny/json-schema-to-typescript/blob/efc311a47e47394ddf6dbba9701a4d2367edee82/src/utils.ts#L166) to also allow "" being part of TS identifier and then use...

does the device really use an eBUS interface? or is this something else? The logged traffic does not look like eBUS protocol at all

It is still on the road map and actually I was browsing for good JSON libs last week for another thing. Anyway, this is a very time consuming thing to...

looks like the adapter is not able to write to the bus

hm, thats a weird answer. ebusd can't be too fast as it depends completely on how quick the data arrives. it is a matter of the eBUS protocol and the...

if you switch off the scan feature and pick the CSV files manually, you would get translated messages as well. but as long as sending does not work reliably, you...

@ivanhoe-code if you don't see any messages being broadcast on the bus, then a readonly interface is useless. @all: there is little trick to circumvent having to manually pick the...

are you running through ttyAMA with ttyebus or how is the connection exactly looking like? it seems some other unit is sending on the bus while the protocol is in...