Ok, I did on July 31, for my v3 hub. Will I need to wait for the next rollout or can I receive this one ?
I can’t get my SwitchBot hub 2 to connect at all.
Most attempts fail pretty much right away with Error 04-201
Only once did it make it to “registering to your Samsung account”, and then it failed again.
I’ve still not got any 49.x updates. My hub is still on 48.5
which version of iOS?
Whatever the latest iOS 17 public beta is.
I am in the beta program for hub firmware however I have just had to go through the CentreCode setup again.
I have 49.7 on my hub and am having issues installing a community-developed LAN driver which is getting errors trying to create and initialize devices.
The logs below are from the CLI during removal and reinstallation of the device. The second set appeared in the CLI almost 3 hours later.
2023-08-07T17:12:47.733026633+00:00 TRACE Virtual Devices V2 Received event with handler device_lifecycle
2023-08-07T17:12:47.733685549+00:00 INFO Virtual Devices V2 <Device: 79d1941f-4743-4e3b-a176-31ba7d6b3f8e (vEdge Creator V2.94)> received lifecycle event: removed
2023-08-07T17:12:47.734667633+00:00 TRACE Virtual Devices V2 Found DeviceLifecycleDispatcher handler in vedgeDriver
2023-08-07T17:12:47.735279966+00:00 WARN Virtual Devices V2 79d1941f-4743-4e3b-a176-31ba7d6b3f8e: vEdge_Masterv2> removed
2023-08-07T17:12:47.735884424+00:00 DEBUG Virtual Devices V2 vEdge Creator V2.94 device thread event handled
2023-08-07T17:12:47.736500549+00:00 TRACE Virtual Devices V2 Received event with handler driver_lifecycle
2023-08-07T17:12:47.744379508+00:00 DEBUG Virtual Devices V2 vEdge Creator V2.94 device thread event handled
2023-08-07T17:13:22.986980191+00:00 TRACE Virtual Devices V2 Setup driver vedgeDriver with lifecycle handlers:
DeviceLifecycleDispatcher: vedgeDriver
default_handlers:
doConfigure:
driverSwitched:
infoChanged:
added:
removed:
init:
child_dispatchers:
2023-08-07T17:13:23.019242275+00:00 TRACE Virtual Devices V2 Setup driver vedgeDriver with Capability handlers:
CapabilityCommandDispatcher: vedgeDriver
default_handlers:
lock:
lock
unlock
partyvoice23922.powersource:
setSource
alarm:
both
off
strobe
siren
colorTemperature:
setColorTemperature
doorControl:
open
close
fanOscillationMode:
setFanOscillationMode
partyvoice23922.inventory8:
setInventory
robotCleanerCleaningMode:
setRobotCleanerCleaningMode
partyvoice23922.shadepause:
push
thermostatCoolingSetpoint:
setCoolingSetpoint
windowShade:
close
open
partyvoice23922.resetselect:
setSelect
partyvoice23922.setco:
setCO
windowShadeLevel:
setShadeLevel
colorControl:
setHue
setSaturation
setColor
videoCamera:
on
off
thermostatMode:
cool
setThermostatMode
heat
emergencyHeat
auto
off
partyvoice23922.location:
setLoc
switch:
on
off
switchLevel:
setLevel
partyvoice23922.createqty:
setCreateQty
partyvoice23922.setilluminance:
setIllum
partyvoice23922.contactswitch3:
setSwitch
switchOn
switchOff
robotCleanerMovement:
setRobotCleanerMovement
partyvoice23922.setpower2:
setPower
audioMute:
setMute
mute
unmute
thermostatFanMode:
setThermostatFanMode
fanOn
fanAuto
fanCirculate
fanSpeed:
setFanSpeed
partyvoice23922.lockswitch4:
setSwitch
switchOn
switchOff
momentary:
push
videoStream:
startStream
stopStream
tvChannel:
channelUp
channelDown
setTvChannel
setTvChannelName
airConditionerFanMode:
setFanMode
airConditionerMode:
setAirConditionerMode
audioVolume:
volumeUp
setVolume
volumeDown
thermostatHeatingSetpoint:
setHeatingSetpoint
mediaPlayback:
play
pause
stop
fastForward
setPlaybackStatus
rewind
tV:
channelUp
channelDown
volumeUp
volumeDown
partyvoice23922.vhumidityset:
setvHumidity
partyvoice23922.vtempset:
setvTemp
partyvoice23922.setenergy:
setEnergy
partyvoice23922.createdev8:
setDeviceType
partyvoice23922.vbatterylevel:
setLevel
child_dispatchers:
2023-08-07T17:13:23.020116066+00:00 INFO Virtual Devices V2 Driver V2.94 Started: Edge Virtual Devices
2023-08-07T17:13:23.023103233+00:00 TRACE Virtual Devices V2 Received event with handler discovery
2023-08-07T17:13:23.023813441+00:00 TRACE Virtual Devices V2 Received event with handler environment_info
2023-08-07T17:13:23.024466816+00:00 DEBUG Virtual Devices V2 Z-Wave hub node ID environment changed.
2023-08-07T17:13:23.025390608+00:00 INFO Virtual Devices V2 Creating vEdge Creator device
2023-08-07T17:13:23.031953108+00:00 DEBUG Virtual Devices V2 Exiting device creation
2023-08-07T17:13:23.032403233+00:00 DEBUG Virtual Devices V2 discovery device thread event handled
2023-08-07T17:13:23.033052983+00:00 TRACE Virtual Devices V2 Received event with handler environment_info
2023-08-07T17:13:24.378327067+00:00 TRACE Virtual Devices V2 Received event with handler device_lifecycle
2023-08-07T17:13:24.385793400+00:00 INFO Virtual Devices V2 <Device: a6b03e4c-944b-47d9-a7da-ca2df36ba08d (vEdge Creator V2.94)> received lifecycle event: added
2023-08-07T17:13:24.396157400+00:00 TRACE Virtual Devices V2 Received event with handler device_lifecycle
2023-08-07T17:13:24.396750025+00:00 INFO Virtual Devices V2 <Device: a6b03e4c-944b-47d9-a7da-ca2df36ba08d (vEdge Creator V2.94)> received lifecycle event: doConfigure
2023-08-07T17:13:24.403424900+00:00 TRACE Virtual Devices V2 Found DeviceLifecycleDispatcher handler in vedgeDriver
2023-08-07T17:13:24.410061900+00:00 INFO Virtual Devices V2 a6b03e4c-944b-47d9-a7da-ca2df36ba08d: vEdge_Masterv2> ADDED
2023-08-07T17:13:24.410514025+00:00 DEBUG Virtual Devices V2 vEdge Creator V2.94 device thread event handled
2023-08-07T17:13:24.416709859+00:00 TRACE Virtual Devices V2 Found DeviceLifecycleDispatcher handler in vedgeDriver
2023-08-07T17:13:24.417361317+00:00 DEBUG Virtual Devices V2 vEdge Creator V2.94 device thread event handled
2023-08-07T17:13:24.417977067+00:00 DEBUG Virtual Devices V2 <Device: a6b03e4c-944b-47d9-a7da-ca2df36ba08d (vEdge Creator V2.94)> doConfigure callback did not fail, transitioning device to "PROVISIONED"
2023-08-07T17:13:24.428818275+00:00 DEBUG Virtual Devices V2 vEdge Creator V2.94 device thread event handled
2023-08-07T17:13:24.642478984+00:00 TRACE Virtual Devices V2 Received event with handler device_lifecycle
2023-08-07T17:13:24.643044525+00:00 INFO Virtual Devices V2 <Device: a6b03e4c-944b-47d9-a7da-ca2df36ba08d (vEdge Creator V2.94)> received lifecycle event: infoChanged
2023-08-07T17:13:24.647582067+00:00 TRACE Virtual Devices V2 Found DeviceLifecycleDispatcher handler in vedgeDriver
2023-08-07T17:13:24.648011650+00:00 DEBUG Virtual Devices V2 Info changed handler invoked
2023-08-07T17:13:24.648632525+00:00 DEBUG Virtual Devices V2 vEdge Creator V2.94 device thread event handled
2023-08-07T17:13:56.622466124+00:00 TRACE Virtual Devices V2 Received event with handler discovery
3 Hours Later…
2023-08-07T19:55:58.818018132+00:00 TRACE Virtual Devices V2 Received event with handler discovery
2023-08-07T19:55:58.851488382+00:00 INFO Virtual Devices V2 Creating vEdge Creator device
2023-08-07T19:55:59.170653507+00:00 ERROR Virtual Devices V2 discovery thread encountered error: [string "init.lua"]:1758: failed to create master device
2023-08-07T19:56:07.514172217+00:00 TRACE Virtual Devices V2 Received event with handler discovery
During the above delay the following shows when I try to open the device.
I have vEdge Creator and it is working for me. Have you tried rebooting your hub?
I didn’t have it, I’m trying to install it for the first time, my hub has been down and up like a yo yo. Seems to be an issue creating the vEdge Creator device for the first time. If it’s working don’t mess with it.
I am going to keep asking… have you rebooted your hub since installed it?
Yes I have.
OK i didn’t do that on this last attempt. I’ve just restarted and it’s burst into life. Just checking the CLI logs for diferences…
Logs are exactly the same except for the 4 additional lines that appeared about 3 hours later the first few times. I assume the reboot is somehow freeing up the install of the Master Device component that gets hung up for some reason.
Hello, with 49.07 I notice synchronization problems with the Vimar devices. If I turn on and off from the app everything is ok, if I act as a physical button, the ON synchronizes very rarely, the OFF never. @pilone have the same problem with the same firmware.
Vimar is an Italian manufacturer and I haven’t seen anyone outside of Italy use them unfortunately. Therefore, problems with these devices are always difficult to solve
Hi, @Diegocampy
Thank you for reaching out, @alissa.dornbos reported your issue, we’ll let you know once we get more info.
There’s some approval process for beta program?
I report another problem: I can no longer use the virtual device creator [ST Edge] vEdge Creator: a virtual device generator for end users - #1954 by Diegocampy
It seems that the initialization of the drive has some problem.
My understanding is that when they are about to start a new round of beta tests they process any outstanding applications and then build a list of hubs that will be in the tests. If there is any problem with the information you have provided they will let you know but they won’t check it again until the next round of tests.
To put it another way, if you applied for the beta programme in response to the 49.x announcement, I would expect you to be accepted around the time of the 50.x announcement and if all is well you will receive that firmware. However if there is a problem with the hub info e.g. mismatched username and hub, you might not get firmware until 51.x even if you fix it immediately. That is how it worked for me in the past.
Hello All.
We will be releasing 49.8 today.
Updates to this build include:
- Resolved delays in device creation and updates, after a hub comes back online.
All users who were part of 49 customer beta will be included in this additional update.
Thank you for your continued support.
The random disconnections of my Vimar devices (and unfortunately not only) have started again. External access to my hub is on if you want to watch something. 