[xxxParticipant 2022-12-21 at 15:13 Post count: 68]

#33722

xxx

• This topic was modified 1 year, 11 months ago by Roeller.
• This topic was modified 1 year, 6 months ago by xxx.

[m00Participant 2022-12-21 at 15:25 Post count: 41]

#33741

I can’t really help with the baos device as I never used it, but regarding the slow download:
What do you define as slow? Some devices can take 30-90 seconds for a full download because KNX is a slow (but resilient) bus.

Are you using the baos 773 as an IP interface for programming the bus? The device supports long frames which means its the fastest way of programming.

I don’t think you need NAT for a local communication from ETS to the integrated IP Interface of the baos 773. (If that’s what you’re trying to do) you should be able to connect via IP tunneling if you enter the IP.
Are you sure you entered the correct IP?

Edit: you can use a tool like advanced IP scanner to verify the IP you are trying to connect to is really the weinzierl 773. I don’t know if this device has KNX Secure, that could also be an issue (KNX IP secure could interfere with you trying to connect)

• This reply was modified 2 years ago by m00.

[sinn3rParticipant 2022-12-22 at 08:37 Post count: 368]

#33748

ETS6 manages connections to the bus per project, with ETS5 this was a ETS-wide setting.
In the top right of your opened project there is a dropdown (showing “automatic” by default) which shows the way ETS will connect to the bus.
There are usually 2 ways to do so:
a) directly to the lan interface (ETS should list this with the found IP address of the KNX lan interface and the port 3671
b) by multicasting to the network via your local lan interface of the computer (which shows something like 224.0.23.12)
The second way is usually the easiest way to connect, but because of your vitualized windows machine the virtual network settings may interfere with that. Be sure to have the network of the virtualization to connect to your local lan network and not block multicast or broadcast.
I never used the BAOS 773 (which is an IP router, not just an IP interface) but it looks like an interesting device, offering access to all group addresses by web service. When using Home Assistant, ioBroker, gira Homeserver, … you won’t need that though.

And yes, welcome to the slow world of KNX ;)
Full application updates (or the first programming) may take a while, up to 90 seconds are not a rare thing. Later you can send updates to the devices which is faster. Firmwareupdates over the KNX bus can be even slower, for example my weather station takes 7 or 8 minutes for an update!

[xxxParticipant 2022-12-23 at 07:02 Post count: 68]

#33769

xxx

• This reply was modified 2 years ago by xxx.
• This reply was modified 2 years ago by xxx.
• This reply was modified 2 years ago by xxx.
• This reply was modified 1 year, 6 months ago by xxx.

[sinn3rParticipant 2022-12-23 at 11:07 Post count: 368]

#33786

Multi-Touch Pro: Hmm, I never saw it in action but the screen resolution looks not very good. At least it seems to be fast responding.
As for the price, I don’t think it’s expensive compared to other devices of this type, but I think vendors need to pay alot of money to KNX.

Hacking KNX: When portforwarding port 3671 from the internet to your KNX IP router, your whole installation can be “hacked”, in fact they do not hack the devices but set random device passwords and you cannot program the devices anymore. And yes, there is no “reset” button on the devices. So do NOT forward port 3671. If you need to program your system from external, use VPN.

I have no clue about the hager te331, but the manual shows how to wire it and an electrician should understand the manual ;)

You can setup what a KNX device should do on powerup. Some devices (like switching actuator with bistable relais) can hold their state when power recycles, not sure about your dimmer. My MDT dimmers can also remember the last value, when KNX power returns they set the last known value and also send the status to the bus, so the switches know. It may be some parameter you are missing. I would not send status object to the bus permanently, only on change, or you may pollute and slow down your bus when many devices are connected.

[m00Participant 2022-12-23 at 12:29 Post count: 41]

#33787

Yeah hager KNX devices are pretty shitty. You need to seither usw rigid copper wires or use a really small screw driver to open the clamp that holds the wires in place. I wouldn’t recommend Hager KNX devices to anyone. They are more expensive and have less functionality than I.e. MDT devices.

I have 10y of KNX experience and have never seen a case of KNX hacking. Potentially its possible either by forwarded ports or if you have devices outside your home (someone could remove a presence detector and reprogram devices potentially… Will never happen IRL)
Homeservers could also be hacked if you forward its ports to the internet.

If you only use VPN to connect to your otherwise closed network, I don’t see a way how someone hacks your system.
If someone IS inside yoye system and has a lot of spare time, they might set a BAU password, but AFAIK you could unload your devices even if a password is set.

Merten/SE Multi touch Pro are okay if you consider they also have a RoomTemperatureController (PI) integrated. Those are often times pretty expensive. The touch is a bit slow some times but you can load your custom symbols which is pretty cool IMO.

I wouldn’t recommend cyclically sending the status, because how often does the power supply go down? If you must, use a really high delay, half an hour or so. It might not be an issue at the start but KNX can support 50 telegrams per second max. If you have useless telegrams convoluting the traffic that can lead in larger installations to problems.

Regarding a LAMP (php?) or home assistant server.. I would highly recommend a more standardized solution, as in example the gira homeserver. (Either as a standalone version (futro 700/720/900/920) or as the virtualized version (hyper-v or VMware) as you can use many premade solutions by others or you can write own logic blocks in a simple py script. Its also much less volatile than some custom made solution which relies on communication between multiple protocols.

[xxxParticipant 2022-12-23 at 13:01 Post count: 68]

#33793

xxx

• This reply was modified 1 year, 6 months ago by xxx.

[sinn3rParticipant 2022-12-23 at 13:01 Post count: 368]

#33795

There were quite some KNX hacks in the last 2 years as searchengines like shodan easily show you forwarded KNX networks. And I think there are no ways to remove the passwords on many devices, they need to be sent in to the manufacturer to be reset or you need to hack the eprom/flash yourself anyhow.

Gira Homeserver is fine to visualize your installation and have your logics running, but to integrate with other smarthome standard it’s quite inferior to most other (even open source) solutions. I use ioBroker myself, I know of alot of guys running openHAB or FHEM for that. Not sure about Home-Assistant though, I tried it a few minutes and did find several devices missing that I am running here. So it’s not an alternative to ioBroker for me. But at least is has a very moden GUI, which is where ioBroker sucks! But nothing can trump Gira Homeserver (experte) ugly GUI wise ;)

[xxxParticipant 2022-12-23 at 13:19 Post count: 68]

#33796

xxx

• This reply was modified 1 year, 6 months ago by xxx.

[xxxParticipant 2022-12-24 at 15:48 Post count: 68]

#33820

xxx

• This reply was modified 1 year, 6 months ago by xxx.

[m00Participant 2022-12-24 at 16:07 Post count: 41]

#33822

I don’t know what you mean with supervisor but usually time is sent onto the bus through a server (Gira X1, Gira Homeserver, PeaKNX or some other visualization or logic server) or a weather station with GPS or a RTC Clock (theben I.e.).
You can send it temporarily manually onto the bus, the devices should keep the time somewhat consistent if they aren’t too old.

[xxxParticipant 2022-12-24 at 17:11 Post count: 68]

#33826

xxx

• This reply was modified 1 year, 6 months ago by xxx.

[ur63Participant 2022-12-25 at 08:52 Post count: 70]

#33839

Also many KNX IP-Interfaces do provide a timeserver functionality, eg. MDT SCN-IP…

[ur63Participant 2022-12-25 at 08:53 Post count: 70]

#33841

Yes, ETS provides functionality to send/set values.

[sinn3rParticipant 2022-12-25 at 08:56 Post count: 368]

#33843

Some IP routers/interfaces also can send date/time from an NTP server to the bus, but yours cannot do this, as it’s primarily not an IP router but an object server that doubles as an IP router. And afaik the software of this device doesn’t offer much beyond that.

In ETS open a diagnostics window and select the group monitor. There you can send values to your group addresses to simulate time.

Home Assistant may also be able to send date/time to the bus, but I think you need to create some logic to do so, as HA is not a real KNX supervisor (as you call it), but some multifunctinal software that can also connect to KNX.
Homeserver is a real KNX supervisor, as it’s made just for this. It can send date/time to the bus by default.

[Author]

Posts